• The Transactions of the Korea Information Processing Society
• /
• v.6 no.10
• /
• pp.2680-2692
• /
• 1999

Software quality is classified by quality of process and product. In experience of Quality Management, it is known that quality level of product as it depends on goodness and badness of process and organization. As a result, improvement of software process has been important subject. According as this trends, ISO 12207 is publicated as standard of software life cycle process by ISO. For UML based object oriented development process, it is necessary that we should research detailed definition of activity and task of ISO 12207 process which is added, deleted or tailored in according to organization and project characteristics. In this thesis, by according with ISO 12207 software life cycle process, UML based object oriented development process is proposed. This process is composed of 7 steps and 19 activities including development phase, activity and product to improve quality of reliability. Usefulness of object oriented process for improvement of software quality is proved at three ways, which are comparative analysis of process characteristics, SPICE process evaluation and SPICE rick analysis.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.400-402
• /
• 2000

소프트웨어 시스템에 대한 요구사항이 증가하고 그 규모가 점차 거대.복잡해짐에 따라 시스템을 개발하기 위한 절차, 방법 등이 무수히 생겨나게 되었다. ISO/IEC 12207 소프트웨어 생명주기 공정 표준은, 존재하고 있는 소프트웨어 개발 및 유지보수에 대한 절차 및 방법에 대한 일반적인 지침을 제시하고, 이전의 프로세스 공정 표준들이 적용될 수 없는 새로운 개발 패러다임을 지원하기 위해 제정되었다. 이 표준은 표준 자체의 특성의 하나인 보편성을 유지하기 위해, 특정 프로세스 모델에 치우치지 않는 기반 표준(Base Standard)의 성격을 갖는다. 결국 기반표준은, 어떠한 프로젝트에서 어떠한 프로세스 모델을 사용하건, 임의의 방법론을 사용하든 모든 경우에 적용될 수 있어야 한다. 최근, 질적인 성장 뿐 아니라 양적으로도 풍부한 성장을 거둔 객체지향 개발 환경에서는 전통적인 개발 환경에서와 많은 차이점을 보이며, 새로운 개발 프로세스들을 제안하고 있다. 본 논문에서는 객체지향 개발 프로세스 중 현재 가장 대중적으로 사용되고 있는 Rational사의 Unified Process를 선택하여 ISO/IEC 12207 표준의 적용성을 고찰해보고, 표준의 발전, 개선방향에 대해 모색해 보겠다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.04a
• /
• pp.528-530
• /
• 2000

소프트웨어 시스템에 대한 요구사항이 증가하고 그 규모가 점차 거대.복잡해짐에 따라 시스템을 개발하기 위한 절차, 방법 등이 무수히 생겨나게 되었다. ISO/IEC 12207 소프트웨어 생명주기 공정 표준은, 존재하고 있는 소프트웨어 개발 및 유지보수에 대한 절차 및 방법에 대한 일반적인 지침을 제시하기 위해 제정되었다. 이 표준은 표준 자체의 특성의 하나인 보편성을 유지하기 위해, 특정 프로세서 모델에 치우치지 않고 기반 표준(Base Standard)의 성격을 갖는다. 결국 표준은, 어떠한 프로젝트에서 어떠한 프로세스 모델을 사용하고 임의의 방법론을 사용하든 모든 경우에 적용될 수 있어야 한다. 그런데 최근 소프트웨어 산업의 새로운 패러다임으로 받아들여지고 있는 컴포넌트 기반 소프트웨어 개발(CBSD)환경에서는, 전통적인 개발환경과 많은 차이점을 지적하며 새로은 개발 프로세서들이 제안되고 있다.[4]. 따라서 본 논문에서는 CBSD환경에서의 ISO/IEC 12207 표준의 적용성을 고찰해보고 표준의발전, 개선 방향에 대해 모색해 보고자한다.

• Convergence Security Journal
• /
• v.3 no.1
• /
• pp.85-94
• /
• 2003

