XASTRO-2 Overview Presentation CCSDS SAWG Athens Meeting 12 th April 2005.

XASTRO-2 Overview

Presentation

CCSDS SAWG Athens Meeting12th April 2005

XASTRO-2 Overview - CCSDS SAWGXASTRO-2 Overview - CCSDS SAWG22

Modelling Approach XASTRO-2 Modelling is based on UML 1.4

XASTRO-2 Framework Architectual Model concepts captured using UML profile (i.e. XASTRO-2 Profile)

Viewpoints based on RM-ODP / CCSDS RASDS

XASTRO-2 Profile is standarded and is itself a UML Model (XMI)

Magic Draw is used, but thereortically any XMI compliant tool can be used (i.e. ArgoUML)

Platform Mappings XML Schema CORBA IDL


Architectural Modelling


Main XASTRO-2 Elements

XASTRO-2Framework

Specification

Models (XMI)

edits

UML Editor

constrains XASTRO-2Profile (XMI)

describes

SpecialisedModel Editors

XMLInstance Model

edits configures

XMLSchema

CORBAIDL Documentation

ProductGeneration

Tools

editsedits

imports


Tools XML Schema Generator

XSLT Processor (SAXON)

CORBA IDL Generator XSLT Processor, Eclipse Modelling Framework, FreeMarker

Documentation Generator XSLT Processor, EMF, FreeMarker, DocBook

Requirements Import Tool XSLT Processor


Communications Viewpoint

Physical Viewpoint

RASDS Viewpoints

Enterprise Viewpoint

Information Viewpoint

Functional Viewpoint

StandardisedData

Models

StandardisedServices

XA

ST

RO

-2 F

ram

ewor

k


Information Viewpoint Primitive Types

Simple Type Definitions

Integer, Float, Enumeration, String

Complex Type Definitions

Structure, Choice, Array (fixed & variable length)

Inheritance

Composite Aggregation

Referencing

Constraints (OCL) can be applied in UML(no platform mapping to XML Schema or CORBA IDL)

Generation of XML Schema supported


Profile Specification Example


Integer Type Definition Example


String Type Definition Example

Valid Value = F457ab31-6754-FFEa-1234-FF11ccCC65eA

Invalid Value = F457ab??-6754-FFEa_1234-FF11cXYZ65eA


Alias Example


Composite Aggregation Example

Cardinality(default = 1)

Role (optional,defaults totype name)

SequenceOrder

Composite Aggregation


Referencing Example

Cardinality(default = 1) Role (optional,

defaults totype name)


Functional Viewpoint Used to specify standard ground system …

services (realised as interfaces) and

functions (realised as functional objects)

Interactions between functional components through Interfaces

Three types of Interfaces supported (based on RM-ODP)

Operation Event Stream

Hierarchical decomposition of components is difficult in UML 1.4 (UML 2.0 much improved)

Generation of CORBA IDL from Operation Interfaces


Functional View Model ExampleFunctions

(Monitoring.Functional View)

<<functional>>ParameterGroup

<<functional>>TMHandler

<<event>>ParameterUpdates

<<event>>DeltaOutOfLimits

<<event>>OutOfLimits

<<event>>Packet

<<functional>>ParameterValidation

...

...

<<functional>>ParameterInterpretation

...

<<operation>>MonitoringDataDefinition

<<operation>>MonitoringDataDefinition

<<event>>ParameterGroupChange

<<operation>>ParameterInterpretation

<<operation>>ParameterGroupControl

<<operation>>ValidationControl

<<operation>>ValidationStatus

<<operation>>Logger

<<operation>>Logger

<<operation>>Logger

<<event>>Packet

<<realize>><<receive>>

<<emit>>





<<emit>> <<emit>>


<<emit>>

<<emit>>


Interfaces Types


Interface Example


Assembly of Components


Behaviour Specification UML 1.4 offers a number of behavioural diagrams which can

be used to specify the behaviour of components

A State Diagram can be used to specify the states and valid transitions between those states of a function component

An Activity diagram can be used to specify the actions / activities that a method performs

Sequence / Collaboration diagrams can be used to show the sequencing of interactions between components


Sequence Diagram Example


Supports modelling of textual requirements and their traceability to the system design

Based on SysML 0.9 (10th Jan 2005) SysML is specified as a UML 2.0 profile

(no UML meta-class extensions)

Import of requirements into UML to be supported

Requirements will be imported from an XML document, which is based on an XML Schema generated from the XASTRO-2 Requirements Metamodel

A custom requirements export tool is required to generate an XML document (containing requirements) conforming to the XML Schema prior to importing requirements

Enterprise Viewpoint (Requirements)


Requirements View Model Example


