1 Systems Engineering CORE ® - A Model Based Approach January, 2004 Jody H. Fluhr Vitech...

11

Systems Engineering

CORE® - A Model Based Approach

January, 2004

Jody H. FluhrVitech Corporation

[email protected]

502.995.8895

22

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

33

Over 250 Clients in 14 Countries

DoD– US Army, US Air Force, US Navy,

USMC Intelligence Agencies

– CIA, NIMA, NSA, NGIC Dept. of Energy

– Sandia, Los Alamos, Idaho Falls, Savannah River, Hanford

NASA Lockheed Martin Boeing Raytheon FedEx MITRE Booz-Allen & Hamilton SAIC Sprint Bearing Point

UDLP Northrop Grumman Orbital Sciences Battelle TRW TASC Canadian Defense Research

(DRDC) General Atomics/Burns and Roe NOKIA Telecommunications Motorola USAA De Beers Diamond Mines (SA) Peugeot/PSA Citroen Israeli Aircraft Industries Litton/PRC

44

The Systems Engineering Dilemma: Complexity and Synchronization

PreliminaryPreliminarySystem System

ConceptsConceptsAndAnd

Existing Existing InterfacesInterfaces

InputsInputsInputsInputs

Needs Needs AndAnd

RequirementsRequirements Operational SystemOperational System

OutputsOutputsOutputsOutputs

Supporting Supporting DocumentationDocumentation

The “Design Churn”The “Design Churn”The “Design Churn”The “Design Churn”

ElectricalEngineeringElectrical

Engineering

ManufacturingManufacturing

Test and VerificationTest and Verification

MechanicalEngineeringMechanicalEngineering

SystemsEngineering

SystemsEngineering

SoftwareEngineeringSoftware

Engineering

QualityEngineering

QualityEngineering Safety

EngineeringSafety

Engineering

ProcurementProcurement

ExternalTeams

ExternalTeams

People with Specialty SkillsPeople with Specialty SkillsPeople with Specialty SkillsPeople with Specialty SkillsWith Their PerspectiveWith Their PerspectiveWith Their PerspectiveWith Their PerspectiveWith Their Tools and ProcessesWith Their Tools and ProcessesWith Their Tools and ProcessesWith Their Tools and ProcessesProducing Their Designs and Work ProductsProducing Their Designs and Work ProductsProducing Their Designs and Work ProductsProducing Their Designs and Work ProductsDesign TeamDesign TeamDesign TeamDesign Team

55

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?

66

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

77

CORECORERepositoryRepository

System Engineering Process

Source Requirements Domain

Architecture Domain

Behavior Domain

V&V Domain

verified by

verified by

Originating requirementstrace to behavior

Originating requirementstrace to physical components

Behavior is allocated tophysical components

verified by

88

An Iterative System Engineering Process

Primary Concurrent Engineering Activities At Each Layer

SourceDocuments

Layer 1(Draft 1)

Layer 2(Draft 2)

Layer n(Final

Specs)

andand

Behavior Analysis

Synthesis/ Architecture

Design V & V

System Design Database Specification & Report Generation

Iterate as Required When Layer Completed

Iterate as Required When Layer Completed

Originating Requirements Analysis

Behavior Analysis


Design V & V


Behavior Analysis


Design V & V


no

yes

Accept HandoverFrom Prior Shift

LP

7

Process Claim Quiting time?

Handover to NextShift

LE

OR LP Leave Workplace

Initial Requirements for this layer are embodied in the model passed from the prior layer

Initial Requirements for this layer are embodied in the model passed from the prior layer

CORE supports a disciplined, iterative approach to CORE supports a disciplined, iterative approach to systems definition.systems definition.

99


CORE Overview - System Engineering Capabilities

Requirements Analysis and Management

Verification and Validation

Design and Implementation Requirements Capture Requirements Analysis Requirements Traceability Requirements Issues and Risks

Physical Architectural Modeling Functional Modeling Operational Scenarios Interfaces – External and Internal System Integration System Issues and Risks

Verification Requirements Development Verification Planning and Status Test Procedure Development Test Configuration Development Verification Issues and Risks

Document Generation System Specifications Interface Control Documents RFP Responses and Proposals Requirements Traceability Reports

1010

CORE Overview – The 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 EditorDatabase Editor

CORERepository

1111

SystemsEngineeringCLASSES

Relationships

Attributes

Element

Document System Components Functions Interfaces Constraints Requirements Risks Issues Etc.

This ‘Database Editor’ view allows browsing of all system elements,This ‘Database Editor’ view allows browsing of all system elements,Relationships, and attributes. Relationships, and attributes.

