FordMsg167BusHiSpd_MDD

Module Design Document

For

FordMsg167BusHiSpd

Jan 10, 2018

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Krishna Anne,

Nexteer Automotive,

Saginaw, MI, USA
Change History

DescriptionAuthorVersionDate
Initial versionKrishna Anne1.016-Nov-2017
Section 5 has been updatedTeam1.010-Jan-2018


Table of Contents

1 FordMsg167BusHiSpd High-Level Description 4

2 Design details of software module 5

2.1 Graphical representation of FordMsg167BusHiSpd 5

2.2 Data Flow Diagram 5

2.2.1 Component level DFD 5

2.2.2 Function level DFD 5

3 Constant Data Dictionary 6

3.1 Program (fixed) Constants 6

3.1.1 Embedded Constants 6

4 Software Component Implementation 7

4.1 Sub-Module Functions 7

4.1.1 Init: FordMsg167BusHiSpdInit1 7

4.1.1.1 Design Rationale 7

4.1.1.2 Module Outputs 7

4.1.2 Init: FordMsg167BusHiSpdPer1 7

4.1.2.1 Design Rationale 7

4.1.2.2 Module Outputs 7

4.2 Server Runables 7

4.3 Interrupt Functions 7

4.3.1 Interrupt Function Name 7

4.4 Module Internal (Local) Functions 8

4.4.1 Local Function #1 8

4.4.1.1 Design Rationale 8

4.4.1.2 Processing 8

4.5 GLOBAL Function/Macro Definitions 8

5 Known Limitations with Design 9

6 UNIT TEST CONSIDERATION 10

Appendix A Abbreviations and Acronyms 11

Appendix B Glossary 12

Appendix C Please references 13

FordMsg167BusHiSpd High-Level Description

Please refer FDD

Design details of software module

Please refer FDD

Graphical representation of FordMsg167BusHiSpd

Data Flow Diagram

Please refer FDD

Component level DFD

Please refer FDD

Function level DFD

Please refer FDD

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Constant NameResolutionUnitsValue
Please refer .m file for constants

Software Component Implementation

Sub-Module Functions

Init: FordMsg167BusHiSpdInit1

Design Rationale

Please refer FDD

Module Outputs

None

Init: FordMsg167BusHiSpdPer1

Design Rationale

Please refer FDD.

Note: No action item is required for the below warning during the DCF check in Davinci Developer.

"The implementation data type <Ford_PrplWhlTot2_Tq_Actl> references the compu method <CM_PrplWhlTot2_Tq_Actl>. This compu method is of category <ScaleLinearTexttable>.

The categories of compu methods that are referenced by implementation data types are restricted to: TEXTTABLE and BITFIELD_TEXTTABLE.(SwcTemplate, constr_1158)"

Module Outputs

None

Server Runables

None

Interrupt Functions

None

Interrupt Function Name

None

Module Internal (Local) Functions

None

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

In Data dictionary, constant parameter PRPNWHLTQMAX_CNT_U16 (Value is 0) and PRPNWHLTQMIN_CNT_U16 (value is 65535). This causes faulty operation for the LIMIT function in the model Design.

UNIT TEST CONSIDERATION

None

Abbreviations and Acronyms

Abbreviation or AcronymDescription

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 Please reference Model (PRM)

  • Automotive SPICE® Process Assessment Model (PAM)

  • ISO/IEC 15288

  • ISO 26262

  • IEEE Standards

  • SWEBOK

  • PMBOK

  • Existing Nexteer Automotive documentation

TermDefinitionSource
MDDModule Design Document
DFDData Flow Diagram

Please references

Ref. #TitleVersion
1AUTOSAR Specification of Memory Mapping (Link:AUTOSAR_SWS_MemoryMapping.pdf)v1.3.0 R4.0 Rev 2
2MDD GuidelineEA4 01.00.00
3Software Naming Conventions.doc2.0
4Software Design and Coding Standards.doc2.1
5FDD: MM059A_FordMsg167BusHiSpd_DesignSee Synergy subproject version
Last modified October 12, 2025: Initial commit (ddf2e20)