• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.639-650
• /
• 2002

We have to carry out systematic, definite requirements analysis for the successful development of software. The UML gives the ways to grasp user or customer requirements and decide the boundary of business systems from the use case modeling. This paper presents how to extract use case diagram from the requirements specification systematically by applying the standardized rules as a part of the study for use case modeling. We modify requirements specification by applying $R_{RS}$ (Rules for Requirements Specification) and extract actor, use case, relationship by applying $R_{A}$(Rules for Actors), $R_{U}$(Rules for Use Cases) and $R_{R}$(Rules for Relationships) to the modified requirements specification separately and then become to make out use case diagram in the end. By applying the rules presented in this paper to the requirements specification for personnel management, we can reduce the existing difficulties of extracting use case diagram based on the narrative descriptions without any standardized rules.rules.

• Journal of KIISE:Computer Systems and Theory
• /
• v.35 no.8
• /
• pp.394-406
• /
• 2008

Even though context is the most important feature in context-aware systems, the existing requirements engineering cannot support methodology for elicitation and specification of contexts. In this paper, we propose a requirements elicitation method and a requirements specification method for context-aware systems. Our requirements elicitation method is a 6-stepped, incremental, and iterative process. At the beginning steps in the process, we identify the requirements for business logic. Afterwards, we gather the requirements for context logic, model contexts, and identify subsystems. For requirements specification, we suggest a context-aware use case diagram, a context diagram for context modeling, and a context-type-use-case-dependency diagram for the traceability of use cases on the change of context types. We also introduce a case study that we apply our approaches to a real system, and a qualitative evaluation of our approaches. Our study will help stakeholders to efficiently elicit requirements for context-aware systems and to specify them clearly.

• Journal of KIISE:Software and Applications
• /
• v.35 no.12
• /
• pp.731-740
• /
• 2008

A railway control system is one of the typical safety-critical systems. It is required to use formal methods for the requirements specification and verification in order to develop the global-standard railway control systems based on the computer systems. In this paper, we develop a guideline for requirements specification using formal methods, and present a case study of the development of a computer-based railway control system through the application of the proposed guideline. We use the Statechart and the Z method for the formal requirements specifications and verify the consistency and completeness of the formal specifications of the requirements.

• Journal of KIISE:Software and Applications
• /
• v.32 no.2
• /
• pp.108-118
• /
• 2005

The software of the nuclear power plant digital control system is a safety-critical system where many techniques must be applied to it in order to preserve safety in the whole system. Formal specifications especially allow the system to be clearly and completely specified in the early requirements specification phase, therefore making it a trusted method for increasing safety. In this paper, we discuss a systematic method, which generates PLC-based FBD programs from the requirements specification using NuSCR, a formal requirements specification method. This FBD programs takes an important position in design specification. The proposed method can reduce the possible errors occur in the manual design specification, and the software development cost and time. To investigate the usefulness of our proposed method, we introduce the fixed set-point rising trip example, a trip logic of BP in DPPS RPS, which is presently being developed at KNICS.

• Journal of the Korean Society of Systems Engineering
• /
• v.14 no.2
• /
• pp.33-40
• /
• 2018

This paper is based on the interim result of ongoing research and development project to develop a software system which support procurement activities, namely PeMSS (Procurement Engineering Management Support System). PeMSS is a system that enables development requirements for each equipment and help designing equipment meeting the purchase requirements. Procurement at EPC (Engineering Procurement and Construction) and operational stage of a plant is an important area that determines the integrity and profitability of the plant. Procurement of unsuitable equipment due to selection of suppliers that do not meet or omit critical requirements in purchase specification can result in enormous cost increase due to such as delay in EPC project, unsatisfactory performance and reduced plant operation time. In spite of the importance of the procurement engineering, there is a lack of support system for systematic preparation of purchase specification, so development of the procurement specification is basically relying on the experience of the engineers in charge. Accordingly, it is needed to develop the PeMSS to help procurement engineers develop procurement specification based on systems engineering approach. This paper introduces the design of the PeMSS.

• Proceedings of the CALSEC Conference
• /
• 2001.02a
• /
• pp.427-444
• /
• 2001

ㆍ ebXML Message Services Requirements Specification - Working Draft 26-May-2000, v0.96 · ebXML Message Services Specification - Working Draft 13-Sep-2000, v0.21 ㆍ ebXML Collaboration Protocol Profile and Agreement Specification - Working Draft 24-Jan-2001, v0.29 · ebXML Technical Architecture Security Specification - Working Draft 5-Feb-2001, vl.02(Under development) ㆍ ebXML Message Service Interface Specification - Under development.(omitted)

• Journal of the Society of Naval Architects of Korea
• /
• v.48 no.3
• /
• pp.207-214
• /
• 2011

Ship design requirements described in the building specification should be reflected in the design process. This paper identifies the configuration of requirements mentioned in the building specification using Ontology Representation Language (OWL). Ontology-based semantic search system specifies the requirement items. Through this extraction, building specifications mentioned for each entry are configured to the tree. Tracking requirements for ship design and a set of procedures to instruct is also used for the V model of systems engineering. The semantic search engine of robot agent and ontology can search the requirements specification document and extract the design information. Thereafter, design requirements for the tracking model that proposes the relationship between the associated BOM(bill of material) and product structure.

• Journal of KIISE
• /
• v.44 no.1
• /
• pp.27-35
• /
• 2017

Many studies have addressed 'Adaptive User Interface (AUI)', wherein the user interface changes in accordance with the situation and the environment of each user at runtime. Nevertheless, previous papers for AUI barely reflected the viewpoints from requirements engineering field, since most of them focused on proposing the architecture and design. In this study, we outline AUI with the perspective of requirements engineering and propose the requirements elicitation and specification method based on concepts which have been researched in the area of self-adaptive system. Step by step, we first redefine and reinterpret the well-known concepts of self-adaptive software, after which the AUI requirements are elicited and specified. Finally, we illustrate a case study, which demonstrates the effectiveness of our method.

• Journal of KIISE:Software and Applications
• /
• v.36 no.7
• /
• pp.531-538
• /
• 2009

Domestic software market is struggling with product's low quality and low return-on-investment. The cause for the problems is due to unclear requirements at the early stage of software project. Studies show that, to lessen the problem, the requirements specification must reflect the right project scope and quantifiable quality goal. To achieve such features, this paper describes a standard guideline for SRS (Software Requirements Specification), which helps in defining the scope of project, measuring and quantifying quality, linking and tracing of requirements, and improving usability. The proposed SRS enables separating the requirements analysis activity from implementation activity and thus can improve subcontract management process in software project.

• Journal of the Korea Society of Computer and Information
• /
• v.6 no.4
• /
• pp.30-37
• /
• 2001

In the conventional development methodologies, requirements are considered to be not changing after the analysis phase. But in the real world requirements can be changed and modified through out the development life cycle according to end-user's more understanding about the target system. new IT technologies, changes of customer environment and market situation, and so on. In this paper, an idea of improving the requirements specification to extend requirements management over the whole development life cycle is proposed to resolve the requirements management problem of development methodologies.