Requirements phase typically
comprises of the following tasks:
Gather,
Analyze & Validate Requirements
Understand
the stakeholders’ business processes and
needs using various elicitation techniques such
as storyboarding, brainstorming, prototyping,
etc.
Capture the domain vocabulary
in a glossary document to maintain consistent
semantics for communication.
Develop a high-level use
case model.
Understand user usability
requirements from the end users the system.
Explore
Architecture Approach
Identify the
critical use cases that drive architectural
and planning decisions.
Explore different candidate
architectures to determine feasibility and evaluate
trade-offs in design.
Major technical risks
such as new technologies, algorithmic complexity,
integration or performance constraints are evaluated
and prototyped, if necessary.
Exhibit, and possibly
demonstrate, at least one candidate architecture
against some of the critical scenarios.
Project
Scoping
Identify the
use cases that are tied to the BSMs and ROI.
Select the system requirements
from the available candidate requirements, using
inputs from stakeholders, BSMs and the estimates.
Check the system requirements
for correctness, consistency, feasibility and
verifiability.
Develop an initial scope
document.
Identify risks and develop
an initial risk assessment/management plan.
