Architecture-First Functional and Non-Functional Requirements
tonymarius.substack.com
Overview Requirements are important. Without requirements a project team doesn't know what to build. It is necessary to help the project team determine how to create the desired application. Requirements always exist, but they are in the mind of the stakeholders. The challenge is to extract those requirements. They are difficult to discover. Some users only know their part of the application and from their point of view. The requirements gathered from them may describe what they are doing now, but not what they need.
Architecture-First Functional and Non-Functional Requirements
Architecture-First Functional and…
Architecture-First Functional and Non-Functional Requirements
Overview Requirements are important. Without requirements a project team doesn't know what to build. It is necessary to help the project team determine how to create the desired application. Requirements always exist, but they are in the mind of the stakeholders. The challenge is to extract those requirements. They are difficult to discover. Some users only know their part of the application and from their point of view. The requirements gathered from them may describe what they are doing now, but not what they need.