Component Implementation

• 1: FordMsg40ABusHiSpd_IntegrationManual
• 2: FordMsg40ABusHiSpd_MDD
• 3: FordMsg40ABusHiSpd_PeerReviewChecklist

1 - FordMsg40ABusHiSpd_IntegrationManual

Integration Manual

For

FordMsg40ABusHiSpd

VERSION: 1.0

DATE: 11-Dec-2017

Prepared By:

TATA

Trivandrum, INDIA

Location: The official version of this document is stored in the Nexteer Configuration Management System.

Revision History

Table of Contents

1 Abbrevations And Acronyms 4

2 References 5

3 Dependencies 6

3.1 SWCs 6

3.2 Global Functions(Non RTE) to be provided to Integration Project 6

4 Configuration REQUIREMeNTS 7

4.1 Build Time Config 7

4.2 Configuration Files to be provided by Integration Project 7

4.3 Da Vinci Parameter Configuration Changes 7

4.4 DaVinci Interrupt Configuration Changes 7

4.5 Manual Configuration Changes 7

5 Integration DATAFLOW REQUIREMENTS 8

5.1 Required Global Data Inputs 8

5.2 Required Global Data Outputs 8

5.3 Specific Include Path present 8

6 Runnable Scheduling 9

7 Memory Map REQUIREMENTS 10

7.1 Mapping 10

7.2 Usage 10

7.3 Non RTE NvM Blocks 10

7.4 RTE NvM Blocks 10

8 Compiler Settings 11

8.1 Preprocessor MACRO 11

8.2 Optimization Settings 11

9 Appendix 12

Abbrevations And Acronyms

References

This section lists the title & version of all the documents that are referred for development of this document

Dependencies

SWCs

Note : Referencing the external components should be avoided in most cases. Only in unavoidable circumstance external components should be referred. Developer should track the references.

Global Functions(Non RTE) to be provided to Integration Project

ComIPduCallout_GGCC_Config_Mgmt_ID_1_HS2, ComTimeoutNotification_VehicleGGCCData

Configuration REQUIREMeNTS

Build Time Config

Configuration Files to be provided by Integration Project

None

Da Vinci Parameter Configuration Changes

DaVinci Interrupt Configuration Changes

Manual Configuration Changes

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Refer DataDict.m file

Required Global Data Outputs

Refer DataDict.m file

Specific Include Path present

No

Runnable Scheduling

This section specifies the required runnable scheduling.

Memory Map REQUIREMENTS

Mapping

* Each …START_SEC… constant is terminated by a …STOP_SEC… constant as specified in the AUTOSAR Memory Mapping requirements.

Usage

Table 1: ARM Cortex R4 Memory Usage

Non RTE NvM Blocks

Note : Size of the NVM block if configured in developer

RTE NvM Blocks

Note : Size of the NVM block if configured in developer

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

None

Appendix

None

2 - FordMsg40ABusHiSpd_MDD

Module Design Document

For

FordMsg40ABusHiSpd

June 19, 20157

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Tata Elxsi,

Trivandrum, INDIA

Change History

Table of Contents

1 Introduction 4

1.1 Purpose 4

2 FordMsg40ABusHiSpd & High-Level Description 5

3 Design details of software module 6

3.1 Graphical representation of FordMsg40ABusHiSpd 6

3.2 Data Flow Diagram 6

Component level DFD 6

Function level DFD 6

4 Constant Data Dictionary 7

4.1 Program (fixed) Constants 7

Embedded Constants 7

5 Software Component Implementation 8

5.1 Sub-Module Functions 8

5.1.1 Init: FordMsg40ABusHiSpdInit1 8

5.1.2 Per: FordMsg40ABusHiSpdPer1 8

5.2 Server Runnables 8

5.2.1 ComIPduCallout_GGCC_Config_Mgmt_ID_1_HS2 8

5.2.2 ComTimeoutNotification_VehicleGGCCData 8

5.3 Interrupt Functions 9

5.4 Module Internal (Local) Functions 9

5.4.1 Local Function #1 9

5.4.2 Local Function #2 9

5.4.3 Local Function #3 10

5.4.4 Local Function #4 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

MDD for FordMsg40ABusHiSpd

FordMsg40ABusHiSpd & High-Level Description

Please refer FDD.

Design details of software module

Graphical representation of FordMsg40ABusHiSpd

Data Flow Diagram

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

Sub-Module Functions

5.1.1 Init: FordMsg40ABusHiSpdInit1

5.1.1.1 Design Rationale

None

5.1.1.2 Module Outputs

None

5.1.2 Per: FordMsg40ABusHiSpdPer1

5.1.2.1 Design Rationale

None

5.1.2.2 Store Module Inputs to Local copies

None

5.1.2.3 Processing of function

None

5.1.2.4 Store Local copy of outputs into Module Outputs

None

Server Runnables

5.2.1 ComIPduCallout_GGCC_Config_Mgmt_ID_1_HS2

