DAS AUTOSAR Configuration Documentation Work Instruction

ID: <DocID>
Revision: 0.4 DAS

Status: Draft AUTOSAR Configuration
documentation
PROPRIETY NOTICE: This copyrighted document is the property of TRW and is disclosed in confidence. It may not be copied, disclosed to others, or used for
Author: Omkar Sudame

Date: 12-Jan-2014 Work Instruction
Page: 1 of 26
DAS
AUTOSAR Configuration documentation
Work Instruction
manufacturing, without the prior written consent of TRW.  2014 TRW
CM System Information (automatically entered):

$ProjectName: $
$RCSfile: $
$Revision: $
$Date: $
$Author: $
Filename: Document1
Template filename: DAS_Work_Instruction_Template.dotx
Template revision: 0.4
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 2 of 26
Revision History
Revision Date Prepared By Reviewed By Approved By Changelog
1.1 16-Oct-2015 Omkar Francesco Initial Version

Sudame Matraxia
1.2 16-Oct-2015 Omkar Added snapshot for

Sudame table view
1.4 19-Oct-2015 Omkar Updated document

Sudame revision
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 3 of 26
Table of Contents
1 Purpose ..............................................................................................................................................4
2 Definitions and Abbreviations .........................................................................................................5
2.1 Definitions .................................................................................................................................. 5
2.2 Abbreviations ............................................................................................................................. 5
3 Scope ..................................................................................................................................................6
3.1 Overview .................................................................................................................................... 6
4 Instructions ........................................................................................................................................6
4.1 Work flow Scenarios .................................................................................................................. 6
4.1.1 Flow for initial design ........................................................................................................... 6
4.1.2 Flow for update in design .................................................................................................... 7
4.2 Work instructions ....................................................................................................................... 8
4.2.1 Exporting configuration from EB Tresos® Studio ................................................................ 8
4.2.2 Creating new project for implementation model.................................................................. 9
4.2.3 Adding SysML profile to implementation model ................................................................ 10
4.2.4 Adding SW domain architecture model to implementation model .................................... 10
4.2.5 Importing AUTOSAR configuration to implementation model........................................... 12
4.2.6 Creating rationale in model ............................................................................................... 16
4.2.7 Establishing traceability through dependency................................................................... 16
4.2.8 Identifying differences in configuration .............................................................................. 18
4.2.9 Generating report for difference between ARPackages ................................................... 20

4.2.10 Removing configuration unit from project ......................................................................... 21
4.2.11 Remove containers/parameters from merged configuration............................................. 22
4.2.12 Adding file as unit to model ............................................................................................... 23
4.2.13 Customizing table/matrix scope ........................................................................................ 23
5 References .........................................................................................................................................26
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 4 of 26
1 Purpose
The purpose of this document is to provide detailed work instructions how to document AUTOSAR
Configuration using IBM Rational Rhapsody®.
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 5 of 26
2 Definitions and Abbreviations

2.1 Definitions
Term Definition
Parameter Parameter defines value for attribute in module. AUTOSAR defines multiplicity, min and
max value and type of parameter in metamodel. Parameter may have type integer,
float, Boolean etc.
Container Container is an aggregation of parameters. Containers are defined in ARXML file with
tag “ECUC-PARAM-CONF-CONTAINER-DEF”.
SW domain architecture Rhapsody Model to design and establish traceability between design to requirements.
model
Implementation model Rhapsody model to establish rationales and traceability between BSW
configuration/SWC description and design. Implementation model is updated by
imported ARXML files.
AUTOSAR Configuration AUTOSAR configuration file is .ARXML file.
file
Rhapsody model file Rhapsody model file is Rhapsody model in .sbs format.
2.2 Abbreviations
Acronym Full Form

AUTOSAR AUTomotive Open System ARchitecture
BSW Basic software in AUTOSAR stack
SWC Application Software component

