System SpecificationSystem of interest

Pascal Krapf, Sebastien Berthier

Syscience

01/05/2019

Reference: Syscience R001, V1

SyscienceSystem Engineering Science

Copyright c© 2017 Syscience R©, all rights reserved

TABLE OF CONTENTS

Table of contents

1 Introduction 31.1 Object of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 System mission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3 Lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.4 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.5 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.5.1 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.5.2 Acronyms definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Stakeholders needs 52.1 Stakeholder context diagram . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Measures of effectiveness . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Environment analysis 103.1 Production use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1.1 Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.2 Utilization use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.1 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.3 Maintenance use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.3.1 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.3.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.4 Retirement use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.4.1 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.4.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4 Operational scenarios 254.1 Collision avoidance scenario . . . . . . . . . . . . . . . . . . . . . . . . . . 264.2 New Destination scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.3 Resume Destination scenario . . . . . . . . . . . . . . . . . . . . . . . . . 29

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 2/30

TABLE OF CONTENTS

1 Introduction

1.1 Object of the document

This document describes the system of interest as a black box, using graphical modelviews. It defines the requirements that the system of interest shall satisfy.

1.2 System mission

The mission of the system of interest consists in providing a service or a product tomain users. The mission is characterized in detail by models and requirements which areidentified in the following paragraphs.

1.3 Lifecycle

The system lifecycle is defined according to standard [IEEE15288]. It can be describedby the following state machine :

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 3/30

TABLE OF CONTENTS

Development

• Concept• Design• Validation

• Concept• Design• Validation

Production

• Parts supply• Assembly• Final check

• Parts supply• Assembly• Final check

Transitionto user

• Showroom• Transportation

• Showroom• Transportation

Utilization

• Utilisation bycustomer

• Utilisation by custo-mer

Maintenance

• Diagnosis• Parts replacements,

repair

• Diagnosis• Parts replacements,

repair

Retirement

• Dismantling• Recycling

• Dismantling• Recycling

SyscienceSystem Engineering Science

Start of production milestone

End of line gate

Delivery to customer

Mission profile ended (km)

lifetime elapsed (years)

Maintenance schedule

Failure

Accident

Not repairableMaintenance accomplished

Figure 1: State LifeCycle: The system lifecycle

1.4 References

• IEEE1220 : IEEE Standard for Application and Management of the Systems En-gineering Process

• IEEE15288 : Systems Engineering - System Life Cycle Processes

• IEEE1471 : IEEE Recommended Practice for Architectural Description of Software-Intensive Systems

1.5 Terminology

1.5.1 Terms

• Stakeholder : entity, person or organization having needs, expectations or con-straints concerning the system of interest

• Lifecycle : succession of phases through which the system passes between theelaboration of the concept and its end of life.

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 4/30

TABLE OF CONTENTS

• Lifecycle phase : phase identified in the lifecycle.

• Diagram : graphical representation of a view of a system

1.5.2 Acronyms definitions

• MBSE : Model Based System Engineering

• RBSE : Requirement Based System Engineering

• COTS : Commercial off the shelf

• SOI : System of interest

• MOP : Measure of performance

• KME : Key measures of effectiveness

• TPM : Technical performance measure

2 Stakeholders needs

Stakeholders are individuals, organizations or enterprise departments who have expecta-tions, needs and constraints for the SOI.Stakeholders are drawn on a context diagram, associated with the collected documents

[IEEE1220] §6.1.1, §6.1.2, §6.1.3).

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 5/30

TABLE OF CONTENTS

2.1 Stakeholder context diagram

Recyclingquality

Recycling strategy[UseCase Retirement]

QualityDepartment 100 ppm quality target

[R004]

Norms &regulationsdepartment

EU Regulation andcertification process

[R001]

Noise andvibrationsengineeringdepartment

Functioning noiseand vibrations spe-cification Refxxx

[R005]

HMI enginee-ring department

