• Proceedings of the Korea Information Processing Society Conference
• /
• 2009.11a
• /
• pp.871-872
• /
• 2009

시스템 또는 소프트웨어의 개발에 있어서 요구사항은 가장 중요한 산출물 중 하나이며, 요구사항의 오류를 수정하는 비용은 프로젝트가 진행됨에 따라 급격히 증가하기 때문에 잘 작성된 요구사항은 개발비용의 절감효과를 가져올 수 있다. 자연어의 모호성으로 발생될 수 있는 오류들을 줄이기 위해 정형적인 언어를 사용하여 요구사항을 명세하고, 요구사항의 완전성을 높일 수 있다. 본 논문에서는 열차제어시스템의 핵심 기능 중 하나인 간격제어모듈의 요구사항을 상태차트로 명세 및 검증 하였다.

• The KIPS Transactions:PartD
• /
• v.8D no.1
• /
• pp.99-104
• /
• 2001

As a plan to counteract solving software crisis, the technology that is called Component Based Software Engineering (CBSE or Componentware) is introsuced. Component Based Software Developement (CBSD) Processes as one of the technique among CBSE have been proposed. Component specification activities among CBSD Processed are necessary and important for generating feusable component. However, the existing CBSD processed can't ensure the correctness in requirements are reflected. In this paper, we propose that formal activities wgich specify component using formal specification language Z which is verified with the ability of analysis and logicality. The proposed activities are composed of 5 tasks and 12 subtasks. By presenting specific 19 products, it is also proposed that component specification activities which are the base of CBSD for reusing. The proposed activities are able to improve qualities of component through correctness and verification of requirements specification of users in the early step of component-based software process.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2018.05a
• /
• pp.253-255
• /
• 2018

기술발전에 따라, 보다 다양한 분야와 영역에 다양한 형태의 임베디드 시스템이 사용됨에 따라, 그에 대한 신뢰성과 안전성에 대한 요구가 증가하면서, 하드웨어 뿐만 아니라 소프트웨어까지도 포함한 부분에 대한 철저한 명세와 그에 따른 검증이 요구되고 있어, 임베디드 시스템 및 소프트웨어의 요구사항 검증을 위해 요구사항 시뮬레이션이라는 기법을 적용하고, 그 효용성을 확인하고자 한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.352-354
• /
• 2004

비기능적 요구사항은 대상 시스템이 지원해야 할 기능적 요구사항의 속성 또는 품질로써 소프트웨어 품질 속성으로 반영된다. 또한 비기능적 요구사항은 설계를 결정하기 위한 중요한 기준으로 사용되므로 소프트웨어 개발 프로세스 전반에 걸쳐 꾸준히 고려하고, 관리해야 한다. 하지만 비기능적 요구사항은 가시성이 없고, 명확히 명세하기가 어려운 특성으로 인해 간과하기 쉽다 따라서 비기능적 요구사항을 실제 모델링에 반영하고, 이를 추적하여 계속적으로 관리하기 일한 노력이 필요하다. 이에 본 논문에서는 내장형 소프트웨어의 비기능적 요구사항을 모델링 하는 절차를 제안하며, 내장형 소프트웨어의 특성을 가진 지능형 조명 제어 시스템의 사례를 통해 비기능적 요구사항을 반영한 모델링을 수행하고, 다이어그램들 사이' 의 비기능적 요구사항에 대한 추적 과정을 살펴본다

• Journal of KIISE
• /
• v.44 no.9
• /
• pp.893-907
• /
• 2017

In safety-critical systems, software defects may have serious consequences. Therefore, defects should be considered during the requirements specification process, which is the first step of a software development lifecycle. Stakeholder requirements that are usually written in natural language are difficult to derived, and there may also be defects due to ambiguity and inaccuracy. To address these issues, we propose a requirement specification method using a standardized Boilerplate and a GSN Model. The Boilerplate is a semi-standard language that follows a predefined format. Due to its ability to provide a consistent representation of the requirements, boilerplate helps stakeholders avoid ambiguities about what they mean and to define the exact meaning of the requirement. Meanwhile, GSN is recognized notation to prepare a Safety Case to prove to authorities that a system is safe. It can be expressed as a functional goal, e.g., Safety Evidence, etc. The proposed study allows an analyst to easily identify a fault from the early stage of the software development lifecycle. The Boilerplate and GSN Model are designed to specify the requirements of safety critical systems and to prove safety conformity through a connection with Safety Evidence. In addition, the proposed approach is also useful to develop secure software by correcting deficiencies in the requirements found during this process.

