SpecificationsOrganizational Structure, Membership Configuration and Terms
20 acceptance test sets for MOD-MBR-STR, one per capability, holding 118 scenarios — 104 of them already bound to an existing test. A scenario names the rules and journey assertions it proves; it never restates them.
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-MBR-STR-001 | Define unit kinds and their permitted places | 8 | 5 | 6 | 8 api | Proposed |
ATS-MBR-STR-002 | Restructure units while preserving dated placement | 11 | 11 | 6 | 9 api · 2 unit | Proposed |
ATS-MBR-STR-003 | Combine units and continue their memberships | 7 | 7 | 3 | 7 api | Proposed |
ATS-MBR-STR-004 | Close units or remove units without retained dependencies | 5 | 5 | 3 | 5 api | Proposed |
ATS-MBR-STR-005 | Find units and inspect current or historical structure | 5 | 5 | 3 | 5 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-MBR-STR-006 | Maintain a unit’s identity and local details | 7 | 5 | 5 | 7 api | Proposed |
ATS-MBR-STR-007 | Describe a unit’s dated relationships with organizations | 6 | 6 | 5 | 6 api | Proposed |
ATS-MBR-STR-008 | Connect unit dues to products and settlement choices | 6 | 5 | 5 | 5 api · 1 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-MBR-STR-009 | Establish programs and their membership context | 3 | 3 | 3 | 3 api | Proposed |
ATS-MBR-STR-010 | Set a program’s affiliation requirements | 4 | 1 | 4 | 4 api | Proposed |
ATS-MBR-STR-011 | Classify memberships and configure organization flow-down | 3 | 3 | 2 | 3 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-MBR-STR-012 | Offer membership through an Accounting product | 7 | 7 | 7 | 7 api | Proposed |
ATS-MBR-STR-013 | Bundle grants and package-specific unit requirements | 5 | 3 | 4 | 5 api | Proposed |
ATS-MBR-STR-014 | Record policies for future package changes | 2 | 2 | 2 | 2 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-MBR-STR-015 | Determine a term’s start and end dates | 10 | 10 | 2 | 9 unit · 1 api | Proposed |
ATS-MBR-STR-016 | Interpret membership status and continuity by date | 9 | 9 | 1 | 9 unit | Proposed |
ATS-MBR-STR-017 | Maintain reasons for membership status actions | 2 | 0 | 2 | 2 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-MBR-STR-018 | Maintain configuration with consistent change safeguards | 8 | 8 | 8 | 8 api | Proposed |
ATS-MBR-STR-019 | Authorize structure and configuration work | 5 | 5 | 5 | 5 api | Proposed |
ATS-MBR-STR-020 | Provision, migrate and remove membership setup | 5 | 4 | 3 | 5 api | Proposed |