• Proceedings of the Korean Society of Surveying, Geodesy, Photogrammetry, and Cartography Conference
• /
• 2003.10a
• /
• pp.257-262
• /
• 2003

This study is aimed to research the management methodology for the process of GIS database construction. In general, used methodologies are made for the purpose of application program development. And the methodologies reflected GIS characteristics are also applied for GIS software development. But the software methodologies are never introduced to construction of GIS database. In this study, various common methodologies are investigated and analyzed, and the methodology which include the characteristic of GIS database construction process as work steps and detail paths is developed and suggested.

• The Journal of the Korea institute of electronic communication sciences
• /
• v.19 no.2
• /
• pp.403-408
• /
• 2024

Software development methods have continued to evolve in response to changes in the environment. Structural methodology, information engineering methodology, and object-oriented methodology are the major trends of this change. Each methodology has its own characteristics and advantages, and its applied fields are different. Engineers performing practical work are familiar with applying each methodology, but are not familiar with applying structural methodologies or information engineering methodologies in an integrated manner. Therefore, the maximum effect of the methodology cannot be obtained. With this in mind, we would like to organize and present examples of how to integrate and apply structural methodology and information engineering methodology to the target of each methodology.

• ETRI Journal
• /
• v.26 no.2
• /
• pp.167-180
• /
• 2004

As component-based development (CBD) rapidly spread throughout the software industry, a comprehensive methodology is needed to apply it more systematically. For this purpose, a new CBD methodology named Magic & Robust Methodology Integrated III (MaRMI-III) has been developed. The purpose of this paper is to present MaRMI-III by its constituent processes and claim that it can be used to support system developers conduct CBD in a consistent manner. First, we review the CBD approach to system development and the role of CBD methodology, and then we explain the several characteristics of MaRMI-III which are considered necessary to the CBD environment. Next, we explain a process model of MaRMI-III which separates the development process from the project management process and prescribes well-ordered activities and tasks that the developer should conduct. Each phase forming the Process Model is explained in terms of its objectives and main constituent activities. Some techniques and workproducts related to each phase are also explained. Finally, to examine the usefulness of MaRMI-III, an analytical comparison with other CBD methodologies and the results of a questionnaire survey are described.

• Journal of Korea Multimedia Society
• /
• v.22 no.2
• /
• pp.292-298
• /
• 2019

Mobile-based software development methodology has been vigorously researched from using object-oriented development methodology and component-based development methodology previous structural developing methodology. There are two types of OS in mobile platform which are android and iOS. There is a problem that the application to be developed is developed depending on the device type. To resolve this problem, first, the system structure and design method should be managed effectively. Second, a basic design guide that can be commonly adapted to the each project is required. In this paper, we define a mobile cross platform meta model based on MDA-development methodology, focusing on reusability, portability and interoperability about non - dependent part of the mobile platform. If the proposed meta-model is applied to manage the related information and all the types of Mobile-Apps become available through independent mobile app development process, henceforward, it will be much of help establishing formulaic mobile-app developmental methodology.

• Proceedings of the KIEE Conference
• /
• 2007.10c
• /
• pp.201-203
• /
• 2007

Safety critical systems are those in which a failure can have serious and irreversible consequences. Nowadays digital technology has been rapidly applied to critical system such as railways, airplanes, nuclear power plants, vehicles. The main difference between analog system and digital system is that the software is the key component of the digital system. The digital system performs more varying and highly complex functions efficiently compared to the existing analog system because software can be flexibly designed and implemented. The flexible design make it difficult to predict the software failures. This paper reviews safety standard and criteria for safety critical system such as railway system and suggests software development methodology for more detail description.

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

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.6
• /
• pp.377-382
• /
• 2013

A convergence software development methodology based on product line engineering provides an architecture model for application development and it also provides workflow as a behavior specification of control component development to develop transaction centric application. To effect a change on software development based on product line engineering it has to be supported by a tool. But almost workflow modeling tools dose not support product line engineering concept. So we need new workflow modeling tool to support the convergence software development methodology. In this paper, we introduce a toolset for workflow modeling that consists of eclipse plug-in applications and open source tool and describe the relationships of tools through example.

• Journal of KIISE:Software and Applications
• /
• v.27 no.5
• /
• pp.488-498
• /
• 2000

Object-oriented methodologies are widely used in the development of huge and complex systems since these methodologies produce the comprehensible and extensible model of systems. In order to apply an object-oriented methodology to a software development, developers should derive a method customized to a specific project from the methodology and, then, construct a development process from the method. Unfortunately, existing object-oriented methodologies lack a systematic facility for the construction of a method and a process. In this paper, we present a customizable object-oriented methodology to support the systematic derivation of a project specific method from the generic methodology. To derive a project specific method from the methodology, we transform the problem of a derivation to a planning problem and apply planning techniques. Our planning technique uses the description of an architecture that captures the structure and characteristics of a software under development as input and constructs an appropriate method with respect to the architecture. The architecture-centered construction facilitates the effective handling for the characteristics of the software since an architecture capture the decisions that must be maintained consistently during the development.

• Journal of KIISE:Software and Applications
• /
• v.28 no.10
• /
• pp.743-756
• /
• 2001

Component-based software development (CBSD) is a method for building large software system by integrating previously-existing software components. Software development method using components has several advantages such that reducing time to delivery and development costs, and increasing productivity etc. But integrating components developed from multiple vendors is too difficult As a result it is required the understanding on the context of use to develop reusable components. The context of use for software component of determined by software architecture. Therefore, it is possible to develop an application based on components if is based on software architecture. Also, it is essential to consider domain concepts for CBSD. To increase the reusability of components. we should develop components in a domain which is a set of related systems. In this paper, we proposed a domain architecture development methodology that supports component-based software development. Domain architecture that represents components and their relationship is produced through domain analysis and design process. We believe that component development methodology using proposed domain architecture can efficiently develop highly reusable components as well as easily develop and application using information acquired from domain architecture.

• Journal of Korea Multimedia Society
• /
• v.18 no.4
• /
• pp.546-556
• /
• 2015

Since the concept of software engineering was first used in 1968 by NATO Science Committee, a lot of research work and improvements have been made on software development methodology and software quality control, but they still fall short of ensuring successful development of small and medium scale software systems. Under these circumstances, Center for Software Engineering (CSE) at National IT Industry Promotion Agency(NIPA) has been conducting studies on quality control methodologies of software visualization well-suited for small and medium scale software systems, and also working on the systemization and quantification of software quality control. In this paper, we attempt to scope on the software development management of domestic and foreign small and medium-sized enterprises that are lying in the blind spot, compared to large enterprises with well-organized software development systems. In particular, based on software visualization that CSE is pursuing for small and medium-sized developers, we propose a practical quality control methodology well-suited for small and medium scale projects, and a low-cost quality control management tool by combining open-source quality control tools. Our proposal is expected to induce developers' mind change in SI-specialized small and medium-sized software enterprises, increase their profits and improve customer satisfaction through project quality control.