Systems Engineering

CORE® - A Model Based Approach

January, 2004

Jody H. Fluhr
Vitech Corporation
www.vitechcorp.com
[email protected]
502.995.8895

1
 Providers of Systems Engineering Solutions
– Consulting
– Training
– Systems Engineering Technology and Tools
• Developers of the CORE Systems Engineering Tool Suite
 Founded in August 1992
 First commercial shipment of CORE in March
1993
 Headquarters in Tysons Corner, Virginia
 US Sales Offices throughout the US
 International Resellers around the world

2
 Over 250 Clients in 14 Countries
 DoD  UDLP
– US Army, US Air Force, US Navy,  Northrop Grumman
USMC
 Intelligence Agencies
 Orbital Sciences
– CIA, NIMA, NSA, NGIC  Battelle
 Dept. of Energy  TRW
– Sandia, Los Alamos, Idaho Falls,  TASC
Savannah River, Hanford
 Canadian Defense Research
 NASA (DRDC)
 Lockheed Martin  General Atomics/Burns and Roe
 Boeing
 NOKIA Telecommunications
 Raytheon
 Motorola
 FedEx
 MITRE
 USAA
 Booz-Allen & Hamilton  De Beers Diamond Mines (SA)
 SAIC  Peugeot/PSA Citroen
 Sprint  Israeli Aircraft Industries
 Bearing Point  Litton/PRC

3
 The Systems Engineering Dilemma: Complexity and Synchronization

Inputs With
People
The
With
With Their
People with
Design
Their
Their Perspective
“Design
with Specialty
Team
Churn”
Perspective
Tools
Specialty
and Skills
Processes
Skills Outputs
Inputs The
With Design
Producing “Design
Their
Their
Producing Their Team
Tools Churn”
Designs and
and
Designs Work
WorkProducts
Processes
and Products Outputs

Electrical
Electrical External
External Software
Software
Engineering
Engineering Teams
Teams Engineering
Engineering
Needs
And
Requirements Operational System

Systems
Systems
Quality
Quality Engineering
Engineering
Engineering
Engineering Safety
Safety
Preliminary Engineering
Engineering
System
Concepts Supporting
And Procurement
Procurement Documentation
Existing
Interfaces Test
Testand
andVerification
Verification
Mechanical
Mechanical
Engineering
Engineering

Manufacturing
Manufacturing

4
 Major Challenge of Systems Engineering

 Managing the complexity to achieve a harmonious solution.

– Many different types of efforts and information must be successfully
managed/executed to achieve project success
• Engineering Elements (Requirements, Functionality, Architecture, System
Resources, etc.)
• Project Elements (WBS, Activities/Tasks, Products, Reviews, Processes,
Budgets, Schedules, etc.)
• Interconnectivity: Elements are related to and affect one another
 Complexity creates Challenges
– Integration Challenge
• How to keep team efforts integrated?
– Consistency Challenge
• How to keep engineering (information, design, documentation, etc.)
consistent across the board?
– Availability Challenge
• How to keep the latest engineering accessible to the whole team?
• How to prevent engineering/decisions based on obsolete/dated
information?

5
 CORE Overview

 CORE – A Systems Engineering Technology

– Developed to support the People who implement the Systems
Engineering Methodology
• Analyze, Decompose and Allocate System Requirements
– Validate Requirements
– Requirements Management  Requirements Engineering
• Define System Behavior
– Functionality
– Operations
• Define System Architecture
– Internal and External Interfaces
– Subsystems/Assemblies/Components
• Define System Verification and Validation
– Verification Requirements
– Verification Planning (Events and Resources)
– Designed to meet the Systems Engineer’s Challenges
6
 System Engineering Process

Behavior Domain
Source Requirements Domain
Originating requirements
trace to behavior

verified by CORE
Repository Behavior is allocated to
physical components
V&V Domain Architecture Domain

verified by

verified by

Originating requirements
trace to physical components
7
 An Iterative System Engineering Process
Primary Concurrent Engineering Activities At Each Layer
Originating Behavior Synthesis/ Design
Requirements Analysis Architecture V&V
Analysis
Layer 1
(Draft 1)
Source System Design Database Specification & Report Generation
Documents
Iterate as Required When Layer Completed

Behavior Synthesis/ Design

Initial Requirements
for this layer are Analysis Architecture V&V
embodied in the
model passed from
Layer 2
(Draft 2)
and

the prior layer

and

System Design Database Specification & Report Generation

Iterate as Required When Layer Completed

Behavior Synthesis/ Design