[Context HMI engi-neering department]

[R003]

Productmarketting

user prestationexpectation [Use-Case Utilization]

Systemof Interest

Preliminary RiskAnalysis ; Dura-bility objectives,

[UseCase Liabilities]

Safety &Durabilitydepartment

Maintenancedepartment

Workshop constraintsdocument ; Diag-nosis specification

[UseCase Maintenance]

Fabricationand Assembly

processdepartment

Assembly constraintsdocument [Use-

Case Production]

Supply chainparts packaging

specification Refxxx

[R002]

Facilitiesmanagement

established life cycleprocess capabilities

SyscienceSystem Engineering Science

Systemof Interest

Figure 2: Context Stakeholders: Context diagram representing the system of interestsurrounded by stakeholders. Documents transmitted by stakeholders are indicated on thelink between stakeholder and system.

Requirement identi-fier

R003

Requirement Text In order to satisfy HMI engineering department, the Systemof Interest shall comply with [Context HMI engineering depart-ment].

Diagram Context Stakeholders

Table 1: R003, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 6/30

TABLE OF CONTENTS

Requirement identi-fier

R005

Requirement Text In order to satisfy Noise and vibrations engineering depart-ment, the System of Interest shall comply with Functioningnoise and vibrations specification Refxxx.

Diagram Context Stakeholders

Table 2: R005, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Requirement identi-fier

R001

Requirement Text In order to satisfy Norms & regulations department, the Sys-tem of Interest shall comply with EU Regulation and certifica-tion process.

Diagram Context Stakeholders

Table 3: R001, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Requirement identi-fier

R004

Requirement Text In order to satisfy Quality Department, the System of Interestshall comply with 100 ppm quality target.

Diagram Context Stakeholders

Table 4: R004, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Requirement identi-fier

R002

Requirement Text In order to satisfy Supply chain, the System of Interest shallcomply with parts packaging specification Refxxx.

Diagram Context Stakeholders

Table 5: R002, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 7/30

TABLE OF CONTENTS

The usershall receivevisual feed

back from ac-tivation status

switch on a lampaccording to ac-tivation status

[R004]

The usershall be ableto activatewith single

finger action allow switch actuationwith effort below 10N

[R003]

the user shallbe able toidentify if

system is active

be equipped with aswitch with two dif-

ferent stable positions

[R002]

The user shallbe able to

deactivate thesystem from

driver positionbe deactivable by a

switch on inner pannel

[R001]

Systemof Interest

avoid switch actuationwith effort below 5N

The usershall not bedisturbed by

unwantedactivation

[R008]

The user shallbe informedfrom activity

switch on a lamp whenactivity is in progress

[R007]

The user shallbe informedfrom failure

switch on a war-ning lamp when

failure is detected

[R006]

The usershall receiveauditive feedback from ac-tivation status

emit a sound during 5seconds after switch on

[R005]

SyscienceSystem Engineering Science

Systemof Interest

Figure 3: Context HMI engineering department: Details concerning HMI needs,cited in Context Stakeholders

Requirement identi-fier

R001

Requirement Text In order to satisfy HMI engineering department, the Systemof Interest shall be deactivable by a switch on inner pannel.

Diagram Context HMI engineering department

Table 6: R001, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Requirement identi-fier

R002

Requirement Text In order to satisfy HMI engineering department, the Systemof Interest shall be equipped with a switch with two differentstable positions.

Diagram Context HMI engineering department

Table 7: R002, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 8/30

TABLE OF CONTENTS

Requirement identi-fier

R003

Requirement Text In order to satisfy HMI engineering department, the Systemof Interest shall allow switch actuation with effort below 10N.

Diagram Context HMI engineering department

Table 8: R003, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Requirement identi-fier

R004

Requirement Text In order to satisfy HMI engineering department, the System ofInterest shall switch on a lamp according to activation status.

Diagram Context HMI engineering department

