Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements (Requirements elicitation techniques (Observations,…
Requirements
Requirements elicitation techniques
Observations
Questionnaires
Focus groups
System interface analysis
Workshops
User interface analysis
Interviews
Document analysis
Prototyping
Storyboards
Brainstorming
BA's tasks
Communication requirements
Lead requirements validation
Document requirements
Manage requirements
Analyse requirements
Plan the requirements approach
Elicit requirements
Identify project stakeholders and user classes
Define bussiness requirements
Facilitate requirements prioritization
User classes
The features they use
The frequency
The tasks they perform
Their application domain experience
Their access privilege or security levels
The platforms they will be using
Their native language
Whether they will interact
Management
Keeping project plans current
Negotiating new commitments
Evaluating the impact of proposed requirements changes
Defining the relationships and dependencies
Defining the requirements baseline
Tracing individual requirements
Tracking requirements status
analyst role on agile projects
Apply facilitation and leadership skills
Help validate that customer needs
Help determine the best approach
Work with customers when they change their minds
Ensure that requirements documentation is at the right level
Work with the rest of the team
Define a lightweight
Characteristics of requirement statements
Prioritized
Unambiguous
Necessary
Verifiable
Correct
Complete
Feasible
Business Rules
Constraints
Action Enablers
Facts
Inferences
Computations
Characteristics of requirements collections
Traceable
Consistent
Modifiable
Complete
Expectation gap: gap between what customer needs and whats developer builds