RvsBattProtn_MDD

Module Design Document

For

RvsBattProtn

October 16, 2017

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 4

1.1 Purpose 4

1.2 Scope 4

2 RvsBattProtn & High-Level Description 5

3 Design details of software module 6

3.1 Graphical representation of RvsBattProtn 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: RvsBattProtn_Init<n> 8

5.1.2 Per: RvsBattProtn_Per<n> 8

5.2 Server Runables 8

5.2.1 <Server Runable Name> 8

5.3 Interrupt Functions 9

5.3.1 Interrupt Function Name 9

5.4 Module Internal (Local) Functions 9

5.4.1 Local Function #1 9

5.5 GLOBAL Function/Macro Definitions 9

5.5.1 GLOBAL Function #1 9

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

Module Design Document for ES252A_RvsBattProtn_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.

RvsBattProtn & High-Level Description

Refer FDD.

Design details of software module

This module provides diagnostics of Reverse Battery Protection Module. Main task is to detect opened Reverse Protection MOSFET channel.

Graphical representation of RvsBattProtn

Data Flow Diagram

Refer FDD

Component level DFD

None

Function level DFD

None

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

Design Rationale

Refer FDD

Module Outputs

Refer FDD

Per: RvsBattProtnPer1

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 Runables

None

Interrupt Functions

None

Module Internal (Local) Functions

None

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

None

UNIT TEST CONSIDERATION

This component uses config params for some configurable constants. However for testing these in PIL/SIL, please use the following strategy:

1. Rename the RvsBattProtn_Cfg_PIL.h file in tools/local/include folder to RvsBattProtn_Cfg.h

2. Replace the RvsBattProtn_Cfg.h file in tools/local/generate folder with the above file.

Now, Tessy must be able to modify the values of these config params. We should then test them with the range that is given in their definition in the DataDict.m file.

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