• 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.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.16 no.4
• /
• pp.2744-2748
• /
• 2015

This paper analyzes the effect on productivity by measuring Function Point per MM(man-month) in a software development project and code inspection which performed in Agile methodology, and introduce the method of applying MDA/MDD technology in the e-government standard framework project. MDA/MDD which recently raising its head is technology that increase software development productivity through automatic transformation form abstract model into lower abstract model, or from model to code. but, many Lessons obtained through the case studies, the analysis suggests a limited effect measurements. In this study, efficient development methodology and utilizing a e-government framework to measure the effectiveness of the MDD to the new measures through a case study applied to real information system development process. In addition to, managing information modeling through integrated repository presents a traceability and visibility.

• Information Systems Review
• /
• v.10 no.3
• /
• pp.185-205
• /
• 2008

As time to market and rapid reaction to changes in demand is much required, agile software development methodologies whose characteristics are great adaptability and short iteration developments are getting more popular. Though there have been a number of literature suggesting the great potential of agile software development, some recent studies have also mentioned its limitations. We believe there remains much confusion as to whether agile approaches are good to introduce or not. In an effort to provide 'real' characteristics of agile development, this paper evaluates Scrum, one of the most used agile approaches, using a software measurement framework. It also presents a Scrum measurement case study of a web portal company. We believe this study will provide some concrete guidelines as to whether Scrum is worth, what are weak points, and how to control the agile process in order to get over the weakness.

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.635-648
• /
• 2004

Extreme programming is the most representative methodology among agile software development methodologies that is agile in business environment which change fast. As software industry is matured, usability of software quality characteristics is emphasized gradually, but effort to obtain usability in extreme programming is insufficient. In this paper, three things lacked in extreme programming are reinforced. First, roles of user interface expert are defined. Second, usability testing method to extreme programming are introduced. Third, development process and products are proposed. The proposed plan is validated by four methods, which analyze supporting software development life cycle, analyze satisfaction of CMM key process areas, analyze satisfaction of CMM practices, and analyze development of green tea shopping mail. Green tea shopping mall is improved 23％ in the estimated running time, 21％ in the learnability. Also, usability is improved 18％ in the heuristic evaluation and 16％ in the questionnaire method.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.16 no.1
• /
• pp.155-162
• /
• 2016

In recent years, hoping the interaction of individuals and rather than software development process and tools, and customers want software that works first, rather than a comprehensive document, in cooperation with the customer, rather than the developer negotiate a contract, to each other stick to the plan I think even more so than the value that corresponds to the change. In view of this, software development is given the autonomy and motivation to project team rather than process-oriented and have a passion and vision and human relations oriented management approach is required. In recent years, increasing the productivity benefits of agile development processes, improved quality, efficiency and customer satisfaction as is demonstrated in the methodology selected to promote the project, attention was given to the experts. Contemporary demands with regard to the methodology chosen to meet your needs, in this paper in the organization, and to solve the problems of product-based Cross functional team proposed methodology Feature Team model, this model is an organizational Cross functional team and the team is not the outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-plan through the driven agile technique-based model and proposed a difference. And the domain analysis, required extraction by conventional JAD (joint application development) meeting the targets for the object-oriented modeling, in modeling and organize, review, aware in advance and the UML Structure and Behavior Diagrams and proposed to proceed with the project.

• International journal of advanced smart convergence
• /
• v.8 no.3
• /
• pp.161-166
• /
• 2019

Viewed in the rate of change in the web environment, it is very difficult to remain the initial planning at the time until the time of launch, and there is a need for a method to accommodate changes and satisfy market demands during the development process. Unlike the traditional waterfall approach of maintaining initial planning, scrum is one of the agile methodologies that enables flexibility to respond to changes in the market and customers' needs and drive customer satisfaction and business success. However, to apply the scrum to a project in actual, the practice method itself is relatively simple but not easy to apply. The reason is that the members of the organization need to understand and participate in scrum's philosophy and principles and the continuous observation and change management should be carried out. Therefore, in this paper, we presented the feature dashboard and customized scrum methodology to enable continuous observation and change management using visibility, and we shared the case that periodically reflected inspection and adaptation with the explanation of the main points. Also, based on the experience with participants, the strengths and weakness of the feature dashboard and the customized scrum methodology are summarized.

