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;
47 Cards in this Set
- Front
- Back
|
What are the tasks of Enterprise Analysis? |
5.1 - Define the Business Need 5.2 - Determine the Gap in capabilities to meet the business need 5.3 - Determine the Solution Approach 5.4 - Define the Solution Scope 5.5 - Develop the Business CaseMnemonic: NGASC |
|
|
What are some typical items in a business case? (beyond BC RAMP)
|
- Context - Benefits - Time & Costs - Impacts - Miscellaneous
BABOK 5.5, Figure 5.20 |
|
|
Which stakeholders should be consulted when defining the business need (EA Task 5.1)?
|
- Customer or Supplier - Domain SME and End User - Implementation SME - Regulator - Sponsor |
|
|
Which stakeholders should be consulted when assessing capability gaps (EA Task 5.2)?
|
- Customer or Supplier - Domain SME - End User - Implementation SME - Sponsor |
|
|
Which stakeholders should be consulted when determining solution scope (EA Task 5.3)?
|
- Customer - Domain SME - End User - Supplier - Implementation SME - Sponsor |
|
|
What are some solution approach examples?
|
Use existing software or technology that are available, but unusedObtain new software by buying or leasing itDevelop custom softwareAdd staff or other resources; make organizational changesImprove business processes or proceduresOutsource or partner with an external org |
|
|
Which stakeholders should be consulted when defining solution scope (EA Task 5.4)?
|
- Domain SME - Implementation SME - Project Manager - Sponsor |
|
|
What are the components of solution scope?
|
- Scope of analysis - Capabilities supported by solution components - Capabilities in individual releases or iterations - Enabling capabilities
Figure 5.16 |
|
|
Which stakeholders should be consulted when defining business case (EA Task 5.5)?
|
- Sponsor - Domain SME - Implementation SME - Project Manager |
|
|
What are the general ways that business needs surface?
|
- Top-down (strategic goals) - Bottom-up (customers/workers) - Middle out (middle managers request change) - External (government, competition, partners) |
|
|
What are the four key considerations for determining the BA Approach (BPM Task 2.1)?
|
- Methodologies available - Needs and objectives - Standards in place - Project approach |
|
|
What are the most common approach methodologies referred to by the BABOK?
|
- Waterfall - Agile (iterative approach) - Lean (focus on value) - Six Sigma (process improvement to reduce defects/improve quality) |
|
|
What are the major aspects of the BPM Task 2.3, Plan BA Activities?
|
The major aspects of planning BA Activities include:
- Determine the BA work that must be done and what deliverables will be produced - Estimate the effort needed to perform the activities - Identify management tools to monitor the progress of activities and deliverables |
|
|
What are the two main goals of the task of “Organize Requirements” (6.2) in the Requirements Analysis knowledge area?
|
The two main goals of the task of “Organize Requirements” are:
1. decide which models are appropriate for representing solution scope 2. represent any relationships/dependences in the models |
|
|
What is the main task for analysis in Requirements Analysis?
|
The main task for analysis in Requirements Analysis is “Specify and Model Requirements” (RA Task 6.3) |
|
|
What are the features and benefits of using models to communicate requirements?
|
- Insight into opportunities for improvement - Supplies details and structure for creating solutions to business needs - Fosters communication among stakeholders - Supports training and knowledge management - Ensures compliance with contracts/regulations |
|
|
What are the three things that a BA does with “Assumptions” (RA Task 6.4) in Requirements Analysis?
|
- Identifies and documents them - Attempts to confirm their accuracy - Management requirements-related risks |
|
|
What are the typical types of constraints that might be encountered on a project?
|
- Business - Technical - External |
|
|
What are the categories of constraints that BAs should identify?
|
- Solution design - Construction - Testing - Validation - Deployment |
|
|
What will a constraint always do to a solution?
|
A constraint will always limit a solution, whether in scope, time, or cost.
|
|
|
What are the attributes of assumptions and constraints that should be captured?
|
The attributes of constraints that should be captured include:
- Date identified - Owner - Impact - Associated risk - Other explanatory information |
|
|
What is the purpose of verifying requirements (RA Task 6.5)?
|
The purpose of verifying requirements is to ensure that they are defined clearly and precisely enough so that they can be designed and developed to meet business needs. This is a quality check to confirm that requirements are:
- Ready for review by stakeholders to validate - Complete and provide all inputs needed to begin construction |
|
|
What is the purpose of validating requirements as a part of requirements analysis?
|
Validating requirements is done to make sure requirements support and implement the business requirements (as defined in the business case or as discovered in Enterprise Analysis). |
|
|
What is a key related task to validating requirements?
|
A key related task to validating requirements is Managing conflict, Task 4.1
|
|
|
What is the purpose of Task 4.2, Manage Requirements Traceability?
|
Manage Requirements Traceability is a useful way to discover and maintain relationships between important facets of requirements.
|
|
|
What are some examples of the relationships that might be traced?
|
The following types of relationships might be traced:
- Business Objectives - Dependencies or other requirements - Team deliverables, such as use and/or test cases - Solution components, such as design docs |
|
|
What are the three reasons cited in the BABOK for citing interrelationships in traceability?
|
- Impact analysis - Requirements coverage - Requirements allocation |
|
|
In order to be re-usable, requirements should be:
|
- Clearly identified and defined - Easily accessible to other analysts on other projects - Stored in a repository for shared access and maintenance |
|
|
What are the requirements of maintaining requirements for re-use (RMC Task 4.3)
|
- Improved impact analysis when new initiatives are proposed or begin - Reduced analysis on new projects by reusing previous deliverables - Enhanced support of system maintenance, training, and compliance |
|
|
What does it mean to “Prepare Requirements Package” RMC Task 4.4?
|
A requirements package is typically a formal collection of requirements documents, packaged together to be complete and to be presented to stakeholders. The intent is to “adequately communication the requirements appropriate for the intended audience.” |
|
|
What are the reasons for preparing a requirements package? |
-Provide early feedback about quality and help with planning - Present analysis of potential alternatives - Formally review and obtain approval - Pass on to the design team as inputs - Validate conformance to contractual and compliance responsibilities - Maintain requirements for re-use |
|
|
What should a requirements packages be?
|
- Understandable - Actionable - Clear - Concise - Have the appropriate level of detail - Only as complete as needed (just enough) - Tailored to the intended recipients |
|
|
Requirements must be ________ to be understood
|
Communicated BABOK states that communication must be “concise, appropriate, and effective” |
|
|
What are the types of communication that might be used to communicate requirements?
|
- Formal and informal conversations - Notes, e.g. interview and observations - Requirements package items (documents/presentations) |
|
|
What are the six tasks of the KA “Solution Assessment & Validation”?
|
They are: P - Assess Proposed Solution A - Allocation Resources R - Assess organizational Readiness T - Define Transition Requirements V - Validate Solution P - Perform Solution Evalution (Evaluate Solution Performance)
Mnemonic: PART VP |
|
|
What is the purpose of the SA Task 7.2 “Allocate Requirements”?
|
To “Allocate Requirements” means assigning of stakeholder and solution requirements to solution components, such as releases. It traces requirements through implementation. |
|
|
What is the goal of the SA Task 7.2 “Allocate Requirements”?
|
The goal of allocating requirements is to realize the maximum value in the final solution.
|
|
|
When can the task “Allocate Requirements” begin?
|
Allocating requirements may begin as soon as the solution approach is selected, and will continue until all requirements have been allocated.
|
|
|
What criteria does the BOK state may be used when allocating requirements?
|
The BOK mentions:
- Organizational units - Job functions - People - Software - Application components - Releases of a solution |
|
|
What is the purpose of the SA task “Assess Organizational Readiness” (7.3)?
|
To help determine if the organization is ready to adopt a proposed solution, an assessment of its ability to incorporate the solution should be done. |
|
|
Besides assessing organizational readiness, what other activities are included in this task?
|
- Communicate solution impacts - Specify training requirements |
|
|
What is the purpose of the SA task “Define Transition Requirements”? (7.4)
|
This task covers requirements to help transition from an existing state or solution to a new solution. |
|
|
What might be done when a new solution is replacing an old one (when “Defining Transition Requirements”)?
|
To aid in the transition process, implementation teams often develop new, temporary capabilities to aid in the transition.
|
|
|
What is the purpose of the SA task “Validate Solution”?
|
The purpose of “Validate Solution” is to validate the solution after construction or implementation, and to identify and propose appropriate responses to known defects.
|
|
|
A “post-implementation assessments” is also known as what SA Task?
|
“Evaluate Solution Performance”
|
|
|
What is the purpose of the SA Task “Evaluate Solution Performance”?
|
The purpose of the task “Evaluate Solution Performance” is to evaluate how the solution is used after implementation and assess their effect on an organization.
|
|
|
What are some reasons why a solution might be modified after deployment?
|
- Manual workarounds (solution is inflexible) - Capturing of additional data not in the solution - New, previously unknown policies regarding the solution (e.g. who can do what) |
