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

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

• International conference on construction engineering and project management
• /
• 2007.03a
• /
• 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.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.12
• /
• pp.113-120
• /
• 2011

Information system gradually increases the complexity and scale of the project, while if the project fails to occur. To analyze the causes of failure of the project a lack of understanding of your project, unclear requirements and requirements change, etc. of the software development life cycle from requirements analysis phase is to find the source of most. In this paper, a software development project needs analysis derived from the traceability between features and functionality, and development needs throughout the life cycle requirements during the ongoing change management tool was designed to allow. And among those related to the project through consultation with a sufficient consensus to build a common understanding of effective communication will discuss the features required to support.

• Journal of the Korean Society of Systems Engineering
• /
• v.6 no.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.

• Korean Journal of Construction Engineering and Management
• /
• v.21 no.6
• /
• pp.3-15
• /
• 2020

For a successful construction project, the requirements of the client should be clearly defined and this should be reflected in the project based on the expertise of each project participant throughout the entire life-cycle. Therefore, it is necessary to establish the concept of Requirements Management to systematize and manage project requirements in terms of information management. This study aims to comprehensively define the concept of requirements management in the architecture industry and to provide a methodological basis for efficiently managing design requirements information by suggesting category of requirements information type and information analysis criteria. In addition, based on the case study, the requirements information was analyzed to propose a systemization methods of requirements management for PMO' design management and information management.

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

• Convergence Security Journal
• /
• v.13 no.5
• /
• pp.97-105
• /
• 2013

It is very important the government project should be supported by enough budget for proceeding. The insufficient budget by poor budget estimating uesd to bring about discontinuing for the project. This is originally caused by inaccuracy for cost estimating about system and evaluating for system requirements on the projet initial phase. The system requirements is technical requirements that converted the user needs and is needs for communicating between stakeholder and developer and manufacturer. Also the system requirements is the primary factor to make the project cost. The cost estimating is not easy due to complication of cost factors and an aberration between cost estimating and actual cost. Specially, on the project initial phase, shortage of detail information for project make more difficult to do cost estimating. This study proposes the architecture for validating proper system requirements by using cost estimations methodology on the project initial phase and shows the computer tool for simulating the proposed architecture.

• International conference on construction engineering and project management
• /
• 2005.10a
• /
• 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
• /
• v.10 no.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.