customer-needs
Customer Needs (CN)
Step 3 of 5 in Problem-Based SRS methodology
Previous: Customer Problems → Software Glance
Next: Software Vision
Required Inputs
Before running this skill, ensure you have:
- Customer Problems (CPs) — from customer-problems skill
- Software Glance — early rough idea of the software solution (provides boundaries)
Definition
Customer Needs describe the outcomes a software system must deliver to solve (or help solve) the customer's problems — not how the system works internally.
More from rafaelgorski/problem-based-srs
problem-based-srs
Complete Problem-Based Software Requirements Specification methodology following Gorski & Stadzisz research. Use when you need to perform requirements engineering from business problems to functional requirements with full traceability.
20zigzag-validator
Validate traceability and consistency across Customer Problems, Customer Needs, and Functional Requirements domains. Use to check completeness, identify gaps, and ensure all requirements trace to real business problems.
4software-vision
Transform Software Glance and Customer Needs into a detailed Software Vision with positioning, stakeholders, features, and architecture. Use after Customer Needs. Step 4 of Problem-Based SRS methodology.
4business-context
Establish structured business context and project principles before problem discovery. Use as Step 0 of Problem-Based SRS to capture project identity, business principles, stakeholders, domain boundaries, and success criteria that feed into Customer Problems identification.
4functional-requirements
Generate Functional Requirements (FR) and Non-Functional Requirements (NFR) from Customer Needs and Software Vision. Creates individual requirement files with traceability. Step 5 of Problem-Based SRS methodology.
4customer-problems
Identify and document Customer Problems (CP) from business context. Use when starting requirements engineering or when stakeholders describe solutions instead of problems. Step 1 of Problem-Based SRS methodology.
4