• Nuclear Engineering and Technology
• /
• v.28 no.6
• /
• pp.594-601
• /
• 1996

To assure quality of safety critical software, software should be developed in accordance with software development procedures and rigorous software verification and validation should be performed. Software verification is the formal act of reviewing, testing or checking, and documenting whether software components comply with the specified requirements for a particular stage of the development phase [1]. New software verification methodology was developed and was applied to the Shutdown System No. 1 and 2(SDS1,2) for Wolsong 2, 3 and 4 nuclear power plants by Korea Atomic Energy Research Institute(KAERI) and Atomic Energy of Canada Limited(AECL) in order to satisfy new regulation requirements of Atomic Energy Control Board(AECB). Software verification methodology applied to SDS1 for Wolsong 2, 3 and 4 project will be described in this paper. Some errors were found by this methodology during the software development for SDS1 and were corrected by software designer. Output from Wolsong 2, 3 and 4 project have demonstrated that the use of this methodology results in a high quality, cost-effective product.

• Aerospace Engineering and Technology
• /
• v.11 no.1
• /
• pp.111-117
• /
• 2012

Agile is a software development methodology which was established for four objectives; people, collaboration, responsiveness, and working software. Thus the Agile methodologies have been applied not only software development fields but also various special areas of technology. ESA (European Space Agency) adopt several Agile methodologies, including Scrum as the key technique, for the software development of ground segment. This article analyzes trends of Agile methodologies and introduction cases of the methodologies for ESA's ground segment software development.

• Journal of the Korean Society of Systems Engineering
• /
• v.14 no.2
• /
• pp.83-88
• /
• 2018

Software has become an integral part of almost any system, triggered by the ever-growing demand for automation and artificial intelligent throughout engineering domains. The complexities of software-centric systems are also increasing, which make software test efforts become essential in software development projects. In this study, we applied systems engineering methodology in generating software test cases. We found out the similarities between requirements analysis and traceability concept of systems engineering and test specification contents of software test. In terms of acceptance test, software test cases could be considered as validation requirements. We also suggested a method to determine test order using a SysML modeling tool.

• Transactions of the Korean Society of Automotive Engineers
• /
• v.20 no.6
• /
• pp.117-125
• /
• 2012

This paper describes a model-based software development methodology for AUTOSAR-ready light software architecture(AUTOSAR-Lite). The proposed methodology briefly represents an application software modeling technique using Matlab/Simulink. Using the proposed technique, application software architecture elements (e.g. software components, runnables, and interfaces) and functional behaviors can be designed in a single modeling environment. From the designed model, the codes of application software is automatically generated using Real-Time Workshop Embedded Coder. The generated application software is easily integrated with hand-coded basic software using the proposed method. In order to evaluate the proposed methodology, a diesel engine management system for a passenger car was employed as a case study. Based on the methodology, 8 atomic software components and 52 runnables are successfully developed, and they are evaluated by engine experiments. From this case study, AUTOSAR compatible model-based application software was successfully developed, and the effectiveness of the proposed methodology was evaluated.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.3
• /
• pp.622-632
• /
• 1999

As the complexity of software development is increasing due to networking, multimedia, and diverse system architecture, the need for effective software development methodology is increasing. Especially, due to software standard and internalization of software market, it is necessary to accept international quality such as ISO 9000-3. In addition, object oriented development methodology is required due to rapid propagation of OO technology and standardization. Recently, UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we develop Java and CORBA-based software, often UML is applied to Java and CORBA-based projects. However, current structural or OMT-based object-oriented methodologies. In this paper, we proposed UML-based development and concrete guidelines for each phase in order to apply UML to software development practically and effectively. Also, we define the transition guidelines and semantics between various development tasks. In addition, the analysis and design techniques of user interface and system development techniques needed in Web application development are presented.

• Journal of Korean Society for Quality Management
• /
• v.25 no.1
• /
• pp.142-155
• /
• 1997

To successfully carry out large scale research projects while su, pp.rting quality assurance of research output, effective and systematic management through utilization of resources such as manpower, time and cost as well as engineering techniques such as component technology and design methodology is required. It is necessary to establish development methodology to su, pp.rt quality assurance. The development methodology covers the contents and procedures of the project, such as division of the project into independently executable units, allocation of resources including researchers, component technology, related know-how and equipment, deployment of research units and integration of the project at the end. In this paper we present systematic development methodology for quality assurance in large scale software development projects by analyzing the contents of the methodology a, pp.ied to the Gigabit Information-processing And Networking Technology development project(GIALT).

• Journal of KIISE
• /
• v.44 no.5
• /
• pp.510-521
• /
• 2017

The software development process (SDP) plays an important basic role in software engineering education. Every software is developed in accordance with a specific SDP which contains all phases of software development. SDP education helps students to understand the overall techniques and the process of software engineering. This paper introduces a software development methodology (i.e., process) - 'OOPT (Object Oriented Process with Traceability),' which was proposed for use in university software engineering classes. The OOPT is based on object-oriented software development, and it defines concrete requirements as well as outputs of each process/phases. It also contains the unit/system testing and a traceability analysis. We have used the OOPT in software engineering classes at Konkuk university for eight years. This paper conveys our experience as well as future extension and improvement plans.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 1995.04a
• /
• pp.776-782
• /
• 1995

This paper presents a methodology for development of a heterarchical control system in Flexible Manufacturing Systems (FMS) environment. A Petri net based model is applied for development of control software. A real-time scheduling methodology for the heterarchical system is also developed and it is used as a software entity in the overall architecture. The partition of generic and specific modules in control software development is emphasized. The control system performs its control tasks in two stages: (1) generation of generic control code and distribution of them to each controller entity prior to system execution; (2) generation of specific control code according to job arrival and its process plan. The control software and the scheduling algorithm are evaluated by a simulation program.

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.179-188
• /
• 2006

MDD/MDA which recently raising its head is technology that increase software development productivity through automatic transformation form higer abstract model into lower abstract model, or from model to code. This paper analyzes the effect on productivity by measuring Function Point per MM(man-month) in a software development project which performed in CBD methodology, and introduce the method of applying MDD/MDA technology in the project.

• The Journal of Information Systems
• /
• v.16 no.4
• /
• pp.243-268
• /
• 2007

It is critical to manage risks to complete IS(Information Systems) projects successfully. Identifying risk factors would be the first step for the project risk management. Previous research has discussed the issue with various points of view, such as different risk factors based on project types and roles involved in their projects. This paper empirically explored how people perceive different risk factors by project development methodology, between self-developing IS using programming language like C, Visual Basic and adapting software package already developed by software venders like ERP, CRM packages. There are researches regarding project risk factors for project management in the several point of views. And there are also researches regarding comparison between self-developing and adapting software packages methodology in IS project. However, there are no study on project risk factors comparison between self-developing IS using programming language and adapting software packages already developed by software venders in IS project. This research can be differentiated from previous ones, because it was considered both point of project risk management and development methodology in IS project. This research results implied meaningful messages to enterprise company to be planned IS projects and people who involved in IS projects. They should consider and need to prepare differently according to each development methodology for preventing project risks. It makes them reduce project risks in each case and complete successfully IS projects. Especially, if they have no experiences for implementing software packages, they can forecast the project risks and prepare them in advance.