• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/126

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

126 Cards in this Set

  • Front
  • Back

What are the Enterprise Analysis techniques that fall under the task of Define Business Need (5.1)?

9.2 - Benchmarking


9.3 - Brainstorming


9.4 - Business Rules Analysis


9.11 - Focus Groups


9.12 - Functional Decomposition


9.25 - Root Cause Analysis

What are the Enterprise Analysis techniques that fall under the task of Assess Capability Gaps (5.2)?

9.9 - Document Analysis


9.32 - SWOT Analysis

What are the Enterprise Analysis techniques that fall under the task of Determine Solution Approach (5.3)?

.1 - General


9.2 - Benchmarking


9.3 - Brainstorming


9.8 - DecisionAnalysis


9.10 - Estimation


9.23 - SWOT Analysis


.2 - Feasibility Analysis

What are the Enterprise Analysis techniques that fall under the task of Define Solution Scope (5.4)?

.1 - General


9.12 - Functional Decomposition


9.13 - Interface Analysis


9.27 - Scope Modeling


9.33 - User Stories


.2 - Problem or Vision Statement

What are the components of a problem statement?

- Define the problem/situation


- Who is affected by the problem?


- What is the impact?


- What are the key benefits of solving the problem



Figure 5.19

What are the Enterprise Analysis techniques that fall under the task of Define Business Case (5.5)?

9.8 - Decision Analysis


9.10 - Estimation


9.16 - Metrics and Key Performance Indicators


9.24 - Risk Analysis


9.32 - SWOT Analysis


9.34 - Vendor Assessment

What are the symbols used in a Decision Tree, and what do they represent?

Square = Decision Node


Circle = Chance Node


Triangle = End of Branch

What are the methods for making decisions using when evaluating Tradeoffs in Decision Analysis?

- Elimination of dominated alternatives (one is “worse” than the other)


- Ranking objectives on a similar scale (uses weighted ranking)

What are all of the Financial Valuation Methods that may be used in Decision Analysis?

- Discounted Cash Flow (DCF)


- Net Present Value (NPV)


- Internal Rate of Return (IRR)


- Average Rate of Return (ROR or ROI)


- Pay-back PeriodCost-Benefit Analysis (CBA)

When using the technique “Metrics and KPIs”, what are the characteristics of a good indicator?

Good indicators are:



- Clear


- Relevant


- Economical


- Adequate


- Quantifiable

What are the types of metrics used in the technique “Metrics and KPIs”?

The types of metrics are:



- Discrete Points


- Thresholds


- Ranges

In the technique “Metrics and KPIs”, what are the three structure quality factors to measure?

- Reliability (stable and consistent)


- Validity (direct measures)


- Timeliness (collection & reporting)

In reporting using the technique “Metrics and KPIs”, which are the preferred types of reports?

- Trends are more credible than a specific metric


- Visuals are more effective than raw numbers

What are the techniques used for the BPM Task 2.1, Planning the BA Approach?

9.8 - Decision Analysis


9.21 - Process Modeling


9.30 - Structured Walkthrough

What are the techniques used for the BPM Task 2.2, Conducting Stakeholder Analysis?

.1 - General


9.1 - Acceptance and Evaluation Criteria Definition


9.3 - Brainstorming


9.14 - Interviews


9.19 - Organizational Modeling


9.21 - Process Modeling


9.23 - Requirements Gathering Workshops


9.24 - Risk Analysis


9.26 - Scenarios and Use Cases


9.27 - Scope Modeling


9.31 - Survey/Questionnaire


9.33 - User Stories


.2 RACI Matrix


.3 Stakeholder Map

Of the many techniques that may be used for Stakeholder Analysis, which ones are the most common?

- RACI Matrix


- Stakeholder Map

What are the techniques used in the Elicitation task “Prepare for Elicitation” (RE Task 3.1)?

9.3 - Brainstorming


9.9 - Document Analysis


9.11 - Focus Group


9.13 - Interface Analysis


9.14 - Interviews


9.18 - Observation


