Modeling Guidelines of Basic Software EA UML Model, No.117, AUTOSAR R21-11(258) CP

Modeling Guidelines of Basic Software EA UML Model, No.117, 2021-11

https://www.autosar.org/fileadmin/standards/classic/21-11/AUTOSAR_TR_BSWUMLModelModelingGuide.pdf

AUTOSAR R21-11記事一覧はこちら。

AUTOSAR 21-11,160文書読んだ。2022年5月中に全部読み。

https://qiita.com/kaizen_nagoya/items/9935c9e58bf82e1e63d2

AUTOSAR 21-11, 62文書読んだ。2022年5月中に半分到達予定。

https://qiita.com/kaizen_nagoya/items/648b32867635993410c8

AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成

https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e

# 用語(terms)
|Term|Description|
|:--|:--|
| Header Files|Chapter 5.1 of each SWS document contains the BSW module’s file structure, in particular its file inclusion structure. Most modules’ include file relationships have a similar structure, in fact some parts are actually identically modeled. Therefore, the Header File structure is being modeled using a class diagram, with stereotyped classes representing the source code- and header files; see section 2.5.1.
| Imported Type Definitions|SWS chapter 8.1 contains a tabular list of imported types. This table is automatically generated from the module dependency as explained in section 2.4.5.
| Type Definitions|SWS chapter 8.2 contains detailed descriptions of all types defined within a given BSW module. For details on the modeling of type definitions refer to section 2.4.8.
|Function Definitions|SWS chapter 8.3 contains a detailed description for each function provided by the BSW module. The description is presented in form of a table with a specific layout. The individual fields of the table are filled from the API function definitions according to section 2.4.3.
| Callback Notifications|Very similar to the Function Definitions, SWS chapter 8.4 contains the callback definitions the BSW module provides. These are callbacks which will be called by other BSW modules, where the lower layer module is typically the caller. A table for each callback notification will be generated for a module’s specified callbacks according to section 2.4.7.
|Scheduled Functions|Scheduled Functions are described in SWS chapter 8.5. The definition of scheduled functions in the BSW UML model is described in section 2.4.3.1. 
| Mandatory Interfaces| SWS chapter 8.6.1 contains a list of “mandatory interfaces” expected by the module. The list is generated from the BSW UML model according to the mandatory dependencies as described in section 2.4.5.2.
| Optional Interfaces|Similarly, the list of “optional interfaces” contained in SWS chapter 8.6.2 is generated from the BSW UML model according to the optional dependencies as described in section 2.4.5.3.
| Configurable Interfaces|SWS Chapter 8.6.3 contains a BSW module’s “Configurable Interfaces”. These are interfaces whose called function name can be configured using ECU configuration parameters. In AUTOSAR, these are typically used for issuing callback notifications, i.e. the module owning the configurable interface uses it to notify a (configurable) upper layer module’s callback. In other words the module defining a “Configurable Interface” calls an other module that implements these interface definition. A table for each callback notification will be generated for a module’s specified callbacks according to section 2.4.7.2.
| Sequence Diagrams|In order to visualize the interaction of a BSW module with other modules, SWS Chapter 9 contains UML Sequence Diagrams for the module’s typical use cases. In order to keep such Sequence Diagrams consistent between different modules within the AUTOSAR BSW stack, they are also modeled within the BSW UML model. The diagrams are being exported to image files by the mmt tool; they are then being included by the SWS document files. For the detailed modeling guidelines see section 2.5.2
| Various Diagrams|The SWS documents of various BSW modules use additional UML diagrams e.g. for either specifying core functionality, or for additionally illustrating dependencies between modules. Some concrete examples are the various state machines used throughout the AUTOSAR BSW stack, for example in the CAN State Manager or in COM manager. Whenever possible, such diagrams should also be modeled in the BSW UML model. This ensures that the sources of the document diagrams will not get lost, and also facilitates their maintenance and keeping a uniform modeling style.
| Modeling of services|BSW Modules belonging to the Service Layer of the AUTOSAR Basic Software Architecture may offer their services in the form of AUTOSAR Service Interfaces. AUTOSAR Service Interfaces are described in terms of the Software Component Template rather than C-language interfaces, and they come in different flavors, e.g. ClientServerInterface, SenderReceiverInterface, ModeSwitchInterface. Consequently, their properties require a different style of modeling than the standard BSW API functions. Modeling of AUTOSAR services is described in section 2.4.9
|Error classification|The SWS chapter "Error classification" (usually located within SWS chapter 7) contains detailed descriptions of all error codes the module uses for • Development Errors • Runtime Errors • Transient Faults For details on the modeling of these errors refer to section 2.4.10.

## 英日
日本語は仮訳

T.B.D.

# 参考(reference)

[1] Layered Software Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture
[2] List of Basic Software Modules
AUTOSAR_TR_BSWModuleList
[3] Glossary
AUTOSAR_TR_Glossary
[4] Specification of Standard Types
AUTOSAR_SWS_StandardTypes
[5] Generic Structure Template
AUTOSAR_TPS_GenericStructureTemplate
[6] Standardized M1 Models used for the Definition of AUTOSAR
AUTOSAR_MOD_GeneralDefinitions