CORE Overview – The CORE Repository

1212

CORE Overview – Engineering Element Example

Element NameElement Name

Other ElementOther ElementAttributesAttributes

Element Element RelationshipsRelationships

This element, “ATC Draft This element, “ATC Draft Specs-7.23.90”, Specs-7.23.90”, documentsdocumentsthese six requirement these six requirement elements.elements.

Element EditorElement Editor

1313

Example: System Requirements Model

documents documents documents documents documents documents

incorporates incorporates incorporates incorporates incorporates

generates incorporates

traces to

allocated to decomposed by

allocated to

ATC.Draft.Specs-7.23.90

Document

1.0

Overall ATC

OriginatingR...

2.0

SystemDefinition

OriginatingR...

3.0

SystemBoundary

OriginatingR...

4.0

Mission

OriginatingR...

5.0

Prime Mission

OriginatingR...

5.1

AutomatedSupport

OriginatingR...

5.2

AircraftSeparation

OriginatingR...

ApprovedSeparation

Issue

5.2.CL

AircraftSeparation.CL

OriginatingR...

1.2.3

Predictincursion ofrestricted air

space

Function

1.1.1

ATCworkstations

Component

1.2.3.1

Detect anincursion ofrestrictedairspace

Function

1.1.1

ATCworkstations

Component

5.4

ObstructionSeparation

OriginatingR...

5.5

Air Traffic Flow

OriginatingR...

5.6

InformationDissemination

OriginatingR...

6.0

ATC Efficiency

OriginatingR...

Date:3/28/2002

Author:SE 007

Number: Name:ATC.Draft.Specs-7.23.90

Children(decomposed)Requirements

RequirementsTraced toFunctionality

FunctionalityAllocated toSystemcomponents

OriginalRequirements

1414









1515

CORE Overview – Functional/Operational Modeling

Process B

ReplicateWith coordination

Process A

Option 2

Yes

No

Option 1

Iterate

F1AND

F2OR

ITF3 F4

IT

LPF5

F6

LE

OR LP

OR

RPF7 F8

RP

ANDF9

CORE provides Functional Flow Block Diagrams (FFBDs) toCORE provides Functional Flow Block Diagrams (FFBDs) tocapture system functionality or operations.capture system functionality or operations.

Each Function is an element in the Repository.Each Function is an element in the Repository.

1616

CORE Overview – Functional Interfaces

AND

F1 F5

F2 F3 F4

AND

Stimulus

Response

F1

F5

Response

Stimulus

F2

F3

F4

Enhanced Functional Flow Block Diagram

N2 Diagram

CORE provides Enhanced Functional Flow Block Diagrams CORE provides Enhanced Functional Flow Block Diagrams and Nand N22 Diagrams to capture Functional Interfaces. Diagrams to capture Functional Interfaces.

1717

kitchen

no cook

cook

customer

# customers

eatingkill

no0.25

yes0.75

# customers

service area

# customers

svc. customer

# customers

AND

IT

F.1

CustomerArrives

IT

IT AND

F.2

Place Order

F.3

Accept Order

AND

F.4

AssembleOrder

IT

IT

F.5

Take Food

F.6

Leave lineIT

IT

F.7

Eat In?

F.8

Eat

OR

F.9

LeaveIT

LP

F.10

Wait To CheckBurgers

F.11

Check burgerSupply

F.12

Cook Burgers

OR LP

AND

customer

food

customerand food

System behavior model defines architecture of simulation model

CORE Overview – Functional/Operational Modeling and Discrete Event Simulation

CORE executes FFBDs in its Discrete Event Simulator allowingCORE executes FFBDs in its Discrete Event Simulator allowingdynamic analysis of functional models and requirements.dynamic analysis of functional models and requirements.

1818

CORE Overview – System/Architecture Modeling

0

Simple AirTraffic Control

System

System

1

SectorCommand

Center

Component

1.1

ADP

Component

1.1.1

ATCworkstations

Component

2

Sensors

Component

2.1

EnRouteRadars

Component

2.2

TerminalRadars

Component

1.1.2

Main Computer

Component

1.2

Center SupportPersonal

Component

1.3

SectorCommand

Facility

Component

1.4

Local Comm

Component

3

Comm

Component

Date:5/28/2002

Author:Engineer 1

Number:0

Name:Simple Air Traffic Control System

The System Architecture or System Hierarchy view shows the The System Architecture or System Hierarchy view shows the breakdown of the system.breakdown of the system.

See Next Slide.See Next Slide.

1919

CORE Overview – System/Architecture Modeling

Attributes of Attributes of this system this system component.component.

Relationships to other elements.Relationships to other elements.

