inf5120 ”modellbasert systemutvikling” ”modelbased system ......v1.1 2007 v1.2 2008 2009 c4isr...

INF5120”Modellbasert Systemutvikling”

”Modelbased System development”Modelbased System development

Lecture 11: 24.03.2014Arne-Jørgen Berre

[email protected] or [email protected]@ @

Telecom and Informatics 1

ContentContent

Oblig 1 (comments) and 2 (questions) Enterprise Architecture - MagicDraw ISO RM/ODP UPDM for MODAF/DODAF SysML


MagicDrawCameo Enterprise ArchitectureCameo Enterprise Architecture


ContentContent EA and the Zachman Framework Architectural Frameworks - (IEEE/ 1471/ISO 42010, ADL,

UML 2.x, TOGAF, UPDM UPDM (DODAF/MODAF, NAF), NIEM TOGAF Service modeling and Service oriented views

Tool support , Metamodels and UML profiles – No Magic, Magic Draw


Zachman Framework – for Enterprise

Based on work by John A. Zachman

VA Enterprise Architecture

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Based on work by John A. Zachman

VA Enterprise Architecture

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Architecture (IBM, 1987)SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

Things Important to the Business

Entity = Class of Business Thing

Processes Performed

Function = Class of Business Process

Semantic Model Business Process Business Logistics Work Flow Model Master Schedule Business Plan

ImportantOrganizations

People = Major Organizations

Business locations

Node = Major Business Locations

Ev ents Significantto the Business

Time = MajorBusiness Event

Business Goalsand Strategy

Ends/Means =Major Business Goals

SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

Things Important to the Business

Entity = Class of Business Thing

Processes Performed

Function = Class of Business Process

Semantic Model Business Process Business Logistics Work Flow Model Master Schedule Business Plan

ImportantOrganizations

People = Major Organizations

Business locations

Node = Major Business Locations

Ev ents Significantto the Business

Time = MajorBusiness Event

Business Goalsand Strategy

Ends/Means =Major Business Goals

MODEL(CONCEPTU AL)

Owner

SYSTEM MODEL(LOGICAL)

MODEL(CONCEPTU AL)

Owner


Ent = Business Entity Rel = Business Relationship

Model

Proc = Business Process I/O = Business Resources

gSystem

Node = Business Location Link = Business Linkage

People = Organization Unit Work = Work Product

Time = Business Event Cycle = Business Cycle

End = Business Objectiv e Means = Business Strategy

Logical DataModel

Application Architecture

Distributed SystemArchitecture

Human InterfaceArchitecture

ProcessingStructure

Business RuleModel

MODEL(CONCEPTU AL)

Owner


MODEL(CONCEPTU AL)

Owner


Ent = Business Entity Rel = Business Relationship

Model

Proc = Business Process I/O = Business Resources

gSystem

Node = Business Location Link = Business Linkage

People = Organization Unit Work = Work Product

Time = Business Event Cycle = Business Cycle

End = Business Objectiv e Means = Business Strategy

Logical DataModel

Application Architecture

Distributed SystemArchitecture

Human InterfaceArchitecture

ProcessingStructure

Business RuleModel

Designer

TECHNOLOGYMODEL(PHYSICAL)

Designer

TECHNOLOGYMODEL

(PHYSICAL)

Ent = Data Entity Rel = Data Relationship

Proc = Application Function I/O = User Views

Node = IS Function Link = Line Characteristics

People = Role Work = Deliv erable

Time = System Event Cycle = Processing Cycle

End = Structural Assertion Means = Action Assertion

Physical DataModel

SystemDesign

TechnologyArchitecture

PresentationArchitecture

ControlStructure

RuleDesign

Designer

TECHNOLOGYMODEL(PHYSICAL)

Designer

TECHNOLOGYMODEL

(PHYSICAL)

Ent = Data Entity Rel = Data Relationship

Proc = Application Function I/O = User Views

Node = IS Function Link = Line Characteristics

People = Role Work = Deliv erable

Time = System Event Cycle = Processing Cycle

End = Structural Assertion Means = Action Assertion

Physical DataModel

SystemDesign


PresentationArchitecture

ControlStructure

RuleDesign

Builder

DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)

