Elicitation and Gathering Flashcards
Agile processes has worked well for _____ projects
SMALL
We will always need experienced _____ requirements analyst for large projects because of the limited availability of knowledgeable users
subject matter experts (SME)
2 levels of requirements elicitation
HIgh level, low level
The requirements analyst must probe and understand the business rationale and justification for the software or the software project
High Level
The requirements analyst must elicit and gather the details of the users’ needs and desires
Low Level
The actual elicitation may be conducted in several modes:
Verbal, Written, Online
_____ is highly recommended for users to expand on their input
Verbal follow up
Throughout all the elicitation and gathering process, the requirements analyst must possess the following vital skills:
be patient, listen carefully, ask for more information when needed
The requirements analyst should also gather existing information that is available in the following documents:
business process document, business and technical policy document, previous system manual
Information that contributes to this high-level business profile includes:
Opportunity/needs, justification, scope, major constraint, major functionality, success factor, user characteristics
(High level) State what high-level problems the software suppliers have been brought in to address
Opportunity/needs
(High level) The company may be losing 50% of customer orders due to poorly managed documents
Opportunity/needs
(High level) Some type of business payback
Justification
(High level) The customer may state that there is P2M of extra inventory
Justification
(High level) Establish the limits and scope of the project
Scope
(High level) The above-mentioned inventory and customer orders are the two top problems that need to be solved ASAP, such that these become areas of MAJOR requirements
Scope
(High level) The allotted budget for the software project.:
Information on budget constraints is important when detailed requirements are being prioritized
Major Constraint
(High level) Vital to have a list of what the customer and the business executives perceive as the major functionality the new software will be delivered
Major Functionality
(High level) goes back to the opportunity and needs stated earlier
Success Factor
(High level) Success of the system depends heavily on how well the users are trained
User Characteristics
(High level)
- person’s job title and formal responsibilities,
- job activities,
- education and experience levels and
- technical competence
User Characteristics
During this activity, some of the more technically savvy requirements analysts should be brought in
Low Level
Low level requirements:
Individual Functionality, Business flow, Data and data formats, User Interfaces, Systems with other interface, (Reliability, Performance, Security, and Adaptability)
(low level) Most obvious group and usually the natural starting point of requirements elicitation
Individual Functionality