Communications Viewpoint Is based on the RM-ODP engineering viewpoint

Is inspired by the Interoperability Technology Association for Information Processing, Japan (INTAP) Engineering Viewpoint Profile (extension of OMG‘s EDOC)


Communications View Example

Communications View

<<node>>

: ServerNode

<<capsule>>

: EJBContainer<<cluster>>

: EJBEntityBean

<<beo>>

Data Group A

<<cluster>>

: EJBEntityBean

<<beo>>

Data Group B

<<cluster>>

: EJBEntityBean

Telemetry Interpretation<<beo>>

<<cluster>>

: EJBEntityBean

<<beo>>

Telemetry Validation

<<capsule>>

: CCMContainer

<<cluster>>

: CCMComponent

<<beo>>

TM Handler

<<nucleus>>

: Linux

IIOPChannel<<channel>>

Functional View

<<functional>>

: ParameterValidation<<functional>>

: ParameterGroupA<<functional>>

: TMHandler

<<refines>><<refines>> <<refines>>


Communications Channel Example

IIOPChannel

<<stub>>: J avaStub

<<binder>>: RMI

<<protocolObject>>: IIOP

<<interceptor>>: Authentication

<<stub>>: CORBAStub

<<binder>>: CORBABinder

<<protocolObject>>: IIOP

<<beo>>Telemetry Interpretation

<<beo>>Telemetry Validation


Physical Viewpoint Very simple Profile

Physical System Elements

Allocation of Computional Nodes (from Communications Viewpoint) to System Elements (i.e. computer)


Physical View ExamplePhysical View

: Ethernet<<systemElement>>

PCNetwork

<<systemElement>>

: PCA<<systemElement>>

: PCB<<systemElement>>

: PCC

: Ethernet<<systemElement>>

OpsNetwork

: Sparc WorkstationWS1<<systemElement>> <<systemElement>>

: Sparc WorkstationWS2 : Alpha WorkstationWS3<<systemElement>>

<<systemElement>>

: Router

Communications View

<<node>>

: ServerNode<<node>>

: ServerNode

<<allocation>> <<allocation>>


Multiple Views

<<systemElement>>: Ethernet

OpsNetwork

<<systemElement>>: Sparc WorkstationWS1

<<systemElement>>: Sparc WorkstationWS2

<<systemElement>>: Alpha WorkstationWS3

<<node>>

: ServerNode

<<capsule>>: EJBContainer

<<cluster>>: EJBEntityBean

<<beo>>Data Group A


<<beo>>Data Group B


<<beo>>Telemetry Interpretation


<<beo>>Telemetry Validation

<<capsule>>: CCMContainer

<<cluster>>: CCMComponent

<<beo>>TM Handler

<<nucleus>>: Linux

<<systemElement>>: Ethernet

PCNetwork

<<systemElement>>: PCB

<<systemElement>>: PCA

<<systemElement>>: PCC

<<node>>

: ServerNode

<<capsule>>: OSProcess

<<beo>>Data Distribution

<<nucleus>>: OpenVMS

<<node>>

: ClientNode

<<capsule>>: .NET MDI Application

<<cluster>>: .NET Component

<<beo>>Data Display A

<<nucleus>>: WindowsXP

<<node>>

: ClientNode

<<capsule>>: .NET MDI Application

<<cluster>>: .NET Component

<<beo>>Data Display B

<<nucleus>>: WindowsXP

Display A(Monitoring.Functional View.Configurations.Monitoring Assembly)

<<channel>>HTTP B

<<channel>>HTTP A

<<channel>>TCPIP

<<functional>>: ParameterInterpretation

<<systemElement>>: Router

<<functional>>: ParameterValidation

<<functional>>: ParameterGroupA

<<functional>>: TMHandler

Data Distribution

<<channel>>IIOPChannel

Communications View

Functional View

Physical View

<<allocation>>

<<refines>>

<<refines>><<refines>>

<<refines>><<refines>>

<<refines>>

<<allocation>><<allocation>>

<<allocation>>


Documentation It is possible to add documentation

information to a model using the documentation profile

The following is supported:

Glossary

References

Dependency relationships can also be made from model elements to glossary definitions or references


Documentation Glossary Example


Documentation References Example


Current Status Framework

Framework Specification Viewpoint Profiles (XMI 1.1) Framework Specification Document

Framework Tools Prototype XML Schema and CORBA IDL Generators

Modelling Framework currently beening used by 2 project teams for the

development of Ground System Models

Portal portal.vega.de/xastro

XASTRO-2 Overview Presentation CCSDS SAWG Athens Meeting 12 th April 2005.

Documents

Transcript of XASTRO-2 Overview Presentation CCSDS SAWG Athens Meeting 12 th April 2005.