© A. H. Levis INCOSE L. 4 - 1 C4ISR ARCHITECTURES AND THEIR IMPLEMENTATION CHALLENGES LECTURE 4 A...

© A. H. LevisINCOSE L. 4 - 1

C4ISR ARCHITECTURES AND THEIR IMPLEMENTATION CHALLENGES

LECTURE 4

A C4ISR ARCHITECTURE FRAMEWORK IMPLEMENTATION PROCESS

CASE STUDY

LEE WAGENHALSALEXANDER H. LEVIS


INTRODUCTION

• This illustrative example of the implementation process is based on a relatively new product developed by the Mobil Corporation called the Mobil SpeedPass.

• It is not an accurate description of the system – it has been created for the express purpose of illustrating the architecture design process

– Highlights the case where a new information technology providing a new capability is grafted on existing large legacy information systems.

– Assumes that some oil company (OilCo) has implemented a new system called FastPass. This example has been chosen in lieu of a DoD example because of its familiarity to a large audience.

• We start with a description of the goal of the system and proceed through the five stages presented in Chapter 3.


STAGE 0 INPUTS AND OPERATIONAL CONCEPT

• We assume that all of the initial research of Stage 0 has been completed and the input documents collected.

• Part of this process is the gathering of information about the Operational Concept.

• In this example, we assume that OilCo has been informed about a new technology that allows information to be encoded in a small device and be retrieved by a small radio signal.

• OilCo believes that such technology can be incorporated in gasoline pumps to make it more convenient for drivers to purchase gasoline via a credit card account.

– Drivers would need to sign up for the FastPass service and provide to OilCo the standard information contained on the credit card they normally use to purchase gasoline.

– OilCo would store this information in a Central database and issue the driver a FastPass device in the form or a rear window mounted tag or a key chain.

– The device would contain a unique code that OilCo could match to the credit card information in the central data base.


STAGE 1 (A1)

Operational Concept (AV1 and D1)

High Level Operational Concept Graphic (OV1)

Analyze

Operational

Concept

A11

Create

High Level

Operational

Concept

Graphic

A12

C4ISR Architecture Framework

Create

Textual

DescriptionA13

Elements, Organizations, Connections

Graphic

Text

FASTPASS: OPERATIONAL CONCEPT

SYSTEM BOUNDARY

Driver enters bayDrive Activates FastPass with deviceAfter Permission, driver selects grade of gas and fuels carDriver leaves

Gas Pump

LAN

WAN

Check credit informationAuthorize credit purchaseUpdate credit information

Turn on FastPass Light to show process is workingIssue Permission to fuelPrint ReceiptTurn off FastPass Light

FastPass light

Gas Station Office

OilCo Central Data Base

Retrieve Driver Information

L. 15 - 2Financial Institution

Driver


STAGE 2 (A2)

Organization List (D3)

Organizational Relationships (D4)

High Level Operational Concept Graphic (OV1)

Functional Decomposition

(IP21)

Create

Functional

DecompositionA21

Select

Organizations

A22

Determine

Organizational

Relationships

A23


Determine

Assets

A24 Define

Operational

Elements

A25Define

Operational

NodesA26

Organizational Intermediate

Products (IP-22)

Organizations

Operational Elements

Organizational Assets

Operational Nodes

Operational Concept (AV1 and D1)

Command Relationship Chart (OV4)

Universal Joint Task List (UJTL-D2)


STAGE 2 INPUTS

• Universal Joint Task List (UJTL)

– The architect selects the appropriate tasks from UJTL and constructs the hierarchy that is appropriate to the domain and that is consistent with the UJTL

• High Level Operational Concept Graphic and Narrative

• Operational Concept and Descriptions

• Organizational Lists and Descriptions

– Includes standard assets that typical organizations have

• Organizational Relationships

– Standard line and staff relationships


FUNCTIONAL DECOMPOSITION

UJTL1. Validate Accounts1.1 Sense FastPass1.2 Retrieve Driver

Information1.3 Validate Credit 2. Operate Pump2.1 Receive Authorization2.2 Dispense Gas2.3 Compute Cost of Sale

3. Prepare Billing3.1 Request Charge3.2 Print Receipt 3.3 Update Accounts

Operate FastPass GasStation System

Validate Accounts

Operate Pump

Prepare Billing

Sense FastPass

Retrieve Driver

Information

Validate Credit

Compute Cost of

Sale

Request Charge

Update Accounts

Print Receipt

Dispense Gas

Receive Authorization


Gas Pump

LAN

WAN



FastPass light

Gas Station Office



Financial Institution

Driver


ORGANIZATIONS

• Four organizational entities are considered as shown the table

• Each organizational entity has assets that are the basis for systems in the systems view:

– The FastPass central data base is maintained by OilCo that manages the FastPass system;

– The Gas Station has a pump, gas, and the electronic ledger for recording sales of gasoline;

– The Financial Institution that issue the credit cards used by the Drivers through the FastPass system, and the Driver.

Organization Assets

OilCo FastPass Central Data Base

Gas Station Pump, Gas, Ledger, Office Database

Financial Institution Financial Account Database

Driver FastPass Account, Credit Account, FastPass Device


OPERATIONAL NODES AND ELEMENTS

• The architect determines operational nodes and elements. They will be used to create the Operational Node Connectivity Description (OV – 2)

• Operational Nodes and Elements are determined with the help of the organizations and the operational concept graphic

• Operational Nodes contain one or more Operational Elements

Operational Node Operational Elements

Driver Driver

Gas Station Pump, Gas Station Office

OilCo OilCo

Financial Institutions Financial Institution


COMMAND RELATIONSHIP CHART (OV-4)

• The Command Relationship Chart depicts direct control and coordination relationships between the organizations selected

• OilCo provides a franchise to the Gas Station and provides the FastPass account to the Driver. Both the Driver and the Gas Station have accounts with the Financial Institution. The Driver and the Gas Station Interact with each other. These relationships are depicted in the Command Relationship Chart

Driver Gas Station

Interacts


OilCo

Provides FastPassProvides AccountProvides Franchise


STAGE 3

Textual Description ofDoctrine, Tactics and

Operational Procedures (D5)

Functional

Decomposition (IP21)

Need Lines (IP-31)

Initial Physical Architecture (IP-32)

Develop

Activity

ModelA31P. 6

Develop

Dynamics

ModelA32

Determine

Need Lines

A36

Define

System

NodesA33


Organizational Intermediate Products (IP-22)

Determine

Systems,

Elements,

and

