• Journal of the Korea Safety Management & Science
• /
• v.9 no.6
• /
• pp.89-96
• /
• 2007

It is well known that the test and evaluation plan (TEP) is very crucial in the successful development of safety-critical systems. As such, this paper discusses an approach to the development of the TEP for a system that should meet safety requirements in the systems development process. It is studied how to incorporate the result of preliminary hazard analysis (PHA) in generating the safety requirements. It is also discussed how to deal with them when the system requirements (i.e., functions, performance, constraints, components, etc) and the safety requirements are integrated into one model. While doing so, we have constructed the required traceability among them, which is necessary and very useful when the safety requirements need to be corrected or be changed. The use of the traceability makes it possible to easily check out whether and how the safety requirements are properly incorporated in the system design process. Furthermore, without the verified traceability, the system cannot be changed or upgraded later. In order to implement the model on a computer-aided tool, we have constructed a database (DB) schema. As a result, the implemented model/DB allows to automatically generate TEP which can be used to measure the performance and safety level of the developed system.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.3
• /
• pp.99-109
• /
• 2021

In recent machine learning studies, in order to consider the quality and completeness of data, derivation of non-functional requirements for data has been proposed from the viewpoint of requirements engineering. In particular, requirements engineers have defined data requirements in machine learning. In this study, data requirements were derived at the data acquisition (DAQ) stage, where data is collected and stored before data preprocessing. Through this, it is possible to express the requirements of all data required in the existing DAQ system, the presence of tasks (functions) satisfying them, and the relationship between the requirements and functions. In addition, it is possible to elicit requirements and to define the relationship, so that a software design document can be produced, and a systematic approach and direction can be established in terms of software design and maintenance. This research using existing DAQ system cases, scenarios and use cases for requirements engineering approach are created, and data requirements for each case are extracted based on them, and the relationship between requirements, functions, and goals is illustrated through goal modeling. Through the research results, it was possible to extract the non-functional requirements of the system, especially the data requirements, from the DAQ system using requirements engineering.

• Journal of Positioning, Navigation, and Timing
• /
• v.11 no.4
• /
• pp.389-395
• /
• 2022

In order to ensure reliability the high-level automated driving such as Advanced Driver Assistance System (ADAS) and universal robot taxi provided by autonomous driving systems, the operation with high integrity must be generated within the defined Operation Design Domain (ODD). For this, the position and posture accuracy requirements of autonomous driving systems based on the safety driving requirements for autonomous vehicles and domestic road geometry standard are necessarily demanded. This paper presents localization requirements for safe road driving of autonomous ground vehicles based on the requirements of the positioning system installed on autonomous vehicle systems, the domestic road geometry standard and the dimensions of the vehicle to be designed. Based on this, 4 Protection Levels (PLs) such as longitudinal, lateral, vertical PLs, and attitude PL are calculated. The calculated results reveal that the PLs are more strict to urban roads than highways. The defined requirements can be used as a basis for guaranteeing the minimum reliability of the designed autonomous driving system on roads.

• 시스템엔지니어링워크숍
• /
• s.4
• /
• pp.17-22
• /
• 2004

This paper present the brief generation process of system requirements or mart UAV from a development obejective. The current Snart UAV requirements deal with the restricted life cycle from development to test and verification exclusive of full life cycle beacuse of the new technology demonstration research program funded by goverments. The Smart UAV system consists of flight vechicle, avionics, communication link, payload, ground control stationand ground supporting system. In thus paper, top-down flown requirememts are intoduced how to allocate to each sub-system.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.23 no.1
• /
• pp.87-95
• /
• 2020

Delivering the weapons system requirements of the military to the acquirer is an essential activity for the development of the defense industry as well as the successful acquisition of a weapons system. In order to ensure successful delivery of requirements, the creation of a weapons system Operational Requirements Document(ORD) has been mandated since 7. 2013. However, according to the results of a study which analyzes recently-created ORD, a number of problems are occurring. For one, some items in created ORDs differ from what the ORD template requires. In addition, the overall mission area of the weapons system to be acquired and the core parts(operation performance, system performance, and core performance) of ORD are being poorly recorded. In response, this study presented a framework(focused on a creating method of overall contents and core parts) for the creation of ORDs which can solve the problems that arose during ORD creation in the past.

• Journal of the Korean Society of Systems Engineering
• /
• v.6 no.2
• /
• pp.7-14
• /
• 2010

Systematic and efficient Management of Development requirements will lead to success of project such as aircraft system development consisting of complex subsystem. For such reason, Requirements management tools have been used in most of project. In the case of FA-50 development project, requirements management tools have been used for systematic and efficient management of FA-50 Requirements. Especially FA-50 system was designed on the basis of the TA-50 configuration. Therefore, it needs traceability of requirements about functions, which have been already developed and will be newly developed. This paper was described about the implementation method of FA-50 development requirements traceability management.

• Journal of the Korea Safety Management & Science
• /
• v.10 no.1
• /
• pp.83-90
• /
• 2008

Development of human-system interfaces (HSI) supporting the interaction between human and automation-based systems, particularly safety-critical sociotechnial systems, entails a wide range of design and evaluation problems. To help HSI designers deal with these problems, many methodologies from traditional human-computer interaction, software engineering, and systems engineering have been applied; however, they have been proved inadequate to develop cognitively well engineered HSI. This paper takes a viewpoint that HSI development is itself a cognitive process consisting of various decision making and problem solving activities and then proposes a design requirements-driven process for developing HSI. High-level design problems and their corresponding design requirements for visual information display are explained to clarify the concept of design requirements. Lastly, conceptual design of software system to support the requirements-driven process and designers' knowledge management is described.

• Convergence Security Journal
• /
• v.13 no.3
• /
• pp.55-62
• /
• 2013

System engineering is critical in today's industry and requirements engineering is an important stage of overall process. Requirements Engineering is the initial step of system development activity in which the requirements from the customer are elicited and documented. This activity is very much vital for the success of the project because all of activities depends upon requirements engineering such as designing, implementation, testing, operation and maintenance. The development process begins by clarifying the need and then articulating the need as a high level solution. In order to minimize the poor requirements and to sure successful projects, Object-Oriented requirements engineering was proposed. Object-Oriented requirements engineering is an approach to encapsulating information about the process and product, as well as functionality in to a requirements object. This paper proposes using the concept of an Operations Concept Harbinger(OCH) that is the prototype of Object-Oriented requirements engineering to develop the requirements with consolidating simultaneously the opinions of various stakeholder in the customer level and trace accurately the transition from User needs to requirements. Then the customer can secure the accurate requirements to meet their needs and traceability from user needs to requirements.

• 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 the Korean Society of Systems Engineering
• /
• v.1 no.1
• /
• pp.32-38
• /
• 2005

This paper presents the brief generation process of system requirements for Smart UAV from a development objective. The current Smat UAV requirements deal with the restricted life cycle from development to test and verification exclusive of full life cycle because of the new technology demonstration research program funded by governments. The Smart UAV system consists of flight vehicle, avionics, communication link, payload, ground control station and ground supporting system. In this paper, top-down flown requirements are introduced how to allocate to each sub-system.