SW Software
reqs Requirements
EB® Elektrobit
IBM® International Business Machines Corporation
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 6 of 26
3 Scope
This document shall be considered when designing BSW and SWCs. Document shall be used to
establish traceability between design and configuration.
Document is intended for software engineers.
3.1 Overview
Traceability is required between design and configuration as well as requirements and design.
Traceability between design and requirement is part of SW domain architecture model. Software
requirements are imported in SW domain architecture using Rhapsody gateway. Use of implementation
model is to establish traceability between SW domain architecture model with configuration. SW Domain
architecture model is referenced in implementation model. AUTOSAR Configuration is imported in
implementation model by importing AUTOSAR configuration file. In implementation model traceability
between configuration and SW domain architecture is established by creating dependencies. Figure 1
provides overview of process.
DOORS module
SW Reqs SW Domain
Rhapsody Architecture
Gateway Reference Rhapsody
-Establish and maintain
unit traceability (forward/backward) model
(<unit>.sbs)
between AUTOSAR configuration
and design/configuration
Implementation requirements
*.arxml
model -Document rationales for generated
configuration from EB
BSW configuration/ Rhapsody
Tresos
-Generate Reports (e.g. studio/AAT
software description AUTOSAR import
traceability, rationales, …)
(<unit>.sbs)
Figure 1 Overview of AUTOSAR configuration documentation
4 Instructions
4.1 Work flow Scenarios
4.1.1 Flow for initial design
Figure 2 provides overview of workflow for initial design. In initial design flow, project for implementation
model is established. Outcome of this workflow is model with traceability between configuration and
design.
Establish
Import SW
Create project Import Create traceability Generating
domain
for verification AUTOSAR rationale between tablular
architecture
model configuration (optional) configuration information
model
and design
Figure 2 Flow for initial design

• Create project for implementation model
o Instruction 4.2.2
• Import SW domain architecture model
o Instruction 4.2.3
o Instruction 4.2.4
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 7 of 26
• Import AUTOSAR configuration

o Instruction 4.2.1 (export AUTOSAR configuration in ARXML form from EB tresos studio)
o Information is stored in ARXML form in AAT tool (Dassault AUTOSAR Builder®). If
AUTOSAR version of project is 4.0.3, ARXML can be imported without any change.
o Instruction 4.2.5 (Only steps 1, 2 & 5)
• Create rationale
o Instruction 4.2.6
• Establish traceability between design and configuration
o Instruction 4.2.7
• Generating tabular information
o Instruction 4.2.12
4.1.2 Flow for update in design

Figure 3 provides overview of workflow for update in implementation model after updates in SW domain
architecture. Implementation model with traceability between design and configuration is already
established (Ref 4.1.1). Workflow is initiated by change in SW domain architecture. If design is updated
there could be some update in AUTOSAR configuration, hence AUTOSAR configuration is re-imported in
implementation model. If design and configuration is updated there could be change in traceability hence
traceability between design and configuration is revisited at end of workflow. If changes in SW domain
architecture model are not reflected in implementation model, unload and load unit for SW domain
architecture model. Use instruction 4.2.1 to export AUTOSAR configuration from EB tresos studio.
Remove
Import AUTOSAR Discard changes Import AUTOSAR Generating
Analyze difference containers/parameters
configuration for done in model for configuration for tablular
in configuration from merged
comparison comparison merging information
configuration
Figure 3 Flow for update in design

• Import AUTOSAR configuration for comparison

• Analyze differences in configuration
o Instruction 4.2.8
o Instruction 4.2.9
• Discard changes done in model for comparison
• Importing AUTOSAR configuration for merging
• Remove containers/parameters from merged configuration
• Creating rationale
o Instruction 4.2.6 (Only step 2)
• Establishing traceability
o Instruction 4.2.7 (Only step 2, 3 & 4)
• Generating tabular information
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 8 of 26
4.2 Work instructions

4.2.1 Exporting configuration from EB Tresos® Studio1
Input / precondition:
BSW configuration in .xdm format.
Tool(s):
EB Tresos studio®
Work steps:
1, Right click on project and select “Im- and exporters...”
2, Create new exporter (Ref. Figure 4)
[a] Creating new exporter [b] Configuring exporter

Figure 4 Create exporter in EB Tresos studio
3, Select “Autosar Im-/Exporter” as Importer/Exporter and “Export only” as Mode (Ref. Figure 4).
Select Next.
4, Provide file location and file name (along with extension .arxml) in “File Name” field. Select
“asc:4.0.3” in “Content type”(Ref. Figure 5) and select finish.
5, Run exporter
1 Only suitable for exporting BSW configuration through EB Tresos Studio®

Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 9 of 26
Figure 5 Create exporter in EB Tresos® studio