Components

A34

Allocate

Activities

A35P. 7

Define Links

A37

Systems/Functions (D8)

System Descriptions (D12)

Activity Model

Products

Operational State Transition Description (OV6b )

Activity Allocations (IP-33)

System Nodes

Systems,

Elements, and Components

Links

Operational Elements

Operational Nodes

Operational Nodes and Organizational Assets

Operational Elements and Nodes

States and Events (D7)


STAGE 3 INPUTS

• Doctrine, tactics, procedures, and practices (Domain)

• Functional Decomposition (Stage 2)

• States and Events that exist in the operational concept (Domain)

• System Descriptions including descriptions of System Functions for the types of systems (from the assets) that the organizations have (or will have)

• Organizational Descriptions and Intermediate Products from Stage 2

– Operational Elements

– Operational Nodes

– Assets


CREATE THE ACTIVITY MODEL (OV-5)

• External System Diagram can be used to capture the interactions of the system with the externalities as described in the Operational Concept

• Helps define the Context Diagram (A-0)

Operate FastPass

System

A0

Authorization_TransactionFastPass_Device

SelectionDisplay

Receipt

Purpose: To describe the operations of the Speed Pass SystemView Point: System Architect

Perform Driver

Activities

A-01

Provide Financial Services

A-02

Financial_Transaction

Bank_Transaction


CONTEXT DIAGRAM

• Easily derived if the External System Diagram is used

Operate FastPass System

A0

P. 2


SelectionDisplay

Receipt

Purpose: To describe the operations of the Speed Pass SystemView Point: System Architect


Bank_Transaction


A0 DIAGRAM

• Matches the Functional Decomposition


SelectionDisplay

Receipt

Validate Accounts

A1

P. 3

Operate Pump

A2

P. 4

Manage Sales

A3

P. 5

Dispensed _Gas_Data


Bank_Transaction

Bank_Transaction

Authorization_Transaction


A1 DIAGRAM - VALIDATE ACCOUNTS

FastPass_Device

DisplaySense FastPass

A11

Retrieve Driver

Information

A12

Validate Credit

A13

Driver Credit Account

FastPass ID



A2 DIAGRAM – OPERATE PUMP Authorization_Transaction

Selection

Display

Dispensed

_Gas_Data

Receive

Authorization

A21

Dispense

Gas

A22

Compute

Cost of Sale

A23


Dispensed_Gas_Data

“on”, grade, gallons

"off", grade, gallons

Gas_Pricing


A3 DIAGRAM – PREPARE BILLING

Receipt

Dispensed _Gas_Data

Request Charge

A31

Print Receipt

A32

Update Accounts

A33

Bank_Transaction

Bank_Transaction


LOGICAL DATA MODEL (IDEF1x) (OV-7)

FastPass_ID (FK)

SPEEDPASS_DEVICE

1

FastPass_IDNameReceipt_OptionDrive_Credit_Acct_Number (FK)

DRIVER_INFORMATION

Defines

Drive_Credit_Acct_Number

DRIVE_CREDIT-ACCOUNT

Quantity_ControlGrade

Transaction_Number (FK)Drive_Credit_Acct_Number (FK)

SELECTION

1

Cost_of_SaleDate_Time (FK)Gas_Station_Information (FK)Transaction_Number (FK)Drive_Credit_Acct_Number (FK)

Quantity_Control (FK)Grade (FK)

DISPENSED_GAS_DATA

1 11

Cost_of_Sale (FK)Transaction_Number (FK)Drive_Credit_Acct_Number (FK)

Date_Time (FK)Gas_Station_Information (FK)

RECEIPT

1

Used_to_compute

Used_For

Included-in

Display-IDDisplay_Content

DISPLAY

Triggers

Triggers

Date_TimeGas_Station_Information

Pricing

GAS_PRICING

Used to Compute

Transaction_NumberDrive_Credit_Acct_Number (FK)

FINANCIAL_TRANSACTION

P

Transaction_Type

Transaction_Number (FK)Drive_Credit_Acct_Number (FK)

Approval

AUTHORIZATION_TRANSACTION

Enables

Triggers

Triggers

Required_For

Used_In

Provides_Data_For Transaction_Number (FK)Drive_Credit_Acct_Number (FK)

Cost_of_Sale (FK)Date_Time (FK)Gas_Station_Information (FK)

BANK_TRANSACTION

1

Purpose: To describe the data structure of the Fast Pass System


OV-6a: OPERATIONAL RULE MODEL

• Activation Rules are created for each activity that is at the lowest level of the decomposition

1. Validate Accounts1.1 Sense FastPass(A11)) R111: If FastPass present then FastPassID = decode(FastPass)

and Display = “Welcome to FastPass”; 1.2 Retrieve Driver Information(A12) R121: If FastPassID = DriverInformation.FastPassID then select(DriverCreditAccount) and Display “Validation Credit”; 1.3 Validate Credit(A13) R131: If DriverCreditAccount present and Authorization Number present then Financial Transaction = Type = 1, Driver Credit Account, Authorization Number, false) and Authorization Number = Authorization Number + 1;


RULE MODEL (CONTINUED)

2. Operate Pump 2.1 Receive Authorization (A21)R211: If Authorization Transaction.approval = True

Then send Authorization Number and Display = “Select Grade and Start Pumping”Else Display = “Please See Attendant”; 2.2 Dispense GasR221: If Authorization Transaction.approval = true and Selection =”on” Then (DispensedGasData. id = Authorization Transaction.driver credit number DispensedGasData.Grade = Selection.Grade; DispensedGas.QuantityControl = Selection.QuantityControl ) And Display = “The Grade of Gas is ”+ DispensedGas.Grade, “The dispensed Quantity of Gas is ”+ DispensedGas.QuantityControl, When Done, Turn off Pump”; 2.3 Compute Cost of SaleR231: If Selection = “off” and DispensedGasData present Then (DispensedGasData. id = Authorization Transaction.driver credit number DispensedGasData.Grade = Selection.Grade; DispensedGasData.QuantityControl = Selection.QuantityControl DispensedGasData.cost =If grade = 1 then QuantityControl * price_RegularElse if grade = 2 then Quantity Control * price_MidgradeElse QuantityControl * price_HiTest) And Display = “Please Wait for Receipt”


RULE MODEL (CONTINUED)

