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

68 lines (41 loc) • 2.12 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
# Business Use-Case Realization Specification Template ## Cover Page - ``Project Name`` - `Business Use-Case Realization Specification:`Business Use-Case Name`` - `Version`1.0`` ## Revision History | Date | Version | Description | Author | | --- | --- | --- | --- | | ``dd/mmm/yy``|``x.x``|`<details>`|`<name>` | ## Ownership & Collaboration - Document Owner: Business Process Analyst - Contributor Roles: System Analyst, Designer, Software Architect - Automation Inputs: Target business use-case specification, collaboration models - Automation Outputs: `business-use-case-realization-<id>.md` detailing sections 1–3 ## 1 Introduction > Summarize the document purpose, scope, references, and structure. Note the relationship between this markdown artifact > and any modeling tools capturing diagrams. ### 1.1 Purpose > Explain the purpose of this realization specification. ### 1.2 Scope > Describe boundaries, associated business use-case models, and impacted domains. ### 1.3 Definitions, Acronyms, and Abbreviations > Reference terminology required to interpret this specification. ### 1.4 References > List supporting documents with identifiers and sources. ### 1.5 Overview > Outline how the remainder of the document is organized. ## 2 Workflow Realization > Describe how the business use case is realized through collaborating business objects. Summarize accompanying diagrams > and explain key interactions. ## 3 Derived Requirements > Capture automation or systemic requirements not covered in the business use-case model but required for > implementation. ## Appendices (Optional) > Link to diagrams, models, or additional evidence supporting the realization. ## Agent Notes - Reference the originating business use-case ID to keep traceability intact. - Detail collaborations so downstream analysts can derive system interactions without reworking diagrams. - Verify the Automation Outputs entry is satisfied before signaling completion. - Reference the originating business use-case ID for traceability. - Describe collaborations so downstream teams can derive system interactions.