• Journal of the Semiconductor & Display Technology
• /
• v.22 no.1
• /
• pp.88-93
• /
• 2023

In software engineering, requirement analysis is an important task throughout the process and takes up a high proportion. However, factors that fail to analyze requirements include communication failure, different understanding of the meaning of requirements, and failure to perform requirements normally. To solve this problem, we derived actors and behaviors using morpheme analysis and BERT algorithms in the Korean requirement document and constructed them as ontologies. A chatbot system with ontology data is constructed to derive a final system event list through Q&A with users. The chatbot system generates the derived system event list as a requirement diagram and a requirement specification and provides it to the user. Through the above system, diagrams and specifications with a level of coverage complied with Korean requirement documents were created.

• Journal of Electrical Engineering and Technology
• /
• v.4 no.1
• /
• pp.87-92
• /
• 2009

Many critical control systems are developed using formal methods. When software applied to such systems is developed, the employment of formal methods in the software requirements specification and verification will provide increased assurance for such applications. Earlier errors of overlooked requirement specification can be detected using the formal specification method. Also, the testing and full verification to examine all reachable states using model checking to undertake formal verification are able to be completed. In this paper, we proposed an eclectic approach to incorporate Z(Zed) formal language and 'Statemate MAGNUM', formal method tools using Statechart. Also we applied the proposed method to train control systems for the formal requirement specification and analyzed the specification results.

• Proceedings of the KSR Conference
• /
• 2007.05a
• /
• pp.1000-1007
• /
• 2007

Recently, many critical control systems are developed using formal methods. When software applied to such systems is developed, the employment of formal methods in the software requirements specification and verification will provide increased assurance for such applications. Earlier error of overlooked requirement specification can be detected using formal specification method. Also the testing and full verification to examine all reachable states using model checking to undertake formal verification are able to be completed. In the comparison of other formal specification methods, we choose the Z formal language for applying to the train control system. Using Z is able to realize higher correctness in the requirement specification, and we propose the Statemate of the best solution in formal verification tools for the system modeling and verification. The Statemate makes it possible to prove thoroughly the system execution from the simple graphical modeling of the complicated train control system. Then we can expect that the model-based formal method combining Z with Statemate will be utilized widely for the railway systems due to various strong points.

• Journal of KIISE:Software and Applications
• /
• v.31 no.7
• /
• pp.869-882
• /
• 2004

This paper proposes an effective method to create logically consistent and structured requirement model by applying consistency control approach of the formal method to the use-case modeling. This method integrates the multi-perspective scattered requirement segments that may overlap and conflict each other into a structured requirement model. The model structure can be analyzed based on context goal and concerned area overlap analysis. The model consistency can be achieved by using specification overlap-based consistency checking method as an integration vehicle. An experimental application to case study shows that the Proposed method can successfully identify requirement overlaps and inconsistency. It can also transfer multi-viewpoint requirement segments into a consistently integrated use-case model to clarify software behaviors and functionality This method helps users to enhance capability to identify specification inconsistency in the use-case modeling at the early stage of software engineering development. The proposed approach can also facilitate communication between users and developers to ensure customer satisfaction.

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

• Nuclear Engineering and Technology
• /
• v.32 no.6
• /
• pp.537-548
• /
• 2000

The requirement of ultra high reliability of the safety critical software can not be demonstrated by testing alone. The specification based on formal method is recommended for safety system software. But there exist various kinds of formal methods, and this variety of formal method is recognized as an obstacle to the wide use of formal method. In this paper six different formal method have been applied to the same part of the functional requirements that is calculation algorithm intensive. The specification results were compared against the criteria that is derived from the characteristics that good software requirements specifications should have and regulatory body recommends to have. The application experience shows that the critical characteristics should be defined first, then appropriate method has to be selected. In our case, the Software Cost Reduction method was recommended for internal condition or calculation algorithm checking, and statechart method is recommended for the external behavioral description.

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

The current software industry has an emerging issue with natural language-based requirement specifications. However, the accuracy of such requirement analysis remains a concern. It is noted that most errors still occur at the requirement specification stage. Defining and analyzing requirements based on natural language has become necessary. To address this issue, the linguistic theories of Chomsky and Fillmore are applied to the analysis of natural language-based requirements. This involves identifying the semantics of morphemes and nouns. Consequently, a mechanism was proposed for extracting object state designs and automatically generating code templates. Building on this mechanism, I suggest generating natural language-based comic images. Utilizing state diagrams, I apply changes to the states of comic characters (protagonists) and extract variations in their expressions. This introduces a novel approach to comic image generation. I anticipate highly productive comic creation by applying software processes to Cartoon ART.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.13 no.9
• /
• pp.4207-4213
• /
• 2012

Software quality is strongly associated with requirement quality. Accordingly, companies are trying effect for enhancing requirement quality. But, it is difficult to verify the requirement of specification format, which have to rely on abnormal business knowledge of analyst. Also, it is insufficient to normal methodology or automated technique for enhancing requirement quality of specification format. In this paper, we propose the process of requirement verification and automated verification tool for enhancing requirement quality. we compare the external view design and internal view design for verifying requirement. In the case study, we evaluate the feasibility of the proposed automated verification technique of requirement.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.14 no.6
• /
• pp.329-338
• /
• 2019

Today's embedded software (SW) developments are mostly preceded by composing Software Requirement Specification (SRS). In particular, in the domain of weapon systems, it is essential to have a systematic method for the verification of the SW functionality. To be more specific, it is crucial to check if the SW functionality is implemented as described in SRS, so-called SW suitability verification. Unfortunately, existing static or dynamic SW testing methods are not sufficient to evaluate suitability with SRS since those testings only verify the robustness of the SW codes. In this paper, we propose an automatic embedded SW suitability verification framework which is based on a structured SRS. The major challenge in the automation of this verification framework is how to get rid of ambiguities in SRS. In order to overcome this challenge, we propose a structured SRS description framework and the supporting toolchain for that. We show how the proposed framework is applied to an actual SRS of a weapon system.

• Convergence Security Journal
• /
• v.5 no.3
• /
• pp.67-73
• /
• 2005

Security requirements must be defined well to reduce software vulnerabilities in requirement specification phase. In this paper, we show how to specify security requirements in structured manner for object-oriented development methodology. Our method specifies security requirements through four phases: defining security objectives, identifying the threat, construct attack tree, and specifying security function. This method would help developers to specify security requirements and functions which software have to possess clearly and systematically.