process approach to autonomous vehicle development · system architecture –eng 3 8 •system...
TRANSCRIPT
Bodo Seifert
March 2, 2017
Director Advanced Engineering
PROCESS APPROACH TO AUTONOMOUS VEHICLE DEVELOPMENT
$36Billion 155,000
312 global sites
SALES (outlook) EMPLOYEES
MANUFACTURING MARKET POSITION
#1North America
#3 World
Complexity
3
• In the automotive realm, the explosion of system complexity is clearly evident– High end vehicles use 50-80 ECU which
contain embedded software
– Approximately 20 million lines of code in those 50-80 modules
• Problem Statement
– Manage requirements for above scope
– Prove verification & validation cover each requirement
– Plan and track the project
– Institutionalize risk management
– Manage suppliers
The Way Out: V-Model Approach
4
Customer
Requirements
System
TestSystem
Requirements
System
Architecture
System
Integration Test
SW/HW
Test
SW/HW
Requirements
SW/HW
Design
SW/HW
Integration Test
Management: Project, Risk, Configuration, Issue Change,
Supplier Quality Assurance, Joint Review, Product Release
HW/SW
Construction
Industry Standards Available
5
• CMMI (Capability Maturity Model Integration)
• Automotive SPICE (Software Process Improvement and Capability Determination)
• HIS (Hersteller Initiative Software)
Process Area
Base Practices
Outcomes
Work ProductsFirst CMM
Published
1987
SPICE Core
team formed
1992
CMMI
Initiative
launched
1997
SPICE
Baseline
1998SPICE
Technical
Report
1999SPICE
Usergroup
formed
2000
ASPICE
Launched
2005
CMMI Ver
1.0 launched
2000
COMMUNICATION
CHANGE MGMT.
DEFINITIONS
Customer Requirements – ENG 1
Main Goals: Gather, process and track evolving customer
needs and requirements. Establish a requirements.
• Continuing communication with the customer is established
• Mechanism established to monitor customer needs continuously
• Mechanism established ensuring customer can easily determine the status
• Change mechanism is established
• Changes identified, associated risks assessed and impact managed
• Agreed customer requirements are defined and baselined
COMMUNICATION
CHANGE MGMT.
DEFINITIONS
System Requirements – ENG 2
• System requirements approved and updated as needed
• Consistency & bilateral traceability are established
• Communicated to all affected parties and baselined
• Changes to the customer's requirements baseline are evaluated for cost,
schedule & technical impact
• Defined set of system requirements established
• Categorized & analyzed for correctness and testability
• Impact evaluated & prioritization for implementing is defined
Purpose: analysis process is to transform the defined
customer requirements into a set of desired system technical
requirements that will guide the design of the system.
COMMUNICATION
CHANGE MGMT.
DEFINITIONS
System Architecture – ENG 3
8
• System requirements, the system architectural design, & their relationships
are baselined & communicated to all affected parties
• Consistency & bilateral traceability are established
• Verification between the system requirements & the system architectural
design is performed
• Identified system elements & meets defined system requirements
• System requirements allocated to the system elements
• Internal & external interfaces of each system element are defined
Purpose: identify which system requirements are to be
allocated to which elements of the system.
Traceability
9
• Prove that customer
requirements are
implemented
• Ensure requirements
are atomic
• Prove each system
requirement is verified
by at least one test
case
• Link between ENG. 1
and ENG. 2 ensures
full customer
requirements
development
Project Execution - ALM Tool
10
• ALM tool to tie all elements together. A well
integrated tool can manage and link the
requirements, provide versioning and KPI
reports
• Main goal: automation, little manual data
manipulation by the development team
Project Planning
RQMT Management
SW Development
Test
Resources
Project Execution - Gates
11
Quote Development Production End of Prod.
Quote
Start
Quote
Approval
Dev. Start
Design
Freeze
DV
Prod.
Tool purchase
PV
PPAPProduction part
approval processLaunch Prep
• Gate milestones need to align with the deliverables
• Deliverables can be tailored to the project needs
• Gates are only passed if the deliverable is available
Project Execution - Initial Plan
12
• Requirements inventory provides number of
documents, pages per document and an
estimate of requirements/document as well
as a prioritization
• Man power estimate can be calculated by
computing the total requirements and
multiplying this number by the estimated
time to process a requirement
• Reuse has to be analyzed
• Consider available resources and then
project the requirements processed per
month
0
1000
2000
3000
4000
5000
Re
qu
ire
me
nts
Customer Requirement Burndown
Design
Freeze
Project ExecutionCustomer Requirements Analysis
13
Necessary Steps:
1. Identify relevant documents from SOW
2. Procure documents
3. Distinguish between requirements and comments
4. Determine requirement ‘goodness’
5. Import the requirements into the ALM tool
Source: Reuse Company
Project Execution - KPI
14
050
100150200250300350400450
Accepted/Rejected
Blank
Review/Check
May June July
Lane
Departure
Radar
Based ACC
Feature By Phase Plan
Radar ACC Lane D.SW Eng. A
SE Eng. X
SE Eng. Y
Radar ACC
Lane Dpt.
Traffic Sign
High Speed FCA
April May June July
Resource Plan
• Similar steps need to be taken for the systems requirements and the HW/SW requirements
• Reuse is a critical concept to manage the sheer number of requirements
Project Execution - Detailed Design
10/10/2017
15
• Proper planning
• Adequate staffingPLANNING
DEFINITIONS• Well defined requirements
• Detailed system architecture design
• Definition of domain requirements
Project Execution - Integration and Test
16
• Resources are planned and availableRESOURCE
AVAILABILITY
READYNESS• Requirements are testable
• Traceability is ensured and verified
Recommendations
17
• Use process model, tailor to your organization
• Pick a suitable ALM tool
• Go from the system of systems to the system, then the sub system and then the element
• Plan your requirements processing and burn-down
• Have risk and change management in place
• Document and communicate your assumptions
• Manage requirements churn
• Enforce traceability and testing on the lower levels of the ‘V’ model
• Plan and monitor your gate deliverables