• Journal of Digital Convergence
• /
• v.11 no.8
• /
• pp.95-108
• /
• 2013

Agile development methods regards an interaction among software developers, operating softwares, and cooperation with customers as its main value. Most of the developing processes undergo a procedure called tailoring to meet the relevant project. Yet, in reality, projects run in disorder due to their overlap with other methods and management processes. As a result, the advantages of agile process cannot be fully used. So, the information system audit has an important role to detect these problems and improve the qualities of agile application projects. Also, researches should be conducted on Agile-based Iformation System Audit Model in order to enhance the effectiveness of agile projects. This paper suggests a model for an information system audit that applied agile developing methods. This model proposes audit domains and check lists for agile-based information system. In order to verify the suitability of the suggested model, more than 89.3% of the checklists were verified as suitable in all domains.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.15 no.6
• /
• pp.147-154
• /
• 2015

Recently agile development process became increasing effectiveness, quality, attention to experts in customer satisfaction, as evidenced in this methodology when selecting projects promoting productive efficiency. With regard to contemporary needs and user requirements on the methodology selected to meet this paper is the product based Cross functional team suggested methodology Feature Team model to solve problems of this model, and organizing the Cross functional team, this team but this outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-driven agile project through the Skills-based model and proposed a difference. And it examined the Agile Maturity metrics. PRINCE2 Agile Health-check entries future development direction of Agile techniques is a requirement of the project outset has studied the subject objective evaluation by the assumption that they can be changed at any time, not fixed this way and for the project team through research The proposed.

• International Journal of Advanced Culture Technology
• /
• v.9 no.1
• /
• pp.210-217
• /
• 2021

In the case of an agile-based project, it was inadequate to perform a comprehensive inspection and evaluation on the establishment and operation of an information system by performing audit only with the audit and inspection elements provided by the existing information system audit and inspection system. In particular, in the case of the test activity area, it was necessary to improve the test activity audit check items to comprehensively check the agile-based development process by applying the existing audit system. To this end, a test activity improvement check model of the agile methodology audit model was presented by applying the repetition concept, a characteristic of the agile methodology. In order to empirically verify the model of this study, a survey was conducted for auditors and designers/developers who have experience in performing agile-based projects and auditing information systems. As a result of the questionnaire on the integrated test and system test in the test stage, more than 70% of the respondents were found to be suitable. More than 80% of the respondents judged that it was appropriate as a result of the questionnaire on "improvement and regression test progress according to integrated test and system test results" and "integrated test and functional actions of components and subsystems".

• Journal of Internet Computing and Services
• /
• v.17 no.5
• /
• pp.173-184
• /
• 2016

Prevalence of Agile methods in software companies is increasing dramatically. Software companies need to employ these methods to overcome the inherent challenges of traditional methods. However, transitioning to Agile approach is a topic of debate and there is no unique and well-defined transition model or framework yet. Although some research studies have addressed barriers and strengths behind the successful Agile deployment, it seems that this process still needs to be studied more in depth. The rationale behind this is the socio-technical nature of Agile transition and adoption. Particularly, the challenges and problems that software companies are facing during Agile transition, show that this process in more difficult than expected. Conducting a large-scale research study revealed that Agile transition and adoption process needs to be supported by several critical prerequisites. This study adopted a Ground Theory with the participation of 49 Agile experts from 13 different countries and empirically identified seven transition prerequisites. These prerequisites focus on the different aspects of the transition. The main aim of this paper is proposing these prerequisites and theoretical and practical implication of these prerequisites. Providing these prerequisites before moving to Agile increases chance of success in Agile transition and adoption and leads to fewer challenges during the change process.

• Journal of Internet Computing and Services
• /
• v.15 no.1
• /
• pp.13-27
• /
• 2014

