FordMsg430BusHiSpd_MDD
Module Design Document
For
FordMsg430BusHiSpd
June 19, 20158
Prepared For:
Software Engineering
Nexteer Automotive,
Saginaw, MI, USA
Prepared By:
Tata Elxsi,
Trivandrum, INDIA
Change History
| Description | Author | Version | Date |
| Initial Version | TATA | 1.0 | 04-Dec-2017 |
| Implemented FDD version 2.0.0 and FDD version 2.1.0 | TATA | 2.0 | 05-Jan-2018 |
Table of Contents
2 FordMsg430BusHiSpd & High-Level Description 6
3 Design details of software module 7
3.1 Graphical representation of FordMsg430BusHiSpd 7
4.1 Program (fixed) Constants 8
5 Software Component Implementation 9
5.1.1 Init: FordMsg430BusHiSpdInit1 9
5.1.2 Per: FordMsg430BusHiSpdPer1 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.4 Module Internal (Local) Functions 9
5.5 GLOBAL Function/Macro Definitions 10
6 Known Limitations with Design 11
Appendix A Abbreviations and Acronyms 13
Introduction
Purpose
MDD for FordMsg430BusHiSpd
FordMsg430BusHiSpd & High-Level Description
Please refer FDD.
Design details of software module
Graphical representation of FordMsg430BusHiSpd

Data Flow Diagram
Component level DFD
Please refer FDD.
Function level DFD
Please refer FDD.
Constant Data Dictionary
Program (fixed) Constants
Embedded Constants
Local Constants
| Constant Name | Resolution | Units | Value |
|---|---|---|---|
| Please refer Data Dictionary .m file | NA | NA | NA |
Software Component Implementation
Sub-Module Functions
5.1.1 Init: FordMsg430BusHiSpdInit1
Design Rationale
None
Module Outputs
None
5.1.2 Per: FordMsg430BusHiSpdPer1
5.1.2.1 Design Rationale
None
5.1.2.2 Store Module Inputs to Local copies
None
5.1.2.3 Processing of function)
None
5.1.2.4 Store Local copy of outputs into Module Outputs
None
Server Runnables
None
Interrupt Functions
None
Module Internal (Local) Functions
Local Function #1
| Function Name | NtcFail | Type | Min | Max | |||
|---|---|---|---|---|---|---|---|
| Arguments Passed | MissMsgDiagEna_Cnt_T_logl | boolean | FALSE | TRUE | |||
| BusHiSpdMissThd_Cnt_T_u16 | uint16 | 0U | 6000U | ||||
| *FordVehOdom_KiloMtr_T_f32 | float32 | (0.0F) | (16777215.0)F | ||||
| Return Value | None | ||||||
Design Rationale
Processing
Please refer to the below path in the FDD model.
MM081A_FordMsg430BusHiSpd/FordMsg430BusHiSpd/FordMsg430BusHiSpdPer1/MsgMiss/NtcFail
GLOBAL Function/Macro Definitions
None
Known Limitations with Design
Datatype of input variable ClrDiagcFlgProxy is uint8 in the data dictionary, but it must be Boolean according to the design in the model.
In the below design path,
MM081A_FordMsg430BusHiSpd/FordMsg430BusHiSpd/FordMsg430BusHiSpdPer1
The inputs to merge block are not the same corresponding to the output signal FordVehOdom.
UNIT TEST CONSIDERATION
None.
Abbreviations and Acronyms
| 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.00 |
| 3 | Software Naming Conventions.doc | 1.0 |
| 4 | Software Design and Coding Standards.doc | 2.1 |
| 5 | FDD: MM077A_FordMsg415BusHiSpd_Design_2.1.0 | See Synergy sub project version |