• Journal of Intelligence and Information Systems
• /
• v.25 no.3
• /
• pp.141-160
• /
• 2019

Agile methodologies in software development, including the development of artificial intelligence software, have been widespread over the past several years. In spite of the popularity of agile methodologies in practice, there is a lack of empirical evidence to identify determinants of success of software projects in which agile methods are used. To understand the role of clients in software project where agile methods are used, we examine the effect of client-side factors, including lack of user involvement, unrealistic client expectations, and constant changes of requirements on project success from practitioners' perspective. Survey methods are used in this study. Data were collected by means of online survey to IT professionals who have experience with software development methodologies, and ordered logit regression is used to analyze the survey data. Results of our study imply the following managerial findings. First, user involvement is critical to project success to take advantage of agile methods. Second, it is interesting that, with an agile method, constant changes of client's requirements is not a negative factor but a positive factor of project success. Third, unrealistic client expectations do negatively affect project success even with agile methods.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.7 no.6
• /
• pp.1351-1359
• /
• 2003

Extreme programming is the most representative methodology among agile software development methodologies which is agile in business environment which change fast. As software industry is matured, usability of software quality characteristics is emphasized gradually, but effort to obtain usability in extreme programming is insufficient. To improve usability of extreme programming, in this thesis, a software life cycle is defined by six phase as exploration, planning, iterations to release, productionizing, maintenance, and death phase. In this thesis, an extreme programming process which can improve usability is proposed by definition of 11 activities including integration testing and acceptance testing for usability testing, The proposed process is validated with four aspects. The proposed process is enhanced to support acceptance testing activity. The proposed extreme programming process is able to support CMM level 4 and quality assurance practice of CMM.

• The KIPS Transactions:PartD
• /
• v.16D no.1
• /
• pp.55-64
• /
• 2009

Various business model and computing environments are currently merged into web services and many web related application products are also develop. Most of IT enterprises in Korea use the Service-oriented architecture (SOA) whenever they develop the web applications. SOA is an approach to loosely coupled, protocol independent, standards-based distributed computing where software resources available on the network are considered as Services. SOA is believed to become the future enterprise technology solution that promises the agility and flexibility the business users have been looking for by leveraging the integration process through composition of the services spanning multiple enterprises. But, There are no specific development methodology to apply into SOA standard model until now. The developer uses the currently existing methodology to develop the application with SOA. The users have some limitations to use it. In this paper, we suggest a Frameworks for applying agile methodology into SOA to address the productivity and quality of small web related project. We design and implement a frameworks architecture for applying the agile method into SOA and describe the process model to implement it. We finally evaluate the frameworks with productivity, flexibility and maintainability.

• Journal of Software Assessment and Valuation
• /
• v.16 no.2
• /
• pp.163-172
• /
• 2020

Recently, concepts of the Fourth Industrial Revolution technologies such as artificial intelligence, big data, and cloud computing have been introduced and the limits of individual or team development policies are being reviewed. Also, a lot of latest technology source codes have been opened to the public, and related studies are being conducted based on them. Meanwhile, the company is applying the strengths of the open source software development methodology to proprietary software development, and publicly announcing support for open source development methodology. In this paper, we introduced several software development methodology such as open source model, inner source model, and the similar DevOps model, which have been actively discussed recently, and compared their characteristics and components. Rather than claiming the excellence of a specific model, we argue that if the software development policy of an individual or affiliated organization is established according to each benefit, they will be able to achieve software quality improvement while satisfying customer requirements.