• Nuclear Engineering and Technology
• /
• 제41권1호
• /
• pp.91-98
• /
• 2009

The "3+3 Process" for safety critical software for nuclear power plants' I&C (Instrumentation and Control system) has been developed in this work. The main idea of the "3+3 Process" is both to simplify the software development and safety analysis in three steps to fulfill the requirements of a software safety plan [1]. The "3-Step" software development process consists of formal modeling and simulation, automated code generation and coverage analysis between the model and the generated source codes. The "3-Step" safety analysis consists of HAZOP (hazard and operability analysis), FTA (fault tree analysis), and DV (design validation). Put together, these steps are called the "3+3 Process". This scheme of development and safety analysis minimizes the V&V work while increasing the safety and reliability of the software product. For assessment of this process, validation has been done through prototyping of the SDS (safety shut-down system) #1 for PHWR (Pressurized Heavy Water Reactor).

• 정보처리학회논문지:소프트웨어 및 데이터공학
• /
• 제8권12호
• /
• pp.465-472
• /
• 2019

오늘날 많은 영역에서 소프트웨어의 사용 범위가 넓어짐에 따라 좋은 소프트웨어 (Good Software)의 개발은 매우 중요하다. 하지만 현실은 소프트웨어 개발의 모든 단계에서 요구사항의 변경이 자주 발생한다. 또한 빈번한 변경으로 인해 설계 복잡성이 증가하여 원래의 설계 목표보다 소프트웨어 품질이 저하될 수 있다. 이러한 문제 해결을 위해, 배드 스멜(Bad Smell) 코드 추출을 위한 코드 가시화 프로세스를 제안한다. 이 방법은 마틴 파울러의 배드 스멜을 기반으로 소스 코드를 식별하여 리팩토링 영역을 가시화 한다. 잦은 요구사항의 변경에도 리팩토링을 통한 소프트웨어의 설계 개선을 기대한다.

• 산업경영시스템학회지
• /
• 제26권4호
• /
• pp.82-90
• /
• 2003

The Systems Engineering, as a methodology for engineering and management of today's ever-growing complex system, is a comprehensive and iterative problem-solving process. The process centers on the analysis and management of the stakeholders' needs throughout the entire life-cycle of a system and searches for an optimized system architecture. There are many essential needs and requirements to be met when a system development task is carried out. Systems Engineering Management Plan(SEMP), as a specification for system development process, must be established to satisfy constraints and requirements of stakeholders successfully and to prevent cost overrun and schedule delay. SEMP defines technical management functions and comprehensive plans for managing and controlling the entire system development process, specialty engineering processes, etc. Especially. in the case of a large-scale complex system development program where various disciplinary engineering such as mechanical; electrical; electronics; control; telecommunication; material; civil engineering etc. must be synthesized, it Is essential to develop SEMP to ensure systematic and continuous process improvements for quality and to prevent cost/schedule overruns. This study will enable the process knowledge management on the subject of SEMP as a core systems engineering management effort, that is, definitely defining and continuously managing specification of development process about requirements, functions, and process realization of it using a computer-aided systems engineering software. The paper suggests a systematic SEMP development process and demonstrates a data model and schema for computer-aided systems engineering software, RDD-100, for use in the development and management of SEMP. These are being applied to the systems engineering technology development task for the next-generation high-speed railway systems in progress.

• 융합보안논문지
• /
• 제4권2호
• /
• pp.71-75
• /
• 2004

The Common Criteria (CC) philosophy is to provide assurance based upon an evaluation of the IT product or system that is to be trusted. Evaluation has been the traditional means of providing assurance. It is essential that not only the customer' srequirements for software functionality should be satisfied but also the security requirements imposed on the software development should be effectively analyzed and implemented in contributing to the security objectives of customer's requirements. Unless suitable requirements are established at the start of the software development process, the re suiting end product, however well engineered, may not meet the objectives of its anticipated consumers. By the security evaluation, customer can sure about the quality of the products or sys tems they will buy and operate. In this paper, we propose a selection guide for If products by show ing relationship between security engineering and security evaluation and make help user and customer select appropriate products or system.

• 인터넷정보학회논문지
• /
• 제19권2호
• /
• pp.43-48
• /
• 2018

