UNPKG

aiwg

Version:

Cognitive architecture for AI-augmented software development with structured memory, ensemble validation, and closed-loop correction. FAIR-aligned artifacts, 84% cost reduction via human-in-the-loop, standards adopted by 100+ organizations.

aiwg.io

jmagly/aiwg

73 lines (43 loc) • 2.26 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
# Software Requirements Specification (Use-Case Driven) Template ## Cover Page - ``Project Name`` - `Software Requirements Specification for`Subsystem or Feature`` - `Version`1.0`` ## Revision History | Date | Version | Description | Author | | --- | --- | --- | --- | | ``dd/mmm/yy``|``x.x``|`<details>`|`<name>` | ## Ownership & Collaboration - Document Owner: System Analyst - Contributor Roles: Software Architect, Test Architect, Requirements Reviewer - Automation Inputs: Use-case model survey, supplementary requirements - Automation Outputs: `software-requirements-specification.md` referencing use-case packages ## 1 Introduction > Outline the purpose, scope, terminology, references, and organization of this SRS. ### 1.1 Purpose ### 1.2 Scope ### 1.3 Definitions, Acronyms, and Abbreviations ### 1.4 References ### 1.5 Overview ## 2 Overall Description > Provide background information and assumptions for the subsystem or feature being specified. ### 2.1 Use-Case Model Survey > Summarize the relevant portion of the use-case model (actors, use-case list, diagrams). Reference external surveys or > reports when available. ### 2.2 Assumptions and Dependencies > Document technical, organizational, or scheduling assumptions and dependencies that influence these requirements. ## 3 Specific Requirements > Capture detailed requirements using referenced use-case reports and supplementary specifications. ### 3.1 Use-Case Reports > Link or embed the detailed use-case specifications responsible for functional behavior. ### 3.2 Supplementary Requirements > Include non-functional and cross-cutting requirements leveraging the Supplementary Specification for this subsystem or > feature. ## 4 Supporting Information > Provide appendices, traceability matrices, UI prototypes, or other materials that assist in applying this SRS. Clarify > whether appendices are normative. ## Agent Notes - Ensure every referenced use-case report exists and is tagged with the same identifier. - Document assumptions and dependencies in Section 2.2 for planning alignment. - Verify the Automation Outputs entry is satisfied before signaling completion. - Ensure every referenced use-case report exists and shares consistent identifiers.