9.22 - Prototyping


9.23 - Requirements Workshops


9.31 - Survey/Questionnaire

What are the techniques used in the Elicitation task “Conduct Elicitation” (RE Task 3.2)?

9.3 - Brainstorming


9.5 - Data Dictionary / Glossary


9.9 - Document Analysis


9.11 - Focus Group


9.13 - Interface Analysis


9.14 - Interviews


9.18 - Observation


9.22 - Prototyping


9.23 - Requirements Workshops


9.31 - Survey/Questionnaire

What are the techniques used in the Elicitation task “Document Elicitation Results” (RE Task 3.3)?

9.3 - Brainstorming


9.9 - Document Analysis


9.11 - Focus Group


9.13 - Interface Analysis


9.14 - Interviews


9.18 - Observation


9.20 - Problem Tracking


9.22 - Prototyping


9.23 - Requirements Workshops


9.31 - Survey/Questionnaire

What are the techniques used in the Elicitation task “Confirm Elicitation Results” (RE Task 3.4)?

9.14 - Interviews


9.18 - Observation

Problem tracking is an elicitation technique uniquely used in which elicitation task? (besides those in DIP OF RIBS)

Problem tracking is a technique used in the task “Document Elicitation Results” (Task 3.3).

Data Dictionary/Glossary is an elicitation technique uniquely used in which elicitation task? (besides those in DIP OF RIBS)
Data Dictionary/Glossary is a technique used in the task “Conduct Elicitation” (Task 3.2).
What are the only two techniques used in the RE Task 3.4, Confirm Elicitation Results?

9.14 - Interviews


9.18 - Observations

Which technique promotes “divergent” thinking?
Brainstorming (9.3) is the technique that promotes divergent thinking, producing a diverse set of options.
What role is needed in brainstorming to guide the group through the technique?
A skilled facilitator is needed to use brainstorming, in order to avoid a chaotic free-for-all.
What are the strengths of using the brainstorming technique (9.3)?

- Elicits many ideas in short period


- Encourages creative thinking


- Can reduce tension during requirements workshops

What are the weaknesses of using the brainstorming technique (9.3)?

- Dependent on participants’ creativity and engagement


- Temptation to debate idea (participants should agreed not to)

What are the strengths of the document analysis technique (9.9)?

- Good starting point for analysis


- Provides a way to cross-check other elicitation results


- Leverages existing documentation to discover/confirm requirements

What are the weaknesses of the document analysis technique (9.9)?

- Limited to “As-is” analysis


- Existing documentation may be outdated or limited


- Time-consuming and tedious

What are the broad categories of document analysis (technique 9.9)?

- Business documentation


- System documentation

What is the purpose of the technique “Focus Groups” (9.11)?

It’s used to gather qualitative data about a problem, opportunity, product, system, etc. and discover stakeholders’ attitudes and perceptions that are grouped into themes.

What are the two types of groups that may be used when doing a Focus Group?

- Homogeneous (same type of users)


- Heterogeneous (different users)

What are the strengths of Focus Groups?

- Elicit many ideas in a single session


- Learn people’s attitudes & desires


- Active discussion to explore and ask questions

What are the weaknesses of Focus Groups?

- Trust may be an issue if topics are sensitive


- Data may be inconsistent with reality


- Lack of group diversity may mean incomplete requirements


- Skilled moderator needed


- Scheduling may be difficult

What are the three types of interfaces referred to in the Interface Analysis technique (9.13)?

- User (human/system)


- Application (system-to-system)


- Hardware-to-hardware

What does the technique interface analysis (9.13) help define?

Interface analysis helps define boundaries of a system by defining the interfaces to users, other systems, or system components that provide functionality, inputs, or outputs.

User interface requirements are best elicited using which technique?

UI requirements are best elicited using prototyping (not interface analysis).

What interface elements need to be defined when performing the Interface Analysis (9.13) technique?

- Inputs/Outputs


- Validation Rules (if any)


- Triggering events

