Systems engineering training and consulting for project success ...
IEEE Std 982.1 - IEEE Standard Dictionary of Measures to Produce Reliable Software
From IEEE Software Engineering Standards Collection:
IEEE Std 982.1. This standard provides definitions of selected measures. The measures are intended for use throughout the software development life cycle in order to produce reliable software. The standard does not specify or require the use of any of the measures. Its intent is to describe the individual measures and their use.
MIL-HDBK-1467 - Software Common Operating Environment [DRAFT]
|File||MIME type||Size (KB)||Language||Download|
ISO/IEC 12207 SW LC Processes - 12207 Tutorial
ISO/IEC 12207 - Software Lifecycle Processes
|Document title Sort descending||Document identifier||Document date||File size||File|
|ISO/IEC 12207 SW LC Processes - 12207 Description||UNKNOWN||77.63 KB||DOWNLOAD!|
|ISO/IEC 12207 SW LC Processes - 12207 Tutorial||1999-04-26||793.5 KB||DOWNLOAD!|
ISO 12207 is an ISO standard for software lifecycle processes. It aims to be 'the' standard that defines all the tasks required for developing and maintaining software.
The ISO 12207 standard establishes a process of lifecycle for software, including processes and activities applied during the acquisition and configuration of the services of the system. Each Process has a set of outcomes associated with it. There are 23 Processes, 95 Activities, 325 Tasks and 224 Outcomes (the new "ISO/IEC 12207:2008 Systems and software engineering -- Software life cycle processes" defines 43 system and software processes).
The standard has the main objective of supplying a common structure so that the buyers, suppliers, developers, maintainers, operators, managers and technicians involved with the software development use a common language. This common language is established in the form of well defined processes. The structure of the standard was intended to be conceived in a flexible, modular way so as to be adaptable to the necessities of whoever uses it. The standard is based on two basic principles: modularity and responsibility. Modularity means processes with minimum coupling and maximum cohesion. Responsibility means to establish a responsibility for each process, facilitating the application of the standard in projects where many people can be legally involved.
The set of processes, activities and tasks can be adapted according to the software project. These processes are classified in three types: basic, for support and organizational. The support and organizational processes must exist independently of the organization and the project being executed. The basic processes are instantiated according to the situation.