Skip to main content

Research of Automotive Change Management and Supportive Risk Management

  • Conference paper
  • First Online:
Soft Computing Applications

Part of the book series: Advances in Intelligent Systems and Computing ((AISC,volume 357))

  • 1064 Accesses

Abstract

“Change Management” in automotive electronic control units (ECU) development project is one of the most important, but undervalued and understood tools to guarantee the success of a project. An ECU embedded within a car electronic environment is constantly under attack of a continuous flow of modifications of specifications throughout the development life cycle until start-of-production (SoP). Root causes for those modifications are, for instance, simply software or hardware implementation errors, improvement for robust design or requirement changes to satisfy the forthcoming demands of the market to ensure the later commercial success. Clearly, it is unavoidable that from the very beginning until the very end of the project “requirement changes” will “expose” the agreed objectives defined by contract specifications, which are product features, budget, schedule, and quality. The following investigation will assume that initially a feasibility study was undertaken to judge the general possibility to achieve the project objectives. Thus the key discussions will focus upon requirement changes or in the latter called RfC’s (Request for Change) and their possible project risk. Building a thorough understanding of prospective threats is of paramount importance in order to establish the adequate project management process landscape to handle RfC’s. In short, how to manage “risks” of RfC’s. Moreover, this paper analyzes and identifies the constraints along the applied automotive Change-Management (CM) processes, reviewing the project life cycle of automotive projects. The research will not limit, bus focus on the investigation of changes during the early phase of the project: the concept-validation and debugging phase (see Fig. 1). In addition, clearly outlines frameworks of supportive processes to improve automotive CM practices with respect to risk management. The examined risk management process will visualize the in- and out-flow status of RfC’s. In addition, deliver instruments to judge the carried risks of RfC have to meet agreed project objectives, consequently minimizing the risk.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 169.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 219.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Abbreviations

CAB:

Change Advisory Board, see also CCB (ITIL® glossary [4])

CCB:

Change Control Board, see also CAB (OEM Terminology)

CD:

Concept-Decision (OEM Terminology)

CDS:

Concept-Development-Sample (OEM Terminology)

Change management:

(ITIL Service Transition) The process responsible for controlling the lifecycle of all changes, enabling beneficial changes to be made with minimum disruption to IT services (ITIL® glossary [4])

CMDB:

Change Management Database for RfC documentation (ITIL® glossary [4])

CMS:

Configuration Management System (ITIL® glossary [4])

CRM:

Change Request Manager or RfC Manager (OEM Terminology)

CRM:

Change Request Management (OEM Terminology)

CRS:

Concept Requirement-Specification (OEM Terminology)

PoC-S:

ECU PoC-Sample (OEM Terminology)

FRS-S:

ECU FRS-Sample (OEM Terminology)

0B-S:

ECU 0B-Sample (OEM Terminology)

ECU:

Electronic Control Unit (OEM Terminology)

EMR:

ECU-Model-Release-Sample (OEM Terminology)

FO:

Functional Owner: Functional Specialist (OEM Terminology)

FRS:

Final Requirement Specification (OEM Terminology)

HW:

Hardware (Common abbreviation)

New-Bug:

New Bug or error report (OEM Terminology)

New-Req:

New Requirement (OEM Terminology)

OEM:

Original Equipment Manufacturer (OEM Terminology)

PD:

Product-Definition (OEM Terminology)

PF:

Project-Feasibility (OEM Terminology)

PM:

Product-Mission (OEM Terminology)

PS:

Pilot Series (OEM Terminology)

Requirement:

(ITIL Service Design) A formal statement of what is needed—for example, a service level requirement, a project requirement or the required deliverables for a process (ITIL® glossary [4])

Requirement:

“A statement of a system service and constraints” [5]

Requirements engineering process:

“The structure set of activities involved in developing system requirements” [5]

Requirements Management:

“The processes involved in managing changes to requirements” (ITIL® glossary [4])

RfC:

Request for Change (ITIL® glossary [4])

SoP:

Start of Production (OEM Terminology)

SW:

Software (Common abbreviation)

VMP:

Validate production process for Mass Production

References

  1. Hutanu A (2014) Research of requirements constraints in automotive projects. Version: 2014. http://www.softwaretestingclass.com/wp-content/uploads/2012/05/v-model-stlc1.png. Accessed 10 Apr 2013

  2. ITIL3 Service transition (2007) ISBN: 978 0 11 331048 7. Copyright 2007

    Google Scholar 

  3. ITIL3 Service transition (2007) ISBN: 978 0 11 331048 7. Copyright 2007, p 52

    Google Scholar 

  4. ITIL® glossary and abbreviations English. http://www.itil-officialsite.com/InternationalActivities/ITILGlossaries_2.aspx, ITIL. www.itil-officialsite.com/InternationalActivities/TranslatedGlossaries.aspx, ITIL® 2011 edition. Accessed 12 Mar 2014

  5. Kotonya G, Sommerville I Requirements engineering—processes and techniques, Wiley. Version, ISBN: 0 471 97208 8, p 6

    Google Scholar 

  6. Sommerville I Software engineering. Addison-Wesley, 6th edn. ISBN: 0-20139815-X, pp 647–650

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Stephan Volker .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer International Publishing Switzerland

About this paper

Cite this paper

Volker, S., Prostean, G., Hutanu, A. (2016). Research of Automotive Change Management and Supportive Risk Management. In: Balas, V., Jain, L., Kovačević, B. (eds) Soft Computing Applications. Advances in Intelligent Systems and Computing, vol 357. Springer, Cham. https://doi.org/10.1007/978-3-319-18416-6_89

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-18416-6_89

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-18415-9

  • Online ISBN: 978-3-319-18416-6

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics