• 제목/요약/키워드: Software Life Cycle Processes

검색결과 41건 처리시간 0.032초

소프트웨어 프로세스 평가 정보 기술 (Information Technology for Software Process Assessment)

  • 최성운
    • 대한안전경영과학회:학술대회논문집
    • /
    • 대한안전경영과학회 2007년도 춘계학술대회
    • /
    • pp.425-435
    • /
    • 2007
  • This paper presents various information technologies of software product evaluation such as process for evaluators, process for developers, and process for acquirers. This study also introduces system life cycle processes and its application guide.

  • PDF

프로그램 관리 관점에 기반을 둔 소프트웨어 아키텍처 생애주기 모델 : 확장된 나선형 모델 (A Software Architecture Life Cycle Model Based on the Program Management Perspective : The Expanded Spiral Model)

  • 고석하
    • Journal of Information Technology Applications and Management
    • /
    • 제20권2호
    • /
    • pp.69-87
    • /
    • 2013
  • The expanded spiral model in this paper consists of five processes of architecture design, architectural construction, architectural maintenance, operation, and architectural management. The former four processes are executed alternatively, while the latter architectural management process is executed continuously interacting with the other processes during the whole life cycle of the system. The expanded spiral model provides a conceptual framework to sort discussions of architectural degeneration into those of product-oriented processes and those of management processes, making it possible to incorporate the models and body of knowledge about project and program management especially those of Project Management Institute, into discussions of architectural degeneration. A good architecture decomposes the software-intensive system into components mutually interacting in a well-formed structure. The architecture design process and the architectural construction process together create the object system with well-designed architecture. The architectural maintenance process prevents the implemented architecture deviate from the designed architecture. The architectural management process monitors the changes of requirements including architecturally significant requirements, supports the other processes to be executed reflecting various perspectives of stake-holders, and creates and documents the reasons of architectural decisions, which is considered as a key element of the architecture.

디지털 원자로 보호계통의 소프트웨어 확인 및 검증 (Software Verification & Validation for Digital Reactor Protection System)

  • 박기용;권기춘
    • 대한전기학회:학술대회논문집
    • /
    • 대한전기학회 2005년도 심포지엄 논문집 정보 및 제어부문
    • /
    • pp.185-187
    • /
    • 2005
  • The reactor protection system is the most important function for the safe operation of nuclear powerplants (NPPs) in that such system protects a nuclear reactor tore whose damage can cause an enormous disaster to the nuclear facility and the public. A digital reactor protection system (DRPS) is being developed in KAERI for use in the newly-constructed NPPs and also for replacing the existing analog-type reactor Protection systems. In this paper, an software verification and validation (V&V) activities for DRPS, which are independent of the DRPS development processes, are described according to the software development life cycle. The main activities of DRPS V&V processes are the software planning documentations, the verification of software requirements specification (SRS) and software design specification (SDS), the verification of codes, the tests of the integrated software and system. Moreover, the software safety analysis and the software configuration management are involved in the DRPS V&V processes. All of the V&V activities are described, in detail, in this paper.

  • PDF

소프트웨어 사업 관리를 위한 지침과 적용방안 (The Guideline for Management of Software Project and Its Application)

  • 유천수;이상호;심승배;조성림;송기호;허정
    • 한국IT서비스학회지
    • /
    • 제8권1호
    • /
    • pp.125-142
    • /
    • 2009
  • The Ministry of Information and Communication announced "The Guideline for Management of Software Project" in October 2006. The public employees(acquirer) have to manage software projects with this guideline. The guideline was based on the International standard(ISO/IEC 12207) and IEEE standard(IEEE/EIA 12207), and was developed by considering the domestic software industry environment. The guideline can help to establish a software acquisition process for appropriate management of software projects, and the process can increase the management productivity of software projects. This study provides the explanation about the guideline with terms of 5W1H(who(user), what(summary), when(time to apply), where(domain of application), why(objective), how(method of use)) for understanding of the guideline.

The Importance of Ethical Hacking Tools and Techniques in Software Development Life Cycle

  • Syed Zain ul Hassan;Saleem Zubair Ahmad
    • International Journal of Computer Science & Network Security
    • /
    • 제23권6호
    • /
    • pp.169-175
    • /
    • 2023
  • Ethical hackers are using different tools and techniques to encounter malicious cyber-attacks generated by bad hackers. During the software development process, development teams typically bypass or ignore the security parameters of the software. Whereas, with the advent of online web-based software, security is an essential part of the software development process for implementing secure software. Security features cannot be added as additional at the end of the software deployment process, but they need to be paid attention throughout the SDLC. In that view, this paper presents a new, Ethical Hacking - Software Development Life Cycle (EH-SDLC) introducing ethical hacking processes and phases to be followed during the SDLC. Adopting these techniques in SDLC ensures that consumers find the end-product safe, secure and stable. Having a team of penetration testers as part of the SDLC process will help you avoid incurring unnecessary costs that come up after the data breach. This research work aims to discuss different operating systems and tools in order to facilitate the secure execution of the penetration tests during SDLC. Thus, it helps to improve the confidentiality, integrity, and availability of the software products.

