• Journal of Aerospace System Engineering
• /
• v.7 no.2
• /
• pp.29-34
• /
• 2013

Safety requirements for aircraft and system functions include minimum performance constraints for both availability and integrity of the function. These safety requirements should be determined by conducting a safety assessment. The depths and contents of aircraft system safety assessment vary depending on factors such as the complexity of the system, how critical the system is to flight safety, what volume of experience is available on the type of system and the novelty and complexity of the technologies being used. Requirements that are defined to prevent failure conditions or to provide safety related functions should be uniquely identified and traceable through the levels of development. This will ensure visibility of the safety requirements at the software and electronic hardware design level. This paper has prepared to study on promoting the efficiency of establishing hierarchical safety requirements from aircraft level function to item level through system safety processes.

• Journal of Information Technology Services
• /
• v.18 no.2
• /
• pp.37-54
• /
• 2019

The purpose of this study is to present an evaluation model to measure the clarification level of stakeholder requirements of public sector software projects in the Republic of Korea. We tried to grasp the quality of proposal request through evaluation model. It also examines the impact of the level of stakeholder requirements on the level of system requirements. To do this, we analyzed existing research models and related standards related to business requirements and stakeholder requirements, and constructed evaluation models for the system operation concept documents in the ISO/IEC/IEEE 29148. The system operation concept document is a document prepared by organizing the requirements of stakeholders in the organization and sharing the intention of the organization. The evaluation model proposed in this study focuses on evaluating whether the contents related to the system operation concept are faithfully written in the request for proposal. The evaluation items consisted of three items: 'organization status', 'desired changes', and 'operational constraints'. The sample extracted 217 RFPs in the national procurement system. As a result of the analysis, the evaluation model proved to be valid and the internal consistency was maintained. The level of system operation concept was very low, and it was also found to affect the quality of system requirements. It is more important to clearly write stakeholders' requirements than the functional requirements. we propose a news classification methods for sentiment analysis that is effective for bankruptcy prediction model.

• Journal of the Korean Society of Systems Engineering
• /
• v.19 no.1
• /
• pp.56-63
• /
• 2023

For the success of system development, it is necessary to systematically manage the requirements that are the basis of system development and its verification results. In order to follow the principles of SE(Systems Engineering)-based V&V(Verification&Validation) process, requirements can be managed by securing the requirements and their establishments, design compliances, and verification compliances according to the system development lifecycle. Especially, in a large-complex system research and development project, such as a space launch vehicle development project, many participants establish, verify, and validate numerous requirements together during the project. Therefore, logical and systematic requirements management, including guarantee of data integrity, change history, and traceability, is very important for multiple participants to utilize numerous requirements together without errors. This paper introduces the practical requirements and verification management for the requirements-based development process in the space launch vehicle development project.

• Journal of Astronomy and Space Sciences
• /
• v.26 no.4
• /
• pp.643-650
• /
• 2009

Korea Astronomy and Space Science Institute (KASI) has been developing one mobile and one stationary SLR system since 2008 named as ARGO-M and ARGO-F, respectively. KASI finished the step of deriving the system requirements of ARGO. The requirements include definitions and scopes of various software and hardware components which are necessary for developing the ARGO-M operation system. And the requirements define function, performance, and interface requirements. The operation system consisting of ARGO-M site, ARGO-F site, and Remote Operation Center (ROC) inside KASI is designed for remote access and the automatic tracking and control system which are the main operation concept of ARGO system. To accomplish remote operation, we are considering remote access to ARGO-F and ARGO-M from ROC. The mobile-phone service allows us to access the ARGO-F remotely and to control the system in an emergency. To implement fully automatic tracking and control function in ARGO-F, we have investigated and described the requirements about the automatic aircraft detection system and the various meteorological sensors. This paper addresses the requirements of ARGO Operation System.

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

