Chip lifecycle / Automotive SPICE lifecycle / Stakeholder, System, Software & Hardware Requirements

Stakeholder, System, Software & Hardware Requirements

Turning what the customer and other stakeholders ask for into agreed stakeholder requirements, then system requirements, then software and hardware requirements, each analysed for correctness, feasibility and verifiability, each with verification criteria, and each traceable both ways to its source and consistent with it, with cybersecurity requirements where the plug-in applies.

Where this stage sits

This stage with its neighbours. Each row is a discipline active here, shaded by how mature its work is by the end of each stage.

Stage

^A05 Project Planning, Quality & Configuration Set-up

^A06 Stakeholder, System, Software & Hardware RequirementsYou are here

^O07 System, Software & Hardware Architecture

Organisation and assessment milestones

PRProcess set released

Project engineering milestones

PEPilot project evaluated PKProject process kick-off PBProject plans baselined RBRequirements baselined ABArchitecture baselined

Sponsorship and management review^A

CL0

CL1

Process definition and improvement^D

CL0

CL1

Project and risk management^A

CL1^A

Configuration, change and problem management^A

Software engineering^D

CL1^D

Hardware engineering^D

CL1^D

Verification and validation^AO

CL0

CL1

Supplier monitoring and acquisition^A

CL0^A

CL1

Cybersecurity engineering (plug-in)^A

CL1^A

Assessment and assessors^A

CL0

CL1

KeyCL0IncompleteCL1PerformedCL2ManagedCL3EstablishedCL4PredictableCL5InnovatingFaded block: Held, the status shown before it still standsFreeze or sign-off pointMilestone for one item; the rest of the work carries onMilestone gateYou are here: Stakeholder, System, Software & Hardware RequirementsAI impactDisruption (red)Augmentation (blue)Opportunity (green)How AI is changing the workWhat the steps mean What the codes mean

Show this chart as a list

Stages

Organisation and assessment milestones

Process set released (PR)

Project engineering milestones

Disciplines

Sponsorship and management review^A
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: the sponsor funds the programme, agrees the scope and target profile and steers the rollout before any project has performed the processes in scope.
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: the sponsor steers the assessed project and removes blockers while its engineering produces the outcomes the assessment will look for.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: the sponsor steers the assessed project and removes blockers while its engineering produces the outcomes the assessment will look for.
Process definition and improvement^D
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: the process office sets the target profile, then defines, pilots and releases the standard process set, tools and training that projects will be rated on.
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: the process office coaches the assessed project as it uses the tailored processes, and collects what does not work in practice.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: the process office coaches the assessed project as it uses the tailored processes, and collects what does not work in practice.
Project and risk management^A
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: the project tailors the standard process, starts on it and baselines its project, risk and supplier plans before engineering produces outcomes.
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: the project is monitored and controlled against its plans, with risks treated and every replan recorded, while the engineering work is done.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: the project is monitored and controlled against its plans, with risks treated and every replan recorded, while the engineering work is done.
Quality assurance^A
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: quality assurance plans its checks of processes and work products for the project, reporting outside the project's line of command.
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: quality assurance checks processes and work products as they are produced, reports what it finds and escalates findings that stay open.^A
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: quality assurance checks processes and work products as they are produced, reports what it finds and escalates findings that stay open.
Configuration, change and problem management^A
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: configuration management sets up the tool chain and plans configuration, change and problem tracking before the first baseline exists.
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: configuration management baselines the requirements, architecture and releases and tracks every change and problem against them.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: configuration management baselines the requirements, architecture and releases and tracks every change and problem against them.
System engineering^A
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: systems engineering elicits the stakeholder requirements, baselines the system requirements and architecture, and verifies the integrated system against them.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: systems engineering elicits the stakeholder requirements, baselines the system requirements and architecture, and verifies the integrated system against them.^D
Software engineering^D
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: software engineering analyses its requirements, baselines the software architecture, designs and builds the units and fixes what verification finds, keeping traceability true.^D
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: software engineering analyses its requirements, baselines the software architecture, designs and builds the units and fixes what verification finds, keeping traceability true.^O
Hardware engineering^D
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: hardware engineering analyses its requirements, baselines the hardware design against the agreed interfaces and verifies it.^D
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: hardware engineering analyses its requirements, baselines the hardware design against the agreed interfaces and verifies it.
Verification and validation^AO
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: verification drafts its strategy from the project plan before any requirement is baselined.
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: verification completes its strategy at the architecture baseline and records unit, integration, software and system results against each baseline.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: verification completes its strategy at the architecture baseline and records unit, integration, software and system results against each baseline.
Supplier monitoring and acquisition^A
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: supplier management names the suppliers in scope, passes the process expectations to them and agrees the supplier terms for the project.^A
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: supplier management monitors supplier deliveries against the agreements and checks them before they enter a baseline.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: supplier management monitors supplier deliveries against the agreements and checks them before they enter a baseline.
Cybersecurity engineering (plug-in)^A
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: cybersecurity derives its requirements from the risk treatment, builds them into the architecture and verifies them in integration and testing.^A
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: cybersecurity derives its requirements from the risk treatment, builds them into the architecture and verifies them in integration and testing.
Assessment and assessors^A
- Project Planning, Quality & Configuration Set-up: maturity CL0, Incomplete. Incomplete: the assessors define the assessment scope and run the gap assessment that records where each process stands today.
- Stakeholder, System, Software & Hardware Requirements: maturity CL1, Performed. Performed: the lead assessor checks readiness against the target profile and plans the formal assessment while the project produces its evidence.
- System, Software & Hardware Architecture: maturity CL1, Performed. Performed: the lead assessor checks readiness against the target profile and plans the formal assessment while the project produces its evidence.

Register or sign in to read on

The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.