Swp_MDD

Module Design Document

For

Swp

Jan 20, 2016

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Krishna Kanth Anne,

Nexteer Automotive,

Saginaw, MI, USA
Change History

Table of Contents

1 Introduction 4

1.1 Purpose 4

1.2 Scope 4

2 PullCmpActv & High-Level Description 5

3 Design details of software module 6

3.1 Graphical representation of PullCmpActv 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: SwpInit1 8

5.1.2 Per: SwpPer1 8

5.1.3 Per: SwpPer2 8

5.2 Module Internal (Local) Functions 8

5.2.1 Local Function #1 8

5.2.1.1 Design Rationale 8

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

MDD for Sweep function

Scope

NA

Swp & High-Level Description

Please refer FDD.

Design details of software module

Please refer FDD.

Graphical representation of Swp

Data Flow Diagram

Please refer FDD.

Component level DFD

Please refer FDD.

Function level DFD

Please refer FDD.

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Software Component Implementation

Please refer FDD.

Sub-Module Functions

Init: SwpInit1

Please refer FDD.

Design Rationale

Dummy Initialization function to correlate with the FDD (.m file)

Per: SwpPer1

Please refer FDD.

Design Rationale

1. For DFs, it was decided to use the module level variables in place of PIMs defined in the FDD (PIM section of .m file), This is a deviation from regular EA4 process. This is to give control over MemMap to avoid MPU violations while writing these variables using xcp.

2. All of the given PIMs from .m file are either defined as of Function level variables (if used in only one function) or Module level variables (if used in more than one function) in DFs.

3. Each of the Function level and Module level variables shall be volatile only when they are intended to be user modifiable as per the data dictionary .m file.

4. Deviations exist in the naming conventions for all of Function level and Module level variables from regular EA4 naming conventions.

Per: SwpPer2

Please refer FDD.

Design Rationale

1. For DFs, it was decided to use the module level variables in place of PIMs defined in the FDD (PIM section of .m file), This is a deviation from regular EA4 process. This is to give control over MemMap to avoid MPU violations while writing these variables using xcp.

2. All of the given PIMs from .m file are either defined as of Function level variables (if used in only one function) or Module level variables (if used in more than one function) in DFs.

3. Each of the Function level and Module level variables shall be volatile only when they are intended to be user modifiable as per the data dictionary .m file.

4. Deviations exist in the naming conventions for all of Function level and Module level variables from regular EA4 naming conventions.

Known Limitations with Design

None.

UNIT TEST CONSIDERATION

1. Please refer Init.txt file in the FDD design: DF002A_Swp_Design for initial values of Function level and Module level variables.

2. For DFs, it was decided to use the module level variables in place of PIMs defined in the FDD (PIM section of .m file), This is a deviation from regular EA4 process.

3. All of the given PIMs from .m file are either defined as of Function level variables (if used in only one function) or Module level variables (if used in more than one function) in DFs.

4. Each of the Function level and Module level variables shall be volatile only when they are intended to be user modifiable as per the data dictionary .m file.

5. Deviations exist in the naming conventions for all of Function level and Module level variables from regular EA4 naming conventions.

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