Difference between revisions of "Relevant Standards"

Revision as of 01:56, 22 August 2011

Introduction

There are a multitude of standards across a number of Standards Development Organizations (SDOs) that are related to systems engineering and systems domains. This topic examines the types of standards and provides a summary of the relevant standards for systems engineering.

Standards Taxonomies and Types of Standards

There are many types of standards that focus on different aspects of systems engineering. Thus, it can be helpful to have a taxonomy that classifies the types of standards and the objective of each type. Table 1 provides the types of standards and a description of the types, as currently is in development through ISO/IEC JTC 1/SC 7. (McBride 2011)

Standard Type	Description of Type
Concepts and terminology	Defines the terminology and describes the concepts of a specific domain.
Process	Elaborates a specific process, giving normative requirements for the essential elements of the process. It may give guidance to the requirements.
Requirements	Describes the requirements for something. Most often used for actions, activities or practices and not objects (see specifications).
Procedure (Practice, Activity)	A specific procedure. Instructions or requirements on how to do something. Could be a description of best practice. Sometimes guidance and sometimes normative.
Guidance	Usually an interpretation and guidance of a published standard.
Management system	Requirements for management.
Specification	Specifies the form, attributes or properties of a subject artefact. Usually an object and usually normative.
Reference model	A reference model or collection of specifications that comprise a reference model.
Process reference model (PRM)	A collection of processes necessary and sufficient to achieve a nominated business outcome.
Process assessment model (PAM)	Requirements and guidance for assessing attributes of nominated processes or attributes of a nominated collection of processes.
Guide to Body of knowledge (BOK)	Collects and describes the current body of knowledge in a domain, or guidance to the body of knowledge.

SE Related Standards

Summary of SE Related Standards

Table 2 contains a summary of SE related standards. This table does not include all SE related standards, as there are many that are very focused on a specific domain, sector or user group (e.g., it does not include standards from a specific government agenda). The table does include standards that are considered to be widely applicable systems engineering and systems life cycle management, such as ISO/IEC/IEEE 15288, System Life Cycle Processes.

Document ID	Organization
ISO/IEC/IEEE 15288	Systems and software engineering - System life cycle processes	ISO/IEC/IEEE
ISO/IEC/IEEE 24765	Systems and software engineering - Systems and software engineering vocabulary	ISO/IEC/IEEE
ISO/IEC/IEEE 42010	Systems and software engineering - Architecture description	ISO/IEC/IEEE
ISO/IEC 26702 / IEEE 1220	Management of the Systems Engineering Process	ISO/IEC/IEEE
ISO/IEC/IEEE 29148	Systems and software engineering - Requirements engineering	ISO/IEC/IEEE
ISO/IEC/IEEE 16085	Systems and software engineering - Risk management	ISO/IEC/IEEE
ISO/IEC/IEEE 15939	Systems and software engineering - Measurement process	ISO/IEC/IEEE
ISO/IEC/IEEE 16326	Systems and software engineering - Project management	ISO/IEC/IEEE
EIA 632	Engineering of a System	TechAmerica
ISO 9001	Quality Management System	ISO
EIA 649	National Consensus Standard for Configuration Management	TechAmerica
ISO/IEC/IEEE TR 24748-1	Systems and software engineering - Guide to Life Cycle Management	ISO/IEC/IEEE
ISO/IEC/IEEE TR 24748-2	Systems and software engineering - Guide to the application of ISO/IEC 15288:2008	ISO/IEC/IEEE
ISO/IEC TR 16337	Systems Engineering Handbook	ISO/IEC/INCOSE
ISO/IEC/IEEE 15289	Systems and software engineering - Content of life-cycle information products(documentation)	ISO/IEC/IEEE
ISO/IEC/IEEE 15026-1	Systems and software engineering - System and software assurance – Part 1: Concepts and vocabulary	ISO/IEC/IEEE
ISO/IEC/IEEE 15026-2	Systems and software engineering - System and software assurance – Part 2: Assurance case	ISO/IEC/IEEE
ISO/IEC/IEEE 15026-3	Systems and software engineering - System and software assurance – Part 3: Integrity levels	ISO/IEC/IEEE
ISO/IEC/IEEE 15026-4	Systems and software engineering - System and Software Assurance – Part 4: Assurance in the life cycle	ISO/IEC/IEEE
ISO/IEC 24783	Guidelines for the application of ISO 9001 to Systems Life Cycle Processes	ISO/IEC
ISO 10303-233	Systems Engineering Data Interchange Standard	ISO
ECSS-E-ST-10C	Systems Engineering General Requirements	ECSS
ECSS-E-ST-10-02	Space Engineering - Verification	ECSS
ECSS-E-ST-10-06	Space Engineering – Technical Requirements Specification	ECSS
ECSS-E-ST-10-24	Space Engineering – Interface Control	ECSS
ECSS-M-ST-10	Space project management – Project planning and implementation	ECSS
ECSS-M-ST-40	Space project management – Configuration and information management	ECSS
ECSS-M-00-03	Space project management – Risk management	ECSS
ISO 31000	Risk Management – Principles and Guidelines	ISO
ISO 31010	Risk Management — Risk Assessment Techniques	ISO
ISO 19439	Enterprise integration - Framework for enterprise modelling	ISO
ISO 15704	Requirements for enterprise-reference architectures and methodologies	ISO
EIA 748	Earned Value Management System	TechAmerica