Table 9: R004, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Requirement identi-fier

R005

Requirement Text In order to satisfy HMI engineering department, the Systemof Interest shall emit a sound during 5 seconds after switch on.

Diagram Context HMI engineering department

Table 10: R005, cited in the figure Context HMI engineering department, and Con-text Stakeholders

Requirement identi-fier

R006

Requirement Text In order to satisfy HMI engineering department, the System ofInterest shall switch on a warning lamp when failure is detected.

Diagram Context HMI engineering department

Table 11: R006, cited in the figure Context HMI engineering department

Requirement identi-fier

R007

Requirement Text In order to satisfy HMI engineering department, the Systemof Interest shall switch on a lamp when activity is in progress.

Diagram Context HMI engineering department

Table 12: R007, cited in the figure Context HMI engineering department

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 9/30

TABLE OF CONTENTS

Requirement identi-fier

R008

Requirement Text In order to satisfy HMI engineering department, the Systemof Interest shall avoid switch actuation with effort below 5N.

Diagram Context HMI engineering department

Table 13: R008, cited in the figure Context HMI engineering department

2.2 Measures of effectiveness

Key measures of effectiveness (KMEs) reflect overall satisfaction level of stakeholder ex-pectations [IEEE1220] §6.1.5.

• Performance (TPM)

• Safety (TPM)

• Operability (KME)

• usability (KME)

• reliability (TPM)

• maintainability (KME)

• time and cost to train (TPM)

• workload (KME)

• human performance requirements (KME)

3 Environment analysis

Use cases can be identified by a systematical analysis of relations of the system of inter-est with external people, physical environment or collaborating systems in each lifecyclephase [IEEE1220] §6.1.6.

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 10/30

TABLE OF CONTENTS

3.1 Production use cases

3.1.1 Diagram

Part transportand manipulationbefore mounting

Manipulationwithout pinching

or cutting bysharp edge

[R production 1]

droppingbefore mounting

[R production 2]

Factory assem-bling : space,

reach, ergonomics

electrostatic shockduring assembling

[R production 3]

fastening withx N effort

[R production 5]

assembling inless than 1 mn

[R production 6]

diagnosis and finalassembly check

[R production 7]

parameter calibration[R production 8]

software update[R production 9]

SOI

SyscienceSystem Engineering Science

Worker

Chemicals

Assembling tools

Assembly process

Diagnostic tool

Figure 4: UseCase Production: UseCase Production, cited in Context Stakeholders

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 11/30

TABLE OF CONTENTS

3.1.2 Requirements

Requirement identi-fier

R production 1

Requirement Text The system SOI shall enable Manipulation without pinchingor cutting by sharp edge in relation with ”Worker”

Diagram UseCase Production

Table 14: R production 1, cited in the figure UseCase Production

Requirement identi-fier

R production 2

Requirement Text The system SOI shall enable dropping before mounting in re-lation with ”Worker”

Diagram UseCase Production

Table 15: R production 2, cited in the figure UseCase Production

Requirement identi-fier

R production 3

Requirement Text The system SOI shall enable electrostatic shock during assem-bling in relation with ”Worker”, and ”Assembling tools”

Diagram UseCase Production

Table 16: R production 3, cited in the figure UseCase Production

Requirement identi-fier

R production 5

Requirement Text The system SOI shall enable fastening with x N effort in rela-tion with ”Assembling tools”

Diagram UseCase Production

Table 17: R production 5, cited in the figure UseCase Production

Requirement identi-fier

R production 6

Requirement Text The system SOI shall enable assembling in less than 1 mn inrelation with ”Assembly process”

Diagram UseCase Production

Table 18: R production 6, cited in the figure UseCase Production

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 12/30

TABLE OF CONTENTS

Requirement identi-fier

R production 7

Requirement Text The system SOI shall enable diagnosis and final assembly checkin relation with ”Diagnostic tool”

Diagram UseCase Production