What are the strengths of the Interface Analysis technique (9.13)?

- More accurate project planning


- Better coordination w/ other systems/projects

What are the weaknesses of the Interface Analysis technique (9.13)?

It only reviews inputs/outputs, and key data elements; doesn’t provide understanding of processes or other details involved

What are the key factors that lead to successful use of the “Interviews” techniques (9.14)?

- Interviewer’s knowledge of the domain


- Interviewer’s experience conducting/documenting interviews


- Rapport of the interviewer with interviewee


- Willingness of interviewee to provide information


- Interviewee’s ability to understand their own requirements and what the business wants from the new system

What are the “types” of interviews?

- Structured - pre-defined, specific questions


- Unstructured - ad-hoc, open-ended questions

What are the types of questions that might be asked in the Interview (9.14) technique?

- Open-ended (to elaborate or probe)


- Close-ended (for single response or to confirm)

What follow-up activities should be conducted after performing an Interview (technique 9.14)?

- Send out notes


- Review notes with interviewees


- Revise notes as needed

What are the strengths of the “Interview” technique (9.14)?

- Simple, direct technique that encourages participation, builds rapport


- Allows full discussions, enabling observations of non-verbals


- Allows for follow-up questions and maintains focus


- Allows for private discussions of sensitive issues

What are the weaknesses of the “Interview” technique (9.14)?

- Not ideal for reaching consensus across wide - range of stakeholders


- Requires considerable time commitment from participants


- Training and experience required for a good interviewer


- Transcription and review of interview notes can be time-consuming


- Interviewer interpretation and possible leading of interviewees

What are the two types of the “Observation” technique (9.18)?

- Passive/invisible (observe, but do not ask questions)


- Active/visible (may ask questions)

What are the strengths of the “Observation” (9.18) technique?

- Realistic & practical insight into business processes performed


- Elicits informal details and actual practices that may not be captured in more formal sessions

What are the weaknesses of the “Observation” (9.18) technique?

- Not viable for new processes


- May be time-consuming and disruptive


- May not observe ALL needed exceptions & critical situations


- Not effective for cognitive processes/unobservable work

Which technique is used for both elicitation and analysis?
Prototyping (9.22) may be used in both elicitation and analysis).
What are the basic purposes of the Prototyping (9.22) technique?

- Scope (horizontal view of a system and it’s navigation)


- Detailed (vertical and narrow functionality and interface details)

What are the two types of Prototypes?

- Throw-away (whiteboard, sticky notes, mock-up, etc.)


- Evolutionary (functional; can be built upon to create working software)

What are the strengths of prototyping?

- Supports visual communication


- Allows for cheap, quick & early feedback


- Electronic versions enhance learning detailed interface needs

What are weaknesses of prototyping?

- Takes time if team gets bogged down in “how” and not “what”


- Throw-away versions can be too rough to convey details


- Electronic versions can mistakenly “look” like functional system


- Too much “design” can constrain development of interfaces

What are the widely varying uses of the technique “Requirements Workshop” (9.23)?

- Scope


- Discover


- Define


- Review


- Prioritize


- Reach closure

Which technique is one of the best ways to discover and define high-quality requirements quickly?
The technique “Requirements Workshops”, when they are well-run is one of the most effective.
What things is the facilitator responsible in the technique “Requirements Workshops” (9.23)?

- Establish professional and objective tone


- Enforce discipline, structure, and ground rules


- Manage meeting & keep team on track


- Facilitate decision-making/build consensus


- Ensure all stakeholders participate and their input is heard


- Ask the right questions, analyze the info provided & follow-up with probing questions

What are the strengths of the “Requirements Workshops” technique (9.23)?

Can elicit requirements quickly, with immediate feedbackGroup setting promotes collaborates and aids in consensusOften cheaper than 1x1 interviews

What are the weaknesses of the “Requirements Workshops” technique (9.23)?

- Availability of participants and scheduling can be challenging


- Success highly dependent on skill of facilitator/participant knowledge


- Having the wrong number/mix of participants can impede progress and/or cause incomplete req’s

