-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Description
Context
As part of the Patterns 2.0 recategorisation it was agreed to add Requirements as a new top-level category - Previously missing from the structure, now included based on SWEBOK framework and group consensus
Requirements: Defined as "Process of gathering and analyzing the needs of stakeholders. This includes an exploration of the problem space and stakeholders, as well as the translation from business requirements and high-level objectives to implementable specifications"
Actions
- Explore potential requirements patterns based on existing requirements engineering work
Metadata
Metadata
Assignees
Labels
No labels