• International conference on construction engineering and project management
• /
• 2013.01a
• /
• pp.502-506
• /
• 2013

The cash flow forecasting is normally done by contractors in construction industry at early stages of the project for contractual decisions. The decision making in such situations involve uncertainty about future cash flows and assessment of working capital requirements gains more importance in projects constrained by cash. The traditional approach to assess the working capital requirements is deterministic in and neglects the uncertainty. This paper presents an alternate approach to assessment of working capital requirements for contractor based on fuzzy set theory by considering the uncertainty and ambiguity involved at payment periods. Statistical methods are used to deal with the uncertainty for working capital curves. Membership functions of the fuzzy sets are developed based on these statistical measures. Advantage of fuzzy peak working capital requirements is demonstrated using peak working capital requirements curves. Fuzzy peak working capital requirements curves are compared with deterministic curves and the results are analyzed. Fuzzy weighted average methodology is proposed for the assessment of peak working capital requirements.

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

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.3
• /
• pp.99-109
• /
• 2021

In recent machine learning studies, in order to consider the quality and completeness of data, derivation of non-functional requirements for data has been proposed from the viewpoint of requirements engineering. In particular, requirements engineers have defined data requirements in machine learning. In this study, data requirements were derived at the data acquisition (DAQ) stage, where data is collected and stored before data preprocessing. Through this, it is possible to express the requirements of all data required in the existing DAQ system, the presence of tasks (functions) satisfying them, and the relationship between the requirements and functions. In addition, it is possible to elicit requirements and to define the relationship, so that a software design document can be produced, and a systematic approach and direction can be established in terms of software design and maintenance. This research using existing DAQ system cases, scenarios and use cases for requirements engineering approach are created, and data requirements for each case are extracted based on them, and the relationship between requirements, functions, and goals is illustrated through goal modeling. Through the research results, it was possible to extract the non-functional requirements of the system, especially the data requirements, from the DAQ system using requirements engineering.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.5 no.10
• /
• pp.1733-1750
• /
• 2011

In the early stages of a software project, it is critical to understand the needs of the customers and elicit their customer requirements. Various requirements elicitation methods have been proposed. However, existing methods still have the limitations such as a limited number of target customers, limited expression of customers' opinions, and difficulty in collecting the customers' opinions continuously. A novel method for eliciting customer requirements is proposed by utilizing a social network service (SNS), which is a shared source of raw information of the customers' needs and opinions. The proposed method is validated to show its effectiveness in overcoming the limitations of existing methods.

• Journal of Engineering Education Research
• /
• v.14 no.4
• /
• pp.62-68
• /
• 2011

Many engineering schools in Korea implement ABEEK programs. One of the core parts of ABEEK is accreditation criterion 2, the program outcomes and their appraisal. This paper tries to discuss the program outcomes and to study the impact of applying the program outcomes to one of the graduation requirements. We show simple survey results for implementing ABEEK programs concerning the program outcomes and their relation to graduation requirements. If the program outcomes are used as one of the graduation requirements, some graduates may satisfy the average grade point for graduation requirements but can not meet the program outcome criteria satisfied by other than regular classes. In this case, the graduate may have trouble to try to meet the program outcome criteria, since he may not be able to stay in school without taking classes. The problems of setting the levels of program outcomes as graduation requirements, non classwork related program outcomes, and work burden to professors should be also prudently reviewed for successful ABEEK implementation.

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

• 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 Korea Multimedia Society
• /
• v.6 no.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.

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

• Journal of the Korean Society of Systems Engineering
• /
• v.12 no.1
• /
• pp.1-5
• /
• 2016

Most of systems engineers make a traceability matrix and attach it to their technical documents as a result of systems engineering activities. I have been working in the field of systems engineering for many years and have been watching traceability matrices created by systems engineers or developers from various companies. I have been thinking that some of them are not suitable in terms of purposes of traceability matrix. In this paper, I would like to suggest a right template for the traceability matrix in conformance to traceability purposes. The key is that traceability matrix should be created from higher level of requirements to current level of requirements.