Table 19: R production 7, cited in the figure UseCase Production

Requirement identi-fier

R production 8

Requirement Text The system SOI shall enable parameter calibration in relationwith ”Diagnostic tool”

Diagram UseCase Production

Table 20: R production 8, cited in the figure UseCase Production

Requirement identi-fier

R production 9

Requirement Text The system SOI shall enable software update in relation with”Diagnostic tool”

Diagram UseCase Production

Table 21: R production 9, cited in the figure UseCase Production

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 13/30

TABLE OF CONTENTS

3.2 Utilization use cases

3.2.1 Diagrams

driver informationabout system state

[sequence Scenario 2]

[R 01]

operation in rainsnow, sun, wind,ice, hail, dust,fog Conditions

[Sequence Scenario 2]

[R 02]

definition ofdestination [Se-

quence Scenario 4][Sequence Scenario 5]

[R 03]

operation by night,day, dusk conditions[sequence Scenario 2]

[R 04]

Operation onpotholes, pavements,

gravel, snow. . .[sequence Scenario 2]

[R 05]

user informa-tion about roadconstraints [se-

quence Scenario 2]

[R 06]

collision avoidance[Sequence Scenario 2]

[R 07]

SOI

SyscienceSystem Engineering Science

C1 : User

C2 : Vehicleoccupants

C3 : External people

ST1 : Publicadministration

C4 : Wheather

C5 : Atmosphe-ric conditions

C7 : Enlightment

C8 : Road

C14 : Signalisation

C15 : Other vehicle

C16 : Support

C17 : Neigboringelectronic systems

C18 : Neigboringelectronic systems

C20 : Power supply

Figure 5: UseCase Utilization: UseCase Utilization, cited in Context Stakeholders

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 14/30

TABLE OF CONTENTS

accoustic comfortduring operation

[R 09]

outer aspect[R 10]

resistance towater ingress

[R 12]

rain exposure[R 13]

river crossing[R 14]

washing byautomaton

[R 15]

high pres-sure cleaning

[R 16]

operation invibrating environment

[R 18]

EMC interactions[R 19]

operation inexternal eletro-magnetic fields

[R 20]

operationwith externalEMC sensitiveenvironment

[R 21]

low and high voltageon power supply

[R 22]

collision withan obstacle

[R 24]

durability inintensive use

[R 25]

emission of CO2,gases, particles

[R 26]

SOI

SyscienceSystem Engineering Science

C1 : User

C2 : Vehicleoccupants

C3 : External people

C4 : Wheather

C9 : River wade

C10 : Washingautomaton

C11 : Garden hose

C12 : Highpressure cleaner

C13 : Detergent

C15 : Other vehicle

C16 : Support

C17 : Neigboringelectronic systems

C20 : Power supply

C23 : Small animals

C25 : Air

Figure 6: UseCase Liabilities: UseCase Liabilities, cited in Context Stakeholders

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 15/30

TABLE OF CONTENTS

3.2.2 Requirements

Requirement identi-fier

R 01

Requirement Text The system ”SOI” shall enable use case ”driver informationabout system state [sequence Scenario 2]” in relation with ac-tor(s) ”C1 : User”

Diagram UseCase Utilization

Table 22: R 01, cited in the figure UseCase Utilization

Requirement identi-fier

R 02

Requirement Text The system ”SOI” shall enable use case ”operation in rainsnow, sun, wind, ice, hail, dust, fog Conditions [Sequence -Scenario 2]” in relation with actor(s) ”C1 : User”, and ”C4 :Wheather”

Diagram UseCase Utilization

Table 23: R 02, cited in the figure UseCase Utilization

Requirement identi-fier

R 03

Requirement Text The system ”SOI” shall enable use case ”definition of desti-nation [Sequence Scenario 4][Sequence Scenario 5]” in relationwith actor(s) ”C5 : Atmospheric conditions”

Diagram UseCase Utilization

