Ing Guidelines Of Basic Software EA UML AUTOSAR TR BSWUML Guide
AUTOSAR_TR_BSWUMLingGuide
AUTOSAR_TR_BSWUMLingGuide
AUTOSAR_TR_BSWUMLingGuide
User Manual:
Open the PDF directly: View PDF
Page Count: 47
- 1 Scope of this Document
- 2 Related Documentation
- 3 Terms and abbreviations
- 4 Requirements on the modeling of the Basic Software
- 4.1 General
- 4.1.1 [TR_BSWUML_00017] UML 2.0
- 4.1.2 [TR_BSWUML_00065] Application of the BSW UML Profile
- 4.1.3 [TR_BSWUML_00001] Allowed elements
- 4.1.4 [TR_BSWUML_00002] Allowed relationships
- 4.1.5 [TR_BSWUML_00053] Allowed set of diagrams
- 4.1.6 [TR_BSWUML_00060] Documentation of elements
- 4.1.7 [TR_BSWUML_00047] Links between diagrams shall be hyperlinks
- 4.2 Structural Design
- 4.2.1 [TR_BSWUML_00054] Use of Packages
- 4.2.2 [TR_BSWUML_00003] Diagrams usage
- 4.2.3 [TR_BSWUML_00038] Component diagram appearance options
- 4.2.4 [TR_BSWUML_00039] Component diagram appearance of BSW module diagrams
- 4.2.5 [TR_BSWUML_00004] Header File Modeling
- 4.2.6 [TR_BSWUML_00005] Basic Software Module Modeling
- 4.2.7 [TR_BSWUML_00010] Component Definition
- 4.2.8 [TR_BSWUML_00009] Version numbers of software modules
- 4.2.9 [TR_BSWUML_00025] ‘Language’ definition of Components
- 4.2.10 [TR_BSWUML_00052] Interface creation
- 4.2.11 [TR_BSWUML_00006] Interface Modeling
- 4.2.12 [TR_BSWUML_00011] Accessing interfaces of other components
- 4.2.13 [TR_BSWUML_00027] Definition of structures
- 4.2.14 [TR_BSWUML_00026] Definition of enumerations
- 4.2.15 [TR_BSWUML_00028] Definition of simple types
- 4.2.16 [TR_BSWUML_00059] Definition of typedefs
- 4.2.17 [TR_BSWUML_00066] Definition of ranges for typedefs
- 4.2.18 [TR_BSWUML_00062] Definition of functions and callbacks
- 4.2.19 [TR_BSWUML_00068] Definition of parameters
- 4.2.20 [TR_BSWUML_00037] Definition of pointer types
- 4.2.21 [TR_BSWUML_00055] Use of parameter kind
- 4.2.22 [TR_BSWUML_00061] Definition of return type
- 4.2.23 [TR_BSWUML_00063] Definition of scheduled functions
- 4.2.24 [TR_BSWUML_00035] Sub elements of BSW modules
- 4.3 Behavioral Design
- 4.3.1 General
- 4.3.2 Sequence Diagrams
- 4.3.3 [TR_BSWUML_00057] Parameter values in sequence diagrams
- 4.3.4 State Machine Diagrams
- 4.3.4.1 [TR_BSWUML_00041] States shall have thick lines
- 4.3.4.2 [TR_BSWUML_00042] A trigger condition shall be defined for each transition
- 4.3.4.3 [TR_BSWUML_00043] Transitions may be modeled with sub-activities
- 4.3.4.4 [TR_BSWUML_00046] Links to parent diagrams shall be drawn as hyperlink diagram references
- 4.3.5 Activity Diagrams
- 4.4 Model synchronization
- 4.5 Documentation generation
- 4.1 General
- 5 BSW UML Profile
- 6 Administrative Info