• Proceedings of the Korea Database Society Conference
• /
• 2010.06a
• /
• pp.13-19
• /
• 2010

Information competitiveness accounts for substantial parts of business competitiveness necessary for business management in the knowledge-information society in the 21st century. To improve quality. productivity and competitiveness through information in the fields of SMEs particularly having difficulties under rapidly changing business environment. the government has operated "SME Information Support Project" for the past 8 years. The methodology for developing the standard for this project known as EISDM (Enterprise Information System Development Methodology) provides communication between IT businesses and SMEs participating in this project. and standardized output document formats and how to make out such documents. Infortunately. the number of personnel partaking in the development project for SMEs is no more than 2~4 per site on average. Further. they are required to complete demand analyses. development. testing and operation in about 6 months. which is a very short period. Moreover, there is too much demand for documentation, which is likely to end up being formal work process just for supervision and inspection. That is, the documentation could be for noting but documents. which will prove useless outputs after the project finishes. Therefore, this study proposes an improvement approach as an information system development methodology taking into account SMEs' characteristics and environment so as to relieve developers from such excessive burden of documentation, to save time and resources through efficient management of software development as the original purpose of the methodology, and to produce required quality software.

• Journal of Information Processing Systems
• /
• v.8 no.4
• /
• pp.539-554
• /
• 2012

Model-driven and component-oriented development is increasingly being used in the development of embedded systems. When combined, both paradigms provide several advantages, such as higher reuse rates, and improved system quality. Performing model-driven and component-oriented development should be accompanied by a component model and a method that prescribes how the component model is used. This article provides an overview on the MARMOT method, which consists of an abstract component model and a methodology for the development of embedded systems. The paper describes a feasibility study that demonstrates MARMOT's capability to alleviate system design, verification, implementation, and reuse. Results indicate that model-driven and component-based development following the MARMOT method outperforms Agile development for embedded systems, leads to maintainable systems, and higher than normal reuse rates.

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

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

• The Journal of Korea Institute of Information, Electronics, and Communication Technology
• /
• v.11 no.3
• /
• pp.215-220
• /
• 2018

This paper limited the participation of large corporations in the mass information market by revising the Software Industry Promotion Act in order to increase business opportunity, equality of opportunity, and capacity building for small and medium sized IT companies. However, it is a fact that the medium and small SW companies have insufficient business capacity and expose various problems such as quality degradation of public information business, inadequate risk management, and deterioration of schedule management. In order to solve this problem, this paper derived the factors of quality deterioration in the system integration project and proposed to carry out the project by using some activities of VISUALIZATION, rigorous test management and Agile Methodology as a solution. Applying these measures to healthcare IT projects developed by midsize / small-sized IT companies has improved communications, improved quantitative progress management and improved project visibility. In addition, it contributed to minimizing defect resolution time, improving the requirement coverage ratio, and shortening unnecessary meeting time.

• Journal of Digital Convergence
• /
• v.10 no.6
• /
• pp.269-274
• /
• 2012

The paper describes the efficient and agile design methodology for the smart phone application, so called the App. Despite the number of smart phones as well as their applications is rapidly being increased recently, the smart and easy methodology for App development is not well developed and not matured in use yet. Since the App is converted to programs or contents from the new ideas, especially, it is important to design and implement the App rapidly and systematically. In order to resolve this problem, we adopt the UI centered approach first of all, emphasizing user-efficient utilization of applications. And we also try to build the whole process in streamlined procedure, making each step reasonable, and the input and output for the step well organized. The design methodology described here is evaluated by designing popular sample application, Scheduler, and also compared with some well-known software design methodologies.

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.8
• /
• pp.555-564
• /
• 2013

Innovative evolution in mobile devices along with recent spread of Tablet PCs and Smart Phones makes a new change not only in individual life but also in enterprise applications. Especially, in the case of medium-large mobile applications for large enterprises which generally takes more than 3 months of development periods, importance and complexity increase significantly. Generally Agile-methodology is used for a development process for the medium-large scale mobile applications, but some issues arise such as high dependency on skilled developers and lack of detail development directives. In this paper, S-MADP (Smart Mobile Application Development Process) is proposed to mitigate these issues. S-MADP is a service oriented development process extending a object-oriented development process, for medium-large scale mobile applications. S-MADP provides detail development directives for each activities during the entire process for defining services as server-based or client-based and providing the way of reuse of services. Also, in order to support various user interfaces, S-MADP provides detail UI development directives. To evaluate the performance of S-MADP, three mobile application development projects were conducted and the results were analyzed. The projects are 'TBS(TB Mobile Service) 3.0' in TB company, mobile app-store in TS company, and mobile groupware in TG group. As a result of the projects, S-MADP accounts for more detailed design information about 'Minimizing the use of resources', 'Service-based designing' and 'User interface optimized for mobile devices' which are needed to be largely considered for mobile application development environment when we compare with existing Agile-methodology. Therefore, it improves the usability, maintainability, efficiency of developed mobile applications. Through field tests, it is observed that S-MADP outperforms about 25% than a Agile-methodology in the aspect of the required man-month for developing a medium-large mobile application.

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