MotRplCoggCmd_MDD
Module Design Document
For
MotRplCoggCmd
Mar 23, 2017
Prepared For:
Software Engineering
Nexteer Automotive,
Saginaw, MI, USA
Prepared By:
Software Engineering
Nexteer Automotive,
Saginaw, MI, USA
Change History
| Version | Description | Author | Date |
| 1 | Initial Version | Selva Sengottaiyan | 09-Feb-2016 |
| 2 | Updated Unit Test consideration | Avinash James | 23-Mar-2017 |
Table of Contents
2 MotRplCoggCmd & High-Level Description 6
3 Design details of software module 7
3.1 Graphical representation of MotRplCoggCmd 7
4.1 Program (fixed) Constants 8
5 Software Component Implementation 9
5.1.1 Init: MotRplCoggCmdInit1 9
5.1.2 Per: MotRplCoggCmdPer1 9
5.1.2.2 Store Module Inputs to Local copies 9
5.1.2.3 (Processing of function)……… 9
5.1.2.4 Store Local copy of outputs into Module Outputs 9
5.2.1.2 Store Module Inputs to Local copies 10
5.2.1.3 (Processing of function)……… 10
5.2.1.4 Store Local copy of outputs into Module Outputs 10
5.2.1 SetMotCoggCmdPrm_Oper 10
5.2.1.2 Store Module Inputs to Local copies 10
5.2.1.3 (Processing of function)……… 10
5.2.1.4 Store Local copy of outputs into Module Outputs 10
5.3 Module Internal (Local) Functions 10
6 Known Limitations with Design 11
Appendix A Abbreviations and Acronyms 13
Introduction
Refer the Design Subproject.
MotRplCoggCmd & High-Level Description
Refer the Design Subproject.
Design details of software module
Graphical representation of MotRplCoggCmd
Refer the Design Subproject.

Data Flow Diagram
Component level DFD
Function level DFD
Constant Data Dictionary
Program (fixed) Constants
Embedded Constants
Local Constants
| Constant Name | Resolution | Units | Value |
|---|---|---|---|
| Refer the Design Subproject. | Refer the Design Subproject. | Refer the Design Subproject. | Refer the Design Subproject. |
Software Component Implementation
<The detailed design of the function is provided in the FDD. The detail design shall only be added to the MDD when it is not provided in the FDD or the FDD is not adequate and clarification is needed.>
Sub-Module Functions
The sub-module functions are grouped based on similar functionality that needs to be executed in a given “State” of the system (refer States and Modes). For a given module, the MDD will identify the type and number of sub-modules required. The sub-module types are described below.
<(Note: For multiple init or per functions, insert new headers at the “Header 3” level – subset of “Sub-Module Functions section above” and follow the same sub-section design shown below . If none required, place the text “None”))>
Init: MotRplCoggCmdInit1
Design Rationale
Refer the Design Subproject
Module Outputs
Refer the Design Subproject
Per: MotRplCoggCmdPer1
Design Rationale
Refer the Design Subproject- ARCHGLBPRM_ONEOVER2PI constant has been used from ArchGlbPrm.h file instead of ONEOVER2PI which is defined in the FDD
Store Module Inputs to Local copies
Refer the Design Subproject
(Processing of function)………
Refer the Design Subproject
Store Local copy of outputs into Module Outputs
Refer the Design Subproject
Server Runables
GetMotCoggCmdPrm_Oper
Design Rationale
Refer the Design Subproject
Store Module Inputs to Local copies
Refer the Design Subproject
(Processing of function)………
Refer the Design Subproject
Store Local copy of outputs into Module Outputs
Refer the Design Subproject
SetMotCoggCmdPrm_Oper
Design Rationale
Refer the Design Subproject
Store Module Inputs to Local copies
Refer the Design Subproject
(Processing of function)………
Refer the Design Subproject
Store Local copy of outputs into Module Outputs
Refer the Design Subproject
Module Internal (Local) Functions
Local Function #1
| Function Name | SinLookup | Type | Min | Max |
| Arguments Passed | Theta_Rad_T_f32 | Float32 | 0 | 2*PI |
| Return Value | Result_Uls_T_f32 | Float32 | 0 | 1 |
Design Rationale
Processing
Refer the design
Known Limitations with Design
None
UNIT TEST CONSIDERATION
Abbreviations and Acronyms
| In the file CDD_MotRplCoggCmd_MotCtrl.c ARCHGLBPRM_ONEOVER2PI constant has been used from ArchGlbPrm.h file instead of ONEOVER2PI which is defined in the FDD. The architecture has changed to include the constant ONEOVER2PI in the architecture global parameter list as ARCHGLBPRM_ONEOVER2PI Abbreviation or Acronym | Description |
|---|---|
Glossary
Note: Terms and definitions from the source “Nexteer Automotive” take precedence over all other definitions of the same term. Terms and definitions from the source “Nexteer Automotive” are formulated from multiple sources, including the following:
ISO 9000
ISO/IEC 12207
ISO/IEC 15504
Automotive SPICE® Process Reference Model (PRM)
Automotive SPICE® Process Assessment Model (PAM)
ISO/IEC 15288
ISO 26262
IEEE Standards
SWEBOK
PMBOK
Existing Nexteer Automotive documentation
| Term | Definition | Source |
|---|---|---|
| MDD | Module Design Document | |
| DFD | Data Flow Diagram |
References
| Ref. # | Title | Version |
|---|---|---|
| 1 | AUTOSAR Specification of Memory Mapping (Link:AUTOSAR_SWS_MemoryMapping.pdf) | v1.3.0 R4.0 Rev 2 |
| 2 | MDD Guideline | EA4 01.00.01 |
| 3 | Software Naming Conventions.doc | 1.0 |
| 4 | Software Design and Coding Standards.doc | 2.0 |