CMMI-DEV Requirements Development
Get Started with This SkillOverview
Draft CMMI-DEV Requirements Development (RD) deliverables: stakeholder needs, customer requirements, and product requirements for ML3.
Getting Started
Add your source materials to the project workspace, then activate the CMMI-DEV Requirements Development skill. The agent will guide you through the process step by step.
Example Conversation
You: We need to document stakeholder needs and product requirements for our new feature (single sign-on) for CMMI RD. We have rough notes from a workshop. Can you turn them into stakeholder needs, customer requirements, and product requirements with traceability?
Agent: I’ll structure the content into: stakeholder needs (who, what they need, constraints); customer requirements (derived from needs, prioritized); product and product-component requirements (allocated, with traceability). I’ll add a short operational concept and traceability matrix. I’ll load the RD reference to align with specific practices.
You: We have three stakeholder groups: end users (SSO convenience), IT (security and compliance), and support (fewer password resets).
Agent: I’ve created
stakeholder-needs.mdandproduct-requirements.md. Needs are grouped by stakeholder; customer requirements are numbered and traced back; product requirements (e.g. SAML 2.0, session handling) are traced to customer requirements. I can add validation scenarios if you want.
Sample Output Excerpt
Excerpt from Requirements Development documents produced with this skill.
Stakeholder needs (excerpt)
| ID | Stakeholder | Need | Priority |
|---|---|---|---|
| SN-01 | End users | Log in once and access all supported apps without re-entering credentials | High |
| SN-02 | IT | Enforce identity and access policies centrally; support SAML 2.0 and existing IdP | High |
| SN-03 | Support | Reduce password-reset and account-lockout tickets | Medium |
Product requirement (excerpt)
| ID | Requirement | Source (customer req) |
|---|---|---|
| PR-01 | The system shall support SAML 2.0 identity provider integration for SSO. | CR-01, CR-02 |
| PR-02 | The system shall establish a single session per user across designated applications after SSO. | CR-01 |