5.2.1.1 Design Rationale

None

5.2.1.2 Processing of function

None

5.2.2 ComTimeoutNotification_VehicleGGCCData

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

Design Rationale

None

Processing

Please refer to the below path in the FDD model.

MM076A_FordMsg40ABusHiSpd/FordMsg40ABusHiSpd/FordMsg40ABusHiSpdPer1/DiagEna

Local Function #2

Design Rationale

None

Processing

Please refer to the below path in the FDD model.

MM076A_FordMsg40ABusHiSpd/FordMsg40ABusHiSpd/FordMsg40ABusHiSpdPer1/MissMsgFaild

Local Function #3

Design Rationale

None

Processing

Please refer to the below path in the FDD model.

MM076A_FordMsg40ABusHiSpd/FordMsg40ABusHiSpd/FordMsg40ABusHiSpdPer1/MissMsgPassd

Local Function #4

Design Rationale

None

Processing

Please refer to the below path in the FDD model.

MM076A_FordMsg40ABusHiSpd/FordMsg40ABusHiSpd/FordMsg40ABusHiSpdPer1/MissMsgPassd/OutpProc

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

In model FordVehGlbRealTiPrev(PIM) value is assigned to FordVehGlbRealTi(Output). But both signal minimum value is not matching in the datadictionary.

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

3 - FordMsg40ABusHiSpd_PeerReviewChecklist

Rev 2.00

29-Nov-17

Nexteer SWC Implementation Peer Review Summary Sheet

Component Short Name:

Windows User: Intended Use: Identify which component is being reviewed. This should match the component short name from the DataDict.m fileand the middle part of the Synergy project name, e.g. Assi for the SF001A_Assi_Impl Synergy project

MM076A_FordMsg40ABusHiSpd_Impl

Revision / Baseline:

Windows User: Intended Use: Identify the implementation baseline name intended to be used for the changed component when changes are approved E.g. SF001A_Assi_Impl_1.2.0

MM076A_FordMsg40ABusHiSpd_Impl_3.0.0

Change Owner:

Windows User: Intended Use: Identify the developer who made the change(s) being reviewed

Matthew Leser

Work CR ID:

Windows User: Intended Use: Identify the Implementation Work CR whose work is being reviewed (may be more than one)

EA4#20816

kzshz2: Intended Use: Intended to identify at a high level to the reviewers which areas of the component have been changed. Rationale: This will be good information to know when ensuring appropriate reviews have been completed. Modified File Types:

Check the file types that needed modification for the Work CR(s); macros for the check boxes will populate the appropriate checklist tabs for the review.

kzshz2: Intended Use: Identify who where the reviewers, what they reviewed, and if the reviewed changes have been approved to release the code for testing. Comments here should be at a highlevel, the specific comments should be present on the specific review form sheet. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. ADD DR Level Move reviewer and approval to individual checklist form Review Checklist Summary:

Reviewed:

At start of review, all items below should be marked "No". At the end of the review, all items should be marked "Yes" or "N/A" where N/A indicates the reviewers have reviewed the existing (unchanged) item and confirmed no updates were needed for the Work CR(s).

N/A

MDD

No

Source Code

No

PolySpace

N/A

Integration Manual

No

Davinci Files

Comments:

Offline review was done for this component for timing as per management decision.

General Guidelines: - The reviews shall be performed over the portions of the component that were modified as a result of the Change Request. - New components should include SWC Owner and/or SWC Design author and Integrator and/or SW Lead as apart of the Group Review Board (Source Code, Integration Manual, and Davinci Files) - Enter any rework required into the comment field and select No. When the rework is complete, review again using this same review sheet and select Yes. Add date and additional comment stating that the rework is completed. - To review a component with multiple source code files use the "Add Source" button to create a Source code tab for each source file. - .h file should be reviewed with the source file as part of the source file. Each peer review shall start with a clean copy of the latest peer review checklist template. Before the peer review, the change owner shall: o Review the previous component peer review and copy any relevant comments to the new review sheet. o Review all checklist items and make all corrections needed, so that the component is ready for peer review. The expectation is that peer review should find very few issues, because the change owner has already used the checklist to ensure the component changes are complete and correct. o Fill in all file name and version information as needed on peer review checklist tabs (file names may be copied from the previous peer review where appropriate) o Fill in checklist answers (Yes/No/NA pulldowns) ONLY on those items which are NA for the current change. All other checklist items should be blank going into the review meeting. During the peer review meeting: o For each page of the review, first review the items already marked as N/A for this change, to confirm that reviewers agree with this assessment; change the checklist box to blank if it is found that the item does apply. o Then review the items with the checklist box blank. After reviewing each of these items, the checklist box will be marked as "Yes", or the checklist box will be marked as "No" with needed rework indicated or with rationale indicated. o If any items are marked "No" with rationale indicated, this must be approved by a software supervisor or the software manager; there is a line in the "Review Board" section of each tab to indicate who approved the "No" items on that tab.