What are the responsibilities of the scribe in a Requirements Workshop?

Document requirement in format agreed to before the workshopKeep track of “parking lot” issues

What are the types of questions that can be used in the “Survey” technique?

- Open-ended - free-form


- Closed-ended - forced choice

Closed-ended survey questions are best for what type of analysis?
Quantitative
Open-ended survey questions are best for what type of analysis?
Qualitative
What are the strengths of the “Survey” technique (9.31)?

- Effective at obtaining quantitative, and possible qualitative data


- May be helpful to reach dispersed stakeholders - Quick and inexpensive

What are the weaknesses of the “Survey” technique (9.31)?

- Open-ended questions may require more BA analysis


- May require follow-up if incomplete/inconclusive


- Not well-suited for gathering information on actual behaviors


- Response rate may be low

What is the purpose of the task “Prioritize Requirements” in the Requirements Analysis knowledge area?

The purpose of prioritizing requirements is to rank requirements relative to each other, using criteria of importance to stakeholders.

What are some possible criteria of importance to stakeholders when defining requirements priority?

Criteria of importance may include:



- Value


- Risk


- Difficulty of implementation

What are the techniques used in the “requirements prioritization” task in Requirements Analysis?

.1 - General


9.8 - Decision Analysis


9.24 - Risk Analysis


.2 - MoSCoW Analysis


.3 - Time boxing/budgeting


.4 - Voting

What do the letters in the mnemonic MoSCoW stand for?

M - Must have


S - Should have


C - Could have


W - Won’t do

What is the technique “time boxing”?
Time boxing fits work into fixed “boxes” of time, and requirements are prioritized based on the most important requirements that can be completed in that time
What is the technique “budgeting”?
Budgeting chooses work based on a fixed budget or timeline, and requirements are based upon what can be accomplished with the available resources.
What are the three general approaches for the “budgeting” prioritization technique?

- All-in - starts with all and items are dropped until can be met within time/budget


- All-out - Add in items until budget/time capacity is reached


- Selective - identify high-priority and add/remove until capacity reached

What are the techniques that may be used to “Organize Requirements” (RA Task 6.2) in Requirements Analysis?

9.4 - Business Rules Analysis


9.6 - Data Flow Diagrams


9.7 - Data Modeling


9.12 - Functional Decomposition


9.19 - Organizational Modeling


9.21 - Process Modeling


9.26 - Scenarios and Use Cases


9.27 - Scope Modeling


9.33 - User Stories

What are the techniques that may be used to “Specify & Model Requirements” (RA Task 6.3) in Requirements Analysis?

9.1 - Acceptance and Evaluation Criteria


9.4 - Business Rules Analysis


9.5 - Data Dictionary and Glossary


9.6 - Data Flow Diagrams (DFDs)


9.7 - Data Modeling


9.12 - Functional Decomposition


9.16 - Metrics & KPIs


9.17 - Non-functional Requirements Analysis


9.19 - Organizational Modeling


9.21 - Process Modeling


9.22 - Prototyping


9.26 - Scenarios and Use Cases


9.28 - Sequence Diagrams


9.29 - State Diagrams


9.33 - User Stories

What are the techniques that may be used to “Define Assumptions and Constraints” (RA Task 6.4) in Requirements Analysis?

9.20 - Problem Tracking


9.24 - Risk Analysis

What are the techniques that may be used to “Verify Requirements” (RA Task 6.5) in Requirements Analysis?

.1 - General


9.1 - Acceptance & Evaluation Criteria


9.20 - Problem Tracking


9.30 - Structured Walkthrough


.2 - Checklists

What are the benefits of using checklists during requirements verification?

- Promote standardization and quality control


- Remainders to include important items


- Consistency of approach and outcomes

What are the techniques that may be used to “Validate Requirements” (RA Task 6.6) in Requirements Analysis?

9.1 - Acceptance & Evaluation Criteria


9.16 - Metrics & KPIs


9.22 - Prototyping


