12207cpt - INTERNATIONAL STANDARD ISO/IEC 12207 SOFTWARE...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
1 INTERNATIONAL STANDARD ISO/IEC 12207 SOFTWARE LIFE CYCLE PROCESSES Raghu Singh Federal Aviation Administration Washington, DC, USA BACKGROUND In 1987 the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) established a Joint Technical Committee (JTC1) on Information Technology. The scope of the JTC1 is "Standardization in the field of information technology systems (including microprocessor systems) and equipments." In June 1989, the JTC1 initiated the development of an International Standard, ISO/IEC 12207 [1], on software life cycle processes to fill a critical need. Since the "cottage" industry era of the late 1970's, software has been establishing itself as an integral part of many scientific and business disciplines. However, environments for developing and managing software have been proliferating for lack of a uniform framework for managing and engineering software. The International Standard fills that critical need by establishing a common framework that can be used by software practitioners to manage and engineer software. Besides, such a uniform framework would promote international trade in software products and services. The International Standard was published August 1, 1995. The following countries participated in the development of the standard: Australia, Brazil, Canada, Czech Republic, Denmark, Finland, France, Germany, Ireland, Italy, Japan, Korea, The Netherlands, Spain, Sweden, the United Kingdom, and the United States of America. The standard is voluntary; that is, it does not in itself impose any obligation upon anyone to follow it. Yet, it may be imposed by an organization through internal policy directive or by individual parties through contractual agreements. The standard is designed for use by one or more parties as the basis of an agreement or in a self-imposed way. BASIC CONCEPTS Software life cycle architecture. The standard establishes a top-level architecture of the life cycle of software. The life cycle begins with an idea or a need that can be satisfied wholly or partly by software and ends with the retirement of the software. The architecture is built with a set of processes and interrelationships among these processes. The derivation of the processes is based upon two basic principles: modularity and responsibility. Modularity. The processes are modular; that is, they are maximally cohesive and minimally coupled to the practical extent feasible. An individual process is dedicated to a unique function. Responsibility. A process is considered to be the responsibility of a party in the software life cycle. In other words, each party has certain responsibilities. Responsibility is one of the key principles of total quality management, as discussed later.) This is in contrast to a "text book approach," where the life
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 cycle functions could be studied as topics or subjects, such as management, design, measurement, quality control, etc. The life cycle processes.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/22/2011 for the course ITC 101 taught by Professor Cuibap during the Three '11 term at Charles Sturt University.

Page1 / 18

12207cpt - INTERNATIONAL STANDARD ISO/IEC 12207 SOFTWARE...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online