A tooleD MethoD to

Supporting Validating/Justifying
solution against operational Need
in engineering easing Impact analysis
ViewPoints
A2 Operational Analysis
A3 What the users of
the system need to
Need understanding

A1

accomplish

F2 F4 Reqs
Product Line Functional &
Managers Requirement
Non Functional Need
F5
Customers Managers
F1 F3
What the system has to
ViewPoints accomplish for the users
Shared & Capitalised
Architecture Models A : Operational activity
F : Function
F21 F22
Architects Logistics C : Component
design authority Engineers C2
F6
Safety, Performance,
SW/HW
Others F1 Logical Architecture
interface Engineers F3
Solution architectural design

IVVQ Manager
Designers & C3 How the system will work
Developpers C1

ViewPoints

F21 F22
C2
F6 C12

F1

C11 C1
F7
C3
C4
Physical Architecture
How the system will be
Buses Processors
developed and built
ViewPoints

compatible with most processes

top-down bottom-up, iterative, legacy-based, mixed

Top-down
OPERATIONAL NEED ANALYSIS Done & Checked

FUNCTIONAL / NON FUNCTIONAL NEED ANALYSIS Done & Checked

Method layers

LOGICAL ARCHITECTURE DESIGN Iterative, incremental Done & Checked

PHYSICAL ARCHITECTURE DESIGN Done & Checked

CONTRACTS FOR DEVELOPMENT & IVVQ Bottom-up, legacy, Reuse Done & Checked

Time
 MethoD StepS taSKS SaMple MoDel

customer BROADCASTING STATION

operational capabilities
Elaborate Radio Programs

Need analysis perform an

Radio contents

what the users of the operational need ENVIRONMENT USER

analysis News Radio channel
system need to Broadcast Radio channels
Music Radio channel
Get news

accomplish Listen to Music

NeeD

perform a capability
System/ trade-off analysis E
Select radio Station

Sw/hw
station
N
perform a functional V Frquency Volume
Need analysis
I
USER
and non-functional R
O
analysis N EM waves Radio signal Audio sound
what the system has M
Receive radio
signal
Play radio
contents

to accomplish for the Formalise and E

N
users consolidate T RADIO SET Radio name

requirements

logical drivers and viewpoints

Frequency tuning
Frequency Station

architecture
Select radio frequency
U
S
Radio E
signal Volume
Build candidate Receive radio signal Play radio signal Select Sound volume R

Design
Sound
RADIO RECEIVER level Audio sound
architectural EM Extract radio RDS Display radio name
wave name Radio

how the system will breakdowns in ENVIRONMENT RADIO CONTROL USER INTERFACE
name

components
expectations select best compromise
architecture

RCA audio cable

patterns
physical Serial
SolutIoNS

RS232
Play radio signal Select radio signal

architecture
RCA
consider reuse of existing
HF REVEIVER
audio AUDIO PROCESSING USER INPUT PROCESSING
cable Serial
AUDIO PROCESSOR RS232 KEYBOARD PROCESSOR
assets design a physical
SPEAKER

Design
Serial
RS232
Q W E
USER
DEMODULATOR Serial A S
Discrete RS232
design a physical I/O

how the system will

ANALOG BOARD
VGA video
reference architecture
Extract radio name Display radio name
cable

be developed & built RDS MANAGER

MICRO CONTROLLER
DISPLAY GENERATION

DISPLAY

validate and check it

1
RADIO SET Speaker

Development
Prime item
BODY USER INTERFACE
HWCI
Controller

contracts ivvQ strategy HF Receiver MAIN RACK

CSCI
Analog board
Demodulator 2
Controller
Audio processor COTS
Audio processing
Analog board
what is expected Radio control
Audio processor CABLING

from each designer/ pBs and component User input processing

Rack mechanics
VGA cable
integration contract
Display

sub-contractor 4
RS 232 cable

Discrete I/O
2
RCA cable
coNceptS DeScrIptIoN MeaNS

- Operational capabilities FUNCTION

- actors, operational entities : functions, op.

- actor activities activities interactions &
- interactions between activities & actors exchanges
- information used in activities &
interactions
- Operational processes chaining
activities
Scenarios:
- scenarios for dynamic behaviour
actors, system,
components interactions
& exchanges

- actors and system, capabilities FUNCTION

- Functions of system & actors

operational processes
- information used in functions & through functions &
exchanges, data model op. activities
- scenarios for dynamic behaviour
- Modes & states
START

MODE 1

MODE 3

MODE 2 END

saMe cOncepts, plus :

- components Modes & states
- component ports and interfaces of actors, system,
- exchanges between components components
- Function allocation to components Breakdown of functions
& components
functional exchanges allocation
SOUND PROFILE TUNING VALUE
Values : From 0 to +100
is composed of

Data model LOUDNESS TREBBLE LEVEL

uses
FREQUENCY BAND
Values : 0.1, 0.2, 3.0, 6.0
Unit : KHz

& scenario contents, BASS LEVEL FREQUENCY

saMe cOncepts, plus :

Values : From 88 to +108
is kind of Unit : MHz

interfaces FILTER VALUE

Values : From -50 to +50

logical ones, and implementing Unit : dB

functional behaviour
- implementation components
supplying resources for behavioural ACTOR 1 ACTOR 2

components component wiring:

- physical links between all kinds of components
implementation components

BEHAVIORAL COMPONENT
Functional Flow

allocation FUNCTION

of op.activities to actors,
- parts numbers, quantities
of functions to components,
- development contract (expected
of behav.components
behaviour, interfaces, scenarios,
to impl.components,
resource consumption, non-functional
properties)
BEHAVIORAL COMPONENT
 System Enable
Function Disable
MODE
Activates

Function
DyNaMIc BehaVIour

User
MODE
Function
Triggers

DATA

USER SYSTEM

References References References

Mode or State

Function

Mode or State

Verifying & checking solution against

Non-functional & Industrial Stakes
Method layers

OperatiOnal need analysis Max reaction time to threat Feared events

Functional chain (Fc) to react to threat.

FunctiOnal/nOn FunctiOnal need analysis critical functional chains associated to events
Maximum allowed latency on Fc

processing & exchanges complexity

lOgical architecture design redundancy paths securing functional chains
Functional chains allocation

resource consumption on Fc common failure modes

physical architecture design
resulting computing latency Fault propagation on Fc

cOntracts FOr develOpMent & ivvQ allocated resources to satisfy latency needed reliability level
VIewpoINtS (exaMpleS)

Cost & Schedule Maintainability IVVQ

NoN fuNctIoNal

Interfaces Safety/security Product Policy

Performance ...

< 2 seconds
ARCHITECTURE CHECK
performance
Operational

Compute function traversal time

Latency : according to implem component
New attribute of functional & comms perf
Deduce achieved latency &

R1
A
Compare redundancy level
Safety

R2 B VOTE Voter : with functional chain criticity

Redundancy :
Propagate HW failures to
R3 C component functional chains
performance

CLIENT
Technical

Load balanced cluster : Compute load based on

Server 1 Server 2 New concept functions & check adequacy
Design by webrand . www.webrand.fr . paris & Nice

Both on computing power and

communication bandwidth

Functions or components
architecture
Resulting

MULTI-VIEWPOINT
CHECK OF ARCHITECTURE