9.24 - Risk Analysis


9.30 - Structured Walkthrough

What are the elements of the RA technique Business Rules Analysis?

- Specific


- Actionable


- Testable


- Atomic (can’t be broken down further)


- Independent of any one process

What are the attributes of business policies (as opposed to business rules)?

Unlike business rules, policies support goals, but are NOT actionable

What are the two types of documenting business rules?

- Text Rules


- Decision Tables/Trees

What is the purpose of the technique “Data Dictionary and Glossary”?

The “Data Dictionary and Glossary” technique is used to foster communication between the business and the project team, and is also used for supplemental data documentation. NOTE: Data dictionaries are typically refined into more detailed data models.

What is the purpose of a “Data Diagram”?

Data diagrams provide a data-centric view of a system, showing the information that is input, output, processed, and stored within a system. It is used to confirm business requirements and translate requirements for developers.

What are the two diagram types of the technique “Data Modeling”?

- Class Diagrams (UML)


- Entity Relationship Diagrams (ERDs)

What is the purpose of “Data Modeling”?

A data model is a combination of diagram and text that describes the data requirements for a solution. The chief types are ERD or Class Diagrams.

What type of documentation is typically used to supplement an ERD?

Data dictionary and/or Business Rules are often used to supplement an ERD.

What are the components of a “Class Model”?

- Classes


- Attributes


- Operations


- Relationships

What are the possible “relationships” that may be shown on a “Class Model” (data model)?

1..1 = one and only one


0..* = zero to many (* = no limit)


1..* = at least one associate, maybe more


0..1 = zero or one

For which types of stakeholders are non-functional requirements useful?

- Users or clients


- Developers

For non-software projects, non-functional types of requirements may also be referred to as what?
For non-software projects, non-functional types of requirements may also be referred to as “Service Level Agreements” (SLAs).
What are the levels that the process modeling can be done at?

- High-level (for as-is of current)


- Medium-level (to understand stakeholders and handoffs)


- Detailed Level (for a to-be view)

What is a trigger when performing process modeling?

A trigger is an event, which can be a request, action or a time that causes a process to kick-off.

What can the technique of process modeling be used for?

Process modeling can help to:



- Discover Requirements


- Document inputs/outputs


- Document the BA Approach


- Uncover Stakeholders

What are the three types of process model conventions in use?

- Flowcharting


- Activity Diagrams (using UML)


- BPMN (Business Process Modeling Notation)

Describe the purpose of the technique “Scenarios and Use Cases”

Scenarios and use cases describe how “actors” interact with a “system” to accomplish a business goal or respond to events.

What are the possible types of scenarios in a Use Case?

- Primary - shortest path


- Alternate - deviations, exceptions (may reconnect with primary path or have a separate ending)

What is the difference between a “scenario” and a “use case”?

A scenario is one part of the use case, and describes the type of path that with taken through the use case (primary or alternate)

What is the purpose of a scope model?

A Scope Model is a technique to visually depict a solution’s scope; typically shows a system, some high-level functionality, and the stakeholders who interact with it.

What does a Sequence Diagram no show?
Sequence diagrams do not show how the objects structurally relate to each other (this is done through Class Diagrams).
What is another use of sequence diagrams (beyond the primary purpose)?
Sequence diagrams can also be used to provide design-like details of how user interface or software elements should work.
How are the object names derived in a Sequence Diagram?
Object names in a Sequence Diagram are derived from the classes on the class diagram (the other type of UML diagram) that accompanies the sequence diagram
What are the two types of messages that occur in a Sequence Diagram?

- Procedural Flow


- Asynchronous Flow

What is “Procedural Flow” in a Sequence Diagram?

Procedural Flow is like an activity diagram whereby the flow is sequential and the sending object waits until a message is received

What is “Asynchronous Flow” in a Sequence Diagram?

Asynchronous Flow implies a flow that allows the sending object to continue processing as other objects are working. A sender can only receive one reply back at a time.

