• 한국IT서비스학회지
• /
• 제18권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 Information Processing Systems
• /
• 제6권3호
• /
• pp.385-402
• /
• 2010

Most of the data warehouse (DW) requirements engineering approaches have not distinguished the early requirements engineering phase from the late requirements engineering phase. There are very few approaches seen in the literature that explicitly model the early & late requirements for a DW. In this paper, we propose an AGDI (Agent-Goal-Decision-Information) model to support the early and late requirements for the development of DWs. Here, the notion of agent refers to the stakeholders of the organization and the dependency among agents refers to the dependencies among stakeholders for fulfilling their organizational goals. The proposed AGDI model also supports three interrelated modeling activities namely, organization modeling, decision modeling and information modeling. Here, early requirements are modeled by performing organization modeling and decision modeling activities, whereas late requirements are modeled by performing information modeling activities. The proposed approach has been illustrated to capture the early and late requirements for the development of a university data warehouse exemplifying our model's ability of supporting its decisional goals by providing decisional information.

• 한국군사과학기술학회지
• /
• 제13권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.

• 한국멀티미디어학회논문지
• /
• 제6권4호
• /
• pp.723-735
• /
• 2003

This research focuses ell an approach for the building of a requirements model for the development of large-scale information systems. It will suggest a set of requirements engineering processes as a procedure of the implementation for building the requirements model. It will also emphasise the evaluation requirements model aimed to refine and complete the requirements model by the different user groups as a cross reference. This paper provides an advanced user-construction requirements within the Event Flow Diagram as a set of requirements engineering process.

• 대한안전경영과학회지
• /
• 제25권3호
• /
• pp.9-15
• /
• 2023

As the first step of risk management, risk identification is inevitable to understand the degree of work safety. However, the safety requirements can be divided in necessary factors and additional factors. Thus, we propose a safety requirements assessment model using Kano model derived from Herzberg's two-factor theory, classifying safety requirements into ideal elements and must-be elements. The Kano model is usually applied to evaluate customer satisfaction divided into three major requirements in the fields of product development and marketing: attractive, must-be, and one-dimensional requirements. Among them, attractive requirement and must-be requirement are matched with ideal element and must-be element for safety requirement classification, respectively. The ideal element is defined as preventive safety elements to make systems more safe and the must-be element is referred to as fatal elements to be essentially eliminated in systems. Also, coefficients of safety measurement and safety prevention are developed to classify different class of safety requirements. The positioning map is finally visualized in terms of both coefficients to compare the different features. Consequently, the proposed model enables safety managers to make a decision between safety measurement and prevention.

• Journal of information and communication convergence engineering
• /
• 제10권3호
• /
• pp.284-294
• /
• 2012

The quality of requirements is one of the key factors in the success of a project. One of the studies on successful projects is the reuse of requirements. However, the rate of failed projects is about 70%, and these projects often fail because of improper requirements. The current techniques for software reuse may not perform requirement engineering appropriately or develop requirements having good characteristics. In order to improve this situation, we propose a model for reusing requirements. We expect that our model will contribute toward increasing project productivity using requirement reuse in existing projects, and reusing requirements that have good quality.

• International journal of advanced smart convergence
• /
• 제9권3호
• /
• pp.227-231
• /
• 2020

Recently, the importance of user experience (UX) has been rapidly increasing. Its utilization is emphasized for development of systems, products, and services. User experience is widely used across industries including services, products, processes, society, and culture. Therefore, if it is unsatisfactory, it is likely to have a direct negative impact on the corresponding system, product, or service. The failure to analyze user experience causes significant damage to the project, which may lead to its failure or redevelopment; it is hence necessary to prioritize the verification of UX in the earliest stages of development. The requirements development stage, which is a preceding stage, is an appropriate stage for the verification of user experience because the identification of user needs is completed and prototypes can be implemented. In this paper, we proposed a systematic requirements development stage; it adds user experience verification activities to the requirements development stage, using the Honeycomb model, which is a widely used tool for verifying the overall UX. User experience verification was added to the existing requirements development activities, which consisted of three steps: model definition and requirements placement, discussions between external and internal stakeholders, and review by internal stakeholders. By easily validating the user experience through this systematic requirements development stage, we expect to minimize the damage to the project due to the failure of the user experience analysis and increase the possibility of success.

• 시스템엔지니어링학술지
• /
• 제2권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.

• 한국철도학회:학술대회논문집
• /
• 한국철도학회 2001년도 추계학술대회 논문집
• /
• pp.35.1-40
• /
• 2001

This study is on the behavior analysis which can define and verify a system requirement through a behavior diagram for High speed rail system. The model considered in this study is limited to the preconditioning control of the control system specification for HSRS. To build an executable model, requirements should be decomposed first into leaf node requirements. The behavior model is composed of input, output, and functions which are linked with leaf node requirements. It is important that a single requirement must specify a single Auction. Using the developed executable model and the traceability between requirements and functions, this study found out a lot of static and dynamic inconsistency, missed and derived requirements. This is to develop and executable behavior model to do functional analysis and be able to verify the integrity of a specification.

• Nuclear Engineering and Technology
• /
• 제51권2호
• /
• pp.463-478
• /
• 2019

The most important non-functional requirements for dependability of any Embedded Real-Time Safety Systems are safety, availability and reliability requirements. System architecture plays the primary role in achieving these requirements. Compliance with these non-functional requirements should be ensured early in the development cycle with appropriate considerations during architectural design. In this paper, we present an application of system architecture modeling for quantitative assessment of system dependability. We use probabilistic model checker (PRISM), for dependability analysis of the DTMC model derived from system architecture model. In general, the model checking techniques do not scale well for analyzing large systems, because of prohibitively large state space. It limits the use of model checking techniques in analyzing the systems of practical interest. We propose abstraction based compositional analysis methodology to circumvent this limitation. The effectiveness of the proposed methodology has been demonstrated using the case study involving the dependability analysis of safety system of a large Pressurized Water Reactor (PWR).