3. Prepare Billing 3.1 Request Charge R321: If CostOfSale > 0 And Driver-Information.Pump-id = DriverCreditAccount Then Financial Transaction = GasStationAccount + DriverCreditAccount + Cost of Sale; 3.2 Print Receipt R321: If DispenseGasData present Then Receipt = Date + Gas Station ID + Gas Station Name + Gas Station Address + + Cost of Sale; Print Receipt 3.3 Update Account R331: If Bank Transaction present Then Update GasStation Account


OPERATIONAL STATE

TRANSITION DIAGRAM

(OV-6b)• Created for the overall

system

• Indicates basic states of the system and the events that causes the system to change states

• Describes the desired behavior of the system per the Operational Concept

Pump Is Idle

Validating CreditDo: Retrieve Driver

Information, ValidateCredit

Dispensing GasDo: Dispense Gas

Computing Cost of SaleDo: Compute Cost of Sale

Printing Receipt

Do: Print Receipt

cCar arrival[FastPass Driver]/Sense FastPass

Credit approved

/Activate Pump

Finish Fueling/Deactivate pump

Receipt printedCost of Sales calculated

Start

Credit disapproved

car arrival[Non FastPass Driver]


ALLOCATE ACTIVITIES

• Decide which activities the operational elements you selected will perform the leaf activities of the functional decomposition

Operational Element Activities


(Update Account)(Validate Credit)

Gas Station Office Update Accounts

OilCo Retrieve Driver Information

Pump

Sense FastPassRequest ChargeReceive AuthorizationDispense GasPrint ReceiptCompute Cost of SaleValidate Credit


SYSTEMS, ELEMENTS, AND FUNCTIONS

• The following type of information is used to allocate operational activities to system functions

System Element Functions Driver FastPass Tag Provide FastPass Tag

Select Option FastPass Sensor Sense FastPass Tag and Decode

FastPass ID Pump Control Unit Control Operation Mode

Request Authorization Request Charge

Message Display (at Pump) Display Message Receipt Printer Print Receipt Calculator Compute Cost of Sale Throttle Valve Dispense Gas

Pump

Communication Unit Receive/ Transmit Signal Sales Database Record Transaction Gas Station Office

Database Communication Unit Receive/ Transmit Signal FastPass Central Database Retrieve Driver Information FastPass Central

Database (OilCo) Communication Unit Receive/ Transmit Signal Account Database Issue Authorization

Manage Database Financial Institutions’ Database Communication Unit Receive/ Transmit Signal


ALLOCATION OF OPERATIONAL ACTIVITIES TO SYSTEM FUNCTIONS

• For each leaf activity of the functional decomposition, decide which system element function(s) will be used to perform the activity

Activities System Functions Sense FastPass Provide FastPass Tag

Sense FastPass Tag and Decode FastPass ID Retrieve Driver Information Retrieve driver Information Validate Credit Request Authorization

Display Message Issue Authorization

Receive Authorization Dispense Gas

Dispense Gas Sense Selection Display Message Dispense Gas

Compute Cost of Sale Display Message Compute Cost of Sale

Request Charge Request Charge Print Receipt Print Receipt Update Account Record Transaction

Manage Database


CREATE NEEDLINES

• Needlines are directed arcs between operational nodes. They represent the need for the flow of operational information between operational nodes. Using the activities that have been allocated to operational nodes and the flow of information between those activities expressed in the IDEF0 model, indicate the operational nodes and needline flows on the following partially completed Operational Node Connectivity Description

Driver Gas Station Mobil

FinancialInstitution


INITIAL PHYSICAL ARCHITECTURE

• The system components and elements that will be used have been determined; assign them to system nodes.

• Using the knowledge gained from defining the needlines, create an initial physical architecture diagram showing the elements and components in system nodes and the communications links between those system elements, components and nodes.

– These links must be consistent with the allocation of activities to system functions and the operational information flows between the activities to be performed by the system functions you determined previously.


INITIAL PHYSICAL ARCHITECTURE

Driver

Financial Institution Database

SpeedPass Central Database

Gas Station Office Database

Radio link

Lan

Wan

PumpWan


STAGE 4 (A4)

Need Lines (IP-31)


Define Operational Information

ElementsA41

Create Operational Node

Connectivity Description

A42

Create Operational Information Exchange

MatrixA43

Create Operational Activity to System

Function Traceability Matrix A44

Create Systems Activity Models

A45P. 9



Activity Model

Products

Activities vs

Operational

Elements

Activities vs

Operational

Elements

Activities vs

System

Functions

Logical Data Model

System Activity

Model Products

Operational Node Connectivity Description (OV2)

Operation

Information

Elements (IP-41)

Operational Information Exchange Matrix (OV3)

Operational Activity to System Function

Traceability Matrix (SV5)

Operational Information Elements (D6)


STAGE 4 INPUTS

• Operational Information Elements (Domain)

• Activity model products (IDEF0, IDEF1x, Rule Model)

• Activity Allocations

• Needlines

• Initial Physical Architecture


OPERATIONAL INFORMATION ELEMENTS

• From the Allocation of Activities to Operational elements, and the flow of information captured in the IDEF0 model, create a table that identifies the Operational Element that is producing the Operation Information. Each Operation Information Element is a flow of information captured in the IDEF0 diagram at the leaf activity level.

Operational Information ElementProducing Operational

ElementAuthorization_Transaction (Approval) Financial institutions

Bank_Transaction (complete) Financial Institutions

Dispensed Gas Data Pump

Display Pump

Authorization_Transaction (request) Pump

Driver Information OilCo

Grade of Gas (Selection) Driver

FastPass Device Driver

Quantity Control (Selection) Driver

Receipt Pump

Bank_Transaction (request) Pump

FastPass ID Pump


OPERATIONAL NODE CONNECTIVITY DESCRIPTION (OV-2)

•The Operational Node Connectivity Diagram can be completed by adding the data flows from the Activity Model to the needlines and the activities to the operational nodes

Provide FastPassSelect Option

Driver

Gas Station

Pump OilCo

Activities


Gas Station OfficeFastPassSelection

DisplayReceipt

FastPass ID

Driver Information

Dispensed Gas_Data

Bank Transaction

ActivitiesUpdate AccountsSense FastPassReceive AuthorizationDispense GasCompute Cost of SaleRequest ChargePrint ReceiptValidate Credit

For GSO

For Pump

Authorization_Transaction (approval)Bank_Transaction Financial Institution

Activities

(Validate Credit)(Update Accounts)

Authorization_Transaction (Request)Bank_Transaction (request)


OPERATIONAL INFORMATION EXCHANGE MATRIX (OV-3)