Output:
BSW configuration in AUTOSAR configuration file is generated.
4.2.2 Creating new project for implementation model

None.
Tool(s):
IBM Rational Rhapsody®.
Work steps:
1, Create new project in Rhapsody.

2, Provide project name and project location. Provide “Project Type” as “AUTOSAR_40” and
“Project Settings” as “AutosarAuthoring”.
Figure 6 Creating AUTOSAR project with Rhapsody

3, If directory with project name does not exist, Rhapsody will create directory. Pop up will appear
on screen to confirm creation of directory, select yes.
Output:
Rhapsody project is created at defined project path.
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 10 of 26
4.2.3 Adding SysML profile to implementation model2

Project as defined in instruction 4.2.2.
Tool(s):
Work steps:
1, From file menu select “Add Profile to Model” (ref. Figure 7)
[a] Adding profile to model [b] Selecting profile to add

Figure 7 Adding profile to model

2, Select SysML.sbs file and select open.
Output:
SysML profile is added to implementation model.
4.2.4 Adding SW domain architecture model to implementation model

Rhapsody model file for SW domain architecture (Figure 8 shows example of SW domain
architecture model).
2 Only valid if SW domain architecture is created with SysML profile

Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 11 of 26
Figure 8 Example of object model diagram in SW domain architecture model

Tool(s):
Work steps:
1, From file menu select: “Add to model” (ref. Figure 9)
Figure 9 Add Rhapsody model file to model
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 12 of 26
2, Select Rhapsody model file for SW domain architecture model. Select option “as reference”
and open (ref. Figure 10). 3
Figure 10 Add Rhapsody model file as reference

Output:
SW domain architecture model appears in implementation model.
Figure 11 Example output showing SW domain architecture model imported in implementation

model
4.2.5 Importing AUTOSAR configuration to implementation model 4

AUTOSAR configuration file.
3 “Add Dependants” option allows adding other *.sbs files referred in SW domain architecture
automatically. In work instruction this option is not selected, as adding referred *.sbs automatically may
lead to circular references. Preferred option is to add referred *.sbs files one by one manually.
4 BSW configuration as well as application model is in form of ARXML file. Work instruction can be used
for BSW as well as application specific ARXML file.
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 13 of 26
Tool(s):
Work steps:
1, From Tools option select “Import AUTOSAR XML Document”
Figure 12 Import AUTOSAR configuration file

2, Importing AUTOSAR configuration file for initial design flow: Select AUTOSAR configuration
file in “From XML file” field. Select option “Import selected ARPackages” and Import (ref Figure 13).
Figure 13 Options for importing AUTOSAR configuration file

3, Importing AUTOSAR configuration file for analysing differences: Select AUTOSAR
configuration file, select option “Import selected ARPackages”, Select Import scheme as “Increment”,
select Increment policy as “Override All” (ref Figure 14).
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 14 of 26
Figure 14 Importing updated AUTOSAR configuration file

4, Importing AUTOSAR configuration file for merging: Select AUTOSAR configuration file, select
option “Import selected ARPackage”, Select Import scheme as “Merge”, Select Merge policy as “Prefer
File” and import (ref Figure 15).
Figure 15 Importing updated AUTOSAR configuration file in merge mode

5, Window with list of all ARPackages in AUTOSAR configuration file will appear on screen.
Select ARPackage of interest and select “ok”.
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 15 of 26
Figure 16 Selection of ARPackage for import

Output:
BSW Configuration/application software model appears as ARPackage.
Figure 17 Example of imported AUTOSAR configuration file in implementation model
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 16 of 26
4.2.6 Creating rationale in model 5

AUTOSAR project with SW domain architecture model (As defined in instruction 4.2.4).
Tool(s):
Work steps:
1, Create new class diagram/object model diagram.
2, Create rationale to class diagram created in step 1. Add comment to diagram, open features of
comment and apply stereotype rationale (Ref Figure 18). Write content of rationale in description tab.
[a] Adding comment in model [b] Applying stereotype to comment
Figure 18 Adding Rationale to model

Output:
Rationale is created in model.
4.2.7 Establishing traceability through dependency