Initial Requirements Architecture V&V
Analysis
for this layer are
embodied in the
Layer n
model passed from Accept H andover
From Prior Shift
LP
7

Process Claim Quiting tim e?

no

OR LP Leave Workplace (Final

the prior layer
Specs)
ye s H andover to N ext
LE
Shift

System Design Database Specification & Report Generation

CORE supports a disciplined, iterative approach to

systems definition. 8
 CORE Overview - System Engineering
Capabilities

Requirements Analysis and Management Design and Implementation

 Requirements Capture  Physical Architectural Modeling
 Requirements Analysis  Functional Modeling
 Requirements Traceability  Operational Scenarios
 Requirements Issues and Risks  Interfaces – External and Internal
 System Integration
 System Issues and Risks

CORE
Repository
Verification and Validation Document Generation
 Verification Requirements Development  System Specifications
 Verification Planning and Status  Interface Control Documents
 Test Procedure Development  RFP Responses and Proposals
 Test Configuration Development  Requirements Traceability Reports
 Verification Issues and Risks

9
 CORE Overview – The CORE Repository

CORE
Repository

 Centralized repository or
database
 Accessible to engineering
team
 Comprised of classes of
elements and elements
themselves
 Elements have attributes
 Elements can have
relationships with other
elements
 Data in repository can be
viewed and manipulated in
various ways

Database Editor
10
 CORE Overview – The CORE Repository
Element

Systems Relationships
Engineering
CLASSES

 Document
 System
 Components
 Functions
 Interfaces
 Constraints
 Requirements
 Risks
 Issues
 Etc. Attributes

This ‘Database Editor’ view allows browsing of all system elements,

Relationships, and attributes. 11
 CORE Overview – Engineering Element Example

Element Name

Other Element This element, “ATC Draft

Attributes Specs-7.23.90”, documents
these six requirement
elements.

Element
Relationships

Element Editor
12
 Example: System Requirements Model

ATC.Draft.
Specs-7.23.90

Document
Original
Requirements
documents documents documents documents documents documents
1.0 2.0 3.0 4.0 5.0 6.0

System System
Overall ATC Mission Prime Mission ATC Efficiency
Definition Boundary

OriginatingR... OriginatingR... OriginatingR... OriginatingR... OriginatingR... OriginatingR...

incorporates incorporates incorporates incorporates incorporates

5.1 5.2 5.4 5.5 5.6

Automated
Support
Aircraft
Separation
Obstruction
Separation
Air Traffic Flow
Information
Dissemination
Children
OriginatingR... OriginatingR... OriginatingR... OriginatingR... OriginatingR...
(decomposed)
Requirements
generates incorporates
5.2.CL

Approved Aircraft
Separation Separation.CL

Issue OriginatingR...

traces to Requirements
1.2.3
Predict Traced to
incursion of
restricted air Functionality
space
Function

allocated to decomposed by
1.1.1 1.2.3.1
Detect an
ATC
workstations
incursion of
restricted
Functionality
Component
airspace
Function
Allocated to
System
allocated to
1.1.1 components
ATC
workstations

Component

Date: Author:
3/28/2002 SE 007
Number: Name:
ATC.Draft.Specs-7.23.90
13
 CORE Overview - System Engineering
Capabilities

Requirements Analysis and Management Design and Implementation

 Requirements Capture  Physical Architectural Modeling
 Requirements Analysis  Functional Modeling
 Requirements Traceability  Operational Scenarios
 Requirements Issues and Risks  Interfaces – External and Internal
 System Integration
 System Issues and Risks

CORE
Repository
Verification and Validation Document Generation
 Verification Requirements Development  System Specifications
 Verification Planning and Status  Interface Control Documents
 Test Procedure Development  RFP Responses and Proposals
 Test Configuration Development  Requirements Traceability Reports
 Verification Issues and Risks

14
 CORE Overview – Functional/Operational
Modeling
Iterate

Option 1
IT IT
F3 F4

Process A
OR OR
F2

No
F6

Option 2
LP OR LP
F5
Yes
LE

AND AND
F1 F9
Replicate
With coordination

Process B
RP RP
F7 F8

CORE provides Functional Flow Block Diagrams (FFBDs) to

capture system functionality or operations.
Each Function is an element in the Repository.
15
 CORE Overview – Functional Interfaces

F1 F5

Stimulus
F1

Stimulus

AND Response AND

F5

F2
F2 F3 F4

F3

Enhanced Functional Flow Block Diagram

Response
F4

N2 Diagram

CORE provides Enhanced Functional Flow Block Diagrams