• Using the activity model and OV 2 as a guide, complete the Operational Information Exchange Matrix. Note that the type and size (in bytes) of information or data and the media are indicated. This information is used to define messages in the Systems Architecture View

Information Description Information Source Information Destination Operational Information

Element Media Size Unit

Operational element

Activity Operational

element Activity

FastPass Device

Microwave

8 Number Driver N/A

Pump Sense FastPass

FastPass ID Data 8 Number Pump Sense FastPass OilCo Retrive Driver Information

Grade of Gas Data 1 Number Driver N/A Pump Dispense Gas Quantity Control

Data 10 Number Driver N/A Pump Compute Cost of Sale

Authorization Transaction (Approval)

Data 8 Number Financial institutions

Validate Credit Pump Receive Authorization

Banking Transaction

Data 10 Number Financial Institutions

(Update Accounts)

Gas Station Office

Update Accounts

Authoization Transaction (Request)

Data 8 Number Pump Validate Credi Financial Institution

(Validate Credit)

Request for Charge

Data 10 Number Pump Request Charge Financial Institution

Update Accounts

Driver Information

Data 9 Number OilCo Retrieve Driver Information

Pump Validate Credit Request Charge Print Receipt

Display Data 19 Number Pump Sense FastPass Operate Pump

Driver N/A

Dispensed Gas Data

Data 19 Number Pump Compute Cost of Sale

Gas Station Office

Update Accounts

Receipt Docu-ment

2x4”

Paper string

Pump Print Receipt Driver N/A


SYSTEM FUNCTIONALITY DESCRIPTION (SV-4)

• Activity Model based on system functions

• Either IDEF0 or Data Flow Diagrams can be used; we will illustrate DFD (advantage, explicit Data Stores)

• Suggest first creating the Context Diagram

• Then work bottom up

– Develop DFD of the system functions at the leaf level

– Aggregate these at an intermediate level and then aggregate the intermediate level into the context diagram


CONTEXT DIAGRAM


FastPass Device

Selection

Display

Receipt

Purpose: To describe the System Functions of the FastPass System View Point: System Architect

Driver Financial Institution


Bank_Transaction


Bank_Transaction


DFD OF PUMP FUNCTIONS

FastPass_Device

Selection

Display

Receipt


Bank_Transaction


Dispensed _Gas_Data

1.1 Sense

FastPass 2

FastPass_ID

Driver Information

1.2 Request

Authorization

1.4 Sense

Selection 1.5

Dispense Gas

1.6 Compute

Cost of Sale

1.7 Request Charge

1.8 Print Receipt

1.3 Display

Message


Driver

Selection

3

Dispensed Gas

Gas_Pricing


0 - DIAGRAM

• Aggregate lower level pages to form 0 - Diagram

FastPass_Device Selection

Display

Receipt

Driver Information

Dispensed _Gas_Data

Authorization_Transaction Bank_Transaction Authorization_Transaction

Bank_Transaction


Driver

FastPass_ID

FastPass Central Database

Driver Information

1 Perform Pump

System Functions

3 Record

Transaction

2 Retreive

Driver Information

Sales Database

Bank_Transaction

Gas_Pricing


OPERATIONAL ACTIVITY TO

SYSTEM FUNCTION

TRACABILITY MATRIX (SV-5)

Documents operational activity allocation

Operational Activities

System System Functions

Sense Fast Pass A11

Retrieve Driver Information A12

Validate Credit A13

Receive Authorization A21

Dispense Gas A22

Compute Cost of Sale A23

Request Charge A31

Print Receipt A32

Update Account A33

Driver Provide FastPass Tag

Select Option

Pump Sense FastPass Tag 1.1

Request Authorization 1.2

Display Message 1.3

Sense Selection 1.4

Dispense Gas 1.5

Compute Cost of Sale

1.6

Request Charge 1.6

Print Receipt 1.8

Gas Station Office

Database

Record Transaction

2

FastPass Central

Database


3

Manage Database Financial Institutions Database Issue

Authorization


PHYSICAL DATA

MODEL (SV-11)

Specifies Messages, Data Store Records, Display Content, etc.

Records Fields Format Selection Quantity Control

Grade of Gas Numeric(10) Numeric(1)

FastPass Device Data FastPass ID (Encrypted) Numeric(8) Dispensed Gas Driver Credit Account Number

Transaction_Number Quantity Control Grade of Gas

Numeric(8) Numeric(10) Numeric(10) Numeric(1)

Bank_Transaction Gas Station Office Account Status Cost of Sale Transaction_Number

Numeric(16) Boolean Numeric(10) Numeric(10)

Authorization_Transaction Transaction_Number Driver Credit Account Approval Content

Numeric(10) Numeric(10) Boolean

Dispensed Gas_Data Driver Credit Account Number Transaction_Number Cost of Sale Quantity Control Grade of Gas

Numeric(8) Numeric(10) Numeric(10) Numeric(10) Numeric(1)

Bank_Transaction.Request Driver Credit Account Gas Station Office Account Cost of Sale Transaction_Number

Numeric(16) Numeric(16) Numeric(10) Numeric(10)

Receipt Gas Station Name Gas Station Address Date Driver Credit Account Name Grade of Gas Quantity Control Cost of Sale

Char(40) Char(40) Numeric(6) Numeric(16) Char(40) Numeric(1) Numeric(10) Numeric(10)


PHYSICAL DATA MODEL (CONT’D)

Data Stores

Records Fields Format Driver Information (FastPass Central Data Base)

FastPass ID Name Driver Credit Account Number

Numeric(8) Char(40) Numeric(16)

Sales Data Base Gas Station Office Account Sales History

Numeric(16) Numeric(10)

Gas Station Office (Gas_Pricing)

Gas Station Office ID Gas Station Name Gas Station Address Gas Unit Price

Numeric(16) Char(40) Char(40) Numeric(10)

Display Records Fields Format Display Display ID

Message Numeric(2) Char(40)


STAGE 5 COMPLETE SYSTEM ARCHITECTURE VIEW PRODUCTS

System Descriptions (D12)

System Evolution Description (SV8)

System Interface Description (SV1)


Define System

Information Elements

A51

Define Communications

SystemsA53

P. 11

Create System Interface

DescriptionA54

Create System

Evolution Description

A55

Define Performance Parameter Set

A56

Create System Performance Parameter

MatrixA57


System Activity

Model Products


System Communications Description (SV2)

System2 Matrix (SV3)

System Information Exchange Matrix (SV6)

System Performance Parameter Matrix (SV7)

System Performance Attributes (D10)