• Journal of KIISE:Computing Practices and Letters
• /
• v.8 no.1
• /
• pp.46-61
• /
• 2002

Among the many phases involved in software development, requirements analysis phase in generally considered to play a crucial role in determining the overall software quality. Therefore, many software development companies manages the phase as one of the important phase. Especially, safety assurance through requirements analysis for safety-critical systems is quite demanding, and national and international bodies routinely require safety demonstration. Among various approaches, inspection and formal methods are generally shown to be effective. In this paper, we propose a formal verification procedure for SCR(Software Cost Reduction)-style SRS(Software Requirements Specification) using the PVS specification and verification procedure and applied this procedure to an industrial system such that a shutdown system for Wolsung nuclear power plant. This system had been verified through inspection not formal verification. The application of formal methods is rare in Korea, so it is very important to experiment about formal verification to industrial systems.

• Journal of KIISE
• /
• v.45 no.1
• /
• pp.36-44
• /
• 2018

Due to the advent of the 4th Industrial Revolution, it is imperative that we aggressively continue to develop state-of-the-art, cutting edge ICT technology relative to autonomous vehicles, intelligent robots, and so forth. Especially, systems based on convergence IT are being developed in the form of CPSs (Cyber Physical Systems) that interwork with sensors and actuators. Since conventional CPS specification only expresses behavior of one system, specification for collaboration and diversity of CPS systems with characteristics of hyper-connectivity and hyper-convergence in the 4th Industrial Revolution has been insufficiently presented. Additionally, behavioral modeling of CPSs that considers more collaborative characteristics has been unachieved in real-time application domains. This study defines the non-functional requirements that should be identified in developing embedded software for real-time constrained collaborating CPSs. These requirements are derived from ISO 25010 standard and formally specified based on state-based timed process. Defined non-functional requirements may be reused to develop the requirements for new embedded software for CPS, that may lead to quality improvement of CPS.

• Journal of KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.157-167
• /
• 2000

As the requirements of a software system become large and complex, it causes some problems such that requirements specification using formal methods becomes larger in its size and less understandable. In order to solve such problems, the concepts of modularity and object are adopted to specify the requirements. In addition, top-down and compositional approach to handle such requirements are also adopted. In our paper, we suggest an object-oriented Petri net, called HOONet, to hierarchically specify and verify the complex requirements by incorporating the concepts of modularity, object, abstraction and refinement into a formal method. Our HOONet method supports the incremental specification and verification of partially described or not yet fully analyzed requirements. We also show the applicability of our method by modeling and verifying the requirements of a reactor safety control system.

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

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.11a
• /
• pp.425-428
• /
• 2004

고품질의 소프트웨어 시스템을 개발하기 위해서 소프트웨어 테스트는 중요하다. 소프트웨어 개발 시에 발견되는 심각한 결함과 오류들은 소프트웨어 시스템이 사용자의 요구사항을 정확히 충족시키지 못하는데 원인이 있다. 테스트 수행 시에 요구사항을 정확히 반영하지 못한다면 반드시 테스트되어야 할 조건들이 누락될 수 있고 테스트의 성취도는 감소한다. 따라서 모든 소프트웨어 테스트는 사용자의 요구사항을 추적할 수 있어야 한다. 이를 위해 본 논문에서는 객체지향 접근방법을 사용하여 사용자의 요구사항을 테스트에 반영하고 추적하기 위한 일관성 유지 기법을 제안한다. 이를 기반으로 요구사항을 만족하는 일관성 있는 테스트케이스를 생성한다.