• Journal of the Korea Society of Computer and Information
• /
• v.13 no.7
• /
• pp.269-280
• /
• 2008

The choice of appropriate methodologies has always been a challenge. It is time to find obstacles when Extreme programming(XP) is adopted. In this paper, we invest status of adoption of XP methodology which is more popularized. We survey how the Values and the Practices of XP can be adopted to developer in terms of the usefulness and the easy of use of XP. As a result, it is regarded as a successful one in improving quality and timeliness through software development process. The Values and Practices, a basis of XP philosophy and its adoption, could be easily accomplished, but other elements - communication, feedback. collective ownership, pair programming, simple design and customer participation - which do not depend on technology could not be accomplished easily. To introduce XP easily in the creative and labor intensive software development fields, the managers and the educators have to make efforts to apply these Values and Practices based on humane characteristics as well as technical elements.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.04a
• /
• pp.577-579
• /
• 2001

eXtreme Programming(이하 XP)은 프로젝트를 수행하는 데에 있어서 흔하게 발생하는 위험 요인들을 Light-weight 한 방법으로 해결하기 위한 방법론이다. XP 개발 방법론은 개발 주기의 단위를 작게 나누어서 피드백을 받는 기간을 짧게 잡았다는 점과, Pair Programming 방법을 도입했다는 점, 개발 과정에서의 고객의 비중을 높이고, 다양한 모듈 테스트/기능 테스트를 통해서 제품의 오류를 최소화 했다는 점 등의 특징을 갖고 있다. 그러나 XP는 소규모의 개발팀일 경우에만 그 효용성이 입증되고 있으며, 수많은 테스트 과정과 개발의 전과정에서의 고객의 적극적인 참여의 요구는 생산 비용면에서나 고객의 부담에 있어서 단점으로 여겨지고 있다. 따라서 본 고에서는 이러한 점들을 보완하기 위한 몇 가지 방안과 더불어 우리나라의 개발 환경에 효과적으로 적용하기 위한 방안을 제시하고자 한다.

• International Journal of Computer Science & Network Security
• /
• v.21 no.6
• /
• pp.143-150
• /
• 2021

Process model is an integral part of software industry. Different process models are used now a days in the industry for different software projects. Process models need to be tailored to address some specific project needs. Agile models are considered as the most widely used process models nowadays. They have distinctive features and the ability to address the dynamic needs of today's software development. Extreme programming (XP) is one of the extensively used agile process model especially for small projects. Many researchers have tried to mold XP to overcome its shortcomings and for better working in specific scenarios. Therefore, many customized versions of XP process model are available today. In this paper, we are going to analyze the latest customizations of XP. For this purpose, a systematic literature review is conducted on studies published from 2012 till 2018 in renowned online search libraries. This comprehensive review highlights the purpose of customizations, along with the areas in which customizations are made, and phases & practices which are being customized. This work will serve the researchers to discover the modern versions of XP process model as well as will provide a baseline for future directions for customizations.

• Journal of Internet Computing and Services
• /
• v.9 no.2
• /
• pp.107-118
• /
• 2008

The XP, the representative methodology of Agile software development, maximizes the effectiveness of the development by focusing on development itself and using primitive and basic process definition that can be easily implemented in the fields. However, the most of XP's practices came from those of engineering and the manogement practices of work product tend to be overlooked. The research on the implementation of those manogement practices has not been performed enough. Because of deficiency of processes that guide the change control over major baselines of work product and that describe proper continuous integration and refactoring in XP, the integrity of those work products is difficult to be guaranteed. To fulfill this work product integrity, CM(configuration manogement) should be hired and CMMI(Capability Maturity Model Integration) is considered to be the best references for that purpose, CMMI defines the required practices of CM and leave implementation details to the organization so that it could customize those practices based on the characteristics of its development methods. The CM process implementation guidelines based on CMMI could provides work product integrity with a way of keeping XP's agility that includes continuous integration, refactoring and small release. In this research, we selected CM process factors applicable to XP among CMMI's CM practices and based on them we developed the CM implementation guidelines.

• The KIPS Transactions:PartD
• /
• v.11D no.6
• /
• pp.1301-1310
• /
• 2004

In distributed office, the pairs can program together using a distributed pair programming system. Many CSCW tools featuring remote screen sharing function have insufficient usability, accessibility to introduce many developers to distributed pair programming. In this paper, we suggest a distributed pair programming system based on IDE, which many developers will accept and use easily. We have do#eloped a user scenario and GUI of the system, making distributed pair programming easier and designed with high extensibility by adapting design patterns and implemented in Java language. Our findings will be of significant help to developers dealing with implementation of distributed pair programming function into some commercial IDE.

• Journal of the Korea Society of Computer and Information
• /
• v.10 no.1 s.33
• /
• pp.15-26
• /
• 2005

As one of the lightweight software development methodology, the XP (Extreme Programming) is the practical means to improve the productivity and qualify of software through the pursuit of 4 values - communication, simplicity, feedback, and courage. It appears, however, the TDD (Test Driven Development). one of the practices of in. has a problem. which is the unavailability of the test driven development in case of the prolonged period of testing or the failure of securing the independency of the test cases. This results in the emphasis on the importance of the Mock Objects recently. The Mock Objects, the one imitating the faulty real code, has the fundamentals of simplicity allowing even manual script but. due to the inefficiency of manual script of the Mock Objects in a real life, it is implemented the Mock Objects Generator such as Mockotjects, EasyMock in Java. It Is found difficult, however to apply the Mock Objects in C language due to its object -oriented Premise as well as the absence of mock objects generators for C language. Therefore, in this Paper it is presented the CMock, a Mock Objects generator fer C language which allows the easy creation of the Mock Objects, and the study is performed to verify the efficiency accordingly.

• International Journal of Computer Science & Network Security
• /
• v.24 no.5
• /
• pp.103-110
• /
• 2024

In the quickly developing world, the idea of the conventional advancement needs to advance[1]. When applied to the advanced work environment, the conventional strategies give as much damage as they do great. Tragically, an absence of versatility in the customary techniques has prompted an inflexible work structure that is truly not viable with the present business. The Agile technique is, subsequently, a more adequate practice, in view of creating programming at a faster speed, while as yet looking after proficiency. The coordinated programming improvement strategies are concentrated in this paper. As per study results, Agile software development group needs solid client association; great light-footed task the executives' measures; item proprietor expands business esteem conveyed by group and need and draw in partners; great deft designing procedures or practices; and great advancements and advancement apparatuses[2]. This examination has suggestions for positive social change since associations that comprehend the basic components might have the option to improve project the executives' systems and money saving advantages prompting higher effectiveness, productivity, and efficiency hence profiting the board, representatives, and client. This survey paper incorporates various methodologies of Agile and their analysis.

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

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