• 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 KIISE:Software and Applications
• /
• v.33 no.7
• /
• pp.615-623
• /
• 2006

A non-functional requirement is a property or quality that the proposed systems have to support the functional requirements. A non-functional requirement is reflected by quality attribute These non-functional requirements playa crucial role during system development, serving as selection criteria for choosing among decisions. It should be continuously considered through the software development process. In spite of the importance of the non-functional requirements, it received little attention because of ambiguousness and invisibility of non-functional requirements. Therefore non-functional model which is a process to analyze the non-functional requirement is proposed for improving the management efficiency of non-functional requirements. Also, this paper presents the trace among the UML diagrams to the conceptual model. According to the non-functional requirement development process, this paper achieved performance-based case study. After then, non-functional requirement should be traced using the UML diagrams.

• The KIPS Transactions:PartD
• /
• v.11D no.7 s.96
• /
• pp.1459-1466
• /
• 2004

As the area of software application is increased. the software is becoming larger and more complex. In addition, development of the high quality software within the limits of the budget is strongly demanded. Many methodologies, such as software process improvement, object-ori-ented development, requirement-engineering, and software metrics have been introduced in the software development process in order to attain such objectives. Among those techniques. Requirements-Engineering gives basic guideline to develop high quality software. In other word. in order to develop high quality software, requirements should be elicited, and described. And with proper reviews and management. the quality of requirements can be improved. In this paper, quantitative measurement method that is based on IEEE Std-830-1998 for the require-ment-specifications is proposed.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.13 no.8
• /
• pp.3307-3314
• /
• 2012

The annual energy demand of the standard rural house models was analyzed using the DesignBuilder. Indoor temperature set-point, U-value of outer wall, type of window, and degree of ventilation were selected as simulation parameters. In all the simulation cases, heating energy demand was higher than cooling energy demand regardless of the building size. When the lower U-value of the outer wall was applied to account for the thicker insulation layer, heating energy demand was decreased while cooling energy demand was increased. However, it is better to reduce the area of outer wall which is directly exposed to outdoor air because reducing the U-value of the outer wall is not effective in decreasing heating energy demand. Among the four different window types, the double skin window is most favorable because heating energy demand is the lowest. For a fixed infiltration rate, higher ventilation rate resulted in an increased heating energy demand and had minor impact on cooling energy demand. As long as the indoor air quality is acceptable, lower ventilation rate is favorable to reduce the annual energy demand.

• The Journal of the Korea Contents Association
• /
• v.8 no.5
• /
• pp.61-71
• /
• 2008

It is often claimed that the descriptive way of documentation is insufficient to define software requirements as being unambiguous. This is caused by not only the difference of knowledge and understanding of the stakeholder as to system but also the difference in the way of documentation like method of representation as well as depth of description. The study explains the process and results of applying a diagraming tool like UML to improve the requirements of GLORY(GLObal Resource management sYstem) initially defined in descriptive way. Especially, the result shows that the requirements are more accurately improved with the good hierarchies and well-leveled functionalities, with the help of diagraming tool, expecting easy maintenance of requirements and prevention of omission of requirements.

• The KIPS Transactions:PartD
• /
• v.18D no.6
• /
• pp.433-442
• /
• 2011

As software is varied and grew in size, the importance of clear understanding and representing customer's need, has been emphasized. It is not easy to drive and define critical system needs, since requirements in early stage of the development, is and conceptual. Technical perspective view, Several theoretical analysis methods and validation techniques are introduced, but in practice, it is hard to drive clear customer's requirement. In this paper, to drive clear customer's requirements, Macrostruktur concept of textlinguistics is used. First, Macrostruktur of textlinguistics is used to analysis descriptive requirements. Second, Macrostruktur-rule is applied to analyzed Macrostruktur data in order to derive Macrostruktur-propositions. Finally, it is proposed to generating Use-case model using derived Macrostruktur-propositions.

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.58-68
• /
• 2006

Requirements are very important to model software architecture. Requirements are divided into functional and quality requirements. Functional requirements are pinpointed subsystems and components. Quality requirements affect the structure of architecture. Thus requirements are essential to understand clearly in order to design software architecture. This paper focuses on a quantitative approach to requirements analysis for modeling architectures. In our proposal, functional requirements are quantified through calculating each priority of components. Quality requirements are quantified through calculating the correlation degree between components and quality attributes. The proposed method is implemented by DRAMA (Domain Requirements Analysis for Modeling Architectures), which fully supports our approach and are developed in Java environments. Our proposal is validated to apply some industrial examples.

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

• The Journal of the Convergence on Culture Technology
• /
• v.7 no.2
• /
• pp.177-184
• /
• 2021

This study aims to develop the model of needs analysis for lifelong education program in order to verify social needs as well as personal needs. The overall process of this study is as follows. Firstly, a questionaire based on six mode classification of lifelong education program was invented in order to apply to program development. Secondly, a questionaire was designed to evaluate personal needs and social needs simultaneously. Thirdly, t-test, needs analysis of Borich model, and the Locus for Focus model were conducted with a view to analyze the difference between personal needs and social needs. As a result, there showed the categories of education which are high in both personal and social needs, whereas a category like certification program is higher in social needs rather than in personal needs. The results represent the necessities of promoting programs which are high in social needs even if there is no personal needs. Therefore the needs survey and the needs analysis need to be conducted to find out not only personal needs but also social needs.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1164-1177
• /
• 2005

As the software development process becomes complicated, software requirements become complicated, too. Many efforts are needed in requirements management. It is impossible to define all requirements of software at first, and the development environment changes as project is gone. As the cost of requirements change management is much more than development cost, the changes should be controled immediately through systematic change management. In this paper, I suggest a method to manage requirements change systematically based on the change management process in software product lines. The requirements change at the application engineering process is analyzed and managed using the domain engineering process because the application requirements are customized from the domain requirements in software product lines. Such the consistent change management helps to make decisions about changes by change impact analysis and alternative solution design. Through this method, the potential change costs can be saved because same change requests are not repeated by controlling the change requests completely.