Table 24: R 03, cited in the figure UseCase Utilization

Requirement identi-fier

R 04

Requirement Text The system ”SOI” shall enable use case ”operation by night,day, dusk conditions [sequence Scenario 2]” in relation withactor(s) ”C7 : Enlightment”

Diagram UseCase Utilization

Table 25: R 04, cited in the figure UseCase Utilization

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 16/30

TABLE OF CONTENTS

Requirement identi-fier

R 05

Requirement Text The system ”SOI” shall enable use case ”Operation on pot-holes, pavements, gravel, snow. . . [sequence Scenario 2]” in re-lation with actor(s) ”C8 : Road ”

Diagram UseCase Utilization

Table 26: R 05, cited in the figure UseCase Utilization

Requirement identi-fier

R 06

Requirement Text The system ”SOI” shall enable use case ”user informationabout road constraints [sequence Scenario 2]” in relation withactor(s) ”C14 : Signalisation”

Diagram UseCase Utilization

Table 27: R 06, cited in the figure UseCase Utilization

Requirement identi-fier

R 07

Requirement Text The system ”SOI” shall enable use case ”collision avoidance[Sequence Scenario 2]” in relation with actor(s) ”C15 : Othervehicle”

Diagram UseCase Utilization

Table 28: R 07, cited in the figure UseCase Utilization

Requirement identi-fier

R 09

Requirement Text The system ”SOI” shall enable use case ”accoustic comfortduring operation” in relation with actor(s) ”C1 : User”, and”C2 : Vehicle occupants”

Diagram UseCase Liabilities

Table 29: R 09, cited in the figure UseCase Liabilities

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 17/30

TABLE OF CONTENTS

Requirement identi-fier

R 10

Requirement Text The system ”SOI” shall enable use case ”outer aspect” in rela-tion with actor(s) ”C1 : User”, ”C2 : Vehicle occupants”, and”C3 : External people”

Diagram UseCase Liabilities

Table 30: R 10, cited in the figure UseCase Liabilities

Requirement identi-fier

R 12

Requirement Text The system ”SOI” shall enable use case ”resistance to wateringress” in relation with actor(s) ”C4 : Wheather”, ”C9 : Riverwade”, ”C10 : Washing automaton”, ”C11 : Garden hose”,”C12 : High pressure cleaner”, and ”C13 : Detergent”

Diagram UseCase Liabilities

Table 31: R 12, cited in the figure UseCase Liabilities

Requirement identi-fier

R 13

Requirement Text The system ”SOI” shall enable use case ”rain exposure” inrelation with actor(s) ”C4 : Wheather”

Diagram UseCase Liabilities

Table 32: R 13, cited in the figure UseCase Liabilities

Requirement identi-fier

R 14

Requirement Text The system ”SOI” shall enable use case ”river crossing” inrelation with actor(s) ”C9 : River wade”

Diagram UseCase Liabilities

Table 33: R 14, cited in the figure UseCase Liabilities

Requirement identi-fier

R 15

Requirement Text The system ”SOI” shall enable use case ”washing by automa-ton” in relation with actor(s) ”C10 : Washing automaton”, and”C13 : Detergent”

Diagram UseCase Liabilities

Table 34: R 15, cited in the figure UseCase Liabilities

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 18/30

TABLE OF CONTENTS

Requirement identi-fier

R 16

Requirement Text The system ”SOI” shall enable use case ”high pressure clean-ing” in relation with actor(s) ”C12 : High pressure cleaner”,and ”C13 : Detergent”

Diagram UseCase Liabilities

Table 35: R 16, cited in the figure UseCase Liabilities

Requirement identi-fier

R 18

Requirement Text The system ”SOI” shall enable use case ”operation in vibratingenvironment” in relation with actor(s) ”C16 : Support”

Diagram UseCase Liabilities

Table 36: R 18, cited in the figure UseCase Liabilities

Requirement identi-fier

