ASPICE
======

The **ASPICE** family brings Automotive SPICE (ASPICE) process compliance to
GitHub Copilot. It covers the full software development lifecycle as defined
by ASPICE SWE.1–SWE.6: from software requirements through architecture,
detailed design, unit testing, integration, and qualification.

.. code-block:: bash

   ubflow-installer install aspice <target-path>


Who is this for?
----------------

Engineering teams in regulated industries — automotive, aerospace, medical
devices — that must demonstrate process compliance (ASPICE, ISO 26262, IEC 62304)
and need GitHub Copilot to generate traceable, auditable work products rather
than ad-hoc code.


The Workflow
------------

.. mermaid::

   flowchart LR
      user(Engineer)
      orch(Orchestrator)
      swe1(SWE.1 Requirements)
      swe2(SWE.2 Architecture)
      swe3(SWE.3 Detailed Design)
      swe4(SWE.4 Unit Test)
      swe5(SWE.5 Integration Test)

      user -- change request --> orch
      orch --> swe1 --> swe2 --> swe3
      swe3 --> swe4
      swe2 --> swe5


Agents at a Glance
------------------

.. list-table::
   :header-rows: 1
   :widths: 25 75

   * - Agent
     - What it does
   * - **Orchestrator**
     - Single entry point for all ASPICE workflows. Accepts a change
       request, determines the scope, and coordinates the specialist agents
       in the correct process order.
   * - **SWE.1 — Requirements**
     - Authors and refines software requirements. Ensures requirements are
       atomic, verifiable, and linked to system-level inputs.
   * - **SWE.2 — Architecture**
     - Derives the software architecture from requirements. Produces
       component diagrams and architecture decisions traceable to SWE.1.
   * - **SWE.3 — Detailed Design**
     - Generates detailed design documents and implementation code for each
       component, linked to the architecture.
   * - **SWE.4 — Unit Test**
     - Creates unit test specifications and test code derived directly from
       the detailed design and requirements.
   * - **SWE.5 — Integration Test**
     - Authors integration test cases that verify component interactions
       against the software architecture.


Good to know
------------

- **Status:** ``draft`` — the orchestrator is under active development;
  specialist agents are planned.
- **Compliance focus:** Every work product is linked back to its source
  requirement via Sphinx-Needs. The traceability matrix is generated
  automatically.
- **Scope:** ASPICE SWE process areas. System-level processes (SYS) and
  supporting processes (SUP, MAN) are planned for a future release.
- **Starting simple?** See the :doc:`Agile family <agile>` first — it
  introduces the ubFlow concepts with less process overhead.