• Nuclear Engineering and Technology
• /
• v.48 no.2
• /
• pp.404-418
• /
• 2016

This paper presents a documentation and development method to facilitate the certification of scientific computing software used in the safety analysis of nuclear facilities. To study the problems faced during quality assurance and certification activities, a case study was performed on legacy software used for thermal analysis of a fuelpin in a nuclear reactor. Although no errors were uncovered in the code, 27 issues of incompleteness and inconsistency were found with the documentation. This work proposes that software documentation follow a rational process, which includes a software requirements specification following a template that is reusable, maintainable, and understandable. To develop the design and implementation, this paper suggests literate programming as an alternative to traditional structured programming. Literate programming allows for documenting of numerical algorithms and code together in what is termed the literate programmer's manual. This manual is developed with explicit traceability to the software requirements specification. The traceability between the theory, numerical algorithms, and implementation facilitates achieving completeness and consistency, as well as simplifies the process of verification and the associated certification.

• 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 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 KIISE:Software and Applications
• /
• v.31 no.6
• /
• pp.750-759
• /
• 2004

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 the NuSCR, which is a qualified formal specification method for specifying nuclear power plant digital control system software requirements. To investigate the application of NuSCR, we introduce the experience of using NuSCR in formally specifying the plant protection system's software requirements, which is presently being developed at KNICS. Case study that shows that the formal specification approach NuSCR is very much qualified and specialized for the nuclear domain is also shown.

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

• Proceedings of the Korean Information Science Society Conference
• /
• 2002.10d
• /
• pp.19-21
• /
• 2002

Writing requirements in formal notation for a safety-critical system can improve software quality and reduce the errors that may arise later on in the software development life cycle. In this paper, we propose a formal specification approach used to describe the nuclear control system. The approach is based on the existing AECL approach that was the only formal specification technique applied to nuclear control systems in the past. Although the approach is AECL-based, the complex descriptions of certain requirements have been reduced by using different specification techniques. We discuss the differences and how the proposed approach provides not only specification but also verification environment.

• 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 KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.120-133
• /
• 2000

Major obstruction of using formal methods for hybrid real-time systems in industry is the difficulty that engineers have in understanding and applying the quantitative methods in an abstract requirements phase. While formal methods technology in safety-critical systems can help increase confidence of software, difficulty and complexity in using them can cause another hazard. In order to overcome this obstruction, we propose a framework for qualitative requirements engineering of the hybrid real-time systems. It consists of a qualitative method for requirements specification, called QFM (Qualitative Formal Method), and a safety analysis method for the requirements based on a causality information, called CRSA (Causal Requirements Safety Analysis). QFM emphasizes the idea of a causal and qualitative reasoning in formal methods to reduce the cognitive burden of designers when specifying and validating the software requirements of hybrid safety systems. CRSA can evaluate the logical contribution of the software elements to the physical hazard of systems by utilizing the causality information that is kept during specification by QFM. Using the Shutdown System 2 of Wolsong nuclear power plants as a realistic example, we demonstrate the effectiveness of our approach.

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

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