R 19

Requirement Text The system ”SOI” shall enable use case ”EMC interactions”in relation with actor(s) ”C17 : Neigboring electronic systems”

Diagram UseCase Liabilities

Table 37: R 19, cited in the figure UseCase Liabilities

Requirement identi-fier

R 20

Requirement Text The system ”SOI” shall enable use case ”operation in externaleletromagnetic fields” in relation with actor(s) ”C17 : Neigbor-ing electronic systems”

Diagram UseCase Liabilities

Table 38: R 20, cited in the figure UseCase Liabilities

Requirement identi-fier

R 21

Requirement Text The system ”SOI” shall enable use case ”operation with exter-nal EMC sensitive environment” in relation with actor(s) ”C17: Neigboring electronic systems”

Diagram UseCase Liabilities

Table 39: R 21, cited in the figure UseCase Liabilities

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 19/30

TABLE OF CONTENTS

Requirement identi-fier

R 22

Requirement Text The system ”SOI” shall enable use case ”low and high volt-age on power supply” in relation with actor(s) ”C20 : Powersupply”

Diagram UseCase Liabilities

Table 40: R 22, cited in the figure UseCase Liabilities

Requirement identi-fier

R 24

Requirement Text The system ”SOI” shall enable use case ”collision with anobstacle” in relation with actor(s) ”C15 : Other vehicle”, and”C23 : Small animals”

Diagram UseCase Liabilities

Table 41: R 24, cited in the figure UseCase Liabilities

Requirement identi-fier

R 25

Requirement Text The system ”SOI” shall enable use case ”durability in intensiveuse ” in relation with actor(s) ”C1 : User”

Diagram UseCase Liabilities

Table 42: R 25, cited in the figure UseCase Liabilities

Requirement identi-fier

R 26

Requirement Text The system ”SOI” shall enable use case ”emission of CO2,gases, particles” in relation with actor(s) ”C25 : Air”

Diagram UseCase Liabilities

Table 43: R 26, cited in the figure UseCase Liabilities

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 20/30

TABLE OF CONTENTS

3.3 Maintenance use cases

3.3.1 Diagrams

disassembling withspace and reach

ergonomic conditons

[R 27]

exposure todust, dirt, oil

[R 34]

part manipu-lation without

pinching, cutting

[R 28]

disassemblingand reassembling

[R 29]

failure codes reading[R 30]

view dynamicparameters

[R 31]

parametersadjustment

[R 32]

software update[R 33]

SOI

SyscienceSystem Engineering Science

Maintenance team

Maintenanceoperator

Mechanical tools

Electronic Tools

Electronic Tools

Workshop

Figure 7: UseCase Maintenance: UseCase Maintenance, cited in Con-text Stakeholders

3.3.2 Requirements

Requirement identi-fier

R 27

Requirement Text The system ”SOI” shall enable use case ”disassembling withspace and reach ergonomic conditons” in relation with actor(s)”Maintenance team”

Diagram UseCase Maintenance

Table 44: R 27, cited in the figure UseCase Maintenance

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 21/30

TABLE OF CONTENTS

Requirement identi-fier

R 34

Requirement Text The system ”SOI” shall enable use case ”exposure to dust,dirt, oil” in relation with actor(s) ”Workshop”

Diagram UseCase Maintenance

Table 45: R 34, cited in the figure UseCase Maintenance

Requirement identi-fier

R 28

Requirement Text The system ”SOI” shall enable use case ”part manipulationwithout pinching, cutting ” in relation with actor(s) ”Mainte-nance operator”

Diagram UseCase Maintenance

Table 46: R 28, cited in the figure UseCase Maintenance

Requirement identi-fier

R 29

Requirement Text The system ”SOI” shall enable use case ”disassembling andreassembling” in relation with actor(s) ”Mechanical tools”

Diagram UseCase Maintenance

Table 47: R 29, cited in the figure UseCase Maintenance

