USA
Canada 
China 
France 
Germany 
India 
Italy 
Mexico 
Middle East 
Singapore 
Spain 
Thailand 
Writing Effective Requirements and Test Cases for Automotive Software Performance Improvement and Capability Determination (Automotive SPICE® ) and HWE PRM/PAM
Writing Effective Requirements and Test Cases for Automotive Software Performance Improvement and Capability Determination (Automotive SPICE®) and HWE PRM/PAM
Register for courses 30 days in advance and get 5% off this price
Note:Pricing is dependent on location and may vary.*Please note, we request those interested to pay shipping and handling. Write to us for more information: info@omnex.com
model in the automotive industry and its subsequent benefits." Download Now:
Course Duration: 3 Days - 8 Hours/day
This three-day course is designed to give the attendee a detailed understanding of writing Effective Requirements and Test Cases through process workshops focused on the system, software and hardware process groups.
The course combines best practices from Automotive SPICE® 3.1 PRM/PAM and HWE PRM/PAM.
Learning Objectives
· Detailed understanding of what Automotive SPICE® is and the motivation behind the model
· Detailed understanding of process capability level 1 (VDA-Scope)
· Detailed understanding of traceability requirements
· Detailed understanding of creating requirements for software and its elements at various levels
· Understanding of how to evaluate process risks and drive process improvements
Day One
· Chapter 1: Introduction and Overview
o Definition
o History
o Structure
o Key Concepts
· Chapter 2: Understanding System/Software Requirements
o Defining Requirements
o Types of Requirements
o Notation for Requirements
o Requirements Elicitation
o Breakout Exercise 1: Introduction of Case Study System Requirements (SYS.2)
o Breakout Exercise 2: SWE Requirements (SWE.1)
· Chapter 3: Architectural Design
o Notation for System Architecture
o Notation for Software Architecture
o Breakout Exercise 3: Develop the Software Architecture using Block Diagram, Timing Chart, and Allocation Matrix for Architectural (SWE.2)
Day Two
· Chapter 4: Developing Software Detailed Design, Unit Construction, and Software Unit Verification
o Develop Software Detailed Design
o Coding Style
o Coding Rules
o Breakout Exercise 4: Deriving Software Detailed Design and Unit Construction (SWE.3)
o Breakout Exercise 5: Software Unit Verification (SWE.4)
o Unit Testing
· Chapter 5: Conducting Software Integration and Integration Testing, and Software Qualification Test
o Test Case Development
o Test Methods
o Breakout Exercise 6: Integration Testing (SWE.5)
o Breakout Exercise 7: Conducting Software Qualification Testing (SWE.6)
Day Three
· Chapter 7: Developing Hardware Requirements
o Defining HW Requirements
o HW Design
o Breakout Exercise 8 – Hardware Requirements Analysis
o Test Methods
· Chapter 8: Creating the V-Model using DFMEA and DVP&R
Who Should Attend
The seminar has been developed for:
· Developers, test engineers, project managers, software quality engineers and managers & other participants involved with development of embedded systems in the automotive industry.
· Hardware designers, test engineers, project managers, hardware quality engineers and managers & other participants involved with development of embedded systems in the automotive industry.
· Software and Hardware managers, Automotive SPICE® Implementers, internal auditors and others who need to understand Automotive SPICE® and how to integrate it into their Quality Management or Functional Safety system will find the training helpful.
Each participant will receive a seminar manual including case studies.
Background in “development projects”, “software development”, “quality management systems”, or “functional safety” will be helpful.
A basic understanding of project management, quality management and system and software engineering processes is helpful, but not required.