Introduction to BOKs & Standards:

• The term "standard" has both a General and Specific meaning:
  • General: as any document produced by a standards body, or
  • Specific: as a specific whole or part of a document that is "required"
  • Therefore, to enable some flexibility:
    • The title of specific documents or volumes, within a "family" or series of related standards, can be identified as one of the three types
    • Within a single document:
      • specific sections can be identified as having one of the three types
      • specific paragraphs or clauses, can be identified as having different levels of "requirement", usually through the use of particular "standards verbs"
    • High-level "standards documents" and (the more general) "Bodies of Knowledge," can include all three types
      .
•  The three types of "standards" and standards verbs are:
  1. Standard
     • "shall" = is required to
     • Standards define mandatory practices, work products, formats, contents (i.e., requirements)
     • The clauses that are considered "pass" or "fail" for measuring compliance
  2. Recommended Practice [CMMI refers to these as "expected" practices]
     • "should" = is recommended that
     • Recommended Practices contain suggested procedures
  3. Guide
     • "may" = is permitted to -- statement of permissible courses of action
     • "can" = is able to -- statement of possibility or capability
     • Guides may (or can):
       • define alternatives and discuss trade-offs for different methods to satisfy a standard,
       • offer guidelines for implementing,
       • recommend tailoring or document "typical" tailoring,
       • define strategy for application of related standards,
       • map between similar standards (e.g., between different standards bodies),
       • translate terminology for different domains, or
       • provide other supportive information
         .
• Alternative Terms Used (with, or in place of, the terms above):
  • Normative = standard, shall
  • Informative = not considered actually part of the "requirements"
    • Usually the "front matter" and sometimes an introduction is defined as informative
    • Additionally, annexes, or other sections provided for understanding, may also be identified as informative
  • CMMI adds an intermediate designation, "Expected" where:
    • some practice is required (that meets the goals and expectations)
    • a common solution is defined, but
    • an alternative solution may be substituted
    • i.e., an "optional requirement"

• Example from the ISO "Family" of Quality Standards:
  • ISO-9000-2000, Quality Management Systems Concepts and Vocabulary, and
  • ISO-9004-2000, Quality Management Systems Guidelines
    • are defined as Informative
  • ISO-9001-2000, Quality Management Systems Requirements
    • Is what you are audited against, i.e.: Normative
  • However, within 9001, there are
    • "required procedures" and "other procedures"
    • Not all of 9001 is "required"
      • Not every clause in 9001 has a "shall", and
      • A "requirement" cay be conditional (e.g., your scope, business, or application domain may determine if it is required)

Selected Software and Systems
Engineering Standards:

• Org -- Standards organization
  • ANSI, BS (British Standard, see BCS), DoD, EIA, FAA, IEC, IEEE, INCOSE, ISSEA, ISO, MIL, NIST, OGC, OMG, SEI, and other standards are included in the table below
