FordHwTqCdng_MDD

Module Design Document

For

FordHwTqCdng

June 19, 20158

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Tata Elxsi,

Trivandrum, INDIA

Change History

Sl. No.DescriptionAuthorVersionDate
1Initial VersionTATA1.011-Jan-2018

Table of Contents

1 Introduction 5

1.1 Purpose 5

2 FordHwTqCdng & High-Level Description 6

3 Design details of software module 7

3.1 Graphical representation of FordHwTqCdng 7

3.2 Data Flow Diagram 7

Component level DFD 7

Function level DFD 7

4 Constant Data Dictionary 8

4.1 Program (fixed) Constants 8

Embedded Constants 8

5 Software Component Implementation 9

5.1 Sub-Module Functions 9

5.1.1 Init: FordHwTqCdngInit1 9

5.1.1.1 Design Rationale 9

5.1.1.2 Module Outputs 9

5.1.2 Per: FordHwTqCdngPer1 9

5.1.2.1 Design Rationale 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.1.3 Per: FordHwTqCdngPer2 9

5.1.3.1 Design Rationale 9

5.1.3.2 Store Module Inputs to Local copies 9

5.1.3.3 Processing of function 9

5.1.3.4 Store Local copy of outputs into Module Outputs 9

5.2 Server Runnables 10

5.2.1 Runnable: FIH_Read_EPS_Direct_BC_Torque 10

5.2.1.1 Design Rationale 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.2.2 Runnable: FIH_Read_EPS_Inverse_BC_Torque 10

5.2.2.1 Design Rationale 10

5.2.2.2 Store Module Inputs to Local copies 10

5.2.2.3 Processing of function 10

5.2.2.4 Store Local copy of outputs into Module Outputs 10

5.3 Interrupt Functions 10

5.4 Module Internal (Local) Functions 10

5.5 GLOBAL Function/Macro Definitions 10

6 Known Limitations with Design 11

7 UNIT TEST CONSIDERATION 12

Appendix A Abbreviations and Acronyms 13

Appendix B Glossary 14

Appendix C References 15

Introduction

Purpose

MDD for FordHwTqCdng

<Component Name> & High-Level Description

Please refer FDD.

Design details of software module

Graphical representation of <Component Name>

C:\Users\ramachandran.mg\Desktop\guru\CF076A_FordHwTqCdng_Impl.JPG

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 NameResolutionUnitsValue
Please refer Data Dictionary .m fileNANANA

Software Component Implementation

Sub-Module Functions

5.1.1 Init: <Component Name>Init1

5.1.1.1 Design Rationale

None

5.1.1.2 Module Outputs

None

5.1.2 Per: <Component Name>Per1

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

5.1.3 Per: <Component Name>Per2

5.1.3.1 Design Rationale

None

5.1.3.2 Store Module Inputs to Local copies

None

5.1.3.3 Processing of function

None

5.1.3.4 Store Local copy of outputs into Module Outputs

None

Server Runnables

5.2.1 Runnable: FIH_Read_EPS_Direct_BC_Torque

5.2.1.1 Design Rationale

None

5.2.1.2 Store Module Inputs to Local copies

None

5.2.1.3 Processing of function

None

5.2.1.4 Store Local copy of outputs into Module Outputs

None

5.2.2 Runnable: FIH_Read_EPS_Inverse_BC_Torque

5.2.2.1 Design Rationale

None

5.2.2.2 Store Module Inputs to Local copies

None

5.2.2.3 Processing of function

None

5.2.2.4 Store Local copy of outputs into Module Outputs

None

Interrupt Functions

None

Module Internal (Local) Functions

None

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

  1. In data dictionary,

Server invocation of GetRefTmr100MicroSec32bit is not defined for the Init runnable (FordHwTqCdngInit1).

  1. The RTE server runnables FIH_Read_EPS_Direct_BC_Torque and FIH_Read_EPS_Inverse_BC_Torque are not available in StdDef.dcf and Ford_MM_4.arxml

Therefore, these runnables have been implemented as Non-RTE runnables for the current release.

  1. The sub function IvsBoostCrv will be implemented in future. Therefore, this sub function is not implemented at the moment.

Note: This has resulted in some Dataflow defects in Polyspace and it will be resolved once the sub function is implemented in the subsequent build.

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 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

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.doc1.0
4Software Design and Coding Standards.doc2.1
5FDD: CF076A_FordHwTqCdng_DesignSee Synergy sub project version
Last modified October 12, 2025: Initial commit (ddf2e20)