Mbs Efor Rail Liem

Model Based Systems Engineering
for GSM-R and Future Systems
Michael Liem
October 25th 2011 – ERA IRCA Conference - Lille

AGENDA

1. Key Reasons for System Design issues
2. Model Based Systems Engineering (MBSE)
3. Rail Dispatcher Communication example
4. Specifying Future Rail Com systems with MBSE
5. Summary

2
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

System Designs often fail . . .

Need of the The specification of the The Design of the As installed at the
operational people consultant in the RFQ supplier customer’s site


Main Reasons for System Design issues
Poor User Requirement Elicitation Mixing Requirements and Design
‘Black Box’ View ‘White Box’ View

System
Requirements System Design

Document Driven Error Prone Process No Requirement traceability


Model Based Systems Engineering
ITS Operator
Requirement Analysis Documents is created
The Model are created
Requirement
SysML
Specification
Model

Requirements Acceptance
Test Cases

System Design System Testing
Design
Specification

Sub-system Design Sub-S. Testing
Implementation

Implementation


Use Case driven Approach – example:
Driver Calls Dispatcher

Driver Dispatcher

These
are only
a few
Use
Cases


Defining System Behavior in the Model
Sequence Diagram automatically created
Push Button Call
Functional Numbering
Access Matrix Check
Location Based Routing

Call Queuing

Connect Loudspeaker


Allocation of Functions to Network
elements – GSM-R Case

GSM-R Network
GSM-R Network

SCP HLR

SCP HLR

MSC
MSC

FTS

FTS
BSC
BSC

BTS
Cab Radio
BTS
Cab Radio
Sequence Diagrams are
automatically generated


Allocation of Functions to Network
elements – LTE Case
RailApplicationServer DispatcherTerm. CabRadio

LTE Based Network
LTE Based Network

Rail Application
Rail Application
Server
Server

PGW
PGW
Dispatcher
Dispatcher
Terminal
PCRF Terminal
Enhanced
PCRF Enhanced
Packet Core- LTE
Packet Core-
LTE

MME
MME
SGW
E-UTRAN
SGW
E-UTRAN

Sequence Diagrams areRadio
eNodeB
Cab
automatically generated.
eNodeB
Cab Radio


End-to-end Traceability
System
Requirement

Use Case
Operational
User Needs

Features to be
implemented

Operational requirements can be linked to model elements


MBSE Approach for futur Rail Com System
BlackBox Spec WhiteBox Spec

GSM-R

WhiteBox Spec
Other Technologies

WhiteBox Spec

LTE for Rail


Summary – Model Based Systems Engineering

Is ‘state-of-the-art’ in designing complex Systems

Enforces proper Systems Engineering principles
Separation between Requirements & Design
end-to-end Traceability

Is ideal to specify a « cleaned-up » FRS (BlackBox) for current
and future Rail communication Systems.

Many Industries are already using MBSE successfully !
So why not we in the Railway Telecom Sector ?

Questions?


Stay in Touch

Michael Liem

Solution Architect
Mission-Critical Networks

Tel.: +33 1 30 77 07 58
Michael.liem@alcatel.lucent.com


Backup


Use case Modelling Steps in SysML

1. Import Requirements from FRS document
2. Define Use Cases in Use Case Diagram
3. Map Requirements to Dispatcher Call Use Case
4. Define BlackBox System Behavior (Activity Diagram)
5. Generate Message Sequence Diagrams
6. Define GSM-R Architecture (Block Definition Diagram)
7. Allocate Functions to Network elements by Drawing ‘Swimlanes’ in
BlackBox Activity Diagram.
8. Generate Message Sequence Diagrams.


Step 1: Import of FRS into the Modelling tool

FRS


Step 2: Define Use Cases


Step 3: Mapping of Requirements to the
Use Case


Step 4, 5: Definition of BlackBox System


Step 6: Definition of GSM-R Architecture


Step 7, 8: Allocating functions and
generating Sequence Diagrams


Example of Model Screenshot

System elements are linked in the model and shown in different diagrams


Mbs Efor Rail Liem

Recommended

Recommended

More Related Content

What's hot

What's hot (18)

Viewers also liked

Viewers also liked (20)

Similar to Mbs Efor Rail Liem

Similar to Mbs Efor Rail Liem (20)

Mbs Efor Rail Liem