• Number
  • Standard identifier number [listed in numeric order independent of source
  • Some unnumbered standards are listed first
  • For a mapping from other acronyms and buzzwords to IEEE standards number, see: http://standards.ieee.org/faqs/buzzwords.html
• Year  -- The year of issue or version number
  • black year indicates the current version
  • blue year indicates the more recent date that an existing standard was reaffirmed (no change)
  • gray year indicates an obsolete version (replaced by a black year).
• Vo -- The IEEE Software Engineering Standards are available as a hard-copy, four volume set (or on CD). This column indicates the volume number that contains standard, based on the 1999 edition. The volumes, and Type of standards, are categorized as follows:

  	Primary Systems and Software Standards noted with yellow high-light
  1	: Customer and Terminology Standards (General Process and Life Cycle Standards)
  2	: Process Standards (Process Standards, Process Area Definitions)
  3	: Product Standards (Work Product, Deliverable, & Plan Standards)
  4	: Resource and Technique Standards
  n	: Newest version by default (hardcopy version in volume reaffirmed)
  n	: hardcopy version (from volume "n") is now obsolete (superseded by newer date)
  x	: superseded standard, hardcopy version no longer valid (color reflects type of previous standard)
  Other Standards not included in 1999 SE Standards collection:
  A	: Appraisal Methods
  B	: Benchmarks (Maturity or Capability Models)
  P	: General Process and Life Cycle Standards
  D	: Data  Item Descriptions (DID) associated with MIL or DoD standards
  H	: High-Order Language (HOL) Standards
  I	: Interface, Notations, and Component Standards
  Q	: General Quality Standards

• PA -- A general characterization of the major Process Area, or discipline, that the standard supports

Note: Standards evolve! I have attempted to assure standard numbers and versions were correct/current at time originally launched, and maintain history as time allows. Please, check with the authoring organization for latest information. For IEEE Standards, use the search engine at: standards.ieee.org/db/status/index.shtml to search based on the standard number (or title) to determine the status of the standard (including the latest version, revision, or reaffirmation). Better yet, join the IEEE Standards Organization.

CCM

CORBA Component Model (CCM) --Specification of: a Component Implementation Definition Language (CIDL); the semantics of the CORBA Components Model (CCM); a Component Implementation Framework (CIF), which defines the programming model for constructing component implementations; a container programming model describing how an Enterprise JavaBeans (EJB) component can be used by CORBA clients, including CORBA components; an architecture of the component container as seen by the container provider; how Component implementations may be packaged and deployed; and definitions of the XML DTDs used by the CORBA Components.

I

TS

Common Object Request Broker Architecture (CORBA^®) - the most popular open middleware standard. http://www.corba.org/

I

TS

CWM

1.1

Common Warehouse Metamodel (CWM™)

TS

MOF

2.0

Meta Object Facility (MOF™) - http://www.omg.org/mof/  bridges the gap between dissimilar meta-models by providing a common basis for meta-models.

TS

SysML

1.0a

Systems Modeling Language (SysML) - http://omgsysml.org/  See brief history on Organization page.

I

TS

UML

2.0

Unified Modeling Language™ (UML^®) - OMG's most-used specification, and used to model not only application structure, behavior, and architecture, but also business process and data structure. The OO notation standard proposed by Rational Software Corporation. See also extensions for Systems Engineering (SysML). UML 2.0 Superstructure is complete. The superstructure defines the six structure diagrams, three behavior diagrams, four interaction diagrams, and the elements that comprise them. See ISO/IEC 19501. The other three parts of UML 2.0 are:
  ● UML 2.0 Infrastructure: The infrastructure defines base classes that form the foundation not only for the UML 2.0 superstructure, but also for MOF 2.0.
  ● UML 2.0 Object Constraint Language (OCL): This allows setting of pre- and post-conditions, invariants, and other conditions.
  ● UML 2.0 Diagram Interchange: This specification extends the UML metamodel with a supplementary package for graph-oriented information, allowing models to be exchanged or stored/retrieved and then displayed as they were originally.

I

RD TS

XMI

2.1

XML Metadata Interchange (XMI^®), the standard for storing and exchanging models using XML

I

TS

ANSI AIAA

043

1992

Guide for the Preparation of Operational Concept Documents [See also IEEE 1362]

P

RM

MIL

498

1994

Military Standard -- Software Development and Documentation;
05-Dec-1994 replaced DoD-Std-2167A-1988, DoD-Std-7935A-1988, and DoD-Std-1703(NS) 1987; This military standard was submitted to IEEE and EIA as an US industry standard and then proposed as an international standard (ISO) J-016. Superseded by 12207 and adopted for use by DoD on May 27,1998.

P

GS

MIL

499B

Defines total system approach for the development of defense systems [medium level of abstraction], life cycle: Pre-concept; Concept Exploration and definition; demonstration and validation; Engineering and Manufacturing Development; Production and Deployment; Operations and Support

P

IEEE

610

1991

Computer Dictionary Project  (P610) - This project was to consolidate the current individual specialty "glossaries" (e.g., 610.12-1990) into one common vocabulary for software professionals. Withdrawn (see 610.2, 610.3, 610.5, 610.12).

P

GS

IEEE

610.02

1987

Standard Glossary of Computer Applications Terminology

P

GS

IEEE

1989

Standard Glossary of Modeling and Simulation Terminology

P

GS

IEEE

610.04

1990

Standard Glossary of Image Processing and Pattern Recognition Terminology

P

GS

IEEE

610.05

1990

Standard Glossary of Data Management Terminology

P

GS

IEEE

610.06

1991

Standard Glossary of Computer Graphics Terminology

P

GS

IEEE

610.07

1995

Standard Glossary of Computer Networking Terminology

P

GS

IEEE

610.10

1994

Standard Glossary of Computer Hardware Terminology

P

GS

IEEE

610.12

1990

Standard Glossary of Software Engineering Terminology (R2002)