• Proceedings of the Korean Society of Computer Information Conference
• /
• 2010.07a
• /
• pp.95-98
• /
• 2010

본 논문에서는 소프트웨어 개발 프로세스 분석 도구인 4-DAT를 이용하여 범용적으로 사용되고 있는 애자일 프로세스인 XP와 스크럼을 비교분석하였고, 게임 개발 프로세스를 평가하기 위한 평가 알고리즘을 제안한다. 새로운 개발 방법 평가 알고리즘은 기존의 4-DAT가 포함하고 있는 4차원의 고려사항을 3차원으로 재정의하여 통합한 것으로, 게임 개발 환경에서 기존의 XP와 스크럼이 가지는 제약성을 보완할 수 있고, 게임 개발을 위한 프로세스의 도입에 있어 부족한 요소를 추출할 수 있다. 실험의 방법으로서 실제 개발한 모바일 게임의 주기와 실행방법을 분석하여 5항목의 상황변수를 정의하였고, 4-DAT가 가지는 기준에 적용하여 기초 자료를 도출하여, 재구성한 3-DAT를 기반으로 정의된 상황변수를 적용하여 분석하였다. 그 결과 6가지의 상황에 따른 데이터를 구하였으며, 이를 종합하여 게임 개발에 적합한 프로세스의 요구사항을 알 수 있었다.

• Journal of Internet Computing and Services
• /
• v.10 no.4
• /
• pp.127-138
• /
• 2009

Mobile web applications are being used and changed rapidly due to the growth of mobile device performance. But, cost of development environment and standards make the high development cost and low productivity. It is main reason that the design and implementation of the applications are more time consuming than general computing environments. In this paper, we propose MWeb(MobileWeb)-Framework based on the agile methodology and Ruby on Rails that is a kind of framework for supporting mobile web application development using mobile web standards. This work consists of the mobile web development architecture and agile process model. MWeb-Framework will support the same user experience to the different devices. We validates the framework by implementing the case studies through suggested mobile web development framework. As a result, we can develop the mobile web applications with productivity and quality. In the future, we will suggest how to make the MWeb-Framework standardization and practically apply the frameworks the various case studies to improve framework potentially problems.

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

• Information Systems Review
• /
• v.13 no.1
• /
• pp.61-74
• /
• 2011

Software industry still has many deep-seated problems. As a natural consequence, it may have to learn from best practices in more mature industry like manufacturing. An example is 'lean' software development which is defined as translation of 'lean manufacturing' principles to the software development domain. The principles include 'eliminate waste' and 'amplify learning.' It was much asserted that these principles are worth applying. Not much study, however, was done on how to practically implement these principles into software development practice. In this study we attempt to present a method in which project lead time and software defects are regarded as major targets of management and are visualized using Cumulative Flow Diagram. We further applied this method on actual projects. The result confirms that agile is positively effective on reducing wastes.

• 한국IT서비스학회:학술대회논문집
• /
• 2010.05a
• /
• pp.529-535
• /
• 2010

오늘날의 엔터프라이즈 IT 환경은 비즈니스 요구사항이 빠르게 변하면서 기존 시스템들의 민첩한 대응이 어렵고, 비즈니스 프로세스가 점점 복잡해지면서 시스템 개발 및 제어가 힘든 상황이다. 이 때문에 관리비용은 점점 증가하고 시스템의 수명주기가 단축되면서 전체적인 개발생산성이 낮아지고 있다. 최근 이와 같은 소프트웨어 개발문제를 극복하기 위해서 XP(eXtreme Programming)와 SCRUM 같은 애자일(agile) 방법론이 등장하게 되었고, 점차 대규모의 엔터프라이즈 어플리케이션 개발에 적용할 필요성이 대두되고 있다. 따라서 본 논문에서는 엔터프라이즈 어플리케이션의 개발생산성을 향상시키고 수명주기를 연장시키는데 효과적인 ISIS(Integrated System of Independent Sub-systems) 개발방법을 제안하고자 한다.

• Journal of Digital Convergence
• /
• v.11 no.2
• /
• pp.205-214
• /
• 2013

Team collaboration is becoming commonplace and it is spotlighted in agile software development projects as well. More efficient teamwork in terms of effective team operation and project performance is very important. Heuristic software development staffing method has been used, but algorithm approach is needed to compensate for it. In this paper, we propose a mathematical approaches for staffing developers in teamwork-based software development projects. This consist of six process, and activities in each processor is defined as a mathematical function placement, and functional deployment matrix is used. A case study is presented in order to prove the usefulness of this approach. This paper is a significant research because a mathematical approach of work assignment is developed for human resources by quantitative logic and it deviate from intuitive or heuristic methods used previously.

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

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

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.4
• /
• pp.215-223
• /
• 2011

It is difficult to apply a Software Process Certification to small scale project, because of much activities and documents for manage project and guarantee the qualities in small manpower. This paper presents optimized Software Process Certification Model for small scale software development, a combine Scrum with essential elements of NIPA's(National IT industry Promotion Agency) SP-Certification model. The proposed model defined minimum Activities and Documents for SP Certification. The model that I showed consists of 16 Processes and 58 Activities, and 39 Artifacts are created. As a result of having compared proposed model with a Standard Process of Small Business, I confirmed that a small scale project's burden reduced because Activity decreased 38% and Document decreased 20%. In order to verify the validity of the proposed model, applied it in two small scale projects, and compare with the project by Scrum process only, it finished that systematic management was possible without additional manpower, and reached SP-Certification level 2.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2015.10a
• /
• pp.1075-1078
• /
• 2015

Three kinds of typical practices to reflect the values of Agile Development Methodology were selected from a previous study. Those were Communicate using Web 2.0 collaboration tools, test-driven development (TDD, Test-Driven Development) method is adopted, and refactoring. In this study, we set up a hypothesis that the adoption of TDD project will make user satisfaction is higher. Select 100 sample projects from SourceForge(sourceforge.net), the most popular open source hosting site, the criteria is we can be determined whether operate in the project (developer least 7 people, bugs can occur more than 100, created the project since 2000). To determine whether the use of automated development tools xUnit of TDD through the CVS and SVN log analysis. Using data from the FLOSSmole and to evaluate the user experience of the project. User satisfaction of each project Rating, bug fix cycle, downloads and pageviews. Through this study, correlates of whether TDD adoption and user satisfaction, we will suggest a reflected the Agile practices new open source development methodology. As a result, it contributes to increase the maturity of the open source community.