The Configuration management process is to establish and maintain the integrity of all the work products of a process or project. This paper discusses the similarities and differences between ISO/IEC 12207 and ISO/IEC 15846. The most widely used models for software process assesment, ISO/IEC 15504, CMM and CMMI can rate maturity of processes. We analyze and compare the practices for measuring Configuration process and propose metric for quantitative measure.

• Proceedings of the CALSEC Conference
• /
• 1998.10a
• /
• pp.149-161
• /
• 1998

For the purpose of developing CALS/EC, it was surveyed ISO/IEC 12207 that was international standard and IEEE/EIA 12207 that was national standard in U.S.A and then peformed analysis comparing with MIL-STD-498 it was called origin of DoD software development process. Also it was surveyed software life cycle Process using doemstic defense area now Software life cycle process based on MIL-STD-498 in defense area was not yet includ the concept of new development philosophy like iterative development and process management according to the characteristics of project. For the purpose of improving software life cycle in defense area, first refined the process. And then on this study it was recommended accomodation of incremental and evolutionary development approach and the method of tailoring based on MIL-STD-498 was able to select and apply the process on the characteristics of project.

• Journal of Information Technology Services
• /
• v.8 no.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.

• Journal of Digital Contents Society
• /
• v.11 no.4
• /
• pp.537-543
• /
• 2010

According to software growth, also software maintenance has been continuously improving. In addition, the existing concept of correct maintenance demands operational management and improvement of service. However, we have various limitation matters to reflect the requirements of service base for maintenance accomplishment. Therefore, we need the study of the service based process for solving such a problem. In this paper, we propose a Service based Software Maintenance Process. Proposed process based on ISO12207 standard for software development and maintenance and compares it with the service based representative standards. In a related works, we study activity of $SM^{MM}$, ITSCMM, ITIL and find out activities to be concerned with and compare it with activity of ISO 12207 and distinguish the maintenance process activity of the service base from maintenance activities. And then, we propose a service management stage. It define four activities and eight artifacts. Finally, we validate the result by comparing the proposed process with a general service operational process.

• Journal of KIISE:Computing Practices and Letters
• /
• v.8 no.2
• /
• pp.155-166
• /
• 2002

Even the short history of the Web system, the technology related to the Web system has been developed rapidly. Yet, the quality of the Web-based application software has not been improved that much. For this reason, the efficient method to develop the Web-based application software is needed. This paper describes the items necessary to develop the Web-based application software. On the basis of ISO/IEC 12207-Software Life Cycle Processes this paper mainly suggests the analysis and design stage of the Web-based model for developing software. Also, this paper describes the methods to define the process and the entity for applying contents to Web-based application software. With the web-based model suggested in this paper the Web-RoadMap Methodology of KCC Information & Communication, a system provider in Korea, has been applied to the public-domain projects. Through the application, Web-RoadMap Methodology has been proved to be an applicable model for analyzing and designing the systems based on the web environments.

• Journal of Information Technology Application
• /
• v.3 no.4
• /
• pp.119-134
• /
• 2001

Improving software product quality is a key to increasing user satisfaction and to achieving competitive edge. There are two approaches to assure high software product quality; development process-oriented and product-oriented. There have been many efforts for improving software quality through process certification, for example, CMM, ISO 9000 family, ISO/IEC 12207, SPICE and Bootstrap. However, a good process alone cannot guarantee good product quality. A need for the evaluation of software product quality by an independent third party is growing rapidly for several reasons. We are concerned with an application of Statistical Quality Control (SQC) to the evaluation of software product quality to obtain the efficiency of evaluation processes and the objectivity of evaluation results. Methods for selecting test cases using a random sampling approach have been discussed and methods for selecting acceptance criteria with respect to software product quality have also been suggested.

• Proceedings of the Safety Management and Science Conference
• /
• 2006.04a
• /
• pp.525-544
• /
• 2006

This paper is to introduce guidelines for project quality management system. International standards such as ISO 10006, IEC 62198, ISO/IEC TR 16326 and ISO 15188 are considered. This study is to discuss guidelines for quality management in projects, and application guidelines for project risk management, and guide for the application of ISO/IEC 12207 to software project management, and project management guidelines for terminology standardization.