Subsystem

Definition

Subsystem

a system that is a part of another system

Classification

As illustrated in the preceding figure, systems are part of the following inheritance hierarchy:

• Type: Concrete
• Superclass: System
• Subclasses:
  • Hardware Subsystem
  • Software Subsystem

Responsibilities

The typical responsibilities of a Subsystem are to:

• Meet the goals of the customer organizations.
• Meet the needs of members of the user organizations.
• Fulfill the associated system requirements.

Contents

The typical contents of a Subsystem include:

• Subsystems containing:
  • Data Components
  • Hardware Components
  • Personnel Components (wetware)
  • Procedural Components (paperware)
  • Software Components

Stakeholders

• Producer:
  • Integration Team
• Evaluator:
  • Independent Test Team
• Approvers:
  • Technical Leader
  • Project Manager
  • Client Representative
• Maintainer:
  • Maintenance Organization
• Users:
  • The User Organizations use the system.

Phases

• Business Strategy: Not Applicable
• Business Optimization: Not Applicable
• Initiation: Not Applicable
• Construction: Initial Exemplar Constructed
• Initial Production: Small Numbers Constructed
• Full-Scale Production: Large Numbers Constructed
• Delivery: Transitioned To Users
• Usage: Used and Maintained
• Retirement: Retired

Preconditions

The Subsystem typically can be started if the following preconditions hold:

• Components exist to be integrated.

Inputs

• Work Products:
  • Subsystems containing:
    • Data Components
    • Hardware Components
    • Personnel Components (wetware)
    • Procedural Components (paperware)
    • Software Components
• Stakeholders:
  • None

Guidelines

• The size, complexity, type, and component parts of a subsystem greatly influence the method used to produce it.