Requirement identi-fier

R 30

Requirement Text The system ”SOI” shall enable use case ”failure codes reading”in relation with actor(s) ”Electronic Tools”

Diagram UseCase Maintenance

Table 48: R 30, cited in the figure UseCase Maintenance

Requirement identi-fier

R 31

Requirement Text The system ”SOI” shall enable use case ”view dynamic pa-rameters” in relation with actor(s) ”Electronic Tools”

Diagram UseCase Maintenance

Table 49: R 31, cited in the figure UseCase Maintenance

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 22/30

TABLE OF CONTENTS

Requirement identi-fier

R 32

Requirement Text The system ”SOI” shall enable use case ”parameters adjust-ment” in relation with actor(s) ”Electronic Tools”

Diagram UseCase Maintenance

Table 50: R 32, cited in the figure UseCase Maintenance

Requirement identi-fier

R 33

Requirement Text The system ”SOI” shall enable use case ”software update” inrelation with actor(s) ”Electronic Tools”

Diagram UseCase Maintenance

Table 51: R 33, cited in the figure UseCase Maintenance

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 23/30

TABLE OF CONTENTS

3.4 Retirement use cases

3.4.1 Diagrams

Storage beforedismantling

Fluids contain-ment duringstoring period

[R 41]

compliancefor materials

under regulation(lead, hexavalent

chrome, quicksiver)

[R 38]

dismantling

Separationof reusablecomponents

[R 35]

materialssorting according

to marking

[R 36]

separation ofplastic parts andmetallic parts

[R 37]

SOI

SyscienceSystem Engineering Science

Recycling operator

Recycling chain

Recycling tools

Natural ecosystem

Air

Water

Soil

Figure 8: UseCase Retirement: UseCase Retirement, cited in Context Stakeholders

3.4.2 Requirements

Requirement identi-fier

R 41

Requirement Text The system ”SOI” shall enable use case ”Fluids containmentduring storing period” in relation with actor(s) ”Water”, and”Soil”

Diagram UseCase Retirement

Table 52: R 41, cited in the figure UseCase Retirement

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 24/30

TABLE OF CONTENTS

Requirement identi-fier

R 38

Requirement Text The system ”SOI” shall enable use case ”compliance for ma-terials under regulation (lead, hexavalent chrome, quicksiver)”in relation with actor(s) ”Natural ecosystem”

Diagram UseCase Retirement

Table 53: R 38, cited in the figure UseCase Retirement

Requirement identi-fier

R 35

Requirement Text The system ”SOI” shall enable use case ”Separation of reusablecomponents” in relation with actor(s) ”Recycling operator”,and ”Recycling tools”

Diagram UseCase Retirement

Table 54: R 35, cited in the figure UseCase Retirement

Requirement identi-fier

R 36

Requirement Text The system ”SOI” shall enable use case ”materials sorting ac-cording to marking” in relation with actor(s) ”Recycling chain”

Diagram UseCase Retirement

Table 55: R 36, cited in the figure UseCase Retirement

Requirement identi-fier

R 37

Requirement Text The system ”SOI” shall enable use case ”separation of plasticparts and metallic parts” in relation with actor(s) ”Recyclingtools”

Diagram UseCase Retirement

Table 56: R 37, cited in the figure UseCase Retirement

4 Operational scenarios

Operational scenarios are identified by the analysis of stakeholder documents [IEEE1220]§6.1.4. Activities are represented by rectangle boxes centered on the lifeline associatedto each actor. The following diagrams describe operational scenarios for the system ofinterest.

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 25/30

TABLE OF CONTENTS

4.1 Collision avoidance scenario

Activities

User ObstacleExternalpeople

EcosystemExternalsystem C

SOI Atmosphere AnimalExtrenalsystem B

Initial state :the system is idle

Requests autopilot activation

Activate auto pilot onuser request [CA01]

Is on trajectory