Migration System (D11)

Create System Information Exchange

Matrix A52

Operation Information

Elements (IP-41)System Information

Elements (IP- 51)

Operational Node Connectivity Description (OV2)

Operational Information Exchange Matrix (OV3)

Communication Systems Description (D9)


SYSTEM INFORMATION ELEMENTS

• The following table is derived from the DFD and the systems that perform the functions in the DFD. It will be used to complete the System Information Exchange Matrix

System Name Content Media Data/Media Format

Security Frequency

Selection Data ASCII Plain Dynamic Driver FastPass Device Microwave Radio Signal Secure Dynamic FastPass ID Data ASCII Secure Dynamic Selection (Sensed) Data ASCII Plain Dynamic Dispensed Gas Data ASCII Plain Dynamic Dispensed Gas_Data

Data ASCII Plain Dynamic

Gas_Pricing Data ASCII Plain Dynamic

Authorization _Transaction (Request)

Data ASCII Secure Dynamic

Driver Information Data ASCII Secure Dynamic Bank_Transaction Data ASCII Secure Dynamic Receipt Document Text Plain Dynamic

Pump

Display (Message) Display Text Plain Dynamic Gas Station Office Database

Bank_Transaction Data ASCII Plain Dynamic


Driver Information Data ASCII Secure Dynamic

Authorization_ Transaction

Data ASCII Secure Dynamic Financial Institutions Database Bank_Transaction Data ASCII Secure Dynamic


LAN/WAN SELECTION

• Using the initial physical architecture and domain knowledge about message size and frequency, determine the type of communication service needed to provide the needed flow of information between system elements, components, and nodes

Driver




Radio link

Lan

Wan

Pump

Wan

10 Mbps TCP/IP

56K/T-1 Link

TCP/IP

56K/T-1 Link

TCP/IP


DEFINE INTERFACE TYPES

Status

• Existing Interface ---------------------S1

Security Classification

• Public Key------------------------------C1

• Plain------------------------------------- C2

Means

• Radio --------------------------------------------------------- M1

• 56 K link X.25------------------------------------------------M2

• T1 Link Frame Relay/ATM-------------------------------M3

• 10/100 Mbps LAN-------------------------------------------M4


SYSTEM INTERFACE DESCRIPTION (SV-1)

Gas Station Office

Database


T-1 link

Banking Support Node

LAN (10 Mbps, TCP/IP)

56K link

Gas Station Support Node

FastPass Service Support Node

Pump

Financial Institutions Database T-1 link

ATM Backbone (TCP/IP)

FastPass Device

Driver Node

Microwave


SYSTEM COMMUNICATIONS DESCRIPTION (SV-2)

Packet Switch (X.25)

ATM/Frame Relay ATM/Frame Relay

Router

56K

Ethernet

Router Router

Gas Station

Office

Database

Ethernet

Financial InstitutionDatabase

Ethernet

FastPass Central

Database

Terminal Terminal

Pump 1

T-1 link TCP/IP

Microwave

FastPass Device

T-1 link TCP/IP


SYSTEM2 MATRIX (SV-3)

Driver

Driver Pump

Pump C1 M1




Status Existing Interface ---------------------- S1

Security Classification Public Key ------------------------------- C1 Plain -------------------------------------- C2

Means Radio ------------------------------------ M1 56 K link X.25--------------------------- M2 T1 Link Frame Relay/ATM---------- M3 10/100 MBPS LAN--------------------- M4

S1 C1 M2, 3, 4

C1 M2, 3, 4




S1 C1 M2, 3, 4

S1 C1 M2


SYSTEM INFORMATION EXCHANGE MATRIX (SV-6)

Input System Function

Output

System Name

Content System Name

Content

Driver FastPass Device

Sense FastPass

Pump FastPass ID

Pump Driver Information

Request Authorization


Authorization Transaction

FastPass ID Pump Dispensed

Gas_Data

Display Message

Pump Message


Authorization Transaction

Driver Selection Sense Selection

Pump Selection

Pump Selection


Authoriza-tion.Approval

Dispense Gas

Pump Dispensed Gas

Pump Dispensed Gas_Data


Pump Dispensed Gas Data

Gas Pricing


Request Charge

Fin ancial Institution Data-base

Bank Transaction


SYSTEM INFORMATION EXCHANGE MATRIX (CONT’D)


Print Receipt Driver Receipt


Driver Information

Retrieve Driver Infor-mation

Pump Driver Information

Pump FastPass ID


Record Transaction

Gas Station DataBase

Bank Transaction


Bank Transaction

Input System Function

Output

System Name

Content System Name

Content

Note: This is not the complete matrix. The columns that specify the parameters of the system information elements have been omitted


SYSTEM PERFORMANCE PARAMETER MATRIX (SV-7)

• Essential for Evaluation

System Name

Performance Parameters

Base Line Objective

Pump FastPass detection accuracy

N/A

99%

FastPass Central

Database

Driver Information verification time

N/A Limit less than 3 seconds

Financial Institutions Database

Credit Validation Time

3 seconds N/A


SYSTEM EVOLUTION DESCRIPTION (SV-8)

Nationwide Distributed

FastPass Service System

Add Extended Products Service

(Gas, Grocery, Other Services)

Add Flexible Account Service