A different view of the same element – it’s attributes and A different view of the same element – it’s attributes and relationships to other elements in the system model.relationships to other elements in the system model.

2020

Power (Secondary)

Av Air Return

Data (Front Panel) RS-232

Av Air Supply

Data (Secondary)

Power (Front Panel)

Cabin Air Supply

Power (Primary)

Cabin Air Return

Electrical Bond

Data (Primary)

Animal Habitat System

System

External System

Component

CORE Overview – System Interfaces

See Next Slide.See Next Slide.

This Interface or Physical Block Diagram is automatically generated This Interface or Physical Block Diagram is automatically generated by CORE based on the data in the repository. by CORE based on the data in the repository.

The “Open Circle” onThe “Open Circle” onthe interface indicates thatthe interface indicates thatthe interface the interface connects throughconnects throughthe Top-Level System to athe Top-Level System to asubsystem.subsystem.

2121


Interface NameInterface Name

Interface DescriptionInterface Description

Interface ConnectivityInterface Connectivity

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

2222

T7 -...

F1 -...

F3 -...

T1 -...

T5 -...

F2 -...

CP1 ...

TD -...

T2 -...

T3 -...

T4 -...

F4 -...

T6 -...

T8 -...

Data (Secondary)

Dat

a (P

ri...

Dat

a (F

ront

Pan

el).

..

Data (Front Panel) Connector

Component

Data (Primary) Connector

Component

Data (Secondary) Connector

Component

Main Processor Assembly

Component

Microprocessor Assembly #1

Component

Microprocessor Assembly #2

Component

Environmental Control Subsystem

Component

External System

Component

Date:3/7/2002

Author:Administrator

Number: Name:Command and Data Handling Subsystem


Data (Secondary) InterfaceData (Secondary) Interface

2323









2424

CORE Overview: Verification & Validation Planning

documents documents

generates traces to traces to

allocated to verified by

satisfied by

defined by uses configuration

formed by formed by formed by formed by

RequirementsDocument #1

Document

Requirement 1

OriginatingRequi...

Issue 1

Issue

Function 1

Function

Subsystem 1

Component

VerificationRequirement 1

VerificationRequi...

Verification Event 1

VerificationEvent

Test Procedure 1

TestProcedure

Test Configuration1

TestConfiguration

Subsystem 1

Component

External Interface 1

Link

Test Enviroment

System

Test System

System

External Interface 1

Link

Requirement 2

OriginatingRequi...

Verification RequirementVerification Requirement

Verification EventVerification Event

Test ConfigurationTest ConfigurationTest ProcedureTest Procedure

Requirement SourceRequirement Source

Source RequirementSource Requirement

Design/ImplementationDesign/Implementation

Tra

ceab

ilit

yT

race

abil

ity

2525

Program and Project Management

consists of consists of consists of

consists of consists of consists of consists of

Project X Team

ResponsibleOrga...

Project Group

ResponsibleOrga...

Fluhr, Jody

ResponsibleOrga...

SystemsEngineering Group

ResponsibleOrga...

Long, David

ResponsibleOrga...

Macdonald, Pat

ResponsibleOrga...

Test EngineeringGroup

ResponsibleOrga...

Plimpton, James

ResponsibleOrga...

includes includes includes includes includes

accomplishes includes includes

includes includes

accomplishes

inputs outputs

accomplishes includes

includes includes includes

Project X

Project

WP.1

RequirementsDevelopment and

Management

WorkPackage

Work Package 1Integrated Process

Activity

1.1

Requirement Analysis

Task

1.1.1

RequirementsExtraction from

Requirements Sources

Task

1.1.1

RequirementsExtraction Process

Flow

Activity

Requirements Sources

Product

IndividualRequirements

Product

1.1.2

RequirementsDecomposition

Task

1.2

RequirementsManagement

Task

WP.2

Technical SolutionDevelopment

WorkPackage

WP.3

Product Developmentand Integration

WorkPackage

WP.4

Validation

WorkPackage

Work Package 4Integrated Process

Activity

4.1

Customer Reviews

Task

4.1.1

System RequirementsReview

Task

4.1.2

Preliminary DesignReview

Task

4.1.3

Critical Design Review

Task

WP.5

Verfication

WorkPackage

Ref. Proceed to ProductDevelopment

AND

AND

Assembly 1.1Integration Process

Assembly 1.1 TestProcess



AND Subsystem 1Integration Process

Subsystem 1 TestProcess

AND





AND Subsystem 2Integration Process

Subsystem 2 TestProcess

AND Top-LevelIntegration Process

Top-LevelVerification

Process

Ref.

DesignAcceptance

Organizational ModelOrganizational Model

Work Breakdown StructureWork Breakdown Structure

Project Functional Flow ModelProject Functional Flow Model

CORE’s Systems EngineeringCORE’s Systems EngineeringMethodology and Capabilities Methodology and Capabilities can be applied to project can be applied to project engineering.engineering.

Refer to ECS Case StudyRefer to ECS Case Study

2626









2727

Number Name Description traces to

OR.1 ContinuousSupport

The Information Management System shall providecontinuous real-time support to the customers and thecollection systems.

C.1 Continuous Operation

OR.2.1 Accept Requests The system shall accept information requests fromcertified customers.

1 Accept And Format Request

OR.2.2 Retain Inventory The system shall retain an inventory of previouslycollected data/products and provide them to users, ifappropriate..

2 Check Product Inventory

8 Put Product In Inventory

9 Get Product From Inventory

OR.2.3 Control MultipleCollectors

The system shall control multiple collectors and multipletypes of collectors.

4 Determine Collector Mix

6 Task Collectors

OR.2.4 Maximum Staff The system shall be staffed at a maximum of 25 personnelon any shift

OR.2.5 ProvideFeedback

The system shall provide feedback on the customer'srequest within twenty four hours.

5 Notify User Of Estimated Schedule

PI.1 Provide Feedback

OR.2.6 PrioritizeRequests

The system shall provide a means of prioritizing thecustomer's requests.

3 Prioritize Request

OR.2.7.1 Monitor SelfPerformance

The system shall monitor its own performance. 11 Evaluate Products vs. Request

OR.2.7.2 Assess SelfPerformance

The system shall assess its own performance. 11 Evaluate Products vs. Request

12 Report Deficiencies AndRecommendations

The content of documents are automatically generated by CORE The content of documents are automatically generated by CORE based on the data in the repository.based on the data in the repository.

CORE Overview – Document Generation

2828

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.

2929

The Total Process and Synchronization

ORD.1 Intelligence Information System Source Requirements

Date:August 3, 1996

Author:System Engineer

Number: Name:

documents documents documents

incorporates incorporates incorporates incorporates

generates causes

constrained by

ORD.1

IntelligenceInformation SystemSource Require...

Document

OR.1

SpecificRequirements

OriginatingRequir...

OR.1.1

Accept Requests


I.1

Media of Requests

Issue

OR.1.2

Retain Inventory


OR.1.3

Control MultipleSensors


OR.1.4

Maximum Staff


R.1

Staffing Per Shift

Risk

OR.2

Continuous Support


SYS.1

IntelligenceInformation System

System

C.1

ContinuousOperation

ConstraintDate:

October 27, 1997Author:

System Engineer

Number:U.1

Name:Context (Root Function For Universe)

AND

C.1

Perform CustomerFunctions

0

Operate IntelligenceInformation System

C.2

Perform CollectorFunctions

AND

products requests

data

status

tasking

Date:August 4, 1996

Author:System Engineer

Number:C.0

Name:Universe

built from built from built from

C.0

Universe

External System

C.1

Customers

External System

C.2

Collectors

External System

SYS.1

IntelligenceInformation System

System

Architecture Domain

Requirements trace to

behavior

Requirements trace to physical components

Function Assess Kill

Function Perform Intercept

Function Request Intercept

Function (With Exits) Discrimina

Function Threat Track

Function Detect & Initiate Track

Resource MIPS

0

5

0 10 20 30 40 50 57.0

Source Requirements Domain

Process Domain

Source Requirement

s Analysis

Behavior Analysis

Architecture

Analysis

Design V & VV&V Domain

Function/ Behavior Domain

Behavior is allocated to

physical components

verified by

verified by

verified by

3030

CORE Deployment Options

Workstation

Integrated application for small teams or on-site modeling/review

Updates

Segments

EnterpriseCollaborative

environment at the product, project, or

enterprise level

CORE2net

Internet

Intranet

Web browser access enabling

collaboration at the enterprise level and

beyond

3131

Backup

3232

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

CORE Deployment Options – Workstation

3333

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

CORE Deployment Options – Enterprise

3434

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

CORE Deployment Options – COREsim

3535

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

CORE Deployment Options – CORE2net Web Server

3636

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)

CORE Deployment Options – CORE2net

3737

CORE Deployment Options – CORE2net

3838

Thank You for Attending.

Jody H. Fluhr

[email protected]

502.995.8895

Vitech Corporation Phone: 703.883.2270

www.vitechcorp.com

Date post:	27-Mar-2015
Category:	Documents
Upload:	maria-gallegos
View:	250 times
Download:	1 times