EcmOutpAndDiagc Module Design Document

Module Design Document

For

EcmOutpAndDiagc

Feb 5, 2016

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Software Group,

Nexteer Automotive,

Saginaw, MI, USA
Change History

Table of Contents

1 Introduction 5

1.1 Purpose 5

1.2 Scope 5

2 EcmOutpAndDiagc & High-Level Description 6

3 Design details of software module 7

3.1 Graphical representation of EcmOutpAndDiagc 7

3.2 Data Flow Diagram 7

3.2.1 Component level DFD 7

3.2.2 Function level DFD 7

4 Constant Data Dictionary 8

4.1 Program (fixed) Constants 8

4.1.1 Embedded Constants 8

5 Software Component Implementation 9

5.1 Sub-Module Functions 9

5.1.1 Init: EcmOutpAndDiagcInit1 9

5.1.1.1 Design Rationale 9

5.1.1.2 Module Outputs 9

5.1.2 Init: EcmOutpAndDiagcInit2 9

5.1.2.1 Design Rationale 9

5.1.2.2 Module Outputs 9

5.1.3 Init: EcmOutpAndDiagcInit3 9

5.1.3.1 Design Rationale 9

5.1.3.2 Module Outputs 9

5.1.4 Init: EcmOutpAndDiagcInit4 9

5.1.4.1 Design Rationale 9

5.1.4.2 Module Outputs 9

5.1.5 Per: EcmOutpAndDiagc_Per 9

5.2 Server Runables 10

5.2.1 CtrlErrOut_Oper 10

5.2.1.1 Design Rationale 10

5.2.1.2 (Processing of function)……… 10

5.3 Interrupt Functions 10

5.4 Module Internal (Local) Functions 10

5.4.1 Local Function #1 10

5.4.1.1 Design Rationale 10

5.4.1.2 Processing 10

5.5 GLOBAL Function/Macro Definitions 10

5.5.1 GLOBAL Function #1 10

5.5.1.1 Design Rationale 10

5.5.1.2 Processing 10

6 Known Limitations with Design 12

7 UNIT TEST CONSIDERATION 13

Appendix A Abbreviations and Acronyms 14

Appendix B Glossary 15

Appendix C References 16

Introduction

Purpose

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.

EcmOutpAndDiagc & High-Level Description

See FDD

Design details of software module

Graphical representation of EcmOutpAndDiagc

Data Flow Diagram

Component level DFD

N/A

Function level DFD

N/A

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Software Component Implementation

Sub-Module Functions

Init: EcmOutpAndDiagcInit1

Design Rationale

Temporary variables were created to read register values into in order to avoid MISRA violations that appear when volatile values are used in conditional statements.

Module Outputs

See FDD

Init: EcmOutpAndDiagcInit2

Design Rationale

Empty function for purposes of memory mapping

Module Outputs

None

Init: EcmOutpAndDiagcInit3

Design Rationale

Non-RTE initialization function for EI Start up Test

Module Outputs

None

Init: EcmOutpAndDiagcInit4

Design Rationale

Non-RTE initialization function for Pseudo Error Injection Start up Test

Module Outputs

None

Per: EcmOutpAndDiagc_Per

None

Server Runables

CtrlErrOut_Oper

Design Rationale

None

(Processing of function)………

Refer to FDD

Interrupt Functions

None

Module Internal (Local) Functions

Local Function #1

Design Rationale

Processing

GLOBAL Function/Macro Definitions

GLOBAL Function #1

Design Rationale

Processing

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