Automotive SPICE: System Requirements Analysis (SYS.2) Lecture Notes

Introduction

Presenter: Bhaskar Vanamali, Principal Assessor and Trainer for Automotive SPICE

Main Focus: System Requirements Analysis (SYS.2)

Objective: Deliver agreed results on time, within budget, and with required quality
**Risks of Not Documenting: **
- Overlooking functionalities
- Misinterpretation of customer expectations
- Additional effort, costs, and delays
- Missing essential functional or non-functional aspects leading to false starts or extra development cycles

Beyond Customer Expectations: Systems must meet standards, norms, regulations
Stakeholder Requirements: Documented stakeholder requirements mapped to internal system requirements forming basis for system testing and downstream processes
Black Box Approach: Describe what the system should do, not how
Example: ECU signals - input at connector pins and expected outputs
Requirement Structuring: Meaningful organization supporting internal distribution (attributes, ISO 26262 classification, functional structuring)
Tools: Requirements management supported by suitable tools (e.g. requirements database)

Challenge: Finding qualified systems engineers
- Requires an all-rounder with knowledge in mechanics, electronics, software
- Solution: Cross-domain team if single engineer is not feasible

Feasibility and Risk: Ensuring requirements are realistic and viable
Testability: Review by testers to ensure requirements are testable
Technical Implications: Assess dependencies and technical impacts (e.g., window regulator ECU's close and anti-pinch functions)
Business Implications: Impact of requirements on costs and timelines
Documentation: Can be split across various tools as per Automotive SPICE guidelines
- Feasibility/risk in requirements database
- Technical implications in change requests
- Cost/timeline impacts in project management tools

Traceability: Ensuring traceability between system and stakeholder requirements
- Methods: Hyperlinks, traceability tools (e.g., DOORS, Rectify), traceability matrices
- Purpose: Support consistency checks, impact assessment for changes, stakeholder expectations reporting
Consistency: Ensuring completeness and correctness of system requirements versus stakeholder requirements
- Essential to review system requirements thoroughly

Thank you for watching!