Chapter 3 - Elicitation
The purpose of BLANK is to validate that the stated requirements expressed by the stakeholder match the stakeholder's understanding of the problem and the stakeholder's needs.
Confirm Elicitation
What four tasks use Stakeholder Concerns as an input?
Confirm Elicitation Results (E) Define Bossiness Need (EA) Define Assumptions and Constraints (RMC) Assess Org Readiness (SAV)
Requirements (stated) is used by what tasks?
Confirm Elicitation Results (E) Define Bossiness Need (EA) Prioritize Requirements (RMC) Specify and Model Requirements (RMC) Define Transition Requirements (SAV)
defines key terms and data relevant to a business domain
Data Dictionary and Glossary
What are the disadvantages of brainstorming?
Dependent on participants' creativity and willingness to participate. Organizational ▶▶and interpersonal politics may also limit participation. Group participants must agree to avoid debating the ideas raised during
list disadvantages to prototyping
Depending on the complexity of the target system, using prototyping to elicit requirements can take considerable time if the process gets bogged down by the "how's" rather than "what's". Assumptions about the underlying technology may need to be made in order to initiate prototyping. A prototype may lead users to develop unrealistic expectations regarding the delivered system's performance, completion date, reliability and usability characteristics. This is because an elaborated, detailed prototype can look a lot like a functional system. Users may focus on the design specifications of the solution rather than the requirements that any solution must address. This can, in turn, constrain the solution design. Developers may believe that they must provide a user interface that precisely matches the prototype, even if superior technology and interface approaches exist.
BLANK is a means to elicit requirements by studying available documentation on existing and comparable solutions and identifying relevant information.
Document Analysis
BLANK is used if the objective is to gather details of existing solutions, including business rules, entities, and attributes that need to be included in a new solution or need to be updated for the current solution.
Document Analysis
A BA has been advised that financial calculations contained in the existing solution must also be contained in the new solution. In order to gain an understanding of the financial calculations referenced, what elicitation technique might be utilized?
Document Analysis - read existing system documentation
to draw forth or bring out (something latent or potential) or to call forth or draw out (as information or a response)
Elicitation
Horizontal and vertical prototypes are BLANK prototypes.
Functional or Evolutionary
This type of prototype extends the initial interface requirements into a fully functioning system and requires a specialized prototyping tool or language. This prototype produces a working software application.
Functional or Evolutionary
The purpose of this task is to ensure all needed resources are organized and scheduled for conducting the elicitation activities.
Prepare for Elicitation
What are the four tasks in the Elicitation knowledge area?
Prepare for elicitation Conduct elicitation Document elicitation Confirm elicitation results
When creating a data dictionary, what attributes should be recorded for each primitive data element?
Name Aliases Values/Meanings Description
What external input is required for the Elicitation Knowledge Area?
Org Process Assets
What does the prepare for elicitation task produce?
1. scheduled resources 2. supporting materials
What is the out put of the Document Elicitation Results task?
Requirements (Stated) and Stakeholder Concerns
When conducting elicitation, the BLANK input is used to determine what information needs to be recorded and tracked as an outcome of the activity. In particular, many requirements attributes must be elicited and captured while performing this task.
Requirements Management Plan
This type of prototype seeks to quickly uncover and clarify interface requirements using simple tools, sometimes just paper and pencil. Such a prototype is usually discarded when the final system has been developed.
Throw Away
While eliciting requirements, its important to guard against scope creep. What technique can help with this?
Tracing - Tracing requirements back to the business goals/objectives helps to validate whether a requirement should be included.
The aim of this technique is to produce numerous new ideas, and to derive from them themes for further analysis.
brainstorming
BLANK is an essential asset for all elicitation techniques to ensure all stakeholders understand key terms and business definitions
data dictionary and glossary
What are the advantages of brainstorming?
elicit many ideas quickly non-judgmental environment enables creative thinking useful to reduce tension among participants
A BLANK is a means to elicit ideas and attitudes about a specific product, service or opportunity in an interactive group environment. The participants share their impressions, preferences and needs, guided by a moderator.
focus group
This type of prototype models a shallow, and possibly wide view of the system's functionality. It typically does not have any business logic running behind the visualization.
horizontal prototype
This technique is appropriate when documenting details about current processes or if the project is intended to enhance or change a current process.
observation
When conducting elicitation, the BA should be sure to capture:
tracing requirements requirement attributes metrics (for future planning)
This type of prototype models a deep, and usually narrow slice of the entire system's functionality.
vertical
What inputs from the BA Planning and Monitoring Knowledge Area are required for the Elicitation Knowledge area?
BA Plan (s) Stakeholder Lists Roles and Responsibilities Requ Management Plan
What inputs from the Enterprise Analysis Knowledge Area are required for the Elicitation Knowledge area?
Business Case Business Need Solution Scope
When preparing for elicitation, what input assist the BA in eliciting business requirements?
Business Need
When preparing for elicitation activates, what inputs ensure that the business analyst understands what information should be elicited from the stakeholders in regards to stakeholder, solution, and transition requirements.
Business Need Solution Scope
List at least three commonly used elicitation techniques.
Interviews Brainstorming Document Analysis Focus Groups Surveys Interface Analysis Observation (job shadowing) prototyping Requirements workshops
When preparing for elicitation, what input assist the BA in eliciting transition, solution and stakeholder requirements?
Solution Scope and Business Case
When preparing for elicitation, what does the BA use to identify stakeholders who should participate?
Stakeholder List, Roles and Responsibilities
Requirements in this state describe the stakeholder's need from the stakeholder's perspective.
Stated
What state are requirements used as a input to the Confirm Elicitation task in?
Stated, Unconfirmed
A BLANK portrays the navigation paths across the interface components. This visual includes abstractions of each screen along with directional arrows that indicate the allowable navigation flows.
Storyboard
list advantages of prototyping
Supports users who are more comfortable and effective at articulating their needs by using pictures, as prototyping lets them "see" the future system's interface. A prototype allows for early user interaction and feedback throw-away prototype can be an inexpensive means to quickly uncover and confirm a variety of requirements that go beyond just the interface such as processes, data, business rules. A vertical prototype can demonstrate what is feasible with existing technology, and where there may be technology gaps. An evolutionary / functional prototype provides a vehicle for designers and developers to learn about the users' interface needs and to evolve system requirements.
