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

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

• Industrial Engineering and Management Systems
• /
• v.11 no.1
• /
• pp.70-81
• /
• 2012

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

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

• 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.2 no.1
• /
• pp.11-17
• /
• 2006

According to the change of customer needs, integration with other systems, and the advent of new technology, it is inevitable for the existing system requirements to be requested to redesign. However, there are actually no methodologies and processes to be able to reorganize the existing requirements or integrate a number of requirements different from each other. The traditional requirements processes do not work when solving such problems. Thus, since the existing approaches to develop requirements are not helpful, many traditional requirement engineering processes can not help falling in Red Ocean. In this paper, in order to solve such the problems, we propose a novel requirements engineering process applying Blue ocean strategy which is used to open a non-competition market not discovered yet. Blue Ocean approach is a novel effective method to elicit and build up new requirements from customers. In order to accomplish the strategy, this paper presents a framework and processes to discover new perspectives and analyze the corresponding requirements. In addition, some pieces of case study are presented to introduce how our approach is applied to practical system developments and the evaluation analysis for how valid it is.

• Convergence Security Journal
• /
• v.13 no.3
• /
• pp.55-62
• /
• 2013

System engineering is critical in today's industry and requirements engineering is an important stage of overall process. Requirements Engineering is the initial step of system development activity in which the requirements from the customer are elicited and documented. This activity is very much vital for the success of the project because all of activities depends upon requirements engineering such as designing, implementation, testing, operation and maintenance. The development process begins by clarifying the need and then articulating the need as a high level solution. In order to minimize the poor requirements and to sure successful projects, Object-Oriented requirements engineering was proposed. Object-Oriented requirements engineering is an approach to encapsulating information about the process and product, as well as functionality in to a requirements object. This paper proposes using the concept of an Operations Concept Harbinger(OCH) that is the prototype of Object-Oriented requirements engineering to develop the requirements with consolidating simultaneously the opinions of various stakeholder in the customer level and trace accurately the transition from User needs to requirements. Then the customer can secure the accurate requirements to meet their needs and traceability from user needs to requirements.

• Journal of information and communication convergence engineering
• /
• v.10 no.3
• /
• pp.284-294
• /
• 2012

The quality of requirements is one of the key factors in the success of a project. One of the studies on successful projects is the reuse of requirements. However, the rate of failed projects is about 70%, and these projects often fail because of improper requirements. The current techniques for software reuse may not perform requirement engineering appropriately or develop requirements having good characteristics. In order to improve this situation, we propose a model for reusing requirements. We expect that our model will contribute toward increasing project productivity using requirement reuse in existing projects, and reusing requirements that have good quality.

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

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