• Proceedings of the Safety Management and Science Conference
• /
• 2007.04a
• /
• pp.425-435
• /
• 2007

This paper presents various information technologies of software product evaluation such as process for evaluators, process for developers, and process for acquirers. This study also introduces system life cycle processes and its application guide.

• Journal of Information Technology Applications and Management
• /
• v.20 no.2
• /
• pp.69-87
• /
• 2013

The expanded spiral model in this paper consists of five processes of architecture design, architectural construction, architectural maintenance, operation, and architectural management. The former four processes are executed alternatively, while the latter architectural management process is executed continuously interacting with the other processes during the whole life cycle of the system. The expanded spiral model provides a conceptual framework to sort discussions of architectural degeneration into those of product-oriented processes and those of management processes, making it possible to incorporate the models and body of knowledge about project and program management especially those of Project Management Institute, into discussions of architectural degeneration. A good architecture decomposes the software-intensive system into components mutually interacting in a well-formed structure. The architecture design process and the architectural construction process together create the object system with well-designed architecture. The architectural maintenance process prevents the implemented architecture deviate from the designed architecture. The architectural management process monitors the changes of requirements including architecturally significant requirements, supports the other processes to be executed reflecting various perspectives of stake-holders, and creates and documents the reasons of architectural decisions, which is considered as a key element of the architecture.

• Proceedings of the KIEE Conference
• /
• 2005.05a
• /
• pp.185-187
• /
• 2005

The reactor protection system is the most important function for the safe operation of nuclear powerplants (NPPs) in that such system protects a nuclear reactor tore whose damage can cause an enormous disaster to the nuclear facility and the public. A digital reactor protection system (DRPS) is being developed in KAERI for use in the newly-constructed NPPs and also for replacing the existing analog-type reactor Protection systems. In this paper, an software verification and validation (V&V) activities for DRPS, which are independent of the DRPS development processes, are described according to the software development life cycle. The main activities of DRPS V&V processes are the software planning documentations, the verification of software requirements specification (SRS) and software design specification (SDS), the verification of codes, the tests of the integrated software and system. Moreover, the software safety analysis and the software configuration management are involved in the DRPS V&V processes. All of the V&V activities are described, in detail, in this paper.

• Journal of Information Technology Services
• /
• v.8 no.1
• /
• pp.125-142
• /
• 2009

The Ministry of Information and Communication announced "The Guideline for Management of Software Project" in October 2006. The public employees(acquirer) have to manage software projects with this guideline. The guideline was based on the International standard(ISO/IEC 12207) and IEEE standard(IEEE/EIA 12207), and was developed by considering the domestic software industry environment. The guideline can help to establish a software acquisition process for appropriate management of software projects, and the process can increase the management productivity of software projects. This study provides the explanation about the guideline with terms of 5W1H(who(user), what(summary), when(time to apply), where(domain of application), why(objective), how(method of use)) for understanding of the guideline.

• International Journal of Computer Science & Network Security
• /
• v.23 no.6
• /
• pp.169-175
• /
• 2023

Ethical hackers are using different tools and techniques to encounter malicious cyber-attacks generated by bad hackers. During the software development process, development teams typically bypass or ignore the security parameters of the software. Whereas, with the advent of online web-based software, security is an essential part of the software development process for implementing secure software. Security features cannot be added as additional at the end of the software deployment process, but they need to be paid attention throughout the SDLC. In that view, this paper presents a new, Ethical Hacking - Software Development Life Cycle (EH-SDLC) introducing ethical hacking processes and phases to be followed during the SDLC. Adopting these techniques in SDLC ensures that consumers find the end-product safe, secure and stable. Having a team of penetration testers as part of the SDLC process will help you avoid incurring unnecessary costs that come up after the data breach. This research work aims to discuss different operating systems and tools in order to facilitate the secure execution of the penetration tests during SDLC. Thus, it helps to improve the confidentiality, integrity, and availability of the software products.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.87-96
• /
• 2006

