Baseline Management - Applying Systems Engineering - Lecture Slides, Slides of Systems Engineering

Download Baseline Management - Applying Systems Engineering - Lecture Slides and more Slides Systems Engineering in PDF only on Docsity!

Baseline Management

Objectives

• Understand the role of Baseline Management (BM)
• Learn the importance of implementing BM in SE projects
• Learn how to plan for and use BM
• Understand the management of change
• Understand the role of reviews and audits

Key Terminology

• Baseline
• Change Control
• Change Control Boards
• Configuration Items (CIs)
• Configuration Control
• Configuration Management
• Configuration Management Plan
• System Documents
• Technical Baseline

What Do We Mean by “Baseline”?

• A living, revised document, set of documents, database, etc. that - describe the problem, mission, customer set, requirements, functions, specifications, architecture, etc. of the system under consideration - is managed and communicated in a structured and planned way
• Often called the “technical baseline”
• Typically managed by the person or organization performing the System Engineering functions
• May include cost and schedule baselines, as directed by the Project Manager

Configuration Control

Configuration Management

• Baseline management is achieved by placing the “baseline” under configuration control
• This process is universally known as Configuration Management
• Differs from Document Control in that it further specifies which of the many controlled or authorized documents are currently applicable
• CM maintains the “traceability” attribute of requirements
• CC should ensure that changes are are known and paid for

What Baseline Management ISN’T!

Baseline Management ISN’T

• Just cost and schedule
• Document control
• Project controls
• Scope and schedule statusing
• “Just another paperwork exercise”
• “More bean-counting”

What Should the

BM Process Include?

• Identifying the elements that need to be controlled
• Change control processes and levels
• Implementing baseline controls
• Managing and communicating baseline changes
• Verifying baseline/product consistency

Graded Approach to Baseline Management

• Cost and risk must be balanced
  • Consider the cost of controlled documentation
  • Consider the cost of project failure
  • Consider any hazards the mission entails
  • Consider the life cycle of the project
  • Consider interfaces with formal configuration management organizations and/or procedures

Identifying the Elements

to be Controlled

• Cost, Schedule, and Technical Baselines
• System Requirements Document (SRD)
• Technical and Functional Requirements (T&FR)
• Interfaces Control Document (ICD)
• Design Drawings and Prints (System Design Description, SDD)
• Design Specifications
• Decision Data, if needed docsity.com

Change Control

• Change Classification
  • Change levels
  • Appropriate review and approval
• Change Control Board
  • Delegated by PM
• Change Process
  • Appropriate to scale and risk
• Deviations, Waivers, and Exemptions

Change Control Boards

• The size and makeup of the Change Control Board (CCB) is directly proportional to the size of the project. It can be one person or several.
• The CCB ensures that:
  • changes are considered
  • approved changes are implemented
  • documentation is complete and up-to-date.

When Configuration Items are

Changed

• Changes to configuration items, when needed, are proposed to the CCB
• Once approved, changes are implemented in the affected item
• Related documents are changed/updated as necessary
• New revisions of the CI documents are issued
• CI documents are controlled and maintained.

Objectives Review

• Understand the role of Baseline Management (BM)
• Learn the importance of implementing BM in SE projects
• Learn how to plan for and use BM
• Understand the management of change
• Understand the role of reviews and audits