(Credit card, Debit card

V 1.0

+6 Mon +18 Mon +36 Mon +48 Mon

V 2.0 V 3.0 V 4.0 Legacy System

Area/Pro duct/Account

Limited FastPass

Service System

Add Nationwide Availability


SYSTEM TECHNOLOGY FORECAST (SV-9)

Technology Area & Capabilities

0-6 Months 6-12 Months 12-18 Months 18+ Months

Security Public key algorithm

Distributed Heterogeneous Database

Middleware and/or proprietary interface

Dynamic active DBMS

Satellite Communication

World wide DAMA (Demand Access Multiple Access) ground terminal migrate into WAN

OilCo Subscriber Roaming

System wide roaming across the boundary of home service area

International roaming across the boundary of domestic service area Heterogeneous DBMS

OPERATIONAL ARCHITECTURE VIEW PRODUCTS


Gas Pump

LAN

WAN



FastPass light

Gas Station Office




Driver


Gas Pump

LAN

WAN



FastPass light

Gas Station Office




Driver

Driver Gas Station

Interacts


OilCo


Driver Gas Station

Interacts


OilCo



SelectionDisplay

Receipt

Validate Accounts

A1

P. 3

Operate Pump

A2

P. 4

Manage Sales

A3

P. 5

Dispensed _Gas_Data


Bank_Transaction

Bank_Transaction


SpeedPass_ID (FK)

SPEEDPASS_DEVICE

1

SpeedPass_IDNameReceipt_OptionDrive_Credit_Acct_Number (FK)

DRIVER_INFORMATION

Defines

Drive_Credit_Acct_Number

DRIVE_CREDIT-ACCOUNT

Quantity_ControlGradeTransaction_Number (FK)Drive_Credit_Acct_Number (FK)

SELECTION

1

Cost_of_SaleDate_Time (FK)Gas_Station_Information (FK)Transaction_Number (FK)Drive_Credit_Acct_Number (FK)Quantity_Control (FK)Grade (FK)

DISPENSED_GAS_DATA

1 11

Cost_of_Sale (FK)Transaction_Number (FK)Drive_Credit_Acct_Number (FK)Date_Time (FK)Gas_Station_Information (FK)

RECEIPT

1

Used_to_compute

Used_For

Included-in

Display-IDDisplay_Content

DISPLAY

Triggers

Triggers

Date_TimeGas_Station_InformationPricing

GAS_PRICING

Used to Compute

Transaction_NumberDrive_Credit_Acct_Number (FK)

FINANCIAL_TRANSACTION

P

Transaction_Type

Transaction_Number (FK)Drive_Credit_Acct_Number (FK)Approval


Enables

Triggers

Triggers

Required_For

Used_In

Provides_Data_For Transaction_Number (FK)Drive_Credit_Acct_Number (FK)Cost_of_Sale (FK)Date_Time (FK)Gas_Station_Information (FK)

BANK_TRANSACTION

1

Purpose: To describe the data structure of the Fast Pass System

Pump Is Idle

Validating CreditDo: Retrieve Driver

Information, ValidateCredit

Dispensing GasDo: Dispense Gas

Computing Cost of SaleDo: Compute Cost of Sale

Printing Receipt

Do: Print Receipt

cCar arrival[FastPass Driver]/Sense FastPass

Credit approved

/Activate Pump

Finish Fueling/Deactivate pump

Receipt printedCost of Sales calculated

Start

Credit disapproved

car arrival[Non FastPass Driver]


Driver

Gas Station

Pump OilCo

Activities



DisplayReceipt

FastPass ID

Driver Information

Dispensed Gas_Data

Bank Transaction


For GSO

For Pump


Activities




Driver

Gas Station

Pump OilCo

Activities



DisplayReceipt

FastPass ID

Driver Information

Dispensed Gas_Data

Bank Transaction


For GSO

For Pump


Activities



Information Description Information Source Information Destination Operational Information

Element Media Size Unit

Operational element

Activity Operational

element Activity

FastPass Device

Microwave

8 Number Driver N/A

Pump Sense FastPass

FastPass ID Data 8 Number Pump Sense FastPass OilCo Retrive Driver Information

Grade of Gas Data 1 Number Driver N/A Pump Dispense Gas Quantity Control

Data 10 Number Driver N/A Pump Compute Cost of Sale

Authorization Transaction (Approval)

Data 8 Number Financial institutions

Validate Credit Pump Receive Authorization

Banking Transaction

Data 10 Number Financial Institutions

(Update Accounts)

Gas Station Office

Update Accounts

Authoization Transaction (Request)

Data 8 Number Pump Validate Credi Financial Institution

(Validate Credit)

Request for Charge

Data 10 Number Pump Request Charge Financial Institution

Update Accounts

Driver Information

Data 9 Number OilCo Retrieve Driver Information

Pump Validate Credit Request Charge Print Receipt

Display Data 19 Number Pump Sense FastPass Operate Pump

Driver N/A

Dispensed Gas Data

Data 19 Number Pump Compute Cost of Sale

Gas Station Office

Update Accounts

Receipt Docu-ment

2x4”

Paper string

Pump Print Receipt Driver N/A

SYSTEM ARCHITECTURE VIEW PRODUCTS

FastPass_Device Selection

Display

Receipt

Driver Information

Dispensed _Gas_Data

Authorization_Transaction Bank_Transaction Authorization_Transaction

Bank_Transaction


Driver

FastPass_ID


Driver Information

1 Perform Pump

System Functions

3 Record

Transaction

2 Retreive

Driver Information

Sales Database

Bank_Transaction

Gas_Pricing



Sense Fast Pass A11


Validate Credit A13


Dispense Gas A22


Request Charge A31

Print Receipt A32

Update Account A33


Select Option



Display Message 1.3

Sense Selection 1.4

Dispense Gas 1.5


1.6

Request Charge 1.6

Print Receipt 1.8

Gas Station Office

Database

Record Transaction

2

FastPass Central

Database


3


Authorization



Sense Fast Pass A11


Validate Credit A13


Dispense Gas A22


Request Charge A31

Print Receipt A32

Update Account A33


Select Option



Display Message 1.3

Sense Selection 1.4

Dispense Gas 1.5


1.6

Request Charge 1.6

Print Receipt 1.8

Gas Station Office

Database

Record Transaction

2

FastPass Central

Database


3


Authorization

Data Stores

Records Fields Format Driver Information (FastPass Central Data Base)

FastPass ID Name Driver Credit Account Number

Numeric(8) Char(40) Numeric(16)

Sales Data Base Gas Station Office Account Sales History

Numeric(16) Numeric(10)

Gas Station Office (Gas_Pricing)

Gas Station Office ID Gas Station Name Gas Station Address Gas Unit Price

Numeric(16) Char(40) Char(40) Numeric(10)

GasStationOffice

Database

FastPass CentralDatabase

T-1 link

BankingSupportNode

LAN(10 Mbps,TCP/IP)

56K link

Gas StationSupportNode

FastPass ServiceSupportNode

Pump

Financial InstitutionsDatabaseT-1 link

ATM Backbone(TCP/IP)

FastPass Device

Driver Node

Microwave

GasStationOffice

Database

FastPass CentralDatabase

T-1 link

BankingSupportNode

LAN(10 Mbps,TCP/IP)

56K link

Gas StationSupportNode

FastPass ServiceSupportNode

Pump

Financial InstitutionsDatabaseT-1 link

ATM Backbone(TCP/IP)

FastPass Device

Driver Node

Microwave



Router

56K

Ethernet

RouterRouter

Gas Station Office

Database

Ethernet

FinancialInstitutionDatabase

Ethernet

FastPassCentral

Database

TerminalTerminal

Pump1

T-1 linkTCP/IP

MicroWave

FastPass Device

T-1 linkTCP/IP



Router

56K

Ethernet

RouterRouter

Gas Station Office

Database

Ethernet

FinancialInstitutionDatabase

Ethernet

FastPassCentral

Database

TerminalTerminal

Pump1

T-1 linkTCP/IP

MicroWave

FastPass Device

T-1 linkTCP/IPT-1 linkTCP/IP

Driver

DriverPump

Pump C1 M1




StatusExisting Interface ----------------------S1

Security Classification Public Key------------------------------- C1Plain-------------------------------------- C2

MeansRadio ------------------------------------ M156 K link X.25--------------------------- M2T1 Link Frame Relay/ATM ---------- M310/100 MBPS LAN--------------------- M4

S1 C1 M2, 3, 4

C1 M2, 3, 4




S1 C1 M2, 3, 4

S1 C1 M2

Driver

DriverPump

Pump C1 M1




StatusExisting Interface ----------------------S1

Security Classification Public Key------------------------------- C1Plain-------------------------------------- C2

MeansRadio ------------------------------------ M156 K link X.25--------------------------- M2T1 Link Frame Relay/ATM ---------- M310/100 MBPS LAN--------------------- M4

S1 C1 M2, 3, 4

C1 M2, 3, 4




S1 C1 M2, 3, 4

S1 C1 M2

P u m p D i s p e n s e d G a s D a t a

P r i n t R e c e i p t D r i v e r R e c e i p t

F a s t P a s s C e n t r a l D a t a b a s e

D r i v e r I n f o r m a t i o n

R e t r i e v e D r i v e r I n f o r -m a t i o n

P u m p D r i v e r I n f o r m a t i o n

P u m p F a s t P a s s I D


R e c o r d T r a n s a c t i o n

G a s S t a t i o n D a t a B a s e

B a n k T r a n s a c t i o n

F i n a n c i a l I n s t i t u t i o n


I n p u t S y s t e m F u n c t i o n

O u t p u t

S y s t e m N a m e

C o n t e n t S y s t e m N a m e

C o n t e n t















O u t p u t

S y s t e m N a m e


C o n t e n t















O u t p u t

S y s t e m N a m e


C o n t e n t

System Name


Base Line Objective


N/A

99%

FastPass Central

Database





3 seconds N/A

System Name


Base Line Objective


N/A

99%

FastPass Central

Database





3 seconds N/A

Nationwide Distributed FastPass Service System

Add Extended Products Service

(Gas, Grocery, Other Services)

Add Flexible Account Service

(Credit card, Debit card

V 1.0

+6 Mon +18 Mon +36 Mon +48 Mon

V 2.0 V 3.0 V 4.0 Legacy System

Area/Pro duct/Account

Limited FastPass

Service System

Add Nationwide Availability

Technology Area& Capabilities





Dynamic active DBMS





International roaming across the boundary of domestic service areaHeterogeneous DBMS

Technology Area& Capabilities





Dynamic active DBMS





International roaming across the boundary of domestic service areaHeterogeneous DBMS


CONCLUSION

• The six stage process has been illustrated using the FastPass example

– A simple example for classroom purposes

– Illustrates important features of typical C4ISR Architectures

• It is one approach to developing the architecture products specified by the C4ISR Architecture Framework

• Alternative approaches are possible; the six stage process can serve as a template to ensure that the alternative approaches cover all needed steps and produce a complete architecture description


SYNTHESIS OF EXECUTABLE MODEL FROM STRUCTURED ANALYSIS BASED ARCHITECTURE

(Demonstration)

LEE W. WAGENHALS

DAESIK KIM

EXECUTABLE MODEL


CONSTRUCTION OF THE COLORED PETRI NETS

• To each IDEF0 model page corresponds a CPN model page.

– The CPN model has the same hierarchical structure as the IDEF0 model

• The activities in the IDEF0 diagram are converted to transitions:

– Decomposed activities are represented by substitution transitions that represent the CPN model page corresponding to the IDEF0 page of the decomposition

• ICOMs are converted to places with the corresponding color set associated with them


CONSTRUCTION OF THE COLORED PETRI NET

• Connect places to transitions with arcs, e.g.,

• Self loops may be introduced to account for:

– Data that are on a longer time scale than others

– Updates, ...

A1

A2

Data Data

t1 t2


CPN MODEL

TOP LEVEL: CORRESPONDS TO CONTEXT DIAGRAM

Inputs

Controls

OutputsDo

HS CondAAW#3

Scenario Driver

HS Scenario#7

Inputs


EXTERNAL SYSTEM DIAGRAM

Purpose: To describe the operations of the FastPass System View Point: System Architect


A0P. 2


SelectionDisplay

Receipt

Perform Driver Activities

A-01

Provide Financial Services

A-02


Bank_Transaction


DESIGN/CPN CONTEXT DIAGRAM

ColorSet

Place Name

Initial Marking


FAST PASS IDEF0 PROCESS MODEL

Purpose: Illustrate IDEF0 and the relationships between the different types of models: process, data and rule

Viewpoint: System Architect

CONTEXT DIAGRAM

Bank_Transaction

Selection

FastPass_Device Authorization_Transaction

Display


Receipt


A0P. 2

FIRST LEVEL OF DECOMPOSITION


Selection

Display

Receipt

Validate Accounts

A1P. 3

OperatePump

A2P. 4

PrepareBilling

A3P. 5

Dispensed _Gas_Data


Bank_Transaction

Bank_Transaction


L. 16 - 9

DESIGN/CPN FIRST LEVEL DECOMPOSITION

L. 16 - 10


DATA MODEL DEFINES COLORSETS

FastPass_ID (FK)

FASTPASS_DEVICE1

FastPass_ID Name Driver_Credit_Acct_Number (FK)

DRIVER_INFORMATION

Defines

Driver_Credit_Acct_Number

DRIVER_CREDIT-ACCOUNT

Quantity_Control Grade Transaction_Number (FK) Driver_Credit_Acct_Number (FK)

SELECTION1

Enables

Cost_of_Sale Date_Time (FK) Transaction_Number (FK) Driver_Credit_Acct_Number (FK) Gas_Station_Information (FK) Quantity_Control (FK) Grade (FK)

DISPENSED_GAS_DATA

1 1 1

Cost_of_Sale (FK) Transaction_Number (FK) Driver_Credit_Acct_Number (FK) Date_Time (FK) Gas_Station_Information (FK)

RECEIPT

1

Required_ForUsed_to_compute

Used_For

Included-in

Display-ID Display_Content

DISPLAY

Triggers

Transaction_Number (FK) Driver_Credit_Acct_Number (FK) Approval


Transaction_Number (FK) Driver_Credit_Acct_Number (FK) Status Cost_of_Sale (FK) Date_Time (FK) Gas_Station_Information (FK)

BANK_TRANSACTION1

Triggers

Provides_info_to

Date_Time Gas_Station_Information Pricing

GAS_PRICING

Transaction_Number Driver_Credit_Acct_Number (FK)

FINANCIAL_TRANSACTIONP

Transaction_Type

Used_in

Used_in

Provides_data

Used_to_Compute

Purpose: To describe the data structure of the FastPass System


COLORSETS FROM ENTITIES

Data Model contains the following entities

• FastPass Device

• Selection

• Financial Transaction

• Authorization Transaction

• Bank Transaction

• Display

• Receipt

• Driver Information

• Dispensed Gas Data

• Gas Pricing

• Driver Credit Account

color Int = int; color Boolean = bool;color String = string;

(* Inputs in "Operate FastPass System" *)color FastPass_Device = Int;color Selection = product Boolean * Int * Int;color Financial_Transaction = product Int * Int * Int * Int * Int * Boolean;color Authorization_Transaction = Financial_Transaction;color Bank_Transaction = Financial_Transaction;

(* Outputs in "Operate FastPass System" *)color Display = product Int * String;color Receipt = product String * Int * Int * Int;

(* Colors in A1 -- Validate Accounts*)color Driver_Information = product Int * Int;

(* colors in A2 -- Operate Pump *)color Dispensed_Gas_Data = product Int * Int * Int * Int * Int;

color Gas_Pricing = product Int * Int * Int;color Accounts = product Int * Int; color Credit_Card_Accounts = product Int * Boolean;

DOMAINS

ATTRIBUTES

GLOBAL DECLARATION NODE


RULE IMPLEMENTATION

Rules in Rule Model are implemented using arc inscriptions, guard functions, and code segments

• Example: Rule for Activity A21: Receive_Authorization

R21: If Authorization_Transaction.approval = true

– Then

• Display.Content = “Select grade and start pumping”,

– Else

• Display.Content = “Credit is not authorized; see attendant”

• And Authorization_Transaction=nil,

RULES IMPLEMENTATION

Rule A21

L. 16 - 14


MODELING EXTERNAL SYSTEM

• The Executable Model can be run manually without explicit models of the external systems

– Analysts provides appropriate markings as the simulation runs

• Alternatively, Design/CPN nets of the external systems can be included to automatically stimulate and respond to the system

– This can speed up the analysis

– Derived with the help of the Dynamics Model

DRIVER CP NET

INPUTS

OUTPUTS

DRIVER ACTIONSL. 16 - 16


EVALUATION USING THE EXECUTABLE MODEL

• Once the executable model has been constructed, it can be used in three forms of evaluation: Logical, Behavioral, and Performance

• The first step is to validate the logic of the model.

– The static views describe the structure, data and rules that manipulate that data to accomplish tasks. We need to verify that the combination of rules data and structure “works”, e.g. the the rules are consistent and complete

– This can be accomplished by executing the model to be sure that it runs properly

– In a sense we are “debugging” the architecture

– Any errors found must be corrected in the appropriate static views to preserve traceability


EXECUTION OF THE MODEL TO VERIFY ITS LOGIC

• A single thread is tested in the model and each step of the execution is examined to ensure that the model is following the logic desired. Any “flaws” will result in either an incorrect response or a deadlock

• The execution should match the dynamics model

DRIVER ARRIVES

L. 16 - 19

DRIVER PRESENTS FASTPASS

L. 16 - 20

VALIDATING CREDIT

L. 16 - 21

AUTHORIZATION RETURNED

L. 16 - 22

CREDIT VALIDATED DISPLAY SAYS START PUMPING

L. 16 - 23

DRIVER STARTS PUMPING

L. 16 - 24

DRIVER FINISHES PUMPING

L. 16 - 25

RECEIPT PRINTED; FINANCIAL TRANSACTION INITIATED

L. 16 - 26

DRIVER LEAVES; BANK TRANSACTION RETURNED

L. 16 - 27

NO MORE ENABLED TRANSITIONS

L. 16 - 28


BEHAVIORIAL EVALUATON

• We now know that the executable model runs. We know that the rules, structure, and data logically work together.

• Next we can examine the behavior of the architecture; this is an examination of the functionality of the architecture

• The behavior of the executable model and the dynamics model should correlate

• The behavior evaluation has several facets:

– Does the architecture produce all the correct output for a given stimulus?

– Does the information arrive at the right functions in the right sequence, I.e., are the inputs processed in the required way?

• The behavior of the architecture can be compared to the user’s requirements


TECHNIQUES FOR BEHAVIOR EVALUATION

• Simulation– The behavior of the architecture can be examined by

running the executable model in simulation with inputs consistent with the operational concept

• State Space Analysis– Colored Petri Nets in general (and Design/CPN in

particular) allow behavioral properties to be verified by analysis without resorting to simulation

– The technique can compliment the multiple running of the model in simulation to reveal overall properties

– These techniques can reveal dead locks (conditions in which the architecture stops executing), infinite cycles (generally not desirable) and maximum number of tokens (queues) that can occur in any place in the architecture.

OCCURRENCE GRAPH OF FASTPASS

• State space analysis tool of Design/CPN

• Verifies behavior– No undesired

dead locks– Single Final

State means consistent behavior

State

Transition

L. 16 - 31


OBSERVATIONS

• Some behavioral evaluation can be accomplished using an executable model derived only from the functional (or operational) architecture view.

– Single stimulus/response analysis can show that the architecture does what it is supposed to.

– Once the architecture has the desired behavior for single stimulus/response it can be evaluated with abnormal behaviors on the part of the external systems. This can reveal errors/omissions in the model.

• Additional behavioral evaluation can be accomplished with some aspects of the physical architecture are included.

– Processors, communications links, etc. may effect the behavior of the architecture (e.g. sequencing of events)

– The impact of time delays and processing times can be evaluated

© A. H. Levis INCOSE L. 4 - 1 C4ISR ARCHITECTURES AND THEIR IMPLEMENTATION CHALLENGES LECTURE 4 A...

Documents

Transcript of © A. H. Levis INCOSE L. 4 - 1 C4ISR ARCHITECTURES AND THEIR IMPLEMENTATION CHALLENGES LECTURE 4 A...