프로젝트 환경과 특성에 따른 소프트웨어 개발 경로 선정 알고리즘 (Algorithm selecting Software development route suitable for Project environment and characteristics)

  • 정병권;윤석민
    • 정보처리학회논문지D
    • /
    • 제13D권1호
    • /
    • pp.87-96
    • /
    • 2006
  • 본 논문은 프로젝트 환경과 특성을 고려하여, 소프트웨어 개발 경로를 커스터마이징 하는 방법을 설계한 것이다. 개발 경로 선정 기준은 ISO/IEC TR 15721 Information Technology Guide for ISO/IEC 12207(Software Life Cycle Processes), ISO/IEC 15504 Information technology - Process assessment의 프로세스 내용에 기반 한 10개의 영역 특성이다. 10개의 영역 특성은 프로젝트 환경과 특성을 반영한 것이며, 프로젝트 개발 경로 선정 항목들을 정의한다. 프로젝트 환경과 특성 항목인 10개 영역 특성 항목을 이용하여 소프트웨어 개발 프로세스를 선정하는 알고리즘을 제시한다. 본 논문에서 제안한 소프트웨어 개발 경로를 커스터마이징 하는 방법을 평가하기 위하여 소프트웨어 개발 경로를 커스터마이징 하는 방법을 반영한 개발 경로 선정 시스템을 가지고 웹 기반 시스템 개발 프로젝트를 적용한다. 그러나 입증된 수작업 프로젝트 경로 프로세스와 시스템에서 출력된 프로젝트 경로 프로세스가 차이가 난다 차이가 나는 주원인은 산출물이 서로 합쳐졌거나, 명칭이 바뀌었기 때문이다. 효과로는 소프트웨어 개발 프로젝트 환경과 특성에 적합한 경로 프로세스를 용이하게 선정한다.

소프트웨어 제품 평가 및 생명 주기 프로세스 (Process for Software Product Evaluation and Life Cycle)

  • 최성운
    • 대한안전경영과학회:학술대회논문집
    • /
    • 대한안전경영과학회 2007년도 춘계학술대회
    • /
    • pp.437-448
    • /
    • 2007
  • This paper introduce information technology of software process assessment. It consists of eight parts such as concepts and introductory guide, a reference model for processes and process capability, performing an assessment, guide to performing assessments, an assessment model and indicator guidance, guide to competency of assessors, guide for use in process improvement, and guide for use in determining supplier process capability.

  • PDF

Requirements on a computer bank of knowledge Alexander S.Kleschev and Vasiliy A.Orlov

  • Kleschev, Alexander S.;Orlov, Vasiliy A.
    • 한국지능정보시스템학회:학술대회논문집
    • /
    • 한국지능정보시스템학회 2001년도 The Pacific Aisan Confrence On Intelligent Systems 2001
    • /
    • pp.249-255
    • /
    • 2001
  • Different kinds of information are used when solving tasks that arise in the life cycle of an applied knowledge based system (KBS). Many of these tasks are still under investigation. Their solving methods are often researched independently of each other due to complexity of the tasks. As a result, systems that realize these methods turn out to be incompatible and therefore could not be used together in the lifecycle of a KBS. The following problem arises here: how to support the full life cycle of a KBS. This paper introduces a class of computer knowledge banks that are intended to support the full life cycle of KBSs. Primary tasks that arise in the full life cycle of a KBS are analyzed. The architecture of a knowledge bank of the introduced class is presented, including an Information Content, a Shell of the Information Content and a Software Content. General requirements on these components are formulated on the basis of the analysis. These requirements depend on the current state of understanding in the life cycle of KBSs.

  • PDF

Methods of Extracting and Providing R&D Documentation Guideline for Licensing Medical Device Software

  • Kim, DongYeop;Lee, Byungjeong;Lee, Jung-Won
    • 인터넷정보학회논문지
    • /
    • 제20권3호
    • /
    • pp.69-75
    • /
    • 2019
  • The safety and performance of medical device software is managed through life-cycle processes, which represent the entire process of research and development (R&D). The life-cycle process of medical device software is represented by an international standard called IEC 62304, ISO/IEC 12207. In order to license the product, the manufacturer must have document artifacts that comply with the IEC 62304 standard. However, these standards only describe the content of the activity and do not provide a method or procedure for documentation. Therefore, this paper suggests R&D documentation guidelines that assist medical device software developers to have R&D documents conforming to the standards. For this purpose, this study identifies the requirements related to documentation among the requirements existing in the standard and extracts them in the form of guidelines showing only the core information of the requirements. In addition, through the Web framework implemented based on this research, the developer can evaluate whether the technical documents are written in accordance with the R&D document guidelines. Medical device software manufacturers can efficiently produce high-quality research and development documents through R&D documentation guidelines, and they can have standards-compliantresearch and development documentation required for licensing procedures.

구조적 또는 정보공학 소프트웨어 개발 방법론 개선 절차 (The Procedure for Improving Structural Methodology or Information engineering Methodology)

  • 정병권;윤석민
    • 정보처리학회논문지D
    • /
    • 제9D권6호
    • /
    • pp.1083-1090
    • /
    • 2002
  • 소프트웨어개발방법론은 급변하는 정보기술변화에 따라가지 못한다. 대부분의 소프트웨어 개발 프로젝트는 구조적 또는 정보공학 방법론을 사용한다. 기존 소프트웨어 개발 방법론이 프로젝트에 적용할 기술이 반영이 안되어 있다면, 프로젝트는 비효율적으로 수행되어진다. 본 논문은 새로운 정보기술을 기존의 구조적 또는 정보공학 방법론에 용이하게 반영하여 개선하는 모델을 제안한다. 본 모델은 소프트웨어 생명주기를 단계들로 나누고 각 단계는 관점 영역으로 나누어 분할된 작은 영역에 새로 적용할 정보기술을 반영하는 분할과 정복 기법을 활용한다. 적용사례는 설계단계를 중심으로 KCC 정보통신(주)에서 사용한 클라이언트 서버 방법론 CS@RoadMap에 웹 기반 소프트웨어 개발절차를 반영하였다. CS@RoadMap방법론에 웹 기술을 반영한 Web@RoadMap방법론을 공공 프로젝트에 적용하였다.