S b C t t

Builder


S b C t t

Ent = Segment/Table Rel = Pointer/Key

Proc = Computer Function I/O = Data Elements/Sets

Node = Hardware/Softw are Link = Line Specifications

People = User Work = Screen Format

Time = Ex ecute Cycle = Component Cycle

End = Condition Means = Action

DataDefinition

Ent = Field

Program

Proc = Language Statement

Netw orkArchitecture

Node = Addresses

SecurityArchitecture

People = Identity

Timing Definition

Time = Interrupt

RuleDesign

End = Sub Condition

Builder


S b C t t

Builder


S b C t t

Ent = Segment/Table Rel = Pointer/Key

Proc = Computer Function I/O = Data Elements/Sets

Node = Hardware/Softw are Link = Line Specifications

People = User Work = Screen Format

Time = Ex ecute Cycle = Component Cycle

End = Condition Means = Action

DataDefinition

Ent = Field

Program

Proc = Language Statement

Netw orkArchitecture

Node = Addresses


People = Identity

Timing Definition

Time = Interrupt

RuleDesign

End = Sub Condition Sub-Contractor

FUNCTIONINGENTERPRISE

Sub-Contractor


Ent = Field Rel = Address

Proc = Language Statement I/O = Control Block

Node = Addresses Link = Protocols

People = IdentityWork = Job

Time = InterruptCycle = Machine Cycle

End = Sub-Condition Means = Step

Data

Ent = Rel =

Function

Proc =I/O =

Netw ork

Node = Link =

Organization

People = Work =

Schedule

Time = Cycle =

Strategy

End = Means =

Sub-Contractor


Sub-Contractor


Ent = Field Rel = Address

Proc = Language Statement I/O = Control Block

Node = Addresses Link = Protocols

People = IdentityWork = Job

Time = InterruptCycle = Machine Cycle

End = Sub-Condition Means = Step

Data

Ent = Rel =

Function

Proc =I/O =

Netw ork

Node = Link =

Organization

People = Work =

Schedule

Time = Cycle =

Strategy

End = Means =


DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

y

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

y

Zachman Framework

Row 1 – ScopeExternal Requirements and DriversBusiness Function ModelingBusiness Function Modeling

Row 2 – Enterprise ModelBusiness Process Models 1

2

Contextual

Conceptual

Contextual

Conceptual

WhyWho WhenWhereWhat How

Row 3 – System ModelLogical ModelsRequirements Definition

234

Conceptual

Logical

Physical

Conceptual

Logical

Physical

Row 4 – Technology ModelPhysical ModelsSolution Definition and Development

Row 5 – As Built

56

As Built

Functioning

As Built

Functioning

As BuiltDeployment

Row 6 – Functioning EnterpriseFunctioning Enterprise

WhyWho WhenWhereWhat How


Functioning EnterpriseEvaluation

Many Architectural Frameworks ….y

ARIS ZACHMAN GERAM

EKA -POPSEKA -POPSEKA -POPS

EN/ISO 19439


NISTAthena OEA

TOGAF 9 (The Open Group)TOGAF 9 (The Open Group)


OpenGGroupADM


Building block evolutiong


Service categories


ISO RM/ODP (ISO 10746)ISO RM/ODP (ISO 10746)

Telecom and Informatics

Why and When: Historical Development of AF’s.

NAFMODAF NAF DNDAF1 7NAF

v1.0MODAF Meta-Model (M3) expressed using UML Notation

v3.1 v1.7

2008

C4ISRMODAFv1 0

MODAFv1 1

2005

MODAFv1 2

2007

DoDAFV2.0

2008

C4ISRArchitecture Framework v2 0

v1.0

2005

v1.1

2007

v1.2

2008

V2.0

2009

C4ISRA hit t

