software-glance
Software Glance
Step 2 of 5 in the Problem-Based SRS process.
Scope
| Aspect | Boundary |
|---|---|
| This skill does | Design the first abstract representation of a software solution |
| This skill does NOT | Specify Customer Needs, define Software Vision, or write Requirements |
| Input from | Step 0: Business Context (business-context skill) + Step 1: Customer Problems (customer-problems skill) |
| Output to | Step 3: Customer Needs (customer-needs skill) |
Definition
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