• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.58-68
• /
• 2006

Requirements are very important to model software architecture. Requirements are divided into functional and quality requirements. Functional requirements are pinpointed subsystems and components. Quality requirements affect the structure of architecture. Thus requirements are essential to understand clearly in order to design software architecture. This paper focuses on a quantitative approach to requirements analysis for modeling architectures. In our proposal, functional requirements are quantified through calculating each priority of components. Quality requirements are quantified through calculating the correlation degree between components and quality attributes. The proposed method is implemented by DRAMA (Domain Requirements Analysis for Modeling Architectures), which fully supports our approach and are developed in Java environments. Our proposal is validated to apply some industrial examples.

• Journal of KIISE:Software and Applications
• /
• v.33 no.8
• /
• pp.655-667
• /
• 2006

This paper proposes a method for counting function point using goal and scenario based requirements. Function Point is a software sizing method and widely used as a basis to estimate software development cost. Requirements elicitation and analysis should be performed before function point analysis but function point analysis method doesn't deal with requirements elicitation and analysis. For that reason, Function point extraction method from existing requirements method is needed and if the requirements method has advantage for traceability and elicitation, it is suitable for managing cost. Goal and scenario method is widely used as requirements elicitation and analysis. It has also good traceability. Therefore, this paper discusses a method for extracting function point from requirements text gathered using the goal and scenario based requirements elicitation technique. The proposed method aims to establish and maintain traceability between function point and requirements text. Text based function point extraction guidance rules have been developed. The proposed methodology has been applied to Order Processing System development.

• Journal of the Korean Society of Systems Engineering
• /
• v.1 no.2
• /
• pp.43-48
• /
• 2005

This paper describes the results of applying States and Modes Analysis, one of the requirements analysis techniques, to the development requirements of flight control software for Smart UAV. State/mode table enabled us to investigate various operation and design concepts, and as a result essential requirements for flight control software were established without omitting necessary requirements. Through the use of scenario-specific state transition diagrams, dynamic behaviours and control/response interfaces between each state and mode could been clearly identified, which made it possible to establish requirements related to dynamic behaviours of states and modes which are essential to the design of flight control software.

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

• The Journal of Society for e-Business Studies
• /
• v.12 no.4
• /
• pp.1-15
• /
• 2007

Traceability links are logical links between individual requirements and other system elements such as architecture descriptions, source code, and test cases. These are useful for requirements change impact analysis, requirements conflict analysis, and requirements consistency checking. However, establishing and maintaining traceability links places a big burden since complex systems have especially yield an enormous number of various artifacts. We propose a feature-oriented requirements tracing method to manage requirements with cost benefit analysis, including value consideration and intermediate catalysis using features. Our approach offers two contributions to the study of requirements tracing: (1)We introduce feature modeling as intermediate catalysis to generate traceability links between user requirements and implementation artifacts. (2)We provide value consideration with cost and efforts to identify traceability links based on prioritized requirements, thus assigning a granularity level to each feature. In this paper, we especially present the results of a case study which is carried out in Apartment Ubiquitous Platform to integrate and connect home services in an apartment complex in details.

• 제어로봇시스템학회:학술대회논문집
• /
• 2000.10a
• /
• pp.419-419
• /
• 2000

This paper describes a requirement analysis for automotive engine design using a computer aided systems engineering tool RDD-100. Because the engine is a complex system with many subsystems, there are many needs of stakeholder throughout the life-cycle of the engine. The originating requirements have been derived from the needs and decomposed into leaf-node requirements with the tool. Many requirement errors have been detected during the decomposition process and resolved by modifying the requirements. Inconsistency problems have been also resolved with the tool, Analysis of engine requirements using RDD-100 brings clarity to engine design early in the development process.

• 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 Information Technology Services
• /
• v.8 no.1
• /
• pp.113-124
• /
• 2009

Value-based requirements engineering process, called The ViRE(Value-Innovative Requirement Engineering) was suggested to create an uncontested market using ERRC(Eliminate, Reduce, Raise, Create) requirements analysis. But ViRE did not provides a quantitative data analysis method for ERRC decision so as to make objective decisions for customers. In this paper, to solve this problem, we suggest a quantitative ERRC analysis method by estimating requirements cost. Our method defines user requirements and decides their weight. Then, it makes quality level table for all the identified requirements and function modules and estimate implementation cost based on their quality levels. Finally, assess each requirement's impact and then evaluate ERRC value. We could get the more objective ERRC values by evaluate the requirement weight. functional module weight, and implementation cost. And we proved the efficiency of our model by a case study, smart student ID system.

• Journal of the Korea Safety Management & Science
• /
• v.13 no.4
• /
• pp.9-16
• /
• 2011

Modern systems become more complex and the demand for systems safety goes up sharply. Thus, the proper handling of the safety requirements in the systems design is getting greatly increased attention these days. Hazard analysis has been one of the active areas of research in connection with systems safety. In this paper, we study a subject on how the hazard analysis results can be incorporated in the systems design. To this end we set up a goal on how to systematically generate safety requirements that should reflect hazard analysis results and be implemented in the systems design and development. To do so, we first review the process for systems design and suggest the associated Model. Then the process and results of hazard analysis are analyzed and Modeled particularly with emphasis on the safety data. The resulting data Model incorporating both the hazard analysis and system life cycle is used in the generation of safety requirements. Based on the developed data Model, the generation of the requirements, the construction of requirements DB, and the change management later on is demonstrated through the use of a computer-aided software tool.

• Journal of the Korean Society for Aviation and Aeronautics
• /
• v.16 no.4
• /
• pp.41-48
• /
• 2008

Functional analysis of air transport mission is conducted to establish the performance requirements of the commercial transport designs. The analysis process begins by making a top-down analysis to the aircraft system level mission functions. Correctly interpreting the top-level performance requirements is the first step in designing and building an aircraft system. Each function and sub-function is allocated and examined to the aircraft level and flight operations phase to optimize the system performance and design requirements, such that these lower-level requirements can be traced back to the top-level requirements they are designed to fulfill. Special attention is given to making sure all interfaces, both internal and external, are addressed. The results are also in good resources of functional hazard assessment involved in certification processes.