v2.0

DoDAFv1.0

1997DoDAFv1.5

2007

Scope of UPDM 2.0Architecture Framework v1.0

19962003 2007Scope of UPDM 1.0

Approved Sept 2008

Started Sept 2009

MACCISNor a


1996

TOGAF1 - … TOGAF9Norway

Towards a Unified Architecture FrameworkFramework


Three Views in DOD A hi F k d C4ISR AFDOD Architecture Framework and C4ISR-AF


DODAF 2 0 - viewpointsDODAF 2.0 viewpoints


EAEA – European Air Traffic Management Enterprise ArchitectureManagement Enterprise Architecture


IEEE 1471 ISO 42010IEEE 1471, ISO 42010


Zachman with OMG standardsZachman with OMG standardsData Function Network People Time Motivation

(What) (How) (Where) (Who) (When) (Why)

Scope(Contexts)

List of things importantto business

SBVR

List of processes thatthe business performs

VDM

List of locations whichthe business operates

VDM

List of organizationsimportant to the business

OSM

List of events/cyclesimportant to the business

DTFV

List of businessgoals/strategies

BMM

Business(Concepts)

System

Semantic ModelODM,

IMM (CWM)

Business ProcessModel

BPMN, CMPM

Business LogisticsSystem

BPMN, CMPM

Workflow ModelOSM, BPMN,

CMPM

Master ScheduleBPMN, CMPM,

DTFV

BusinessPlan

SBVR

Logical Data Model Application Distributed Human Interface Process Structure Business RuleSystem(Logic)

Technology(Physics)

gODM,

IMM (CWM), UML

ppArchitecture

SoaML, UMLSystem Architecture

SoaML, UMLArchitecture

BPMN, CMPMBPMN, CMPM,

DTFVModel

SBVR

Physical Data ModelIMM (CWM), UML

System DesignSoaML, UML


SoaML UMLPresentationArchitecture

Control StructureBPMN, CMPM,

DTFV

RuleDesignSBVR(Physics)

Component(Assemblies)

( ) SoaML, UML DTFV SBVR

Data DefinitionIMM (CWM), UML

ProgramUML

NetworkArchitecture

UMLSecurity

Architecture

TimingDefinitionDTFV

RuleDefinitionSBVR

Operation(Instances)

Data Function Network Organization Schedule Strategy


OMG standards coverageOMG standards coverageData Function Network People Time MotivationData

(What)Function

(How)Network(Where)

People(Who)

Time(When)

Motivation(Why)

Scope(Contexts)

List of thingsimportant

to business

List of processesthat the business

performs

List of locationswhich the business

operates

List of organizationsimportant to the

business

List of events/cyclesimportant to the

business

List of businessgoals/strategies

BMMVDM OSMSBVR( )

Business(Concepts)

p p

Semantic ModelBusinessProcessModel

BusinessLogisticsSystem

WorkflowModel

MasterSchedule

BusinessPlan

BPMN

CMPMODM

System(Logic)

Technology

Logical Data Model ApplicationArchitecture

DistributedSystem

Architecture

HumanInterface

Architecture

ProcessStructure

Business RuleModel

Physical Data Model System Design Technology Presentation Control Rule

SBVR

DTFVUMLIMM

CMPM

SoaML(Physics)


Physical Data Model System Design Architecture Architecture Structure Design

Data Definition Program NetworkArchitecture


TimingDefinition

RuleDefinition

DTFV(CWM)


Data Function Network Organization Schedule Strategy


UPDM coverageUPDM coverage

Data(What)

Function(How)

Network(Where)

People(Who)

Time(When)

Scope

Motivation(Why)

(Contexts)

Business(Concepts)

BPMNUPDM

System(Logic)

Technology

SoaML

(Physics)




Model Based SystemsEngineering and Interoperability BMMg g p y

Business Architecture

BPMNVDMCaseMgmtOSMBusiness Architecture

(SysML Context + BPMN 2.0/BMM)