Breadth and Level of Detail of Key SE Related Standards

Figure 1 shows the level of detail and the coverage of the life cycle for some key standards or groups of standards.

Figure 1 - Breadth and Depth of Key SE Related Standards (Source: Roedler 2011)

Linkages to Other Systems Engineering Topics

This topic has linkages to the most of the SE topics, since the set of sets in Table 2 include cover most of the SE activities. Thus, specific linkages are not provided.

Practical Considerations

Key pitfalls and good practices related to systems engineering standards are described in the next two sections.

Pitfalls

Some of the key pitfalls encountered in the selection and use of SE standards are:

Pitfall Name	Pitfall Description
Turnkey Process Provision	Expecting the standard to fully provide your SE processes without any elaboration or tailoring.
No Need for Knowledge	Expecting that the standard can be used without any functional or domain knowledge, since the standard is the product of collective industry knowledge.
No Process Integration	Lack of integrating the standards requirements with the organization or project processes.

Good Practices

Some good practices, gathered from the references:

Good Practice Name	Good Practice Description
Tailor for Business Needs	Tailor the standard within conformance requirements to best meet business needs.
Integration into Project	Requirements of the standard should be integrated into the project via processes or product/service requirements.

References

Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Citations

List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Roedler, Garry. 2010. "An Overview of ISO/IEC/IEEE 15288, System Life Cycle Processes." Asian Pacific Council on Systems Engineering (APCOSE) Conference 2010.

Primary References

ISO/IEC/IEEE. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2008.

ISO/IEC/IEEE. 2009. Systems and Software Engineering - System and Software Engineering Vocabulary. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 24765:2009.

ANSI/EIA. 2003. Processes for engineering a system. Philadelphia, PA, USA: American National Standards Institute (ANSI)/Electronic Industries Association (EIA), ANSI/EIA 632‐1998.
ISO/IEC/IEEE. 2011. Systems and software engineering - Requirements engineering. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission/ Institute of Electrical and Electronics Engineers (IEEE), (IEC), ISO/IEC/IEEE 29148.

ISO/IEC/IEEE. 2011. Systems and software engineering - Architecture description. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 42010.

Additional References

All additional references should be listed in alphabetical order.

ISO/IEC/IEEE. 2007. Systems and software engineering - Measurement process. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 15939.
ISO/IEC/IEEE. 2006. Systems and software engineering - Risk management. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 16085.
ISO. 2009. Risk management—Principles and guidelines. Geneva, Switzerland: International Organization for Standardization (ISO), ISO 31000:2009.
ISO/IEC. 2009. Risk management—Risk assessment techniques]]. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 31010:2009.
ISO. 2003., Space systems - Risk Management. Geneva, Switzerland: International Organization for Standardization (ISO), ISO 17666:2003.
ISO/IEC/IEEE. 2009. Systems and Software Engineering - Project Management]]. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 16326.
ISO/IEC/IEEE. 2009. Systems and Software Engineering - System and software assurance, Part 1: Concepts and definitions. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15026-1.
ISO/IEC/IEEE. 2010. Systems and Software Engineering - System and software assurance, Part 2: Assurance case. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15026-2.
ISO/IEC/IEEE. 2011. Systems and Software Engineering - System and software assurance, Part 3: Integrity levels. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15026-3.
ISO/IEC/IEEE. 2011. Systems and software engineering - Content of life-cycle information products(documentation). Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15289.

Systems and software engineering - Content of life-cycle information products(documentation)

Article Discussion

[Go to discussion page]

<- Previous Article | Parent Article | Next Article ->

Signatures

@@ Line 320: / Line 320: @@
 ===Citations===
 List all references cited in the article.  Note:  SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for additional information.
+Roedler, Garry. 2010. "An Overview of ISO/IEC/IEEE 15288, System Life Cycle Processes." Asian Pacific Council on Systems Engineering (APCOSE) Conference 2010.
 ===Primary References===