• Title/Summary/Keyword: Requirements Process

Search Result 2,714, Processing Time 0.041 seconds

A Requirements Management Process to improve the Requirements Management of Development Methodologies (개발방법론의 요구사항 관리를 개선하기 위한 요구사항 관리 프로세스)

  • Sin, Jong-Cheol;Gu, Yeon-Seol
    • The KIPS Transactions:PartD
    • /
    • v.9D no.1
    • /
    • pp.81-90
    • /
    • 2002
  • More than 50% of defects and errors in the software development projects are related to the requirements[14]. But the development methodologies can not provide enough supports to the requirements management and changes. In the real world, the requirements keep changing as the requirements at the early development phase are usually incomplete, the developer′s understanding of the problem will be constantly changed during the software process, and new requirements may emerge with the organizational and environmental changes. In this paper, a requirements management process that can be integrated into the development methodologies is proposed to extend the requirements management over the whole development life-cycle and to support the requirements changes at the design/implementation/test phases. To evaluate the proposed process, it was compared to the existing requirements managements processes and models, and examined through a integration test with a widely used development methodology "MaRMI" to show the expected improvements at each development phase.

A Software Development Process Supporting Non-Functional Requirements (비기능적 요구사항을 지원하는 소프트웨어 개발 프로세스)

  • Jung, Hyo-Taeg;Joo, Sang-Hyun
    • Journal of The Institute of Information and Telecommunication Facilities Engineering
    • /
    • v.9 no.1
    • /
    • pp.13-18
    • /
    • 2010
  • As the importance of non-functional requirements has increased, many researchers have become interested in the software development process for non-functional requirements including the notation, modeling, and assessment of non-functional requirements. However, the characteristics of non-functional requirements are so sophisticated and there are many topics which have not been solved until now. In order to address one of the unsolved problems, we propose a systematic software development process to support the management of non-functional requirements. The process consists of six steps, each of which is composed of detailed activities. Using the proposed process, the non-functional requirements can be managed and modeled more effectively and systematically than previous ones.

  • PDF

Framework for Determining Requirements in the Weapons systems Acquisition Process (무기 획득과정에서의 요구사항 결정 프레임워크)

  • Yun, Ha-Neul;Ok, Young-Ho;Wang, Ji-Nam
    • Journal of the Korean Society of Systems Engineering
    • /
    • v.8 no.1
    • /
    • pp.77-82
    • /
    • 2012
  • In Weapons acquisition process, if the requirements are not clear, it leads to confusion and conflict in business. In the development of next-generation weapons, to define and derive requirements has to start from decision of operational concept. It is difficult task and has many uncertainties. This paper has goal about development of knowledge acquisition process that derive military operational scenario-based requirements acquisition process and framework that classify and save the derived requirements for next project. That framework can generate new class and category, also suggest that verification of requirements. It help to derive and manage the requirements, and make it easy to grasp the requirements. Accordingly, it can help make military requirement plan and weapon acquisition process.

Communication-Centered Project Management for Requirements Definition Phase

  • Ishii, Nobuaki;Muraki, Masaaki
    • Industrial Engineering and Management Systems
    • /
    • v.11 no.1
    • /
    • pp.39-47
    • /
    • 2012
  • Requirements definition, which determines a project baseline, has a strong impact on the success of a project. However, since in-depth requirements are gradually revealed through the requirements definition process, the requirements definition is not a straight forward process and often falls into disorder. Thus project management standpoints are critical for the success of the requirements definition. In this paper, we present a framework and mechanisms of communication-centered project management, which controls the requirements definition process based on the situation of communication-oriented activities among stakeholders. In addition, we present a communication-centered project plan with a planning method. The project plan, which represents a time schedule of requirements definition activities, is made by a simulation-optimization algorithm using a stakeholder matrix showing the relations of requirements domains and relevant stakeholders. The effectiveness and the significance of communication-centered project management at the requirements definition phase are demonstrated by numerical examples.