correct trajectoryif collision risk isdetected [CA02]

Is on trajectory

correct trajectoryif collision risk isdetected [R0002]

Adapt to new tra-jectory [CA03]

Adapt to new tra-jectory [CA04]

User request

Trajectory

Observed scene

Trajectory

Observed scene

New trajectory

SyscienceSystem Engineering Science

Figure 9: Sequence Collision Avoidance: Operational scenario for the system ofinterest

Requirement identi-fier

CA01

Requirement Text The system ”SOI” shall ”Activate auto pilot on user request” when receiving ”User request”

Diagram Sequence Collision Avoidance

Table 57: CA01, cited in the figure Sequence Collision Avoidance

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 26/30

TABLE OF CONTENTS

Requirement identi-fier

CA02

Requirement Text The system ”SOI” shall ”correct trajectory if collision risk isdetected” when receiving ”Observed scene”

Diagram Sequence Collision Avoidance

Table 58: CA02, cited in the figure Sequence Collision Avoidance

Requirement identi-fier

CA03

Requirement Text The system ”Extrenal system B” shall ”Adapt to new trajec-tory” when receiving ”New trajectory”

Diagram Sequence Collision Avoidance

Table 59: CA03, cited in the figure Sequence Collision Avoidance

Requirement identi-fier

CA04

Requirement Text The system ”External system C” shall ”Adapt to new trajec-tory” when receiving ”New trajectory”

Diagram Sequence Collision Avoidance

Table 60: CA04, cited in the figure Sequence Collision Avoidance

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 27/30

TABLE OF CONTENTS

4.2 New Destination scenario

Activities

User ObstacleExternalpeople

Braking system

SOI Road Ecosystem GPS system

Initial state : thesystem is OFF

Switch on the auto pilot

If no destination me-morized, ask the user to

define destination [ND01]

Defines destination

Ask for the cur-rent position [ND02]

transmits current position

Calculates path and delay

Requests autopilot activation

Starts movement

Switch on

Request to define destination

Destination

position request

current position

delay

activation

SyscienceSystem Engineering Science

Figure 10: Sequence New Destination: Operational scenario for the system of interest

Requirement identi-fier

ND01

Requirement Text The system ”SOI” shall ”If no destination memorized, ask theuser to define destination” when receiving ”Switch on”

Diagram Sequence New Destination

Table 61: ND01, cited in the figure Sequence New Destination

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 28/30

TABLE OF CONTENTS

Requirement identi-fier

ND02

Requirement Text The system ”SOI” shall ”Ask for the current position” whenreceiving ”Destination”

Diagram Sequence New Destination

Table 62: ND02, cited in the figure Sequence New Destination

4.3 Resume Destination scenario

Activities

User ObstacleExternalpeople

Braking system

SOI Road Ecosystem GPS system

Initial state : thesystem is OFF

Switch on the auto pilot

If destination al-ready memorized,

display the memorizeddestination [RD01]

validates memo-rized destination

Ask for the cur-rent position [RD02]

transmits current position

Calculates path and delay

Requests autopilot activation

Starts movement

Switch on

Memorized destination

Destination

position request

current position

delay

activation

SyscienceSystem Engineering Science

Figure 11: Sequence Resume Destination: Operational scenario for the system ofinterest

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 29/30

TABLE OF CONTENTS

Requirement identi-fier

RD01

Requirement Text The system ”SOI” shall ”If destination already memorized,display the memorized destination” when receiving ”Switch on”

Diagram Sequence Resume Destination

Table 63: RD01, cited in the figure Sequence Resume Destination

Requirement identi-fier

RD02

Requirement Text The system ”SOI” shall ”Ask for the current position” whenreceiving ”Destination”

Diagram Sequence Resume Destination

Table 64: RD02, cited in the figure Sequence Resume Destination

Syscience R001, V1, 01/05/2019, Pascal Krapf, Sebastien Berthier et al. Page 30/30