and N2 Diagrams to capture Functional Interfaces.
16
 CORE Overview – Functional/Operational
Modeling and Discrete Event Simulation
# customers

F.1
customer
IT Customer IT
Arrives

customer

# customers

F.2

Place Order

F.4
service area
IT AND AND Assemble IT
Order

F.3

Accept Order

food

# customers

F.5 F.6
svc. customer
AND IT IT AND
Take Food Leave line

customer
and food

# customers

F.8
yes
0.75 Eat

F.7 F.9
eating
IT OR IT
kill Eat In? Leave

no
0.25

F.12
cook
Cook Burgers

F.10 F.11
kitchen
LP Wait To Check Check burger OR LP

System behavior model defines

Burgers Supply

no cook

architecture of simulation model

CORE executes FFBDs in its Discrete Event Simulator allowing

dynamic analysis of functional models and requirements.
17
 CORE Overview – System/Architecture
Modeling
0

Simple Air
Traffic Control
System

System

1 3

Sector
Command Comm
Center

Component Component

1.1 1.2 1.3 1.4

Sector
Center Support
ADP Command Local Comm
Personal
Facility

Component Component Component Component

1.1.1 1.1.2

ATC
Main Computer
workstations

Component Component

See Next Slide. Sensors

Component

2.1 2.2

EnRoute Terminal
Radars Radars

Component Component

The System Architecture or System Hierarchy view shows the Date:

Number:
5/28/2002
Author:

Name:
Engineer 1

0 Simple Air Traffic Control System

breakdown of the system.

18
 CORE Overview – System/Architecture
Modeling

Attributes of
this system
component.

Relationships to other elements.

A different view of the same element – it’s attributes and

relationships to other elements in the system model. 19
 CORE Overview – System Interfaces

Cabin Air Return

Cabin Air Supply

Data (Front Panel) RS-232

Data (Primary)

Data (Secondary)
See Next Slide.
Electrical Bond
Animal Habitat System External System
Av Air Supply

Av Air Return

The “Open Circle” on

the interface indicates that
the interface connects through
Power (Front Panel)
the Top-Level System to a
subsystem. Power (Primary)

Power (Secondary)

System Component

This Interface or Physical Block Diagram is automatically generated

by CORE based on the data in the repository.
20
 CORE Overview – System Interfaces

Interface Name

Interface Description

Interface Connectivity

All things that appear on any diagram are elements in the Repository.

21
 CORE Overview – System Interfaces

Data (Front Panel) Connector

Component

Data (Front Panel)...

Data (Primary) Connector