OSMSBVR

Enterprise Architecture (EA) forSystems of Systems

(UPDM) I)(UPDM)

DA

,Osl

o)

rabi

lity

ctur

e (M

DI

System & IT Service oriented Driv

enec

ture

(M

Inte

rope

Arc

hite

c

Architecture(UML&SysML/SoaML)

Mod

elD

Arc

hite

UML 2.0SoaMLSysML


SysML

What is UPDM? - SummaryUPDM 1.0 is a standardized way of expressing

D DAF 1 5 d MODAF 1 2 t f t i

What is UPDM? - Summary

DoDAF 1.5 and MODAF 1.2 artefacts using UML and SysML UPDM is NOT a new Architectural Framework UPDM is NOT a new Architectural Framework UPDM is not a methodology or a process UPDM 2.0 is scheduled to address DoDAF 2.0,

MODAF 1.2, NAF 3.x, and DNDAF 1.7UPDM 1.0 was developed by members of the

OMG with help from industry and governmentOMG with help from industry and government domain experts.

UPDM 1 0 has been implemented by multipleUPDM 1.0 has been implemented by multiple tool vendors. Tools supporting UPDM 1.0 are available now.


UPDM: UML Profile for DoDAF and MODAFUPDM: UML Profile for DoDAF and MODAFDoDAF and MODAFDoDAF and MODAF

Context Stakeholders

NAF Meta Model CADM 1.5DoDAF 2.0 OntologyMODAF Meta Model

DoDAF 1.5 Concepts

US DoD UK MOD NATO

Canada/Australia

UPDM Domain Meta ModelUPDM Profile Meta Model

Canada/Australia OMG, INCOSE

OMG XMI UML SysML

UPDM Profile&

CADM AP233 UJTL

XMI, UML, SysML BPMN UPMS, BMM

End Users

&Library

renc

es

tions

IDEF

XMI

UML

<<import/merge>>CDD

SF List

Aerospace Commercial

Tool Vendors

UML4SysMLSysML

rnal

Ref

er

ansf

orm

at

BPMN SoaML

UML

SysML Extensions

SoaML BMM

SSDD

etc

CONOPS

Software Systems Enterprise

Exte

r

Tra SoaMLSoaML, BMM,

SBVr Extensionsetc.

BMM


Products -- Reports -- Simulations

UPDM - – Unified Model for DODAF and MODAF


UPDMUPDM


Enterprise ArchitectureEnterprise Architecture Modeling with UPDM


Introduction

Enterprise Architecture modelingEnterprise Architecture modelingNo rocket science! It's a standard! UPDM:UPDM: Unified Profile for MODAF and DoDAF


What is Enterprise Architecture?


Enterprise Architecture

Business, partners, customersApplication ecosystemApplication ecosystemSystem of system architectureThe worldNot: application or deviceNot: application or device


Enterprise Architecture F kFrameworks

ZachmanTOGAFFederal enterprise architectureFederal enterprise architecture

Framework (FEAF)DoDAF/MODAF/DNDAF/NAF Etc


UML EA Framework

Semantic classificationExtra rules for constructionAdditional dataTraceability between viewsTraceability between views


UPDM

Unified Profile for DoDAF and MODAF (UPDM)( )Developed by OMG with DoD supportCreated by multiple vendors governmentsCreated by multiple vendors, governments,

customersI l t hit t f D D MOD d th Implements architecture for DoD, MOD, and others


UPDM 2.0 Standard

Approved by the OMG September 2011 with DoD/MOD support Approved by the OMG September, 2011 with DoD/MOD support Implements DoDAF 2.0 guidance and traced to DM2 metamodel

as a UML extension Submitted to DISR as Emerging September, 2011 (in registry 14

November 2011) Beta from existing UPDM vendors Beta from existing UPDM vendors UPDM 1.0 to 2.0 conversion available now


Advantages of UPDM

Leverages existing UML tools and capabilities A t t d l t / t f d l Automated completeness/correctness of models Supported by multiple vendors in consistent form

C t i bl i t d d b d Customizable via standard-based methods/interoperability

Supports executable architecture via executable UML Supports executable architecture via executable UML


Structure


Simple Example

Two things (very simple model)Presentation not in build orderPresentation not in build orderKey elements of UPDM used


High Level Operational Concept

Elevator Speech of the architecture Summarizes the key concepts of the

architecture Picture, not a model Usually one diagram per project, but there mayUsually one diagram per project, but there may

be many if required. HLOC can be composite diagramHLOC can be composite diagram


OV-1 Thing Concept


Thing HLOC


Operational Resource Flow (OV-2)

Documents logical view of performers and logical data interactions

S i th hit t ' b i i i t Summarizes the architecture's business viewpoint Business, not the implementation of the business Al d t b ild OV 3 (O ti l E h M t i ) Also used to build OV-3 (Operational Exchange Matrix)

and others


Thing World


A Sign of Things to Come

K t I t t d d l Key concept: Integrated model Not just pretty pictures Trace to other concepts Show what you need to communicate Show what you need to communicate Goal: Executable


More Things


Whole/Part Hierarchy

Composite can show detailed communication paths Further details added via portsp Same thing as Internal Block Diagram


Part Design Method


Operational Exchanges


The World


Operational Resource Flow Matrix (OV 3)(OV-3)

Report of operational exchanges Business-level Interface Exchange Requirement

(IER)( ) Performance and Information Assurance

parametersparameters Shows who, what, how


OV-3 Operational Resource Flow M t iMatrix


All Exchanges


Organization Chart (OV-4)

Organization Structure Roles in organizationRoles in organization Example or actual organizations Part of the system architecture


OV-4 Organizational Chart Typical


Operational Activity Decomposition TTree

Hierarchy of Operational Activities Relationship of activities to sub-activities Relationship of activities to sub activities Reuse of activities Related resources


Decomposition of Activity


Other Information


Operational Activity Flow

Behavior definitionUse of other activities (calls) Logic/constraints of behavior Logic/constraints of behavior Swimlanes for orchestration across performers

( I t ti O i )(see Interaction Overview)


Send


Receive


Interaction OverviewInteraction Overview


OV-5b Overview


OV-6a Operational Rules

Constraints of the architectureWhat the architecture must doUML Constrains used throughout theUML Constrains used throughout the

architectureI l d t id li t Includes agreements, guidance, policy etc.


OV-6a Operational Rules


OV-6b Operational State

Valid states of performersOwned by the subject performerOwned by the subject performerUML State machine


Thing Two


OV-6c Operational Event Trace

Validates operational use of architecturepRoles are instances of performersCan use methods on performers for further detailCan use methods on performers for further detail Flows can be displayed from OV-2Usually owned by a contextual performer


Thing World


Capability Related


CV-3 Capability Phasing


CV-4 Capability Dependencies


CV-6 Capability to Operational A ti it M iActivity Mapping


Systems Interface Description

Shows how systems communicate Can include humans and organizationsCan include humans and organizations Physical manifestation of the Operational

Resource Flow


Widgets


Implementation Matrix


SV-2 Widget Network


SV-3 System to System Matrix


SV-4a


System Overview


SV-5a Operational Activity to S t F ti T bilit M t iSystem Funtion Traceability Matrix


System Resource Matrix


SV-7 Typical Measures


SV-8 Evoloution of Widgets


Services ViewServices View


Service Context


UPDM IN PRACTICAL USE

Relevant approach for Enterprise Architecture Agile: Iterative model development Accepted and promoted by the DoD Reporting and traceability Integrated architecture and development Integrated architecture and development Useful tool for capturing customer requirements


OV-1a: Operational Context GraphicOV-1a: Operational Context GraphicOV-1a [High Level Operational Concept] Maritime Rescue

Rescue Helo : Aircraftcontrol trackInfo

Yacht : Boat

distressSignal

trackInfo

assistance

Monitor Unit : Monitor Naval Ship : BoatRescue Boat : Boat

distressSignal

trackInfo control control

C2 Center : Control Center


OV-1: Operational Context GraphicOV-1: Operational Context Graphic


OV-2 Operational NodesOV-2 Operational NodesOV-2 [Node] Search and Rescue (With Ports)

«PerformerRole»PoS : Place of Safety

SN

«PerformerRole»SN : Search

POS

SAC

TCN

WO : warningOrder

SN1SN

PIDS C

RN

Stat : statusDS2 : distressSignal

Tsk : tasking

«PerformerRole»PiD : Person in Distress

SN2RN«PerformerRole»RN : Rescue

TCNSAC

PID

DS3 : distressSignal

Tsk : tasking

Ctrl : control

RN PIDRNSN

TI : trackInfoRqst : request

Ctrl : controlTsk : tasking

DS1 : distressSignal

«PerformerRole»TC2N : Tactical C2

MNSAC

SN

«PerformerRole»MN : Monitoring

TCN

«PerformerRole»SAR AC : SAR Asset Control

TCN

TI : trackInfoRqst : request


OV-5 Activity DiagramOV-5 Activity DiagramOV-5 [Architectural Description] Operational Activities

«Activity(Operational)»Search

«ActivityPerformedByPerformer»

«ActivityPerformedByPerformer» «ActivityPerformedByPerformer»«Performer»

«block»Search

«StandardOperationalActivity»Find Victim

«Activity(Operational)» «StandardOperationalActivity»

«Activity(Operational)»Receive Distress Signal

y y y y

«ActivityPerformedByPerformer» «ActivityPerformedByPerformer»Send Warning Order Monitor Health

«Activity(Operational)»Rescue

y y y y

«Performer»«block»

«Activity(Operational)»R i Di t Si l

«StandardOperationalActivity»R Vi ti


«ActivityPerformedByPerformer»«ActivityPerformedByPerformer»

Rescue Receive Distress SignalRecover Victim

«StandardOperationalActivity»Provide Medical Assistance



OV-5 Activity DiagramOV-5 Activity Diagramrm

erR

ole»

Per

son

inst

ress

: Send Distress Signal

reportedLocation reportedCondition

Search

«Activity(Operational)»

e«P

erfo

PiD

: Di

erR

ole»

earc

h

distressSignal

location

: Find Victim: Send Warning Order

condition

: Monitor Health

distressSignal

: Receive Distress Signal

«Per

form

er»

«blo

ck»

: Sea

rch

and

Res

cue

«Per

form

SN

: S

eR

ole»

cue

warningOrder

distressSignal

«Per

form

erR

RN

: R

esc

erR

ole»

lace

of

ety

: Receive Distress Signal

location

: Recover Victim

condition

: Provide Medical Assistance

warningOrder

«Per

form

eP

oS :

Pl

Saf

e : Process Warning Order : Transit To SAR Operation

updatedCondition udpatedLocation


SV-1: Resource Interaction SpecificationSV-1: Resource Interaction SpecificationSV-1 [System] Maritime Rescue Unit v1

«SystemRole»MRT : Maritime Rescue TeamMRT : Maritime Rescue Team

«OrganizationRole»Driver : MRT Boat Driver

«SystemRole»MR Boat : Boat

BI : boatInstruction

«DataExchange»«ItemFlow»

«OrganizationRole»Searcher : MRT Searcher

Med«SystemRole»Beacon : Lighting Device

Mon

BCI : beaconInstruction


«OrganizationRole»Radio Operator : MRT Communicator

«SystemRole»Radio : Communication Device

Comm

RI : radioInstruction


«DataExchange»

«OrganizationRole»Rescue Swimmer : MRT Swimmer

«SystemRole»Life Preserver : Life Saving Device

LPI : lifePreserverInstruction


«DataExchange»

«OrganizationRole»Pilot : MRT Helicopter Pilot

«SystemRole»MR Aircraft : Aircraft

Air

AI : aircraftInstruction



SV-2: Resource Interaction SpecificationSV-2: Resource Interaction SpecificationSV-2 [System] Maritime Rescue Architecture v1

«SystemRole»yRescue Unit : Maritime Rescue Unit v1

«SystemRole»MR Boat : Boat

Src

RscDS : distressSignal

«SystemRole»Yacht : Boat

Src

Rsc

«SystemRole»MR Aircraft : Aircraft

«MaterielRole»Monitor : ESM System

dsIn

trkIn«MaterielRole»

Distress Beacon : Lighting Device

dsOut «MaterielRole»Monitor : ESM System

dsIn trkIntrkIn

DS : distressSignal

TRK1 : trackTRK2 : track

«MaterielRole»Radio : Communication Device

receiver «MaterielRole»Radio : Communication Device

transmitter

receiver

«MaterielRole»Digital Service : Link 16

tdmReceiver

tdmTransmitter

trkOut

«MaterielRole»Digital Service : Link 16

tdmTransmitter

tdmReceiver

trkOutRI1 : radioInstruction

RI2 : radioInstruction

TD1 : TDM

TD2 : TDM

transmitterreceiver tdmTransmitter tdmReceiver


SysML Example: Requirements TraceabilitySysML Example: Requirements Traceabilityreq [Package] SAR Initial Requirements

«requirement»

txt

UNCLOS 1982

The United Nations Convention on the Law of the Sea(UNCLOS), Article 98:Every State shall require the master of a ship flying itsflag, in so far as he can do so without serious danger tothe ship, the crew or the passengersto render assistance to any person found at sea in dangerof being lostto proceed with all possible speed to the rescue ofpersons in distress, if informed of their need of assistance,in so far as such action may reasonably be expected ofhimafter a collision, to render assistance to the other ship, its

d it d h ibl t i fcrew and its passengers and, where possible, to informthe other ship of the name of its own ship, its port ofregistry and the nearest port at which it will call.

«requirement»

txtThe primary framework for the U.S. SAR system is provided in the NSP. This key document, which is produced by theN ti l S h d R C itt (NSARC) d i d b hi h l l ffi i l ithi th F d l t

US NSP

«deriveReqt»

«Capability»«block»

Recovery


Assistance

National Search and Rescue Committee (NSARC) and signed by high-level officials within the Federal government,should be familiar to all SAR personnel, and is included as Appendix A to this Supplement. The NSP describes the U.S.SAR organization, key authorities and their responsibilities, and primary principles and policies upon which our SARsystem is based. The NSP was developed taking into account the provisions of the IAMSAR Manual, Volume 1, Chapter5 and its Appendix I.

subRequirements«requirement» Proceed to Rescue«requirement» Render Assistance«requirement» Post Collision«trace»

«trace»

«requirement»

txtThe ship master shall proceed with all possible speed tothe rescue of persons in distress, if informed of their needof assistance, in so far as such action may reasonably beexpected of him

Proceed to Rescue«requirement»

txtThe ship master shall render assistanceto any person found at sea in danger ofbeing lost

tracesFrom

Render Assistance«requirement»

txtThe ship master shall render assistance to the other ship, itscrew and its passengers and, where possible, to inform theother ship of the name of its own ship, its port of registryand the nearest port at which it will call

Post Collision


Assistance

«Capability»«block»Inform

«Capability»«block»Search

«StandardOperationalActivity»Assist Victim

«StandardOperationalActivity»Track Victim

«StandardOperationalActivity»Find Victim

expected of himparentRequirement

«requirement» US NSP

tracesFrom«Capability» Recovery«Capability» Assistance

and the nearest port at which it will call.tracesFrom

«Capability» Inform«Capability» Assistance

«trace» «trace» «trace»«refine» «refine»«refine»


Assistance InformSearch

AssociatedAssociatedAnalysis Tools


Related Elements

Traceability MatrixD d M t iDependency Matrix Related elements display Show relationships Show ports Show ports Show internal structure
