• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.8
• /
• pp.391-400
• /
• 2017

Software architecture plays a key role in satisfying non-functional requirement (NFR), i.e. quality requirements and constraints. Architecture design methods and tactics for conventional NFR are largely available in literatures. However, the methods for the target system-specific non-conventional NFRs are not readily available; rather architects should invent the design methods from their experiences and intuitions. Hence, the hardship to design architectures for non-conventional NFRs is quite high. In this paper, we provide a systematic architecture design methodology for non-conventional NFRs. We provide a five-step process, and detailed instructions for the steps. In the process, we treat the traceability among artifacts and seamlessness as essential values for supporting effective architecture design. We apply the methodology on designing architectures for a platform software system. We believe that the proposed methodology can be effectively utilized in designing high quality architectures for non-conventional NFRs.

• The Korean Journal of Archival Studies
• /
• no.67
• /
• pp.5-55
• /
• 2021

The purpose of this study is to promote future research and practical application in the field of records systems by informing the revision of the ISO 16175 standard set and analyzing its main contents, which was widely used as a record management functional requirements. Based on the experience of participating in the developing process of this International Standard since 2015, this study analyzed the context and process of revision, and the main contents of the standard, and sought to draw limited implications and proposed follow-up researches connected to the practice of the Korean records systems. The previous ISO 16175 sets had been produced as ISO 16175-1, 2, 3 in 2010-2011, and which were restructured and revised into new ISO 16175-1, 2 in 2020 in line with the revision of ISO 15489 and changes in the digital environment. Main title of the International Standard is processes and functional requirements for software for managing records, and Part I provides high-level functional requirements and associated guidance for applications that manage digital records, Part II provides guidance for selecting, designing, implementing and maintaining software for managing records. This standard assumes that the records system does not necessarily have to be a single system or software solely for records management and that it should be able to perform record management function in any forms.

• Nuclear Engineering and Technology
• /
• v.27 no.3
• /
• pp.385-392
• /
• 1995

A software engineering process has been developed for the design of safety critical software for Wolsong 2/3/4 project to satisfy the requirement of the regulatory body. Among the process, this paper described the detail process of validation testing peformed to ensure that the software with its hardware, developed by the design group, satisfies the requirements of the functional specification prepared by the independent functional group. To perform the test, test facility and test software ore developed and actual safety system computer was connected. Three kinds of test cases, i.e., functional test performance test and self-check test were programmed and run to verify each functional specifications. Test failures ore fedback to the design group to revise the software and test result were analyzed and documented in the report to submit to the regulatory body. The test methodology and procedure were very efficient and satisfactory to perform the systematic and automatic test. The test results were also acceptable and successful to verify the software acts as specified in the program functional specification. This methodology can be applied to the validation of other safety-critical software.

• The KIPS Transactions:PartD
• /
• v.12D no.4 s.100
• /
• pp.617-626
• /
• 2005

To design a software system many architecture styles have to be combined to construct the overall architecture of the system What to choose among various architecture styles or architectural approaches depends on the fact of what kind of functional or non-functional quality requirements the system should satisfy In this study, we define the method to choose suitable architectural approaches by the satisfaction level of system requirements that is evaluated through estimation about technical parts of architectural approaches, and verify the evaluation method by the case study that apply the evaluation method to choose architectural approaches for message system.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.28 no.2
• /
• pp.91-103
• /
• 2003

Use case modeling on UML (Unified Modeling Language) is getting widely used in OOAD and CBD and it is considered a useful technique in dealing with the complexity of the requirements analysis. However, some of the problems with use case modeling are that it is not structured, difficult to handle non-functional requirements, and to analyze impacts among use cases. To alleviate these problems, we propose a scenario-based goal-oriented approach for use case modeling. The proposed approach is to apply a goal-oriented analysis method to use case modeling. Since goal-oriented analysis method is not systematic and many heuristics are involved, we have adopted scenarios as the basis for goal extraction. The proposed method is applied to CBIS (City Bus Information Subsystem) in ITS (Intelligent Transportation System) domain. The proposed approach helps software engineers to analyze the impact among use cases and represent non-functional requirements.

• Journal of Aerospace System Engineering
• /
• v.7 no.2
• /
• pp.29-34
• /
• 2013

Safety requirements for aircraft and system functions include minimum performance constraints for both availability and integrity of the function. These safety requirements should be determined by conducting a safety assessment. The depths and contents of aircraft system safety assessment vary depending on factors such as the complexity of the system, how critical the system is to flight safety, what volume of experience is available on the type of system and the novelty and complexity of the technologies being used. Requirements that are defined to prevent failure conditions or to provide safety related functions should be uniquely identified and traceable through the levels of development. This will ensure visibility of the safety requirements at the software and electronic hardware design level. This paper has prepared to study on promoting the efficiency of establishing hierarchical safety requirements from aircraft level function to item level through system safety processes.

• 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: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 the Korea Institute of Information and Communication Engineering
• /
• v.18 no.1
• /
• pp.149-154
• /
• 2014

Quality is the value that can be measured by observing the characteristics of the service quantity or quality. QoS is predictable service traffic to a minimum requirements what passed in network. In the course of Smart Medical Information System Development there exist some functional requirements to satisfy quality objectives. The functional smart domains of healthcare information systems consists of Patient Module, a smart sensing and communication domain, RFID Tag Readers and the behavior domain, Homecare Station Domain, Clinical Station. This study is performed on evaluation methodology of u-health service satisfaction quality of each domain. In this paper QoS metrics and the quality of medical information requirements, functional requirements are separated by. Quality parameters consists of six items and the functional requirements and quality requirements 20 details the five items and consist of 20 detailed items. On this study the quality evaluation methodology of Korean smart health information quality assessment matrix 2 - factor evaluation method is proposed. The overall framework of this paper is organizing the specific criteria of quality of medical information system and modeling quality evaluation process under all smart environment.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.16 no.6
• /
• pp.267-276
• /
• 2021

The automotive industry and academic research have been continuously conducting research on standardization such as AUTOSAR (AUTomotive Open System ARchitecture) and ISO26262 to solve problems such as safety and efficiency caused by the complexity of electric/electronic architecture of automotive. AUTOSAR is an automotive standard software platform that has a layered structure independent of MCU (Micro Controller Unit) hardware, and improves product reliability through software modularity and reusability. And, ISO26262, an international standard for automotive functional safety and suggests a method to minimize errors in automotive ECU (Electronic Control Unit)s by defining the development process and results for the entire life cycle of automotive electrical/electronic systems. These design methods are variously applied in representative automotive safety-critical systems. However, since the functional and safety requirements are different according to the characteristics of the safety-critical system, it is essential to research the AUTOSAR functional safety design method specialized for each application domain. In this paper, a software functional safety mechanism design method using AUTOSAR is proposed, and a new failure management framework is proposed to ensure the high reliability of the product. The AUTOSAR functional safety mechanism consists of memory partitioning protection, timing monitoring protection, and end-to-end protection. The fault management framework is composed of several safety SWCs to maintain the minimum function and performance even if a fault occurs during the operation of a safety-critical system. Finally, the proposed method is applied to the Shift-by-Wire system design to prove the validity of the proposed method.