Welcome to our new site version. Your web page bookmarks may have changed, please search for pages by title to update them. Having problems ? Please try clearing your web browser cache and hard-reloading your web page first before contacting our webmaster.

software management

IEEE Std 1298 - Software Quality Management System. Part 1: Requirements. Adopted From Standards Australia

Body

From IEEE Software Engineering Standards Collection:

IEEE Std 1298. This is Australian Standard AS 3563.1-1991. This standard establishes requirements for a software developer’s quality management system. It identifies each of the elements of a quality management system to be designed, developed, and maintained by the developer with the objective of ensuring that the software will meet the requirements of a contract, purchase order, or other agreement.

Defined by

IEEE Std 1074 - IEEE Standard for Developing a Software Project Life Cycle Process

Body

From IEEE Software Engineering Standards Collection:

IEEE Std 1074. This standard defines the set of activities that constitute the processes that are mandatory for the development and maintenance of software. The management and support processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement, are covered. Associated input and output information is also provided. Utilisation of the processes and their component activities maximises the benefits to the user when the use of this standard is initiated early in the software life cycle. This standard requires definition of a user’s software life cycle and shows its mapping into typical software life cycles. It is not intended to define or imply a software life cycle of its own.

Defined by

IEEE Std 1058 - IEEE Standard for Software Project Management Plans

Body

From IEEE Software Engineering Standards Collection:

IEEE Std 1058.1. This standard specifies the format and contents of software project management plans. It does not specify the procedures or techniques to be used in the development of project management plans, or does it provide examples of project management plans, instead the standard sets a foundation for an organisation to build its own set of practices and procedures for developing project management plans.

Defined by

ISO/IEC 12207 - Software Lifecycle Processes

Defined by
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.

Software Assurance Technology Center (SATC)

Body

From http://satc.gsfc.nasa.gov/:

The Software Assurance Technology Center (SATC) was established in 1992 as part of the Systems Reliability and Safety Office at NASA Goddard Space Flight Center (GSFC). The SATC was founded with the intent to become a center of excellence in software assurance, dedicated to making measurable improvement in both the quality and reliability of software developed for NASA at GSFC. SATC is self-supported with internal funding coming from research and application of current software engineering techniques and tools. Research funding primarily originates at NASA headquarters and is administered by it's Software IV&V Facility in Fairmont, WV. Other support comes directly from development projects for direct collaboration and technical support.