Requirements engineering is an important phase in a system's life cycle. It is important to perform it correctly. The increasing complexity of systems makes requirements engineering activities more difficult. Non-functional requirements are drivers to emerge how much emergent system properties to aim for success. All functional requirements may be satifsfied, but if the level of desired non-functional requirements are overlooked, the system development will fail. There is growing awareness of the importance of defining non-functional requirements early in the process among the requirements engineering (RE) community. This paper propses a SysML based approach for non-functional requirements to identify and specify very early in the process or requirements engineering.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.13 no.5
• /
• pp.801-807
• /
• 2010

Requirements management is one of the most essential activities of systems engineering in developing successful weapon systems. Particularly it is very important to consistently manage the traceability among the user requirements, the system requirements, the development specifications and the testing plans throughout the entire life cycle of the weapon system. However, the most part of requirements-related activities has centered around the functional and performance requirements but the integrated logistics support(ILS) requirement has not properly been managed. In this regard, a special attention is needed to develop and manage the ILS requirements. To do so, the ANSI/EIA-632 standard can be referred as a starting point since the ILS requirements of the weapon system under development are specified by the enabling products whereas the functional and performance requirements are covered by the end product requirements. Specifically, we first review and model several cases of previous weapon systems development, which reveals the problem of interest. Then, under the framework of ANSI/EIA-632, we study a hierarchical model for effectively managing ILS requirements by analyzing the features of ILS requirements. Finally, the value of the proposed model is discussed through the case study of electronic warfare equipment.

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.189-198
• /
• 2006

This study assumed that the best road guidance system for the vision impaired is a robot and analyzed and verified the requirements of road guidance system. In order to do so, the characteristics and inconveniences of the vision impaired as passengers and pedestrians were examined and their reactions to warnings and dangerous situations were analyzed. Users' needs and robots' functional requirements were applied to analyze the requirements of road guidance system. To verify whether the proposed requirements would be applied to robots effectively, a service scenario was used.

• Proceedings of the KSR Conference
• /
• 2008.06a
• /
• pp.1083-1088
• /
• 2008

The first task for the development of a train system is to define the system and to determine its requirements. Reliability target is one of the requirements defined in the system requirements. In railway applications it is advised to follow the procedures given in IEC 62278 to fulfill reliability requirements. The reliability requirements are derived from the customer's needs. The way in which the system requirements reflect the customer's needs is strongly dependent on the characteristics of the product. In general the customer of commercial trains presents the system requirements from their needs. However, the relation between the customer and supplier is equivocal for a project to development a prototype train, and the reliability program should be different from that of an usual commercial project. This paper deals with the reliability management and assessment plan carried out for the on-going "Next generation high-speed train development project".

• Journal of the Korean Society of Systems Engineering
• /
• v.2 no.2
• /
• pp.33-38
• /
• 2006

It is well known that efficient management and thorough implementation of stakeholder requirements is vital for a successful development of a large-scale and complex system. Equally important is to make sure that all the requirements be correctly realized in the developed system. For the purpose, verification requirements are derived with traceability from the system requirements. This paper discusses a step by step process for constructing the requirements verification model which includes : 1) the schema modeling both requirements and their traceability; 2) the template documenting the verification requirements; 3) the verification model constructed from the schema; and 4) the test and evaluation plan that can be printed automatically.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.11S
• /
• pp.3299-3308
• /
• 1999

One of the most important prerequisites for a successful software process is the collaboration and software requirements negotiation of all stakeholders in the software development process. Remote users using computer networks can negotiate software requirements by computer supported system, and can share their informations. The goal of software requirements negotiation system is an integration of all win conditions and an agreement after resolution of conflicts. The existing systems need an exclusive system and must be dependent on specific platform and network. Users must have the knowledge of all stakeholder's status and use homogeneous collaborating applications. This paper presents the Web-based software requirements negotiation system for the purpose of resolution of the existing systems' problems. The Web-based software requirements negotiation system can be driven by WinWin Spiral model, and it is based on hybrid execution method. The proposed system is validated and tested on heterogeneous environments.