This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Component Implementation

Component Implementation

Component Documentation

1 - FordMsg3B3BusHiSpd_IntegrationManual

Integration Manual

For

FordMsg3B3BusHiSpd

VERSION: 1.0

DATE: 04-Dec-2017

Prepared By:

Tata Elxsi,

Trivandrum, INDIA.

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

Revision History

Sl. No.DescriptionAuthorVersionDate
1Initial versionTATA1.004-Dec-2017

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 NvM Blocks 10

8 Compiler Settings 11

8.1 Preprocessor MACRO 11

8.2 Optimization Settings 11

9 Appendix 12

Abbrevations And Acronyms

AbbreviationDescription
DFDDesign functional diagram
MDDModule design Document
<ADD more to the table if applicable>

References

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

Sr. No.TitleVersion
1FDD: MM072A_FordMsg3B3BusHiSpd_DesignSee Synergy Sub Project Version
2Software Naming Conventions1.0
3Software Design and Coding Standards2.1
<Add if more available>

Dependencies

SWCs

ModuleRequired Feature
None

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_BodyInfo_3_HS2, ComTimeoutNotification_Ignition_Status.

Configuration REQUIREMeNTS

Build Time Config

ModulesNotes
None

Configuration Files to be provided by Integration Project

None

Da Vinci Parameter Configuration Changes

ParameterNotesSWC
None

DaVinci Interrupt Configuration Changes

ISR NameVIM #Priority DependencyNotes
None

Manual Configuration Changes

ConstantNotesSWC
None

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Refer DataDict.m file in the FDD

Required Global Data Outputs

Refer DataDict.m file in the FDD

Specific Include Path present

No

Runnable Scheduling

This section specifies the required runnable scheduling.

InitScheduling RequirementsTrigger
FordMsg3B3BusHiSpdInit1NoneRTE (Init)
RunnableScheduling RequirementsTrigger
FordMsg3B3BusHiSpdPer1NoneRTE (10 ms)
Srv RunnableScheduling RequirementsTrigger
ComIPduCallout_BodyInfo_3_HS2None

On invocation of

CComIPduCallout_BodyInfo_3_HS2.Oper(NON-RTE)

Srv RunnableScheduling RequirementsTrigger
ComTimeoutNotification_Ignition_StatusNone

On invocation of

ComTimeoutNotification_Ignition_Status.Oper(NON-RTE)

Memory Map REQUIREMENTS

Mapping

Memory SectionContentsNotes
None

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

Usage

FeatureRAMROM
None

Table 1: ARM Cortex R4 Memory Usage

NvM Blocks

None

Compiler Settings

Preprocessor MACRO

None.

Optimization Settings

None.

Appendix

None.

2 - FordMsg3B3BusHiSpd_MDD

Module Design Document

For

FordMsg3B3BusHiSpd

June 19, 20157

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Tata Elxsi,

Trivandrum, INDIA

Change History

DescriptionAuthorVersionDate
Initial VersionTATA1.004-Dec-2017

Table of Contents

1 Introduction 5

1.1 Purpose 5

2 FordMsg3B3BusHiSpd & High-Level Description 6

3 Design details of software module 7

3.1 Graphical representation of FordMsg3B3BusHiSpd 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: FordMsg3B3BusHiSpdInit1 9

5.1.1.1 Design Rationale 9

5.1.1.2 Module Outputs 9

5.1.2 Per: FordMsg3B3BusHiSpdPer1 9

5.1.2.1 Design Rationale 9

5.1.2.2 Store Module Inputs to Local copies 9

5.1.2.3 Processing of function) 9

5.1.2.4 Store Local copy of outputs into Module Outputs 9

5.2 Server Runnables 9

5.2.1 ComIPduCallout_BodyInfo_3_HS2 9

5.2.1.1 Design Rationale 9

5.2.1.2 (Processing of function) 9

5.2.2 ComTimeoutNotification_Ignition_Status 9

5.2.2.1 Design Rationale 9

5.2.2.2 (Processing of function) 9

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.4.2 Local Function #2 10

5.4.2.1 Design Rationale 10

5.4.2.2 Processing 10

5.4.3 Local Function #3 11

5.4.3.1 Design Rationale 11

5.4.3.2 Processing 11

5.4.4 Local Function #4 11

5.4.4.1 Design Rationale 11

5.4.4.2 Processing 11

5.4.5 Local Function #5 12

5.4.5.1 Design Rationale 12

5.4.5.2 Processing 12

5.5 GLOBAL Function/Macro Definitions 12

6 Known Limitations with Design 13

7 UNIT TEST CONSIDERATION 14

Appendix A Abbreviations and Acronyms 15

Appendix B Glossary 16

Appendix C References 17

Introduction

Purpose

MDD for FordMsg3B3BusHiSpd

FordMsg3B3BusHiSpd & High-Level Description

Please refer FDD.

Design details of software module

Graphical representation of FordMsg3B3BusHiSpd

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

Constant NameResolutionUnitsValue
Please refer Data Dictionary .m fileNANANA

Software Component Implementation

Sub-Module Functions

5.1.1 Init: FordMsg3B3BusHiSpdInit1

Design Rationale

None

Module Outputs

None

