driving worldwide business excellence

Writing Effective Requirements and Test Cases

Seminar Content

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.

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, ASPICE Implementers, internal auditors and others who need to understand ASPICE and how to integrate it into their Quality Management or Functional Safety system will find the training helpful.

Recommended Training and/or Experience

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.

Seminar Materials

Each participant will receive a seminar manual including case studies.

Seminar Goals

  • 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

Workshop Agenda

Day One

  • Chapter 1: Introduction and Overview
    • Definition
    • History
    • Structure
    • Key Concepts
  • Chapter 2: Understanding System/Software Requirements
    • Defining Requirements
    • Types of Requirements
    • Notation for Requirements
    • Requirements Elicitation
    • Breakout Exercise 1: Introduction of Case Study System Requirements (SYS.2)
    • Breakout Exercise 2: SWE Requirements (SWE.1)
  • Chapter 3: Architectural Design
    • Notation for System Architecture
    • Notation for Software Architecture
    • 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
    • Develop Software Detailed Design
    • Coding Style
    • Coding Rules
    • Breakout Exercise 4: Deriving Software Detailed Design and Unit Construction (SWE.3)
    • Breakout Exercise 5: Software Unit Verification (SWE.4)
    • Unit Testing
  • Chapter 5: Conducting Software Integration and Integration Testing, and Software Qualification Test
    • Test Case Development
    • Test Methods
    • Breakout Exercise 6: Integration Testing (SWE.5)
    • Breakout Exercise 7: Conducting Software Qualification Testing (SWE.6)

Day Three

  • Chapter 7: Developing Hardware Requirements
    • Defining HW Requirements
    • HW Design
    • Breakout Exercise 8 – Hardware Requirements Analysis
    • Test Methods
  • Chapter 8: Creating the V-Model using DFMEA and DVP&R


Search for Training

Course Keyword:


Start Date:

/ /

End Date:

/ /


Plantech-Omnex Partnership ppapandaudits