AUTOSAR project with SW domain architecture model and AUTOSAR configuration file imported
(As defined in instruction 4.2.4 & 4.2.5).
Tool(s):
5 Optional
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 17 of 26
Work steps:
1, Create object model diagram/class diagram or use one which is created in instruction 4.2.6.
2, Add objects and requirements from SW domain architecture model to diagram created in step
1.
3, Add configuration parameters/containers from imported AUTOSAR configuration to diagram.
Create dependency from configuration parameter/container to object/rationale/requirement.
4, Add stereotype to dependency (add stereotype (from PredefinedTypes) to dependency, open
features of dependency and apply stereotype “refine”6) (Ref Figure 19).
Figure 19 Adding stereotype to dependency

Output:
Figure 20 shows example output.
6 Ref Platform architecture manual for use of stereotypes

Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 18 of 26
Figure 20 Example of class diagram from implementation model

4.2.8 Identifying differences in configuration
Project with updated SW domain architecture model
AUTOSAR configuration imported in for analysing differences (Ref instruction 4.2.5).
Tool(s):
Work steps:
1, Two ARPackages with same name should be visible in project, right click on first ARPackage,
select unit compare (ref. Figure 21). Use “<<Select>>” option in dropdown and select First ARPackage as
unit 1 and second ARPackage as unit 2 (ref. Figure 22).
7 In diagram green blocks represent parameters/containers from AUTOSAR configuration. Blue blocks
represent objects from SW domain architecture. Red blocks represent requirements (from SW domain
architecture). Colors for objects are formatted for distinguishing objects, after following instruction similar
diagram is created although objects may have different colors.
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 19 of 26
Figure 21 Compare units

[a] Comparing units
[b] Selecting unit 1 [c] Selecting unit 2

Figure 22 Selecting units for comparison
Output:
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 20 of 26
Diffmerge window gets open
Figure 23 Differences between two ARPackages

4.2.9 Generating report for difference between ARPackages
Comparison of two ARPackages as outcome of instruction 4.2.8.
Tool(s):
Rhapsody DiffMerge®.
Work steps:
1, Under Tools menu select “Report Differences>All”
[a] Generating report for difference in [b] Example of report generated in consol
ARPackages
Figure 24 Generating difference report with DiffMerge

2, Copy generated report from consol in document.
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 21 of 26
Output:
Report is generated for differences in configuration (ref. Figure 24).
4.2.10 Removing configuration unit from project

Rhapsody project created as defined in step 4.2.8.
Tool(s):
Work steps:
1, Remove unit created by importing AUTOSAR configuration file (Right click on unit and select
delete from model). (Hint: second ARPackage is to be deleted)
Figure 25 Delete unit from implementation model

Output:
Only one ARPackage is present in implementation model.
Figure 26 implementation model after removing ARPackage
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 22 of 26
4.2.11 Remove containers/parameters from merged configuration

Rhapsody project as defined in instruction 4.2.10.
Difference report generated in instruction 4.2.9.
Tool(s):
Work steps:
1, In difference report, search for “<Object name> exists only on left side” and ignore results with
structure “Dependency “<Object name> exists only on left side”8.
Figure 27 Example list of parameters/containers to be removed

2, Search parameters found in step 2 in implementation model and delete them one by one from
model (Search name of parameter/container in rhapsody, locate comment and delete from model) (ref
Figure 28).
[a] searching container/parameter [b] delete container/parameter
Figure 28 Deleting parameter from model
8 In notepad++ use regular expression ^ (.*?) (?!.*Dependency) (.*?) exists only on left side
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 23 of 26
Output:
Configurations are merged in model.
4.2.12 Adding file as unit to model

Rhapsody project as defined in instruction 4.2.11.
Tool(s):
Work steps:
1, Add (e.g. EVOTable.sbs9) file as unit to implementation model. To add file to model select
“File>Add to Model”. Select option ”As Unit”.
Figure 29 Add file to model as unit

Output:
Packages from file are added to model.
4.2.13 Customizing table/matrix scope

Rhapsody project with table and matrix layout.
Tool(s):
Work steps:
9 Example file is provided at location url:integrity://skobde-