Data (Pri...
Component

Data (Secondary)
Data (Secondary) Connector
External System

Component
Component

Environmental Control Subsystem Data (Secondary) Interface Main Processor Assembly

Component CP1 ...

Component

TD -...

T6 -...

T4 -...

T3 -...
Microprocessor Assembly #1
T1 -...

F3 -...

F1 -...

Component

T8 -...

T7 -...

T5 -...
Microprocessor Assembly #2
T2 -...

F4 -...

F2 -...

Component

Date: Author:
3/7/2002 Administrator
Number: Name:
Command and Data Handling Subsystem
22
 CORE Overview - System Engineering
Capabilities

Requirements Analysis and Management Design and Implementation

 Requirements Capture  Physical Architectural Modeling
 Requirements Analysis  Functional Modeling
 Requirements Traceability  Operational Scenarios
 Requirements Issues and Risks  Interfaces – External and Internal
 System Integration
 System Issues and Risks

CORE
Repository
Verification and Validation Document Generation
 Verification Requirements Development  System Specifications
 Verification Planning and Status  Interface Control Documents
 Test Procedure Development  RFP Responses and Proposals
 Test Configuration Development  Requirements Traceability Reports
 Verification Issues and Risks

23
 CORE Overview: Verification & Validation
Planning

Requirements
Document #1
Requirement Source
Document

documents documents

Requirement 1 Requirement 2 Source Requirement

OriginatingRequi... OriginatingRequi...

generates traces to traces to

Traceability
Issue 1 Function 1 External Interface 1
Design/Implementation
Issue Function Link

allocated to verified by

Verification Requirement
Verification
Subsystem 1
Requirement 1

Component VerificationRequi...

satisfied by

Verification Event 1 Verification Event

VerificationEvent

defined by uses configuration

Test Procedure Test Procedure 1

Test Configuration
1 Test Configuration
TestProcedure TestConfiguration

formed by formed by formed by formed by

Subsystem 1 External Interface 1 Test Enviroment Test System

Component Link System System

24
 Program and Project Management

Project X Team
Organizational Model
ResponsibleOrga...

consists of consists of consists of

Systems Test Engineering

Work Breakdown Structure

Project Group
Engineering Group Group

ResponsibleOrga... ResponsibleOrga... ResponsibleOrga... Project X

Project
consists of consists of consists of consists of
includes includes includes includes includes
WP.1 WP.2 WP.3 WP.4 WP.5
Requirements
Technical Solution Product Development
Development and Validation Verfication
Fluhr, Jody Long, David Macdonald, Pat Plimpton, James
Management
Development and Integration

WorkPackage WorkPackage WorkPackage WorkPackage WorkPackage

ResponsibleOrga... ResponsibleOrga... ResponsibleOrga...

accomplishes ResponsibleOrga...
includes includes accomplishes includes
1.1 1.2 4.1

Work Package 1 Requirements Work Package 4

Requirement Analysis Customer Reviews
Integrated Process Management Integrated Process

Activity Task Task Activity Task

1.1.1
includes

Requirements
1.1.2
includes
4.1.1
includes
4.1.2
includes
4.1.3
includes
Project Functional Flow Model
Requirements System Requirements Preliminary Design Assembly 1.1
Extraction from Critical Design Assembly
Review 1.1 Test
Decomposition Review Review Integration Process Process
Requirements Sources
Task Task Task Task Task

accomplishes
1.1.1
Requirements AND AND Subsystem 1 Subsystem 1 Test
Extraction Process Integration Process Process
Flow
Activity

inputs outputs Design

Acceptance
Assembly 1.2 Assembly 1.2 Test
Individual Integration Process Process
Requirements Sources
Requirements

Product Product

Top-Level
Ref. Proceed to Product AND AND Top-Level R
Verification
Development Integration Process
Process

CORE’s Systems Engineering

Methodology and Capabilities Assembly 2.1
Integration Process
Assembly 2.1 Test
Process

can be applied to project AND AND Subsystem 2 Subsystem 2 Test

engineering.
Integration Process Process

Assembly 2.2 Assembly 2.2 Test

Integration Process Process

Refer to ECS Case Study

25
 CORE Overview - System Engineering
Capabilities

Requirements Analysis and Management Design and Implementation

 Requirements Capture  Physical Architectural Modeling
 Requirements Analysis  Functional Modeling
 Requirements Traceability  Operational Scenarios
 Requirements Issues and Risks  Interfaces – External and Internal
 System Integration
 System Issues and Risks

CORE
Repository
Verification and Validation Document Generation
 Verification Requirements Development  System Specifications
 Verification Planning and Status  Interface Control Documents
 Test Procedure Development  RFP Responses and Proposals
 Test Configuration Development  Requirements Traceability Reports
 Verification Issues and Risks

26
 CORE Overview – Document Generation

Number Name Description traces to

OR.1 Continuous The Information Management System shall provide C.1 Continuous Operation
Support continuous real-time support to the customers and the
collection systems.
OR.2.1 Accept Requests The system shall accept information requests from 1 Accept And Format Request
certified customers.
OR.2.2 Retain Inventory The system shall retain an inventory of previously 2 Check Product Inventory
collected data/products and provide them to users, if
8 Put Product In Inventory
appropriate..
9 Get Product From Inventory
OR.2.3 Control Multiple The system shall control multiple collectors and multiple 4 Determine Collector Mix
Collectors types of collectors.
6 Task Collectors
OR.2.4 Maximum Staff The system shall be staffed at a maximum of 25 personnel
on any shift
OR.2.5 Provide The system shall provide feedback on the customer's 5 Notify User Of Estimated Schedule
Feedback request within twenty four hours.
PI.1 Provide Feedback
OR.2.6 Prioritize The system shall provide a means of prioritizing the 3 Prioritize Request
Requests customer's requests.
OR.2.7.1 Monitor Self The system shall monitor its own performance. 11 Evaluate Products vs. Request
Performance
OR.2.7.2 Assess Self The system shall assess its own performance. 11 Evaluate Products vs. Request
Performance
12 Report Deficiencies And
Recommendations

The content of documents are automatically generated by CORE

based on the data in the repository.

27
 COREscript and API

 Scripting language provided in CORE

– Object Oriented Query Language
– Document/Report Generation
• MS Word compatible (Rich Text Format)
• MS Excel compatible
• HTML
• Text
• Over 30 open-source reports (System Specifications, Interface
Specifications, etc.) are provided
– Query and Analysis
 Application Program Interface
– Provides access to Engineering Repository information by
external applications
– Automation of information exchange with applications such as
PDM, DOORS, etc.
28
 The Total Process and Synchronization
C.1

Perform Customer
Functions

Source Requirements Requirements Function/

Domain trace to products status requests

ORD.1
behavior
AND
0

Operate Intelligence
AND
Behavior Domain
Intelligence Information System
Information System
Source Require...
Document

documents documents documents data tasking

OR.1 OR.2 SYS.1

Specific
Requirements
Continuous Support
Intelligence
Information System
C.2 Behavior is
OriginatingRequir... OriginatingRequir... System Perform Collector
Functions
allocated to
OR.1.1
incorporates
OR.1.2
incorporates
OR.1.3
incorporates
OR.1.4
incorporates
C.1
constrained by
physical
components
Behavior
Control Multiple Continuous
Accept Requests Retain Inventory Maximum Staff
Sensors Operation
Date: Author:
OriginatingRequir... OriginatingRequir... OriginatingRequir... OriginatingRequir... Constraint
October 27, 1997 System Engineer

I.1
generates
R.1
causes
Analysis Number:
U.1
Name:
Context (Root Function For Universe)

Media of Requests Staffing Per Shift

Issue Risk

Date: Author:
August 3, 1996 System Engineer
Number:
ORD.1
Name:
Intelligence Information System Source Requirements Source Architecture Architecture Domain
Requirement Analysis
s Analysis C.0

Universe

verified by External System

built from built from built from

Design V & V C.1 C.2 SYS.1

V&V Domain Customers Collectors

Intelligence
Information System

External System External System System

Process
Date: Author:
Resource MIPS 5 August 4, 1996 System Engineer
0 Number: Name:

Domain
Function Detect & Initiate Track

Function Threat Track

C.0 Universe
Function (With Exits) Discrimina

Function Request Intercept

Function Perform Intercept

Function Assess Kil

verified by
0 10 20 30 40 50 57.0 verified by
Requirements trace to
physical components

29
 CORE Deployment Options

Workstation CORE2net
Enterprise
Collaborative
environment at the
Se product, project, or Intranet
gm enterprise level
en
ts
Up
da
tes
Integrated application
for small teams or on-
site modeling/review
Internet Web browser
access enabling
collaboration at the
enterprise level and
beyond

30
Backup

31
 CORE Deployment Options – Workstation

 CORE Workstation
– Fully functional, single-user version of CORE
• Self-Contained Database Management System
• Executes on standalone computer workstation
– Databases can be exported and imported
– Operates in conjunction with CORESim Product
• CORESim provides Discrete-Event Simulation capability
– System Requirements
• Windows 95/98/Me or Windows NT/2000/XP
• 300 MHz processor or higher
• 128 MB RAM
• 80 MB available hard disk space

32
 CORE Deployment Options – Enterprise

 CORE Enterprise
– Client-Server Version of CORE
– Provides scalability for project teams
– Provides access to engineering repository from clients on local-
area network
– Enterprise Server System Requirements
• Windows NT/2000/XP (Professional or Server Additions)
• 10BaseT Network (or better)
• 128 MB RAM
• 300 MHz CPU or higher
– Enterprise Client System Requirements
• Windows 95/98/Me or Windows NT/2000/XP
• 300 MHz processor or higher
• 128 MB RAM
• 80 MB disk free space
• TCP/IP protocol LAN access to Enterprise Server

33
 CORE Deployment Options – COREsim

 COREsim
– Adds Discrete Event Simulation capability to CORE
– Dynamically interprets behavior models (FFBDs)
– Utilized to identify timing, resource utilization and model
inconsistencies
– System Requirements
• No additional resources required

34
 CORE Deployment Options – CORE2net Web
Server

 CORE2net Enterprise Web Server

– Allows any workstation with a web browser and internet access
to Engineering Repository on Enterprise Web Server
– Operates in Enterprise Configuration Only
– Requires user name and password (same as Workstation and
Enterprise)
– Web-based html interfaces
• Predefined views and queries
• Customizable html interfaces can be developed and deployed

35
 CORE Deployment Options – CORE2net

 CORE2net allows users to

access the CORE Engineering
Repository on the Enterprise
Server using the Internet
 Provides browsing capability
 Authorized users can change
element information
 Execute queries or generate
views (see next slide)

36
CORE Deployment Options – CORE2net

37
Thank You for Attending.

Jody H. Fluhr
[email protected]
502.995.8895

Vitech Corporation Phone: 703.883.2270

www.vitechcorp.com

38