当前位置:网站首页>[AUTOSAR CP general 1. how to read AUTOSAR official documents]

[AUTOSAR CP general 1. how to read AUTOSAR official documents]

2022-07-23 12:28:00 Rest of life

Many friends may not have downloaded all series Autosar Official documents , I know everyone is lazy , I've sorted all of them under my download directory Autosar file , At the same time, a simple classification is made ( As shown in the picture below ), If you are interested, you can download it yourself , This time Downloading may require 1 Yuan , It's not In order to make money Of , As a reward for yourself , Only in this way can I feel myself Value recognized , At the same time, I hope you can Cherish and value the achievements of others
OK, let's not talk more nonsense , Let's get to the point : How to read Autosar Official documents !!!

 Insert picture description here
 Insert picture description here

AUTOSAR The document type

First look at the name of the document , Does it seem to have classification ,SRS、SWS、TR……
 Insert picture description here
What do these represent ?
Below I make a summary of these abbreviations :
 Insert picture description here

We may need to pay attention to or use more documents with red boxes above SWS

Every part of the document has its reason for existence , It's hard to find out its train of thought by looking at it casually . Open one of the documents ( for example :AUTOSAR_SWS_OS.pdf) have a look , What's in it , Here are a few simple explanations :
 Insert picture description here

“1 Introduction and functional overview”, This is an overview , That is, what is the content or function of this document , Achieve what purpose, etc , By reading this, you can roughly know whether this document is the one you want to see , Is there anything you want to get .

This document describes the essential requirements on the AUTOSAR
OperatingSystem to satisfy the top-level requirements presented in the
AUTOSAR SRS [2].

“ 3 Related documentation”, What documents need to be referred to or relied on for the function of this document .

3.1 Input documents

[1] Layered Software
ArchitectureAUTOSAR_EXP_LayeredSoftwareArchitecture.pdf

[2] Requirements on Operating System

AUTOSAR_SRS_OS.pdf

[3] General Requirements on Basic Software Modules

AUTOSAR_SRS_BSWGeneral.pdf……

**5 Dependencies to other modules”,** This chapter describes which other modules the content of the current document depends on , How to manage those modules , Even if the current document does not force dependency on other modules , I will also talk about some related contents , Like this OS Documents .

There are no forced dependencies on other modules, however:

  • It is assumed that the operating system may use timer units directly to drive counters.
  • If the user needs to drive scheduling directly from global time, then a global time interrupt is required.
  • If the user needs to synchronize the processing of a schedule table to a global time, the operating system needs to be told the global
    time using the SyncScheduleTable() service.

“ 6 Requirements Traceability”, Traceability to requirements , That is, according to which requirements the functions are implemented , There is a one-to-one correspondence .

 Insert picture description here
Here's the point

7.Functional Specification This chapter details the functions of this module , What are the functional requirements , What are the requirements and so on , So read this chapter , You will know what this module is for , How is the implementation principle

8 API specification”, This content is more important , The data type definition of this document is described in detail 、 Macro definition 、 Error code meaning , And the detailed description and constraints of the function interface .

This chapter contains the APIs offered by the operating system. Note
that not all services are available in all scalability classes, and
that the behavior of some services is extended for specific
scalability classes. For example, API to relatively start a schedule
table has an additional check if the schedule table allows
implicitsynchronization. This check is only performed in SC2 and SC4
where synchronization of schedule tables is supported.

9 Sequence diagrams”, This chapter is also very important , From here, we can clearly see the dynamic behavior of various time sequences , It is very helpful to understand this module .

 Insert picture description here

原网站

版权声明
本文为[Rest of life]所创,转载请带上原文链接,感谢
https://yzsam.com/2022/204/202207230539181001.html