• Transactions of the KSME C: Technology and Education
• /
• v.1 no.2
• /
• pp.199-204
• /
• 2013

In this paper, a new system requirement management tool and its application on the Urban Transit Maglev Project were introduced. In most R&D projects on complexity system such as transportation system, Systems Engineering(SE) activities are included on each project, and SE teams are using commercial computer-based tools to perform the SE activities. Even though SE tools help to manage huge data and documents on engineering efficiently, but well-designed functions of SE tools which support SE activities are not sufficiently used on the whole process of system engineering. In order to computer-based SE tools are to be effectively used on project management, most engineers who takes engineering and coordination roles, at least sub-project managers should be familiar to the tool and could be easily use it, but usability of commercial SE tools are very difficult for normal engineers with no experience on SE activities and SE tools. To overcome this difficulty, we developed a new system requirement management tool considering each user's scenario on using engineering tools. The developed tool could not cover whole SE processes, but designed to perform requirement engineering such as system requirements(SRs) management, specification management, traceability management, SRs' verification activity management and so on. All the entities on SR database are inter-connected by pre-recognized traceabilities, so even non-specialists on SE can easily browse the database and find entities concern, and linked information such as interacted entities, legal or engineering constraints, coordination documents, status of development and verification and so on. Also functions for SR verification tools, TPM(Technical Performance Measure) tools, DB searching tools with traceability, and report generation tools are included on the system.

• International journal of advanced smart convergence
• /
• v.13 no.1
• /
• pp.99-107
• /
• 2024

In AI image generation tools, most general users must use an effective prompt to craft queries or statements to elicit the desired response (image, result) from the AI model. But we are software engineers who focus on software processes. At the process's early stage, we use informal and formal requirement specifications. At this time, we adapt the natural language approach into requirement engineering and toon engineering. Most Generative AI tools do not produce the same image in the same query. The reason is that the same data asset is not used for the same query. To solve this problem, we intend to use informal requirement engineering and linguistics to create a toon. Therefore, we propose a sequence diagram and image generation mechanism by analyzing and applying key objects and attributes as an informal natural language requirement analysis. Identify morpheme and semantic roles by analyzing natural language through linguistic methods. Based on the analysis results, a sequence diagram and an image are generated through the diagram. We expect consistent image generation using the same image element asset through the proposed mechanism.

• Journal of the Korean Society of Systems Engineering
• /
• v.10 no.1
• /
• pp.57-64
• /
• 2014

We propose a methodology to automatically extract the requirements from the documents and check the traceability between them. The documents include not only the text file but also PDF or image files. We also suggest a method to visualize the result with maps, numbers, and graphs. By comparing the results with those of expert reviews, we show that it is necessary to use knowledge-based method in future instead of the word-based method for improving the reliability. The results give more values when they are applied in already existing documents than those of newly developed product.

• Journal of Information Technology Applications and Management
• /
• v.17 no.3
• /
• pp.1-24
• /
• 2010

Most of enterprises depend on a data modeler during developing their management information systems. In formulating business requirements for information systems, they widely and naturally use the interview method between a data modeler and a field worker. But, the discrepancy between both parties would certainly cause information loss and distortion that lead to let the systems not faithful to real business works. To improve or avoid modeler-dependant data modeling process, many automated data design CASE tools have been introduced. However, since most of traditional CASE tools just support drawing works for conceptual data design, a data modeler could not generate an ERD faithful to real business works and a user could not use them without any knowledge on database. Although some CASE tools supported conceptual data design, they still required too much preliminary database knowledge for a user. Against these traditional CASE tools, we proposed a Requirement-Oriented Entity Relationship Model for automated data design tool, called ROERM. Based on Non-Stop Methodology, ROERM adopts inner systematic modules for complete and sound ERD that is faithful to real field works, where modules are composed of interaction modules with a user, rules of schema operations and sentence translations. In addition to structure design of ROERM, we also devise detailed algorithms and perform an experiment for a case study.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.9 no.1 s.24
• /
• pp.135-143
• /
• 2006

