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

항공 및 국방 산업 둥에서는 고안전성 임베디드 시스템의 신뢰성과 안전성을 보장하기 위해 임베디드 시스템의 설계 및 구현에 정형기법을 적용하고 있다. 본 논문은 그러한 정형기법을 적용하여 임베디드 시스템 소프트웨어의 요구사항 명세(Software Requirements Specification : SRS)와 요구명세를 바탕으로 실제 구현을 위한 설계명세(Software Design Specification : SDS)를 정형기법을 이용하여 명세하였다. 본 논문은 정형 명세 언어로 작성된 요구명세와 설계명세 간의 부합성 검사를 하고 더 나아가 임베디드 시스템 요구 분석에서 더 정확하게 소프트웨어를 구현할 수 있는 방법을 제시하고자 한다.

• Journal of KIISE:Software and Applications
• /
• v.34 no.9
• /
• pp.773-784
• /
• 2007

Aspect-Oriented Programming (AOP) has focused on improving the modularity of the crosscutting concerns. The existing AOP methodology has been mainly focused on the implementation method of programs and thus developer-oriented concern extraction and development were performed. Recently, many studies for applying AOP to the entire software development processes ranging from requirement analysis to design and implementation are being conducted. But specification methods having consistency from the initial phase of concern extraction to implementation phase are not sufficient. In this paper, we have presented the specification of crosscutting concerns so as to solve these problems. The specification of crosscutting concerns provides guidelines and specification from the requirement analysis phase to the process of converting extracted crosscutting concerns to codes. This method reduces the gap to the process of mapping extracted crosscutting concerns into a single class and thus enhances program development and understandability. In addition, it raises program reusability, maintenance and extensibility by enhancing traceability.

• The Journal of the Korea Contents Association
• /
• v.5 no.5
• /
• pp.51-58
• /
• 2005

Software development process evolves by component based development(CBD) process and introduction to configuration management system is risen recently. In this paper, we explained component configuration management system evolved out of CBD methodology and focused on the specification management in component configuration management. The component specification is being based on XML that is a normalization document. Also, component version management and dependency management are achieved by a component name. And component dependency information is just the integration information using a component specification name used in the composition when component specification is composed. Thus we confirmed possibility of version management and dependency management using the specification.

• The Transactions of The Korean Institute of Electrical Engineers
• /
• v.66 no.9
• /
• pp.1379-1384
• /
• 2017

To guarantee safety and reliability, RAMS(Reliability Availability Maintainability and Safety) activity for a communication software in train communication network is studied. In this paper, preliminary hazard analysis in RAMS activities is studied for the communication software. Preliminary hazard analysis is done through library for communication software that the specification is defined by IEC 61375. The hazards are defined, then causes and consequence for each hazard are defined. The total 36 preliminary hazards are classified. For high severity hazards are changed to acceptable level by upgrading of system requirement specification.

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

• The Transactions of the Korean Institute of Electrical Engineers P
• /
• v.57 no.2
• /
• pp.65-71
• /
• 2008

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 this paper, we propose an eclectic approach to incorporate Z(Zed) formal language and 'Statemate MAGNUM' which is formal method tools using Statechart for applying to the railway signaling systems.

• Journal of the Korea Society of Computer and Information
• /
• v.11 no.6 s.44
• /
• pp.49-57
• /
• 2006

While developing a complex reactive software system. it is very important to analyze the user requirement and reflect it to the developed system. Therefore understanding the need of users precisely and promptly is the key to the successful software system development. Among several requirement specification languages, message sequence charts (MSCs), also known as sequence diagrams in UML are the most widely used scenario notation. Live Sequence Charts (LSCs) are a variant ot MSCs, characterized by its message abstraction facility and the modality of scenarios. In this paper, I define the formal semantics of LSC specification including the essential language constructs such as pre-charts, variables, assignment and conditions. The range of the formalized LSC language has been broadened, and the scope of the formalized semantics is much closer to the complete LSC specification.

• Proceedings of the Korea Society for Industrial Systems Conference
• /
• 1998.10a
• /
• pp.655-662
• /
• 1998

This paper is on the anlaysis for real-time software requirement . This method can be used for TNPIN(Timed Numerical Petri Net) as a easy communication means with a real-users. It is based on the RTTL(Real Time Temporal Logic) for correctness fo the system. TNPN is used to represent a behavior specification language, the validity of specified behaviors in TNPN is expressed in RTTL , and analyzed through the reachability graph. Thus , the requirement of between user and system is satisfied. By the example of shared track, the validity of the property of real-time (safetiness, responsiveness, liveness, priority) is verified. Also, this framework is give to connection with a object natually.

• Journal of Korea Society of Industrial Information Systems
• /
• v.4 no.1
• /
• pp.1-6
• /
• 1999

This paper is on the analysis for the real-time software requirement. This method can be used for TNPN(Timed Numerical Peri Net) as a easy communication means with real-users. It is based on the RTTL(Real Time Temporal Logic) for correctness the system. TNPN is used to represent a behavior specification language, the validity of specified behaviors in TNPN is expressed in RTTL, and analyzed through the teachability graph. Thus, the requirement between user and system is satisfied Using the example of shared track, the validity of the property of real-time(safetiness, responsiveness, liveness, priority) is verified. Also this framework if given to connection with a object, natually.

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