• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.155-168
• /
• 2006

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

• Journal of the Korea Society for Simulation
• /
• v.19 no.1
• /
• pp.153-160
• /
• 2010

Most part of errors in software development process are included during the stage of requirements definition and design. And correction or elimination of errors from those stages requires much more efforts and costs than those from the later part of software development process. However, despite of the importance of the validation of requirement definition and design stages, several kinds of problem have made it hard to be done successfully. Therefore, in this paper, we introduce a novel validation process for the preliminary design stage. The validation process is based on simulations of model and it can be used to validate requirements and model simultaneously. Models in the validation process will take only the behavior of software and be built on Ptolemy framework. The usability of our validation process is confirmed with a case study over DNS system environment. And the result of simulation shows well-known errors or vulnerabilities can be found with simulations of model which has the behavior of software. This means our validation process can be used as a process to validate requirements and models during the early stage of software development process.

• Journal of KIISE:Software and Applications
• /
• v.27 no.4
• /
• pp.384-392
• /
• 2000

As a software becomes more complicated and large-scaled, it is very important for a software engineer to analyze user's requirements precisely and apply them effectively in the development stage. Due to the growth of the internet, the necessity of requirements elicitation and analysis in distributed environments has also become larger. This paper proposes a requirements elicitation supporting system that offer the basis for effectively analyzing requirements collected in distributed environments. The proposed system automatically categorizes collected requirements sentences into selected subject fields by measuring their similarity using a similarity measurement technique. Therefore, it reduces the difficulties in the initial stage of requirements analysis and it supports rapid and correct requirements analysis. This paper verifies the efficiency of the proposed system in similarity measurement techniques through experiments, and presents a process for requirements specifications elicitation using the embodied system

• Journal of Digital Convergence
• /
• v.11 no.9
• /
• pp.45-54
• /
• 2013

Currently, the domestic nursing information system software products are being developed competitively with the participation of many companies, generating quantitative development with high value added. However, it is true that the study that concurrently adds qualitative enhancements to such quantitative development has been inadequate. In order to secure international competitiveness in the field of nursing information system software, it is necessary to establish quality requirements on this system, and along with it, establish an evaluation system on the nursing information system software products. The purpose of this study is to analyze the accompaniment and technology of the nursing information system, and by identifying the requirements, establish test and evaluation system of the said system.

• Journal of Internet Computing and Services
• /
• v.22 no.3
• /
• pp.59-66
• /
• 2021

This study proposes a requirements monitoring method that systematically performs traceability management and change management for requirements in order to improve the quality of software systems in the software development process. To this end, we present the artifact change history management models to systematically perform change management for individual artifacts and the traceability matrixes to define the relationship between artifacts. It also proposes a visual dashboard that makes it easy to grasp the situation in which changes are propagated to related artifacts when specific artifacts change.

• 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 KIISE
• /
• v.44 no.1
• /
• pp.27-35
• /
• 2017

Many studies have addressed 'Adaptive User Interface (AUI)', wherein the user interface changes in accordance with the situation and the environment of each user at runtime. Nevertheless, previous papers for AUI barely reflected the viewpoints from requirements engineering field, since most of them focused on proposing the architecture and design. In this study, we outline AUI with the perspective of requirements engineering and propose the requirements elicitation and specification method based on concepts which have been researched in the area of self-adaptive system. Step by step, we first redefine and reinterpret the well-known concepts of self-adaptive software, after which the AUI requirements are elicited and specified. Finally, we illustrate a case study, which demonstrates the effectiveness of our method.

• KIPS Transactions on Software and Data Engineering
• /
• v.9 no.11
• /
• pp.357-366
• /
• 2020

As the proportion and complexity of software embedded in aircraft increase, risk factors such as mission failure, function failure and performance failure due to software errors also increase. In the mission-critical software systems such as aircraft software, managing requirement traceability is essential to maintain the software systems with minimal period and cost. However, the development company is not accurately complying with the guideline for managing requirement traceability due to various reasons such as development cost and schedule. Therefore, it is not easy to systematically establish and maintain requirement traceability. In the paper, we analyze actual test cases of aviation software systems from the viewpoint of requirements traceability in order to learn if there are failure cases of test cases due to the absence of systematic traceability management activities. We also check the risks associated with the failure cases according to the type and severity of the cases. As a result of analyzing a total of 7 aircraft-mounted software, failure cases could be divided into three types: omission of requirements, lack of connection between requirements and test procedures, and omission of test procedures. There were a total of 18 failure cases, 6 for each type. The numbers of high, middle and low risks were 1, 13 and 4, respectively, where the number of middle risks is largest.

• Journal of information and communication convergence engineering
• /
• v.7 no.3
• /
• pp.247-252
• /
• 2009

The Internet has made a huge impact on the way we, as humans, communicate. During the last decade a series of new communication mediums have emerged and communication protocols have come and gone. This puts new requirements on the development process and architecture of the communication platforms, operated by communities, in order to proactively ensure support for future communication protocols. Even further, additional requirements are added when the software itself will be maintained by a community. In this paper we explore the world of Open Source Software. We present our suggestions of usable design-principles and our process in developing a sustainable information system.

• Current Industrial and Technological Trends in Aerospace
• /
• v.6 no.2
• /
• pp.69-79
• /
• 2008

As the cost of the operational spacecraft simulator is a large portion of the spacecraft cost and its requirements increase, it is given the pressures to reduce the cost and the development period. For that reason, the space industry with the coordination of ESA has made a study of the reuse in a wide scope across space projects. Its scope includes not only simulation software itself but also software requirements, design, work experience and developing process/methodology. The standard for simulator model portability and the efficiency enhancement of the development process as a result have been successfully applied to several projects. This paper describes the recent trend of the spacecraft simulator in Europe and the present status of its the study and the development.