mks.kobde.trw.com:7001/si/viewhistory?project=/DAS/040%5fTest%5fProjects/%3cAC1KEVO%3e%20A
C1000%20EVO%20radar%20only%20core/200%5fAnalysis/600226%2dDocumentationArBaseSWConfig
uration/WP%5f1028276%5fTool%5fDevelopment/Example/BSW%5fDoctest%5f0/BSW%5fDoctest%5frpy
/project.pj&selection=%22EVOTable.sbs%22
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 24 of 26
1, Open feature of matrix view, select ArPackage in “From” field. Select Package (referenced
from software domain architecture) in “To” field (ref Figure 30).
Figure 30 Scope for matrix view

2, Open feature of table view (relation table), select ArPackage and Package (referenced from
software domain architecture) in Scope field (Ref Figure 31).
Figure 31 Scope for relation table

3, Open features of table view, select ArPackage in Scope field (ref Figure 32).
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 25 of 26
Figure 32 Scope for table

4, Select “Toggle empty row” for matrix view and relation table view to hide empty rows.
Output:
Tables and matrix are generated for implementation model.
Figure 33 Example of table in implementation model
Filename: Document1
ID: <DocID>
Revision: 0.4 DAS
documentation

Page: 26 of 26
5 References
Reference Title Remarks
1 DAS PLATFORM Architecture Manual url:integrity://skobde-
mks.kobde.trw.com:7001/si/viewhistory?proj
ect=/DAS/015%5fArchitecture/20%5fSoftwar
e/ArchManual/project.pj&selection=%22Arch
itectureManualMain.doc%22
Filename: Document1

DAS AUTOSAR Configuration Documentation Work Instruction

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DAS AUTOSAR Configuration Documentation Work Instruction

Uploaded by

Copyright:

Available Formats

ID: <DocID>

Revision: 0.4 DAS

Author: Omkar Sudame

CM System Information (automatically entered):

Author: Omkar Sudame

Revision Date Prepared By Reviewed By Approved By Changelog

1.1 16-Oct-2015 Omkar Francesco Initial Version

1.2 16-Oct-2015 Omkar Added snapshot for

1.4 19-Oct-2015 Omkar Updated document

Author: Omkar Sudame

4.2.9 Generating report for difference between ARPackages ................................................... 20

Author: Omkar Sudame

Author: Omkar Sudame

2 Definitions and Abbreviations

Acronym Full Form

SWC Application Software component

Author: Omkar Sudame

Figure 1 Overview of AUTOSAR configuration documentation

Figure 2 Flow for initial design

Author: Omkar Sudame

• Import AUTOSAR configuration

4.1.2 Flow for update in design

Figure 3 Flow for update in design

• Import AUTOSAR configuration for comparison

Author: Omkar Sudame

4.2 Work instructions

[a] Creating new exporter [b] Configuring exporter

1 Only suitable for exporting BSW configuration through EB Tresos Studio®

Author: Omkar Sudame

Figure 5 Create exporter in EB Tresos® studio

4.2.2 Creating new project for implementation model

1, Create new project in Rhapsody.

Figure 6 Creating AUTOSAR project with Rhapsody

Author: Omkar Sudame

4.2.3 Adding SysML profile to implementation model2

[a] Adding profile to model [b] Selecting profile to add

Figure 7 Adding profile to model

4.2.4 Adding SW domain architecture model to implementation model

2 Only valid if SW domain architecture is created with SysML profile

Author: Omkar Sudame

Figure 8 Example of object model diagram in SW domain architecture model

Figure 9 Add Rhapsody model file to model

Author: Omkar Sudame

Figure 10 Add Rhapsody model file as reference

Figure 11 Example output showing SW domain architecture model imported in implementation

4.2.5 Importing AUTOSAR configuration to implementation model 4

Author: Omkar Sudame

Figure 12 Import AUTOSAR configuration file

Figure 13 Options for importing AUTOSAR configuration file

Author: Omkar Sudame

Figure 14 Importing updated AUTOSAR configuration file

Figure 15 Importing updated AUTOSAR configuration file in merge mode

Author: Omkar Sudame

Figure 16 Selection of ARPackage for import

Figure 17 Example of imported AUTOSAR configuration file in implementation model

Author: Omkar Sudame

4.2.6 Creating rationale in model 5

[a] Adding comment in model [b] Applying stereotype to comment

Figure 18 Adding Rationale to model

4.2.7 Establishing traceability through dependency

Author: Omkar Sudame

Figure 19 Adding stereotype to dependency

6 Ref Platform architecture manual for use of stereotypes