SerlComTrcvIf_MDD

Module Design Document

For

SerlComTrcvIf

February 21, 2018

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 SerlComTrcvIf & High-Level Description 5

3 Design details of software module 6

3.1 Graphical representation of SerlComTrcvIf 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: SerlComTrcvIfInit1 8

5.1.2 Per: SerlComTrcvIfPer1 8

5.2 Server Runables 8

5.3 Interrupt Functions 8

5.4 Module Internal (Local) Functions 9

5.4.1 Local Function MonitorERRN 9

5.4.2 Local Function ReadAndAnalyze 9

5.4.3 Local Function AnalyzeRegister 9

5.4.4 Local Function ParityErrorCheck 10

5.5 GLOBAL Function/Macro Definitions 11

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

Module Design Document for SerlComTrcvIf.

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.

SerlComTrcvIf & High-Level Description

The Serial Communication Transceiver Interface function monitors error status of FlexRay transceiver, reads the Status Registers via SPI and sets appropriate NTCs.

Design details of software module

Graphical representation of SerlComTrcvIf

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

Design Rationale

Refer FDD

Module Outputs

None

Per: SerlComTrcvIfPer1

Design Rationale

Refer FDD

Store Module Inputs to Local copies

None

(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

Local Function MonitorERRN

Design Rationale

Implementation of Simulink block "MonitorERRN".

Processing

Refer Simulink block "MonitorERRN".

Local Function ReadAndAnalyze

Design Rationale

Implementation of Simulink block "ReadAndAnalyze".

Processing

Refer Simulink block "ReadAndAnalyze".

Local Function AnalyzeRegister

Design Rationale

Implementation of Simulink block "AnalyzeRegister".

Processing

Refer Simulink block "AnalyzeRegister".

Local Function ParityErrorCheck

Design Rationale

Implementation of Simulink block "ParityErrorCheck".

Processing

Refer Simulink block "ParityErrorCheck".

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