• Journal of Information Processing Systems
• /
• v.6 no.3
• /
• pp.385-402
• /
• 2010

Most of the data warehouse (DW) requirements engineering approaches have not distinguished the early requirements engineering phase from the late requirements engineering phase. There are very few approaches seen in the literature that explicitly model the early & late requirements for a DW. In this paper, we propose an AGDI (Agent-Goal-Decision-Information) model to support the early and late requirements for the development of DWs. Here, the notion of agent refers to the stakeholders of the organization and the dependency among agents refers to the dependencies among stakeholders for fulfilling their organizational goals. The proposed AGDI model also supports three interrelated modeling activities namely, organization modeling, decision modeling and information modeling. Here, early requirements are modeled by performing organization modeling and decision modeling activities, whereas late requirements are modeled by performing information modeling activities. The proposed approach has been illustrated to capture the early and late requirements for the development of a university data warehouse exemplifying our model's ability of supporting its decisional goals by providing decisional information.

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

• Journal of the Korea Society of Computer and Information
• /
• v.24 no.7
• /
• pp.19-29
• /
• 2019

Requirements traceability is regarded as one of the important quality attributes in software requirements engineering field. If requirements traceability is guaranteed then we can trace the requirements' life throughout all the phases, from the customers' needs in the early stage of the project to requirements specification, deployment, and maintenance phase. This includes not only tracking the development artifacts that accompany the requirements, but also tracking backwards from the development artifacts to the initial customer requirements associated with them. In this paper, especially, we dealt with the traceability between functional requirements and non-functional requirements. Among many Information Retrieval (IR) techniques, we decided to utilize Latent Semantic Indexing (LSI) and Latent Dirichlet Allocation (LDA) in our research. Ultimately, we conducted an experiment on constructing traceability by using two techniques and analyzed the experiment results. And then we provided a comparative study between two IR techniques in constructing traceability between functional requirements and non-functional requirements.

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

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

The purpose of this research is to develop the technology to meet the requirements of the design content, and to build a 'Requirement Information Management Model' for the design project. The model that should be used in the early design stage will undergo the following process: First, basic requirements would be defined by extracting the design content in the form of a reusable library of space units. At the next stage, requirement information should be modified after considering unique characteristics for the project and conflict problems between function and performance.

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

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

• 제어로봇시스템학회:학술대회논문집
• /
• 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.

• Korean Journal of Computational Design and Engineering
• /
• v.20 no.2
• /
• pp.182-192
• /
• 2015

In recent years, numerous studies have attempted to extract quantity data by using Building Information Modeling (BIM). In terms of open-BIM based quantity take-off at the early design stage, only few studies were conducted in the field of cost engineering. A lack of compatibility of open BIM for information exchange is postulated as the cause. The Industry Foundation Classes (IFC) extension model has been developed to accommodate the interoperability with quantity take-off software. Improvement of open BIM for quantity take-off needs exchange requirements and model guidelines. For this purpose, the quantity data of IFC models were analyzed using BIM analysis tools. This paper also provides a proposal of requirements on open BIM based quantity take-off at the early design stage. Further this study have been develop the interface system for open BIM based quantity take-off requirements with the results on this study.

• Journal of the Korean Society of Systems Engineering
• /
• v.11 no.2
• /
• pp.61-73
• /
• 2015

The early-phase naval ship design demands requirements synthesis rather than design synthesis, which conducts engineering design for several domains on a detailed level. Requirements synthesis focuses on creating a balanced set of required operational capabilities satisfying user's needs and concept of operations. Requirements are evolved from capability based languages to function based language by statistical exploration and engineering design which are derived in the following order: concept alternative, concept baseline, initial baseline and functional baseline. The early-phase naval ship design process can be divided into three passes: concept definition, concept exploration and concept development. Main activities and outcomes in each pass are shortly presented. Concept definition is the first important step that produces a concept baseline through extensive design space exploration promptly. Design space exploration applies a statistical approach to explore design trends of existing ships and produce feasible design range corresponding to concept alternative. It further helps naval systems engineers and operational researchers by inducing useful responses to user and stakeholders' questions at a sufficient degree of confidence and success in the very early ship design. The focus of this paper is on the flow of design space exploration, and its application to a high-speed patrol craft. The views expressed in this paper are those of the authors, and do not reflect the official policy or rule of the Navy.