Agile methodologies have gained recognition as efficient development processes through their quick delivery of software, even under time constraints. However, like other agile methods such as Scrum, Extreme Programming (XP) and The Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD) has been criticized due to the unavailability of security elements in its twelve practices. In order to examine this matter more closely, we conducted a systematic literature review (SLR) and studied literature for the years 2001-2012. Our findings highlight that, in its current form, the FDD model partially supports the development of secure software. However, there is little research on this topic, as detailed information about the usage of secure software is rarely published. Thus, we have been able to conclude that the existing five phases of FDD have not been enough to develop secure software until recently. For this reason, security-based phase and practices in FDD need to be proposed.

• Journal of Korea Multimedia Society
• /
• v.20 no.4
• /
• pp.660-670
• /
• 2017

In case of auditing of the information system development project applying agile methodology, it is not appropriate to carry out a comprehensive check on the establishment of information system with only the existing check on software. This study considers the characteristics of the agile methodology in terms of Information System Auditing. To improve inspection quality of development project with agile methodology by deriving detailed check items of test activities at each stage, this study proposes a strategy to improve the check on software for the test activities of the supervisory model that is suitable for agile methodology, which emphasizes repetitive work.

• Journal of Information Technology Services
• /
• v.20 no.1
• /
• pp.41-54
• /
• 2021

The SW-centered battlefield management information system R&D project takes a long period of 5-10 years or more by applying a complex and rigid batch acquisition strategy. In order to solve this problem, it is necessary to institutionalize a rapid and flexible battlefield management information system R&D project management procedure applying agile development methodology, and a government project management organization and contract management method to support it In this study, we analyzed the case of applying the Agile development method centered on Scrum to the US SW-centered weapon system R&D project and the characteristics and problems of the battlefield management information system R&D project in Korea, and suggested improvement measures as follows. First, the battlefield management information system R&D model applies the hybrid development method, and the system requirements analysis and system structure design use the existing waterfall development procedure, and the agile method is applied from the SW requirements analysis to the system integration stage. Second, flexible adjustment of performance, schedule, and cost by organizing an Agile IPT in which military (requirements) - DAPA (project management) - developer - functional specialized organizations (test and evaluation, quality, government research institutes, etc.) participate. Third, improving the Basic Order Agreement so that it can be applied to agile R&D.

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.5
• /
• pp.303-310
• /
• 2013

Agile software development methodology is a lightweight software development method, plays an important role in the software development team. In this paper, we propose programs that in when agile development co-operation, team management, team collaboration and project management tasks can be high efficiency and allocation of human resources. The proposed model, the use of 6-Sigma priority assignment, established a mathematical model of the operation and distribution of human resources is the most reasonable people go to work. Cooperation makes team-based agile development can improve efficiency. This method improve staff efficiency by teamwork to improve the productivity of software development.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.8 no.2
• /
• pp.646-663
• /
• 2014

Scrum is one of the most popular and efficient agile development methods. However, like other agile methods such as Extreme Programming (XP), Feature Driven Development (FDD), and the Dynamic Systems Development Method (DSDM), Scrum has been criticized because of lack of support to develop secure software. Thus, in 2011, we published research proposing the idea of a security backlog (SB). This paper represents the continuation of our previous research, with a focus on the evaluation in industry-based case study. Our findings highlight an improved agility in Scrum after the integration of SB. Furthermore, secure software can be developed quickly, even in situations involving requirement changes of software. Based on our experimental findings, we noticed that, when integrating SB, it is quite feasible to develop secure software using an agile Scrum model.

• International Journal of Aeronautical and Space Sciences
• /
• v.18 no.4
• /
• pp.709-718
• /
• 2017

This paper proposes the guidance laws for an agile turn of air-to-air missiles during the initial boost phase. Optimal solution for the agile turn is obtained based on the optimal control theory with a simplified missile dynamic model. Angle-of-attack command generating methods for completion of agile turn are then proposed from the optimal solution. Collision triangle condition for non-maneuvering target is reviewed and implemented for update of terminal condition for the agile turn. The performance of the proposed method is compared with an existing homing guidance law and the minimum-time optimal solution through simulations under various initial engagement scenarios. Simulation results verify that transition to homing phase after boost phase with the proposed method is more effective than direct usage of the homing guidance law.