Design Requirements-Driven Process for Developing Human-System Interfaces (설계 요건 중심의 인간-시스템 인터페이스 개발 프로세스)

  • Ham, Dong-Han
    • 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.

An Approach to Managing Requirements Change Systematically in Software Product Lines (소프트웨어 프로덕트 라인에서 체계적인 요구사항 변경 관리 방법)

  • Park, Ji-Hyeon;Moon, Mi-Kyeong;Yeom, Keun-Hyuk
    • Journal of KIISE:Software and Applications
    • /
    • v.32 no.12
    • /
    • pp.1164-1177
    • /
    • 2005
  • As the software development process becomes complicated, software requirements become complicated, too. Many efforts are needed in requirements management. It is impossible to define all requirements of software at first, and the development environment changes as project is gone. As the cost of requirements change management is much more than development cost, the changes should be controled immediately through systematic change management. In this paper, I suggest a method to manage requirements change systematically based on the change management process in software product lines. The requirements change at the application engineering process is analyzed and managed using the domain engineering process because the application requirements are customized from the domain requirements in software product lines. Such the consistent change management helps to make decisions about changes by change impact analysis and alternative solution design. Through this method, the potential change costs can be saved because same change requests are not repeated by controlling the change requests completely.

On the Construction of Requirements DB to Improve the Work Environment of Locomotive Cabs (철도차량 운전실의 작업환경 개선을 위한 요구사항 DB 구축에 관한 연구)

  • Sim, Sang-Hyun;Lee, Jae-Chon;Park, Chan-Woo
    • Journal of the Korea Safety Management & Science
    • /
    • v.13 no.4
    • /
    • pp.71-79
    • /
    • 2011
  • The work environment of locomotive cabs has long been an important issue in the design of railload systems since it is quite critical in terms of system's operational safety. It is getting more attention as the running speed of the trains goes up these days. To this end, this paper describes how to systematically construct a DB for the requirements set in the course of the improvement process for the aforementioned cab work environment. As a solution approach, we have adopted the requirement architecture concept to cover the whole activities required to do such as in requirements generation, DB construction, change management, and traceability management. Specifically, based on the requirement architecture framework a requirement process to collect requirements for improvement is discussed, and the guide lines are suggested for verification and validation of the developed requirements. In addition, a base schema and requirements templates are developed, which will be used in generating requirements and constructing a DB. Finally, it is demonstrated how the requirements DB for locomotive cabs can be constructed using a computer-aided tool in an integrated fashion.

Practical Requirements and Verification Management for Requirements-based Development Process in Space Launch Vehicle Development Project (요구조건 기준의 개발 수행을 위한 우주발사체 개발사업의 실제적인 요구조건-검증 관리 체계)

  • Dong Hyun Cho;Jun Hyouk Jang;Il Sang Yoo
    • 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.

A SysML Based Approach for identifying and specifying Non-Functional Requirements (SysML을 이용한 비기능 요구사항 정의 방법)

  • Kim, Jeen Wook
    • 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.

  • PDF

Process of Thinking on the Form in Product Design (제품디자인의 형용사고과정)

  • 조종호
    • Archives of design research
    • /
    • v.4 no.1
    • /
    • pp.31-37
    • /
    • 1991
  • Process of thinking on the form in product design includes the process in which unclear requirements are transformed into defined concepts, and the process in which the design as a form conforming to the concepts in conc1uded.(The former is called fconceptualizationJ which deals with abstract matters, and the latter "manipulation of the formJ which deals with more embodied matters) In conceptualization process the operation which transform the diverse requirements in the initial phase of de\ulcornersign to related linguistic expressions or to an image that directly suggests the form is executed. In the process of manipulation of the form the transformation to design as the description of relationships between the formal elements of the design solution resulted from the transformed requirements. It is the job of selecting the most suitable formal elements, balancing the relationships between them, out 01 the possibilities that reside in the individual attributes of formal elements, and finally leading to the design as the end solution. This writing focuses down to the wilfulness and ambiguity of design, and the diversity of design solution after the requirements, formal elements, and the process of relating the formal attributes to each other is built up the two phases.ases.

  • PDF