Professional Documents
Culture Documents
System Architecture Template
System Architecture Template
Prepared By:
System Architecture Team
Nexteer Automotive
Draft/
Released
Table of Contents
1 Modeling Methodology.............................................................................................4
2 Scope.........................................................................................................................5
2.1 Functional Scope..........................................................................................................................5
3 Alternative Architecture.............................................................................................6
4 Features List...............................................................................................................7
5 EPS Operational Domain............................................................................................9
6 EPS Physical Domain................................................................................................11
7 EPS Functional Domain............................................................................................15
7.1 Connect driver to road wheels...................................................................................................18
7.2 Monitor driver input..................................................................................................................18
7.3 Monitor environment system characteristics.............................................................................18
7.4 Communication with external environment..............................................................................18
7.5 Provide Assistance.....................................................................................................................18
7.6 Protect System...........................................................................................................................19
7.7 Provide power supply................................................................................................................19
7.8 Exhibit dynamic system behavior...............................................................................................19
7.9 Support EPS Logic Processing.....................................................................................................19
8 EPS System Dynamic Behavior (System State Machine)............................................20
9 Table Views..............................................................................................................21
9.1 Table - Interface Signal Description............................................................................................21
9.2 Table - System Function Interfaces.............................................................................................21
9.3 Table - System Function – Subsystem Function Interfaces.........................................................21
1 Modeling Methodology
bdd [Package] _1_Modeling Method [Modeling Methodology1]
«EP S Sy sF unction»
port_0
Standard Ports Eps System
are used Function
interface with
«EP S Sy stem» System Functions
EPS System
«MechanicalA ctuatorF uncion» «P ow erpck F unction» «Driv rSensingSubsy stF unction»
Mechanical Powerpack Driver Sensing
1 Actuator Function Subsystem
Directed
«EP S Subsy stm» Composition Function Function
EPS SubSystem relation is used to
decompose the
system into small «Motor Sensing F unction» «C ontrol M odule F unction» «MotorA ssembly F unction»
subsystems
Motor Sensing Control Module Motor Assembly
«full» Subsystem Function Function
«P ow erpack Subsy stem»
:EPS SubSystem Function
Powerpack
Subsystem
«proxy» «Softw are F unction» «Electronic Hardw are F unction»
Full ports are :StubInterfaceBlock
Software Electronic
used to interface
Function Hardware
with external
Function
environment.
«C ontrolmodule Subsy stem»
Control Module
Subsystem
These are the stereotypes of SysML 'Block' used to represent the EPS functions,
These are the stereotypes of SysML individual stereotypes created to represent the each function group.
'Block' used to represent the EPS system
physical domain. EPS System stereotype
is used to represent the EPS and
EPS Subsystem stereotype is used to
represent EPS subsystems like
Mechanical Actuator, Powerpack,
Driversensing Subsystem. Likewise
powerpack subsystems are rpresented «EP S F eature»
by Powerpack Subsystem and EPS Feature
This stereotype is used to represent the EPS features.
control module subsystems are
represented by Controlmodule
Subsystem stereotype.
2 Scope
2.1 Functional Scope
This System architecture document list down all features and functions applicable for <Customer Name>
<Program Number>.
Note:
Features: Customer controlled
Function: Nexteer controlled
3 Alternative Architecture
<Team to select one of the below applicable approach>
EPS core system architecture is a legacy system with well proven and defined architecture. Program <name>
uses the existing core architecture <as is/ with a few configuration & variation>. Hence an alternative
architecture evaluation is not required.
A new system architecture was developed for Program <name>. Hence an alternative architecture analysis was
conducted. <This is stored at Location/ This is available in embedded file/ This is available below for reference
(Paste the analysis)>
Note: Above strategy needs review and approval from System Architecture Workshop Group <Remove this
statement before baselining this work product>
4 Features List
«V ehicle»
Automobile
«Operator»
«EP S Sy stem»
1
1
itsDriver
EPS itsEPS
Driver
«V ehicle Subsy stem» 1
Steering Wheel itsSteering Wheel
* «V ehicle S ubsy stem»
itsSteering knuckle Steering knuckle
«V ehicle Subsy stem» *
Vehicle ECU itsVehicle ECU
This diagram shows operational domain of the EPS, i.e., the EPS in the context of its environment. This
includes the humans that are intended to operate and interact with the system, external objects that might
influence the system, and environmental elements that could impact the system.
IAD [Vehicle] Automotive Power Stee ring Doma in [IAD#1 Of Automotive Powe r Steering Domain]
1 «EPSSysUsage»
:EPS 1..* «VehicleSubsysUsage»
:Powe rSupply :Vehicle Batte ry
:Powe rSupply
«full»
:Exte rnalForces
:Stee ringInput
This diagram shows how EPS is interacting with another systems/subsystem in its operational domain. It shows
the external interfaces of the EPS.
Note: This section needs to be customized as per program specific requirements
This diagram shows the physical decomposition of the EPS, i.e., how EPS is decomposed to smaller
subsystems and subsystems decomposition. EPS is decomposed to Powerpack, Mechanical Actuator and Driver
Sensing Subsystem.
Powerpack is further decomposed to Control Module, Motor Sensing Subsystem and Motor Assembly. Control
Module is decomposed to Electronic Hardware and Software.
This is the Physical Internal Architecture Diagram for the EPS System. This diagram shows how the parts of
"EPS" are connected internally and interfaces between its parts (subsystem / subfunction).
:~DistributedSupplyVoltage
:SensedMotAg
:DistributedSupplyVoltage
:~SensedHwTq
:GeneratedMotorTorque
:~SensedHwTq
:~SensedHwAg
:~SensedHwAg
«full»
:Communication :MotorPhaseVoltage
«full»
:Communication
«full»
:PowerSupply «full»
:PowerSupply
«full» «full»
:EpsEnable :EpsEnable
This is the Internal Architecture Diagram for the EPS Subsystem called Powerpack. This diagram shows how the
parts of "Powerpack" are connected internally and interfaces between its parts (subsystem / subfunction).
:HwTqHW2SW :~HwTqHW2SW
«full» «full»
:PowerSupply :PowerSupply
:PwrSpplyRailsStat :~PwrSpplyRailsStat
:HwAgHW2SW :~HwAgHW2SW
:~SensedMotAg :~SensedMotAg
:FilteredEPSEnable :~FilteredEPSEnable
:FltrdSplyVltgHW2SW :~FltrdSplyVltgHW2SW
:CMTempHW2SW :~CMTempHW2SW
:MotCurrentHW2SW :~MotCurrentHW2SW
:~WD_IN
:WD_IN
:~SensedHwAg :~SensedHwAg
:~SineVoltageSignal :SineVoltageSignal
:~MemoryServices :MemoryServices
:~CommunicationServices :CommunicationServices
:RxAuthenticatedData
:~RxAuthenticatedData
:~TxMACGenData
:TxMACGenData
:~RxMACVerfyData
:RxMACVerfyData
«full» :TxSecuredData
:EpsEnable :~TxSecuredData
:ImcRxTx
:~ImcRxTx
:~NVMData
:NVMData
:ECUIdnHW2SW :~ECUIdnHW2SW
:ImcBus
:MotorPhaseVoltage :MotorPhaseVoltage
:DistributedSupplyVoltage :DistributedSupplyVoltage
This is the Internal Architecture Diagram for the Powerpack Subsystem called Control Module. This diagram
shows how the parts of "Control Module" are connected internally and interfaces between its parts
(subsystem / subfunction).
Note: This section needs to be customized as per program specific requirements
«E P S S y stem»
EPS
«E P S S y sF unction»
1_Connect Driver to road wheels
«E P S S y sF unction»
2_Monitor Driver Input
«E P S S y sF unction»
4_communication with external environment
«E P S S y sF unction»
6_Protect system
«E P S S y sF unction»
7_Provide power supply
«E P S S y sF unction»
8_Exhibit dynamic system behaviour
«E P S S y sF unction»
9_Support EPS logic processing
This diagram shows the functional decomposition of the EPS, these are the different functionalities of EPS to
fulfill the customer requirements. These functions are referred as system functions.
«E PS S y sF uncUsage»
«full» «full» 1
:SteeringOutput :SteeringOutput :1_Connect Driver to road
wheels
«full»
«full»
:SteeringInput 1 «EPS Sy sF uncU sage» 1 «EPS Sy sF uncU sage»
:SteeringInput
:2_Monitor Driver Input :3_Monitor Environment system characteristics
«full»
«full» :ExternalForces
:ExternalForces
«full»
:EpsEnable
1 «E PS S y sF uncUsage» 1 «EPS Sy sF uncU sage»
:4_communicat :8_Exhibit
ion with dynamic system
external behaviour
environment _2MntrDrvInp_8
_2MntrDrvInp_4
_3MntrEnvSysChar_4 _3MntrEnvSysChar_8
«full»
:EpsEnable
_4CommWithExtEnv_8
_4CommWithExtEnv
_5PrvdAssist_8
«full»
:Communication _7PrvdPwrSup_4
_8ExhbtDynBhvr_4 _7PrvdPwrSup_8
_9EPSPrcLgc_4
_8ExhbtDynBhvr
«full»
:Communication
_6PrtcnSys_4
_9EPSPrcLgc_8
1 «E PS S y sF uncUsage»
:5_Provide
Assistance
_2MntrDrvInp_5
1 «EPS Sy sF uncU sage»
:9_Support EPS
_2MntrDrvInp_9 logic processing
_3MntrEnvSysChar_5
_4CommWithExtEnv_5 _3MntrEnvSysChar_9
_5PrvdAssist
_4CommWithExtEnv_9
_6PrtcnSys_5
_7PrvdPwrSup_9
_7PrvdPwrSup_5
_8ExhbtDynBhvr_9
_8ExhbtDynBhvr_5
_9EPSPrcLgc
_9EPSPrcLgc_5
This is the Internal Architecture Diagram for the EPS System called EPS. This diagram shows how the parts of
"EPS" are connected internally and interfaces between its parts (subsystem / subfunction).
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 1.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 2.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 3.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 4.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 5.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 6.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 7.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 8.
Click on Pdf to see the function definition diagram (FDD) and Internal Architecture Diagram IAD(s) of Function 9.
Note: This functional architecture(section 7) needs to be customized as per program specific requirements
S1_OFF
C 8[[Reception of a request for immediate transition to OFF ||
No reception of wake up signal]]
Note:This System Dynamic Behavior needs to be customized as per program specific requirements
9 Table Views
This package contains different table views of the system like list of functions with description, list of features,
contracts between the functions, external interfaces data, Interface block descriptions etc.
Note: These tables needs to be customized as per program specific requirements
This table shows the long names for the interface signals used in Internal Architecture Diagrams (IAD’s).
This table shows the Interfaces between the system functions of EPS system
This table shows the Interfaces between the system functions and subsystem functions of EPS system