02
Requirements Engineering
Clear, traceable and testable requirements, written in language both business and engineering accept.
The problem we solve
Most rework in a software project starts before the code: ambiguous requirements, subjective acceptance criteria and scope that changes without a record. Smart7 elicits, specifies and prioritises requirements with EARS-notation criteria and traceability all the way to testing.
Reference standards
- ISO/IEC/IEEE 29148
- BABOK v3
- Notação EARS
Deliverables
- Requirements specification (SRS)
- Acceptance criteria in EARS notation
- Requirement-to-test traceability matrix
- Backlog prioritised with MoSCoW
Method
-
01
Elicitation
Interviews, workshops and analysis of existing processes.
-
02
Specification
Functional and non-functional requirements and business rules.
-
03
Validation
Stakeholder review and refinement of acceptance criteria.
-
04
Management
Change control, versioning and scope impact analysis.
Need support in Requirements Engineering?
Describe your context on WhatsApp and we will point to a path — even if it is not with us.