System Integration - Applying Systems Engineering - Lecture Slides, Slides of Systems Engineering

Download System Integration - Applying Systems Engineering - Lecture Slides and more Slides Systems Engineering in PDF only on Docsity!

System Integration

Objectives

• Define systems Integration
• Identify systems Integration activities
• Develop the relationship between interfaces and

integration actions

• Demonstrate a method for identifying interfaces
• Define when formal interface control is necessary

and the use and content of interface control

documents.

Key Terminology

• Integration
• Interfaces
• Interface control (documents)
• System integration
• Product integration
• Process integration.

System Integration…

What is it?

• Google search results in 419,000 hits. We must be well

integrated!

• INCOSE:
  • The System Integration (SI) function is to establish system internal interfaces and interfaces between the system and larger program(s). The SI function includes the integration and assembly of the system with emphasis on risk management and continuing verification of all external and internal interfaces (physical, functional and logical).
• The system integration process connects the many separate

solutions into a system solution.

• Integrates the product components into a whole.
• Integrates the process components into a whole.
• Structures the processes such that they integrate the product.
• Assures the the primary requirement, i.e., the product system satisfies the paying customer’s needs.

Life cycle

• See Textbook page 195 on (Chapter 8).
• The process is the integrating mechanism.
• The various life cycle phases and system levels

are all connected by feed back to assure an

integrated system.

• Evolutionary design is a particularly integrated

development and design system, and was

selected by the DOD for just that reason.

Requirements Management

• Note the distinction between Requirements Analysis and

Requirements Management

• Requirements Analysis analyzes the system and the

requirements to ensure that a complete and accurate

(consistent, traceable, verifiable, functional, readable, and

correct) set of requirements exist.

• Requirements Management ensures that over the course of

the project, a person or organization continually monitors

activities and verifies that they are consistent with the project

level requirements. Since the top level requirement is that it

satisfy the customer needs, this process will assure

integration.

I/O Analysis

Transport

Ship

Convey

Receive

Receipts

Packaged Materials

Packaged Materials

Use of N – Squared Diagrams

Convey

Ship

Receive

Receipts

Packaged Materials

Shipping Notice

ICD

Transported material ICD Materials carried list Materials carried characteristics list Package size, shape,... Package environments Package container

ICD = Interface control document

Interface Control

Analysis

• Analysis produces integration by search and

detect

• Errors
• Inconsistencies
• Inaccuracies
• Incompleteness
• Functionality.

Tests

• See Textbook, p. 138.
• Integration is intimately related to the test

function.

• Test verifies integration.
• Test-failures integrate the processes by

returning the fix of the failure to the

responsible system process.

Organization

• Projects can be organized in a manner designed to provide integration.
  • Put a person in charge of each major functional area (the approach used by SBW Project: - Environmental Regulation - Community Action Plan - Product – customer interface - Paying customer interface - Safety - Engineering discipline - Risk management - etc.
  • IPT, CPT, Systems Engineers assigned to various areas (the approach used by BWIP, Pit 9 Stage II).

Change Control

• Well structured change control process where

the changes controlled are primarily technical

instead of simply cost.

• In this system, the change control board

would have to be technically competent, work

hard, conduct analyses – not just a monthly

meeting of the “good ol’boys.”

Reviews and Updates

• Review cost and schedule baselines and risk

assessments for modification due to integration

activities.

• Update the System Design Document with

integration and interface data.

• Conduct a System Design Review.
• Update technical baselines to reflect changes

resulting from the review.

• Manage the interface activities per the

negotiated interface agreements.

Document Hierarchy

• Development of a detailed document hierarchy

early in the project.

• Assign topics, authors, reviewers, and approvers.
• Assign functions and requirements for each

document.

• Assign predecessor and successor documents.
• Budget for all documents:
  • This was the process followed in the old 499 A days, attempted in the DOE 4700 days, and used in Government Bureaucracies (IRS).