aiup/aiup-core
AI Unified Process - stack-agnostic core methodology (requirements, entity model, use cases)
93
1.43x
Quality
95%
Does it follow best practices?
Impact
93%
1.43xAverage score across 10 eval scenarios
Securityby
Passed
No known issues
REFERENCE.mdskills/requirements/references/
Requirements Reference
ID Prefixes
| Prefix | Type | Example |
|---|---|---|
| FR | Functional Requirement | FR-001 |
| NFR | Non-Functional Requirement | NFR-001 |
| C | Constraint | C-001 |
Priority
| Priority | Description |
|---|---|
| High | Must have. Core functionality or critical quality. |
| Medium | Should have. Important but system works without it. |
| Low | Nice to have. Can be deferred to future releases. |
Status
| Status | Description |
|---|---|
| Open | Requirement defined but not yet implemented. |
| In Progress | Currently being implemented. |
| Implemented | Implementation complete, pending verification. |
| Verified | Tested and confirmed working. |
| Deferred | Postponed to a future release. |
| Rejected | Removed from scope. |
NFR Categories
| Category | Description |
|---|---|
| Performance | Speed, throughput, response time |
| Scalability | Ability to handle growth |
| Availability | Uptime, fault tolerance |
| Security | Authentication, authorization, encryption |
| Usability | User experience, accessibility |
| Maintainability | Code quality, documentation, modularity |
| Portability | Platform independence, deployment flexibility |
Constraint Categories
| Category | Description |
|---|---|
| Technical | Technology stack, platforms, integrations |
| Business | Budget, resources, organizational policies |
| Schedule | Deadlines, milestones, time constraints |
| Regulatory | Legal, compliance, industry standards |
| Operational | Deployment, maintenance, support requirements |