A bank moves currency from the mam office to the tranches daily for operational use. To avoid paying overnight interest, the branch** return the currency at the end of the business day. The Bank requires a new inventory management system to account for the whereabouts of the cash at all times A software provider has proposed a heavily customized version of their standard inventory management software. As the project progresses, the business analyst (BA) identifies a number of subtleties that would suggest a fully made to order solution may be a better option for the bank. What inputs does the BA need to perform the analysis?
The BA needs to compare the value and costs of different design options, such as a customized version of the existing software or a fully made to order solution. The potential value is the benefit that the solution will provide to the bank, such as improved efficiency, accuracy, and security. The design options are the alternative ways of meeting the needs and requirements of the bank, such as modifying the existing software or developing a new one. The BA needs to evaluate the trade-offs between the value and costs of each option and recommend the most feasible and desirable one.Reference:
CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Strategy Analysis, page 217
Business Analysis Body of Knowledge (BABOK ) Guide, Version 3, Section 6.4: Define Design Options, pages 142-144
Certified Business Analysis Professional (CBAP) | Coursera, Course 3: Strategy Analysis, Week 3: Define Design Options
You are the business analyst for your organization and you are completing the manage requirements traceability process. You are tracking the requirements to determine how the requirements are interrelated with one another and with the actual delivery of the project scope.
There are actually three reasons why the business analyst should trace requirements.
Which one of the following is not one of the three reasons why trace requirements is useful?
Quality control is not one of the reasons why trace requirements is useful, but a process that monitors and measures the quality of the project deliverables and outputs against the quality standards and criteria established in the quality management plan. Quality control is used to make certain that the project team members are completing the project work according to the project plan and meeting the stakeholder expectations.Quality control involves performing quality audits, inspections, tests, reviews, and validations to identify and correct any defects, errors, or deviations from the specifications1.
The other three options are valid reasons why trace requirements is useful. Trace requirements is a technique that involves establishing and documenting the relationships between requirements and other aspects of the product management process, such as design elements, test cases, releases, and incidents.Trace requirements is useful for the following purposes234:
Impact analysis: Trace requirements helps to evaluate the impact of a potential change or a problem on the requirements and the solution. By tracing the dependencies and links between requirements and other items, the business analyst can quickly and easily assess the scope, cost, time, and risk implications of the change or the problem, and plan the appropriate response actions.
Requirements coverage: Trace requirements helps to ensure that all the requirements are fulfilled by the solution and that all the solution components contribute to the requirements. By tracing the alignment and mapping between requirements and solution components, the business analyst can verify that the solution meets the stakeholder needs and expectations, and that there are no gaps or redundancies in the solution.
Requirements allocation: Trace requirements helps to assign requirements to solution components and to releases.By tracing the distribution and allocation of requirements to different parts of the solution and to different phases of the project, the business analyst can prioritize and schedule the requirements based on their value, risk, dependency, and complexity, and ensure that the solution is delivered incrementally and iteratively.Reference:1: Project Quality Management: Processes & Tools | Villanova University52: Requirements Traceability - The What, Why and How | Netmind63: Requirements traceability -- why and how to do it?74: Requirements traceability : What, why and how - Modern Analyst8
You are the business analyst for a smaller project where there are few requirements. Management would still like you to create a method to trace the few requirements for this project.
What type of matrix would be best in this instance?
A requirements trace matrix (RTM) is a tool that helps to ensure that the project's scope, requirements, and deliverables remain consistent and aligned throughout the project lifecycle. It traces the requirements from their origin to their fulfillment by linking them to other project artifacts, such as design documents, test cases, and solution components. An RTM can also be used to verify that all requirements are met and to identify changes to the scope when they occur. An RTM is especially useful for smaller projects where there are few requirements, as it can help to track the progress and status of each requirement and avoid scope creep. A requirements trace matrix is not the same as a roles and responsibility matrix (A), a RACI matrix (B), or a coverage matrix , which are different types of matrices that serve different purposes in project management.Reference:
IIBA BABOK Guide v3, p. 30, 176, 264
Requirements Traceability Matrix -- RTM - Project-Management.com
CBAP/CCBA/ECBA Certification Practice Test | MindsMapped, Question 6
Wanda is the business analyst for her organization and she is currently working on the specify and model requirements process. One of the elements of this process is the documentation of the textual requirements.
Wanda must describe the capabilities of the solution, any conditions that must exist for the requirements to operate, and what third component of the textual requirement?
According to the BABOK Guide, textual requirements are one of the forms of specifying and modeling requirements. Textual requirements are written statements that describe the characteristics of the solution in a clear, concise, and consistent manner. Textual requirements typically consist of three components: the capability of the solution, the condition under which the requirement is applicable, and the constraint that may limit the solution. The capability describes what the solution must or should do, the condition describes the situation or scenario in which the requirement is relevant, and the constraint describes the restriction or limitation that may affect the solution's ability to meet the requirement. For example, a textual requirement for a banking system could be:
The system shall allow customers to withdraw cash from any ATM machine (capability) within the network (condition) up to a maximum of $500 per day (constraint).
[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.2.11
Textual Requirement Artifacts - Blueprint Online Help - HelpDocs, paragraph 1
How to Model Textual Requirements - Formal Mind GmbH, paragraph 2
You are the business analyst for a large project that will create new software for the entire organization. This new software will affect all of the administrative assistants in the organization schedule meetings, reserve facilities, and share calendars. There are approximately 2,400 administrative assistants in your organization and not all of these people can attend requirements gathering workshops.
What approach can you use to manage and gather requirements from these 2,400 administrative assistants?
When the number of stakeholders is too large or dispersed to involve them all in the requirements elicitation process, one possible approach is to use representatives or proxies. These are stakeholders who can act on behalf of a larger group of stakeholders and provide their input, feedback, and approval for the requirements. The representatives should be selected based on their knowledge, experience, authority, and availability. They should also communicate regularly with the group they represent and ensure that their views and needs are accurately reflected. Meeting with a small group of administrative assistants that will serve as representatives for the remaining administrative assistants can help to manage and gather requirements from these 2,400 administrative assistants in an efficient and effective way.Reference:BABOK Guide v3, page 51;CBAP / CCBA Certified Business Analysis Study Guide, page 159.
Giulia Romano
6 days agoEmily Baker
1 month agoRachel Clark
2 months agoRichard Hill
2 months agoDonna Brown
3 months agoIbrahim Ahmed
3 months agoMark Walker
4 months agoErik Kristiansen
4 months agoCharles Flores
5 months agoJason Bell
6 months agoKaren Nguyen
6 months agoBarbara Rogers
6 months agoCynthia Young
6 months agoStephen Wilson
6 months agoNancy Roberts
6 months agoBarbara Murphy
6 months agoJoana
7 months agoYolande
7 months agoMarshall
7 months agoRia
8 months agoMartina
8 months agoAhmed
8 months agoJolanda
8 months agoBritt
9 months agoParis
9 months agoBernadine
9 months agoEmmett
9 months agoCatherin
9 months agoBen
10 months agoAlva
10 months agoJunita
10 months agoJerry
10 months agoEugene
11 months agoWava
11 months agoNatalya
11 months agoBeckie
11 months agoLuke
12 months agoFreeman
1 year agoMargret
1 year agoWillard
1 year agoEstrella
1 year agoJestine
1 year agoAshley
1 year agoVal
1 year agoVerdell
1 year agoAlline
1 year agoLindsay
2 years agoLenita
2 years agoThora
2 years agoMarget
2 years agoHollis
2 years agoGlen
2 years agoMattie
2 years agoLuther
2 years agoWillis
2 years agoMarguerita
2 years agoVesta
2 years agoLucy
2 years agoRoosevelt
2 years agoPaola
2 years agoJenise
2 years agoPatria
2 years agoTalia
2 years agoNieves
2 years agoShoshana
2 years agoThurman
2 years agoIsadora
2 years agoBambi
2 years agoPhillip
2 years agoVinnie
2 years agoRolande
2 years ago