This paper describes a requirement architecture modeling for the front end of KT-1 export version requirement definition processes to construct SDS(system development specification). The requirement definition process is a highly conceptual process that is difficult to carry out. This paper focuses on how to perform the KT-1 export version requirements definition process including the integration of process, methods and tools for the front-end activity of requirements definition process. This requirement model is structured in four segments, including requirement layering, requirement categorization, life cycle stakeholder and requirement definition process using Computer-Aided Systems Engineering tool(CORE).

• Korean Journal of Computational Design and Engineering
• /
• v.5 no.2
• /
• pp.136-143
• /
• 2000

The appearance of new machine tools with higher flexibility is in need of a basic structure design system for establishing the systematic and rationalized design and manufacturing procedures. In this study. the basic structure design system for machine tools is realized based on the modular construction method. Machine tools are represented as a whole and modular complex with the directed graph, and all possible structural configurations and codes of machine tools for satisfying the machining requirement are derived from the DNA data and connecting patterns of basic structural elements. Especially the structural configurations of machine tools are visualized by the solid modeling techniques and 3-D graphics techniques.

• Nuclear Engineering and Technology
• /
• v.31 no.1
• /
• pp.58-67
• /
• 1999

The purpose is to produce a model of nuclear reactor trip logic caused by the steam generator water level of Wolsong 2/3/4 unit through an activity chart and a statechart and to produce C language automatically using Statechart-based Formalism and Stalemate MAGNUM toolset suggested by David Harel Formalism. It was worth attempting auto-generation of C language though we manually made Software Requirement Specification(SRS) for safety-critical software using statechart-based formalism. Most of the phases of the software life-cycle except the software requirement specification of an analysis phase were generated automatically by Computer Aided Software Engineering (CASE) tools. It was verified that automatically produced C language has high productivity, portability, and quality through the simulation.

• Journal of the Korean Society of Manufacturing Technology Engineers
• /
• v.19 no.4
• /
• pp.440-448
• /
• 2010

Recently, there are many corporations, schools and institutes that apply TRIZ to solve technical problems. However, in reality, only a few cases of brainstorming applications exist in utilizing forty principles of TRIZ due to the difficulty at TRIZ problem definition. In order to facilitate TRIZ applications, this study proposes the utilization of requirement definition and description tool of systems engineering in TRIZ problem definition. No requirement definition exists in general problem types that TRIZ approach is used in implementing system solution. At most of problem situations, TRIZ users reversely infer that certain problem belongs to which requirement definition it is and recommends TRIZ tools to be used for the exact problem definition. This study also proposes TRIZ problem definition method by applying the results of requirement definition process. The application of TRIZ is demonstrated to the general situation with no problem definition where the proposed method enables the proper use of TRIZ.

• The Journal of Society for e-Business Studies
• /
• v.9 no.3
• /
• pp.129-144
• /
• 2004

CASE tools supporting component based development should include functions for modeling, project management, and supporting other phases activities of the development process. Functional requirements of CASE tools supporting component based development are proposed in this paper. Required functions are identified by analyzing the existing CBD CASE tool, and are categorized into modeling, project management, and supporting other phases activities.

• Journal of Aerospace System Engineering
• /
• v.8 no.1
• /
• pp.36-41
• /
• 2014

KAFASAT is a CubeSat which has a high level mission of testing the possibility of establishing the LEO satellite constellation providing the role of communication nodes and quasi-realtime image recognition of battlefield in accordance with the aspect of future-war-environment. The high level mission is developed using the Pugh selection method, which is one of system engineering tools. In order to accomplish the high level mission objectives and deduce engineering level requirements, system engineering tools such as Analytic Hierarchy Process and Quality Function Deployment are used. The subsystem synthesis in the context of system engineering process is done using a developed integrated design environment. The paper also includes the conceptual design results of the KAFASAT, which can be used as a baseline for upcoming preliminary design.