Various artifacts that are produced as software R&D project progresses contain research plan, research report, software requirements and design descriptions, etc. When conducting a software R&D project, it is necessary to confirm that the developed system has implemented its research requirements well. However, various research results make it difficult to design appropriate tests. So, there is a practical need for us to comprehensively handle the planning, execution, and reporting of software test for finding and verifying information related to the research. In this paper, we propose a useful method for software test process in R&D project which supports model based software testing. The proposed method supports automation of test design and generation of test data by explicitly separating each step of System Under Test (SUT). The method utilizes the various models representing the control flow of the function to extract the information necessary for testing the system. And it supports a systematic testing process based on TMMi and ISO 29119. Finally, we show the validity of the method by implementing a prototype with basic functionality to generate test data from software behavioral models.

• Journal of information and communication convergence engineering
• /
• 제7권3호
• /
• pp.247-252
• /
• 2009

The Internet has made a huge impact on the way we, as humans, communicate. During the last decade a series of new communication mediums have emerged and communication protocols have come and gone. This puts new requirements on the development process and architecture of the communication platforms, operated by communities, in order to proactively ensure support for future communication protocols. Even further, additional requirements are added when the software itself will be maintained by a community. In this paper we explore the world of Open Source Software. We present our suggestions of usable design-principles and our process in developing a sustainable information system.

• 한국IT서비스학회지
• /
• 제2권1호
• /
• pp.135-143
• /
• 2003

As the functional and nonfunctional requirements of defence systems become more complex and precise, concerning about the systematic development of software embedded into the defence systems has become surged up. In order to develop more reliable and correct software, and to extend the life cycle of the developing software, adoption of some engineering technologies such as development process, methodology, CASE tools and documentation is essentially required. This paper introduce an approach to technical information management in embedded software development process, with an instance, airborne ECM system development project. Particularly, we suggest and explain how to guide the software development according to process and methodology, and how to generate technical documents using CASE tool.

• 한국전산구조공학회:학술대회논문집
• /
• 한국전산구조공학회 2008년도 정기 학술대회
• /
• pp.464-469
• /
• 2008

Information Delivery Manual (IDM) is a documentation format for capturing the information requirements among various AEC project tasks and their software uses. The authors analyzed the structural engineering and analysis domain and were able to define its process model definition and the information flow required for the process by following the methodology stated in the IDM format. The authors believe that The manual has its potentials for further enhancements for IFC-based process integration by transferring it into a information model schema, which can be later referenced by the software applications to automatically determine which data need to be exchanged.

• 한국컴퓨터정보학회논문지
• /
• 제23권12호
• /
• pp.115-122
• /
• 2018

As the proportion of software in weapon systems increases, the impact of software on the overall system is growing. As a result, software quality management becomes important, and related regulations and work manuals for quality assurance activities at each stage in the R & D process are becoming more sophisticated. However, due to the characteristics of the weapon system software that is developed as a customized form for the purpose of a specific mission, there are limits to specifying and definitizing the detailed requirements (upper and lower level) according to various operational concepts during the development process. Due to this, software modification (patch change, shape change due to upgrade, etc.) occurs on account of many defects and performance improvement in the mass production and operation stage after the development is completed. In this study, we analyze the characteristics of these weapon system softwares and propose quality improvement methods based on ISO / IEC / IEEE 29119 test method.

• 정보과학회 논문지
• /
• 제44권5호
• /
• pp.510-521
• /
• 2017

소프트웨어 개발 프로세스(Software Development Process: SDP)는 소프트웨어공학 교육에서 가장 기초적이며 중심적인 역할을 한다. 모든 소프트웨어는 개발의 시작부터 마지막까지를 모두 포함하는 특정 SDP에 기반해서 개발된다. 따라서, SDP 교육은 소프트웨어공학의 제반 기술에 대한 이해를 도울 수 있다. 본 논문은 대학의 소프트웨어공학 수업에서 활용할 수 있는 소프트웨어 개발 방법론(프로세스)인 OOPT(Object Oriented Process with Traceability)를 소개한다. OOPT는 객체지향 소프트웨어를 개발하기 위한 방법론으로서, 각 단계마다 구체적인 요구사항과 산출물을 정의하고 있으며, 단위/시스템 시험 및 추적성 분석 등의 추가적인 내용들도 포함하고 있다. 본 논문은 OOPT에 대한 적용 사례로서 다년간의 건국대학교 컴퓨터공학과 소프트웨어공학 관련 수업들을 소개하고 있으며, 향후 개선 및 발전 방향을 포함한다.