• Industrial Engineering and Management Systems
• /
• 제11권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.

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

• 국제학술발표논문집
• /
• The 2th International Conference on Construction Engineering and Project Management
• /
• pp.635-641
• /
• 2007

The construction starts its business by receiving the order from client and owner. The client presents requirements and related information so that the desired result can come out while the designer and the builder express and implement the building according to set objectives and goals of project based on information on project environment and presented requirements. Because the construction project makes decisions on such objectives at its early stage and previous stage becomes the situation for decision making of next stage as the computation to implement decisions get performed. Accordingly, this study has mentioned necessity of requirement analysis and systematization of construction project, analyzed the work of construction's early stage and resented a plan for objective of construction project requirement definition model in which requirements engineering has been applied and using it while making decisions on designing.

• 한국컴퓨터정보학회논문지
• /
• 제16권12호
• /
• pp.113-120
• /
• 2011

정보시스템 구축 프로젝트의 복잡성과 규모가 점차 커지면서, 프로젝트가 실패하는 경우가 발생한다. 프로젝트의 실패의 원인을 분석해보면 사용자의 프로젝트 이해 부족, 불명확한 요구사항 및 요구사항변경 등으로 소프트웨어 개발 생명주기 중 요구사항 분석 단계에서 대부분의 원인을 찾을 수 있다. 본 논문은 소프트웨어 개발 프로젝트에서 요구분석을 통해 도출된 기능과 변경요구 기능간의 추적 등 개발 생명주기 전체 기간 동안 지속적인 요구사항 변경 관리가 가능하게 하는 도구를 설계하였다. 그리고 프로젝트 관련자들 사이에서 충분한 합의와 협의를 통해 공통의 이해를 구축하는 효과적인 의사소통을 지원하는데 필요한 기능에 대해 논의한다.

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

• 한국건설관리학회논문집
• /
• 제21권6호
• /
• pp.3-15
• /
• 2020

성공적 건설 프로젝트의 수행을 위해 발주자의 요구사항을 명확히 정의하고, 전 생애주기를 포괄하여 각 사업 참여자의 전문기술을 통해 이를 프로젝트에 반영해야 한다. 이에 프로젝트 요건을 정보관리 차원에서 체계화 관리하기 위한 요건관리(Requirements Management)의 개념 정립이 요구된다. 본 연구에서는 건축분야 요건관리의 개념을 포괄적으로 정의하고, 요건정보 유형과 정보 분석기준을 제시하여 설계 요건정보를 효율적으로 관리하기 위한 방법론적 기반을 마련하고자 하였다. 또한 이를 사례연구에 적용하여 요건정보를 도출 및 분석하였으며, 발주자 설계관리 및 지식관리 관점에서 요건관리 시스템화 방향을 제안하였다.

• 한국철도학회:학술대회논문집
• /
• 한국철도학회 2008년도 춘계학술대회 논문집
• /
• 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".

• 융합보안논문지
• /
• 제13권5호
• /
• pp.97-105
• /
• 2013

국가에서 추진하는 모든 프로젝트는 예산이라는 변수에 영향이 크다. 정확한 소요예산 판단불가로 프로젝트 추진 중에 추가적인 예산소요가 발생하여 사업의 중단 혹은 재검토 사례가 빈번히 발생하고 있다. 이는 프로젝트 소요제기단계 및 이를 획득하기 위한 선행연구단계에 제시된 시스템요구사항의 평가와 소요예산의 부정확성으로 기인한다고 평가된다. 시스템요구사항은 사용자가 작성하는 사용자 요구사항과 구별하여 사용자 요구사항을 바탕으로 획득조직에서 시스템의 기술적 요구사항으로 전환하는 것을 말하며 획득조직과 개발자 혹은 제작자 사이에 의사소통을 위한 것이다. 시스템 요구사항 수준은 프로젝트 규모를 결정하는데 중요한 요소로, 시스템요구사항에 대한 비용측면의 적정성 확인은 필수적이다. 그러나 프로젝트 비용요소가 복잡하고 각 요소별로 기준이 상이하여 비용추정이 쉽지 않고 추정된 비용의 오차율도 커서 활용에 어려움이 있었으며, 특히 시스템요구사항을 도출하는 프로젝트 초기단계에는 프로젝트와 관련된 세부자료의 부족으로 비용추정에 어려움이 있었다. 본 연구에서는 요구공학과 비용추정방법에 대한 이론적인 근거를 바탕으로 시스템요구사항 도출 후 비용추정방법을 활용하여 적정성을 검증하고 대안을 비교 후 최적안을 선정하는 아키텍처를 솔루션으로 제시하였고, 이를 위하여 활용 가능한 모수비용추정방법(Parametric Cost Estimating)를 토대로한 비용추정 전산도구인 SEER Cost-IQ를 소개하였다.

• 국제학술발표논문집
• /
• The 1th International Conference on Construction Engineering and Project Management
• /
• pp.774-779
• /
• 2005

Client requirements is a concept with increasing interest in relation to several outcomes of companies, and in particular, in the event of apartment project that takes large share in the domestic construction industry, diverse angle of survey is performed to discover the client requirements and reflect them to the project to improve the quality. For this purpose, it is required to learn the client requirements and apply it in the apartment project, and the QFD (Quality Function Deployment) linked ROQ (Return On Quality) is a technique used in the manufacturing that surveys the client requirements to improve the customer satisfaction, and apply it to the quality improvement program to improve the profitability in this process. In this study, through the application of the ROQ process, the plan to improve the apartment quality management is presented. For this purpose, the consumer interview survey, FGI (focus group interview) survey and the client requirements are analyzed, and thereafter, through the interview with the specialist, the quality improvement program that enables the application to the product development of new apartment product is established. Through this process, the new apartment quality management improvement plan is presented.

• International journal of advanced smart convergence
• /
• 제10권2호
• /
• pp.130-137
• /
• 2021

In the current software project, it is still very difficult to extract and define clear requirements in the requirement engineering. Informal requirements documents based on natural language can be interpreted in different meanings depending on the degree of understanding or maturity level of the requirements analyst. Also, Furthermore, as the project progresses, requirements continue to change from the customer. This change in requirements is a catastrophic failure from a management perspective in software projects. In the situation of frequent requirements changes, a current issue of requirements engineering area is how to make clear requirements with unclear and ambigousrequirements. To solve this problem, we propose to extract and redefine clear requirements by incorporating Design Thinking methodologies into requirements engineering. We expect to have higher possibilities to improve software quality by redefining requirements that are ambiously and unclearly defined.