What is a “State Diagram”?
State Diagrams depict the various states which an entity or class flows through during its lifetime, along with the events or triggers that prompt one state to another.
What can state diagrams help discover?
State Diagrams can help discover missing data attributes and processes
What are the key components of User Stories?

- Actor


- Description


- Benefit

What are the techniques used in the Requirements Management & Communication task “Manage Solution Scope & Requirements” (4.1)?

.1 - General


9.20 - Problem Tracking


.2 - Baselining


.3 - Signoff

What is the only technique used in the Requirements Management & Communication task “Manage Requirements Traceability” (4.2)?
Coverage Matrix (aka Traceability Matrix)
When would a Coverage Matrix most likely be used?

When there are relatively few requirements to traceWhen it has been decided to trace only high-level requirements, features, or models

What are the techniques for the task of “Maintain Requirements for Reuse”?
This is a trick question. There are no specific techniques used for this task.
What are the techniques for the task of “Prepare Requirements Package”?
Requirements DocumentationRequirements for Vendor Selection
What are the types of requirements documentation that might be used to “Prepare Requirements Package”?

- Business Requirements Documents (BRD)


- Product Roadmap


- Software/System Requirements (SRS)


- Supplementary Requirements Specification


- Vision Document

What are the three types of documents that may be used for Vendor Assessment Documentation when “Preparing a Requirements Package”?

RFP - request for proposal


RFI - request for information


RFQ - request for quote

What things might be included in a vendor request?

- Business/Stakeholder Requirements


- Business strategy or architecture


- Technical environment and constraints


- Legal, regulatory, or gov. req’s


- Solution cost or total cost of ownership


- Alignment with overall biz strategy


- Solution’s architecture, performance, quality, support


- Solutions’ extensibility and ability to integration with other apps


- Supplier’s sustainability, and/or supplier’s profile and reputation

What are the techniques used for the RMC Task “Communicate Requirements”?

9.23 - Requirements Workshops


9.30 - Structured Walkthrough

What is the only “primary” technique for the knowledge area “Requirements Management and Communication”?

9.30 - Structured Walkthrough

What is the purpose of the technique “Structured Walkthrough” (9.30)?

A structured walkthrough is a formal session designed to “communicate, verify, and validate requirements”



AKA - Requirements Review

What are the techniques for the SA task “Assess Proposed Solution”?

9.1 - Acceptance & Evaluation Criteria


9.8 - Decision Analysis


9.34 - Vendor Assessment

What are the techniques for the SA task “Allocate Requirements”?

9.1 - Acceptance & Evaluation Criteria


9.4 - Business Rules Analysis


9.8 - Decision Analysis


9.12 - Functional Decomposition


9.21 - Process Modeling


9.26 - Scenarios & Use Cases

What are the techniques for the SA task “Assess Organizational Readiness”?

.1 - General


9.1 - Acceptance & Evaluation Criteria


9.6 - Data Flow Diagrams


9.11 - Focus Groups


9.14 - Interviews


9.31 - Survey/Questionnaire


9.19 - Organization Modeling


9.20 - Problem Tracking


9.21 - Process Models


9.24 - Risk Analysis


9.32 - SWOT Analysis


.2 - Force Field Analysis

What are the techniques for the SA task “Define Transition Requirements”?

9.4 - Business Rules Analysis


9.6 - Data Flow Diagrams


9.21 - Process Models


9.19 - Organizational Modeling


9.7 - Data Modeling

What are the techniques for the SA task “Validate Solution”?

9.1 - Acceptance & Evaluation Criteria


9.25 - Root cause analysis


9.20 - Problem tracking

What are the techniques used in the SA task “Evaluate Solution Performance”?

9.8 - Decision analysis


9.11 - Focus Group


9.18 - Observation


9.31 - Survey/questionnaire

What is the one primary technique used by the knowledge area Solution Assessment & Validation?
9.34 - Vendor Assessment

What are some criteria for evaluating a vendor?

- Financial security of the vendor


- Capability of maintaining certain staffing levels


- Commitment to keeping skilled staff to support the solution