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

• Proceedings of the Korea Information Processing Society Conference
• /
• 2021.05a
• /
• pp.33-36
• /
• 2021

Corona 19 minimizes face-to-face contact, and online untact platforms are emerging in the medical sector. However, there are potential risks of medicine expiration, medicine misuse, and responsible materials management for secure delivery. In this paper, we investigate three key functional requirements for online pharmacy, and design the blockchain based online pharmacy to meet the requirements. To protect the patient's privacy and to ensure tamper-free traceability, we incorporate the multi-level access authentication scheme for each participant (governments, medical circles, and patients). We show that our system guarantees patient's privacy without further system modification.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.8
• /
• pp.391-400
• /
• 2017

Software architecture plays a key role in satisfying non-functional requirement (NFR), i.e. quality requirements and constraints. Architecture design methods and tactics for conventional NFR are largely available in literatures. However, the methods for the target system-specific non-conventional NFRs are not readily available; rather architects should invent the design methods from their experiences and intuitions. Hence, the hardship to design architectures for non-conventional NFRs is quite high. In this paper, we provide a systematic architecture design methodology for non-conventional NFRs. We provide a five-step process, and detailed instructions for the steps. In the process, we treat the traceability among artifacts and seamlessness as essential values for supporting effective architecture design. We apply the methodology on designing architectures for a platform software system. We believe that the proposed methodology can be effectively utilized in designing high quality architectures for non-conventional NFRs.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.29 no.4
• /
• pp.753-773
• /
• 2019

CV(Connected Vehicle) technology provides safety-related services and user convenience-related services to vehicle. Safety-related services can cause privacy problem by continuously transmitting vehicle information to nearby vehicles or base stations. Therefore, safety-related services should provide vehicle anonymity for privacy protection. However, if convenience-related services such as payment services fail to provide vehicle anonymity, driver information related to safety-related services may also be leaked. In this paper, we design a payment protocol based on ECQV(Elliptic Curve Qu-Vanstone) impicit certificate and group signature that provides BU-anonymity and traceability. The proposed payment protocol makes it impossible to track vehicles from payment transactions history by separating roles of payment system components. Moreover, we define the security requirements that the vehicle payment protocol must satisfy and show that the protocol satisfies the requirements.

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

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.5
• /
• pp.115-126
• /
• 2012

It is very important to trace whether all the requirements has been reflected in the developed system. However, most existing researches apply Requirement Traceability Matrix(RTM) to the whole SDLC according to the development methodology. RTM has no practical value because it has not only too many pursuit items but also its tracking method is very complicated and the practical management in developing the information system is not accomplished nearly. Therefore, in this study, we proposed an enhanced RTM which was composed of only necessary items and allow us to manage the applied area effectively from Request for Proposal(RFP) or the proposal stage to SDLC stage then confirmed the effect through six actual applicable cases of information system development project of "K" company.

• Journal of the Korean Society of Systems Engineering
• /
• v.15 no.2
• /
• pp.57-65
• /
• 2019

The weapon system applies the rule that the system engineering procedure must be applied at the acquisition stage. Naval ships, which are one of the important naval weapon systems, take a long period of time to acquire, and the leadership must be commissioned. Therefore, in order to acquire a naval ship, high risk management is necessary, and it is necessary to promote business success through effective application of system engineering which is a scientific management method. However, in the case of naval ships, there are no specific procedures and methods for applying the system engineering. Therefore, research on application method of system engineering which can be easily used by person in charge is necessary. This should have a simple approach to ensure effective business performance by systematically refining and simplifying existing works. QFD (Quality Function Deployment) is a way to improve product satisfaction, impress customers, reduce defective products, reduce design errors, and reduce costs. This systematically develops these mutual relationships by converting the needs of customers into quality characteristics of products and defining them as the design quality of products considering the functions, quality, and process elements of parts. The purpose of this research is to present concrete methodology at the practical level using QFD in a way to ensure traceability of requirements which is an important element of system engineering.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.25 no.4
• /
• pp.22-31
• /
• 2002

A high-speed rail system represents a typical example of large-scale multi-disciplinary systems, consisting of subsystems such as train, electrical hardware, electronics, control, information, communication, civil technology etc. The system design and acquisition data of the large-scale system must be the subject under strict configuration control and management. Not only the requirements of the large-scale system dictate the contracts with the suppliers but also become the basis for the development process, project execution, system integration, and testing. The requirements database provide the system design specification of all development activities. Using the RDD-100, a systems engineering tool, the Korea next-generation high-speed rail program can establish requirements traceability and development process management in performing the enabling train technology development projects. This paper presents the results from a computer-aided systems engineering application to the Korea next-generation high-speed railway project. Especially, the focus of the study was on requirement management and PBS(Product Breakdown Structure) management.

• Transactions of the KSME C: Technology and Education
• /
• v.1 no.2
• /
• pp.199-204
• /
• 2013

In this paper, a new system requirement management tool and its application on the Urban Transit Maglev Project were introduced. In most R&D projects on complexity system such as transportation system, Systems Engineering(SE) activities are included on each project, and SE teams are using commercial computer-based tools to perform the SE activities. Even though SE tools help to manage huge data and documents on engineering efficiently, but well-designed functions of SE tools which support SE activities are not sufficiently used on the whole process of system engineering. In order to computer-based SE tools are to be effectively used on project management, most engineers who takes engineering and coordination roles, at least sub-project managers should be familiar to the tool and could be easily use it, but usability of commercial SE tools are very difficult for normal engineers with no experience on SE activities and SE tools. To overcome this difficulty, we developed a new system requirement management tool considering each user's scenario on using engineering tools. The developed tool could not cover whole SE processes, but designed to perform requirement engineering such as system requirements(SRs) management, specification management, traceability management, SRs' verification activity management and so on. All the entities on SR database are inter-connected by pre-recognized traceabilities, so even non-specialists on SE can easily browse the database and find entities concern, and linked information such as interacted entities, legal or engineering constraints, coordination documents, status of development and verification and so on. Also functions for SR verification tools, TPM(Technical Performance Measure) tools, DB searching tools with traceability, and report generation tools are included on the system.

• Journal of KIISE:Software and Applications
• /
• v.34 no.5
• /
• pp.419-430
• /
• 2007

It is very important to track whether software is properly developed according to requirements. This study suggests a method to track requirements by using a tracking table. In this study, the tracking table indicates why such requirements are included by detailing the content of requests for proposals and proposals. The table also facilitates verification of the consistency between outputs and the integrity by having ID codes of each requirement mapped to each output. Furthermore, as this study was conducted, it was found that some factors were required to be added or supplemented to the outputs at the requirement gathering stage of MaRMI-Ⅲ v.4.0 methodology. Thus, this study seeks to present this additional result along with the enhanced tracking table. By verifying outputs, the tracking table presented in this study will help to reduce all kinds of risks and problems that may occur in software development due to the lack of management of requirements. In addition, the output of the requirement-gathering stage of MaRMI-Ⅲ v.4.0 methodology will be improved/supplemented according to the creation of tracking tables; this will increment the applicability of the MaRMI-III methodology.