Use Case Template

Purpose: Template for documenting GenAI use cases in the COVESA GenAI Working Group
Version: 2.0 Proposal
Last Updated: November 5, 2025

Open

🔹 Quadrant 1 — Overview & Challenges

Purpose: contextualize why this use case exists and what pain point it solves.

🔹 Quadrant 2 — Approach & Architecture

Purpose: describe how the solution addresses the challenge.

🔹 Quadrant 3 — Execution & Status (Roadmap)

Purpose: capture timeline, dependencies, and progress milestones.

🔹 Quadrant 4 — Outcomes & Scorecard

Purpose: show results and measurable value.

Use Case: [UC-XXX] [Use Case Title]

Status: Proposed / In Progress / Implemented
Last Updated: [Date]
Author/Owner: [Name/Team]

Classification

Process Area Legend

V-Model Stages:

• REQ - Requirements Management

• ARC - Architecture & System Design

• DES - Detailed Design

• IMP - Implementation

• TST - Testing & Validation

• INT - Integration

• VEH - Vehicle Validation & Homologation

Supporting Processes:

• PM - Project Management

• CFG - Configuration Management

• QA - Quality Assurance

• SUP - Supplier Management

• RIM - Risk Management

• DOC - Documentation & Knowledge Mgmt

Description

Objective: [One-sentence summary of what the use case accomplishes]

[Paragraph describing the use case in detail. What problem does it solve? Why does it matter?]

Business Value

• [Key benefit 1]

• [Key benefit 2]

• [Key benefit 3]

Actors & Stakeholders

Primary Actor

[Who initiates this use case? Role and organization, usually from the "home" Process Area team]

Supporting Actors

Stakeholders Affected

• [Stakeholder 1]

• [Stakeholder 2]

Preconditions

What must be true before this use case can execute:

1. [Precondition 1]

2. [Precondition 2]

3. [Precondition 3]

Trigger

What initiates this use case:

• [Trigger event]

Main Flow

Step-by-step description of how the use case works:

1. [Actor] performs [action]

2. [GenAI] retrieves [artifact] from [tool] via MCP

3. [GenAI] analyzes [what is analyzed]

4. [GenAI] generates [output]

5. [Actor] reviews and [next action]

Alternative Flows

Alternative Flow 1: [Scenario Name]

[Description of alternative path]

Cross-Boundary Impacts

If this use case affects other Process Areas, describe:

Upstream Impact (Previous Process Areas)

• Affected Areas: [Process areas]

• What Changes: [What gets affected in earlier stages]

• Actions Needed: [Who needs to do what]

Downstream Impact (Later Process Areas)

• Affected Areas: [Process areas]

• What Changes: [What gets affected in later stages]

• Actions Needed: [Who needs to do what]

Organizational Impact

• Other Process Area Owners Affected: [Who]

• Communication Needed: [What needs to be communicated]

• Dependencies: [What they depend on, what depends on them]

Example

"This UC is homed in REQ (Requirements Management), but when a requirement conflicts with architecture, it triggers upstream conversations with ARC team. Changes also flow downstream to DES (Detailed Design) and IMP (Implementation)."

GenAI Capabilities Required

MCP/A2A Services Needed

From Requirements Tool:

• requirement.get() - Retrieve requirement by ID

• requirement.search() - Search requirements

• requirement.get_relations() - Get relationships

From [Tool Category]:

• service.method() - Description

From [Tool Category]:

• service.method() - Description

AI/LLM Capabilities Needed

Constraints & Limitations

• [Constraint 1]

• [Constraint 2]

Expected Outcomes

Success Criteria

1. [Measurable outcome 1]

2. [Measurable outcome 2]

3. [Measurable outcome 3]

Deliverables

• [Deliverable 1] (format, location)

• [Deliverable 2] (format, location)

Quality Metrics

• [Metric 1]: [Target value]

• [Metric 2]: [Target value]

Related Use Cases

Tool Integration Points

Tool Categories Involved

Supplier/Vendor Notes

• Primary Owner (Home Process Area): [Organization/Team that owns this UC]

• Supporting Organizations (Cross-Boundary): [Other orgs/teams involved]

• Vendor name: [Relevant notes about their tool, API availability, MCP support status, etc.]

•  

Implementation Notes

Reference Implementation

• Status: Not started / In progress / Available

• Location: [GitHub repo / Confluence page / Other]

• Language: Python / JavaScript / Other

• Maintainer: [Name/Team]

Technical Considerations

• [Technical note 1]

• [Technical note 2]

• [Technical note 3]

Known Limitations

• [Limitation 1]

• [Limitation 2]

Example / Walkthrough

[Detailed walkthrough showing how the use case works with real example data]

Example Input

Example Processing

Example Output

Metrics & Success Measurement

Adoption Metrics

• Target adoption: [%] within [timeframe]

• Target tool vendors with MCP support: [number]

Efficiency Metrics

• Time reduction: [baseline] → [target]

• Cost reduction: [baseline] → [target]

• Quality improvement: [baseline] → [target]

Quality Metrics

• Accuracy: [target %]

• Completeness: [target %]

• False positive rate: [target %]

Risks & Mitigation

Dependencies

External Dependencies

• [Dependency 1]

• [Dependency 2]

Tool Dependencies

• [Tool 1] with [feature/capability]

• [Tool 2] with [feature/capability]

Organizational Dependencies

• [Dependency 1]

• [Dependency 2]

Timeline & Roadmap

Questions & Discussion

Open Questions:

• [Question 1]

• [Question 2]

For Discussion:

• [Topic 1]

• [Topic 2]

Appendix

References

• [Link to related documentation]

• [Link to standard]

• [Link to tool documentation]

Glossary

Related Standards

Document History

Sign-Off / Approval