This paper focused on the method for customizing software development path, considering the project environments and characteristics. he selection standard of development path is composed of ten items, based on the process of ISO/IEC TR 15721 Information Technology Guide for ISO/IEC 12207 (Software Life Cycle Process) and ISO/IEC 15504 Information technology - Process assessment. The ten items were reflected the project environments and characteristics, at the same time the items conduct the adjustment item of selecting project development path. An algorithm for selecting software development path through items of the project environments and characteristics is presented. To test the algerian in this paper, a system for selecting development path, which reflected algorithm was developed. The development project for web-based system were also adopted to the system for selecting development path. In addition, provened hand-worked project path process differed from machine-worked project path process. The reason why it differs is that outputs were mixed or their names were changed. The effect is to select easily software development route suitable for project environment and characteristics.

• Proceedings of the Safety Management and Science Conference
• /
• 2007.04a
• /
• pp.437-448
• /
• 2007

This paper introduce information technology of software process assessment. It consists of eight parts such as concepts and introductory guide, a reference model for processes and process capability, performing an assessment, guide to performing assessments, an assessment model and indicator guidance, guide to competency of assessors, guide for use in process improvement, and guide for use in determining supplier process capability.

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 2001.01a
• /
• pp.249-255
• /
• 2001

Different kinds of information are used when solving tasks that arise in the life cycle of an applied knowledge based system (KBS). Many of these tasks are still under investigation. Their solving methods are often researched independently of each other due to complexity of the tasks. As a result, systems that realize these methods turn out to be incompatible and therefore could not be used together in the lifecycle of a KBS. The following problem arises here: how to support the full life cycle of a KBS. This paper introduces a class of computer knowledge banks that are intended to support the full life cycle of KBSs. Primary tasks that arise in the full life cycle of a KBS are analyzed. The architecture of a knowledge bank of the introduced class is presented, including an Information Content, a Shell of the Information Content and a Software Content. General requirements on these components are formulated on the basis of the analysis. These requirements depend on the current state of understanding in the life cycle of KBSs.

• Journal of Internet Computing and Services
• /
• v.20 no.3
• /
• pp.69-75
• /
• 2019

The safety and performance of medical device software is managed through life-cycle processes, which represent the entire process of research and development (R&D). The life-cycle process of medical device software is represented by an international standard called IEC 62304, ISO/IEC 12207. In order to license the product, the manufacturer must have document artifacts that comply with the IEC 62304 standard. However, these standards only describe the content of the activity and do not provide a method or procedure for documentation. Therefore, this paper suggests R&D documentation guidelines that assist medical device software developers to have R&D documents conforming to the standards. For this purpose, this study identifies the requirements related to documentation among the requirements existing in the standard and extracts them in the form of guidelines showing only the core information of the requirements. In addition, through the Web framework implemented based on this research, the developer can evaluate whether the technical documents are written in accordance with the R&D document guidelines. Medical device software manufacturers can efficiently produce high-quality research and development documents through R&D documentation guidelines, and they can have standards-compliantresearch and development documentation required for licensing procedures.

• The KIPS Transactions:PartD
• /
• v.9D no.6
• /
• pp.1083-1090
• /
• 2002

The software development methodology has not caught up with the rapid change of information technology. Most of the software development projects use structural methodology or information engineering methodology. If established software development methodologies don't reflect technologies applied to the project, the project may be performed ineffectively. This paper describes a model in which we can apply a new information technology to an already existed structural methodology or information engineering methodology. This model uses the technique of the divide and conquer that software development life cycle is divided into phases, each phase is divided into viewpoint- areas and the software development processes of a new information technology are applied to each small area. By using the design phase this paper shows application example, in which I applied web-based development processes to CS@RoadMap Methodology of KCC Information & Communication, a system provider in Korea. The CS@RoadMap Methodology reflecting the Web technology, Web@RoadMap Methodology, has been applied to the public-domain projects.