5.1.2 Per: FordMsg3B3BusHiSpdPer1

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_BodyInfo_3_HS2

5.2.1.1 Design Rationale

None

5.2.1.2 (Processing of function)

None

5.2.2 ComTimeoutNotification_Ignition_Status

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

Function NameDiagEnaTypeMinMax
Arguments PassedFordTrlrBackupAssiEnad_Cnt_T_u08Uint80U1U
FordCanDtcInhb_Cnt_T_u08Uint80U1U
ClrDiagcFlgProxy_Cnt_T_u08Uint80U1U
FordMfgDiagcInhb_Cnt_T_u08Uint80U1U
FordMissMsgDiagcInhb_Cnt_T_u08Uint80U1U
FordInvldMsgDiagcInhb_Cnt_T_u08Uint80U1U
*MissMsgDiagEna_Cnt_T_loglBooleanFALSETRUE
*FordVehIgnStsInVldMsgDiagEna_Cnt_loglBooleanFALSETRUE
Return ValueNone

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM072A_FordMsg3B3BusHiSpd_SIL/FordMsg3B3BusHiSpd/FordMsg3B3BusHiSpdPer1/DiagEna

Local Function #2

Function NameMissMsgDeterminationTypeMinMax
Arguments PassedBusHiSpdMissThd_Cnt_T_u16Uint160U6000U
MissMsgDiagEna_Cnt_T_loglBooleanFALSETRUE
*FordVehIgnStsVal_Cnt_T_enumFord_Ignition_Status0U15U
*FordVehLifeCycModVal_Cnt_T_enumFord_LifeCycMde_D_Actl0U3U
*FordVehIgnStsVldVal_Cnt_T_loglBooleanFALSETRUE
Return ValueNone

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM072A_FordMsg3B3BusHiSpd_SIL/FordMsg3B3BusHiSpd/FordMsg3B3BusHiSpdPer1/MissMsgDetermination

Local Function #3

Function NameMsgPrsntTypeMinMax
Arguments PassedBusHiSpdInvldThd_Cnt_T_u16Uint160U6000U
MissMsgDiagEna_Cnt_T_loglBooleanFALSETRUE
FordVehIgnStsInVldMsgDiagEna_Cnt_loglBooleanFALSETRUE
Ford_Ignition_Status1_Cnt_T_enumFord_Ignition_Status0U15U
Ford_LifeCycMde_D_Actl1_Cnt_T_enumFord_LifeCycMde_D_Actl0U3U
*FordVehIgnStsVal_Cnt_T_enumFord_Ignition_Status0U15U
*FordVehLifeCycModVal_Cnt_T_enumFord_LifeCycMde_D_Actl0U3U
*FordVehIgnStsVldVal_Cnt_T_loglBooleanFALSETRUE
Return ValueNone

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM072A_FordMsg3B3BusHiSpd_SIL/FordMsg3B3BusHiSpd/FordMsg3B3BusHiSpdPer1/Msg_Present

Local Function #4

Function NameOutpProcgTypeMinMax
Arguments PassedFord_Ignition_Status1_Cnt_T_enumFord_Ignition_Status0U15U
Ford_LifeCycMde_D_Actl1_Cnt_T_enumFord_LifeCycMde_D_Actl0U3U
*FordVehIgnStsVal_Cnt_T_enumFord_Ignition_Status0U15U
*FordVehLifeCycModVal_Cnt_T_enumFord_LifeCycMde_D_Actl0U3U
*FordVehIgnStsVldVal_Cnt_T_loglBooleanFALSETRUE
*FordVehIgnStsInp_Cnt_loglBooleanFALSETRUE
Return ValueNone

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM072A_FordMsg3B3BusHiSpd_SIL/FordMsg3B3BusHiSpd/FordMsg3B3BusHiSpdPer1/Msg_Present/OutputProcessing

Local Function #5

Function NameElpdTiTypeMinMax
Arguments Passed* VldElpdTi_Cnt_T_loglBooleanFALSETRUE
* InvldElpdTi_Cnt_T_loglBooleanFALSETRUE
Return ValueNone

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM072A_FordMsg3B3BusHiSpd_SIL/FordMsg3B3BusHiSpd/FordMsg3B3BusHiSpdPer1/Msg_Present/OutputProcessing/ElpdTi

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

None

UNIT TEST CONSIDERATION

None.

Abbreviations and Acronyms

Abbreviation or AcronymDescription

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

TermDefinitionSource
MDDModule Design Document
DFDData Flow Diagram

References

Ref. #TitleVersion
1AUTOSAR Specification of Memory Mapping (Link:AUTOSAR_SWS_MemoryMapping.pdf)v1.3.0 R4.0 Rev 2
2MDD GuidelineEA4 01.00.00
3Software Naming Conventions.doc1.0
4Software Design and Coding Standards.doc2.1
5FDD: MM072A_FordMsg3B3BusHiSpd_DesignSee Synergy sub project version

3 - FordMsg3B3BusHiSpd_PeerReviewChecklist
























Rev 2.0029-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
MM072A_FordMsg3B3BusHiSpd_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
MM072A_FordMsg3B3BusHiSpd_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#20800





























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/AMDD


NoSource Code


NoPolySpace









































N/AIntegration Manual


NoDavinci 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.