FordMsg215BusHiSpd_MDD

Module Design Document

For

FordMsg215BusHiSpd

Prepared For:

,

Prepared By:

TATA ELXSI,

INDIA

Change History

Table of Contents

Table of Contents 3

1 Introduction 4

1.1 Purpose 4

1.2 Scope 4

2 FordMsg215BusHiSpd & High-Level Description 5

3 Design details of software module 6

3.1 Graphical representation of FordMsg215BusHiSpd 6

3.2 Data Flow Diagram 6

3.2.1 Component level DFD 6

3.2.2 Function level DFD 6

4 Constant Data Dictionary 7

4.1 Program (fixed) Constants 7

4.1.1 Embedded Constants 7

5 Software Component Implementation 8

5.1 Sub-Module Functions 8

5.1.1 Init: FordMsg215BusHiSpdInit1 8

5.1.2 Per: FordMsg215BusHiSpdPer1 8

5.2 Server Runables 8

5.3 Interrupt Functions 8

5.4 Module Internal (Local) Functions 8

5.5 GLOBAL Function/Macro Definitions 8

6 Known Limitations with Design 9

7 UNIT TEST CONSIDERATION 10

Appendix A Abbreviations and Acronyms 11

Appendix B Glossary 12

Appendix C References 13

Introduction

Purpose

Module Design Document for MM057A_FordMsg215BusHiSpd_Impl.

Scope

The following definitions are used throughout this document:

• Shall: indicates a mandatory requirement without exception in compliance.

• Should: indicates a mandatory requirement; exceptions allowed only with documented justification.

• May: indicates an optional action.

FordMsg215BusHiSpd & High-Level Description

The purpose of the Ford Message 215 Bus High Speed function is to provide the Electric Power Steering system with trailer Back up Assist and Gear Lever Position signals from CAN. The Ford Message 215 function will perform the missing message and signal invalid diagnostics as well as provide a validity signal for the signal values and received message.

Design details of software module

Graphical representation of FordMsg215BusHiSpd

Data Flow Diagram

Refer FDD

Component level DFD

Refer FDD

Function level DFD

Refer FDD

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Software Component Implementation

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.

Init: Init1

Design Rationale

Refer FDD

Module Outputs

Refer FDD

Per: Per1

Design Rationale

Refer FDD

Store Module Inputs to Local copies

Refer FDD

(Processing of function) ………

Refer FDD

Store Local copy of outputs into Module Outputs

Refer FDD

Server Runnables

ComIPduCallout_APIM_Send_Signals_2_FD1

5.2.1.1 Design Rationale

None

5.2.1.2 Processing of function

None

ComTimeoutNotification_TrlrAidMde_D_Rq

5.2.2.1 Design Rationale

None

5.2.2.2 Processing of function

None

Interrupt Functions

None

Module Internal (Local) Functions

Local Function #1

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

None.

UNIT TEST CONSIDERATION

None

Abbreviations and Acronyms

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

References