A business analyst (BA) working on a recently implemented project is approached by the sponsor to provide artifacts that can be used organization-wide for the long-term. Which of the following should the BA provide?
A business analyst (BA) working on a recently implemented project is approached by the sponsor to provide artifacts that can be used organization-wide for the long-term. Which of the following should the BA provide?
Process models are visual representations of workflows, activities, and interactions within business processes. They can be used across various projects and departments for continuous improvement, training, and documenting procedures. Since they provide a comprehensive view of how the organization operates, they are suitable for organization-wide and long-term use.
High-level business requirements document - Wouldn't have required Details; Transition requirements document is temporary; Project solution architecture - Shouldn't be associated to a specific Solution or technology
C - Process models
5.2.6 Process Modelling: used to identify requirements associated with the processes that may be available for reuse.
and also "business requirement: A representation of goals, objectives and outcomes that describe why a change has been initiated and how success will be assessed"pg 443. Hence it cant be A. The answer is Process Model
A process model can also be used in documenting operational procedures. At a high (enterprise or context) level, the model provides a general understanding of a process and its relationship to other processes.
Best answer is C. Process models: Process models visually represent the workflows, activities, and interactions within the business processes. They can provide valuable insights into how the organization operates and can be used for continuous improvement initiatives. This option aligns well with providing artifacts for long-term organizational use.
Yêu cầu càng high level thì càng dễ reuse
Transition requirements document seems to be appropriate. This is because they have limited reference to currently implemented project and is more applicable for future reuse. Other documents are likely to have ties to current project e.g., Process models for CRM implementation project cannot be used for a hardware optimization project limiting its reuse in future, etc.
A. 5.2.4.3 Requirements at high levels of abstraction may be written with limited reference to specific solutions. Requirements that are represented in a general manner, without direct ties to a particular tool or organizational structure, tend to be more reusable. These requirements are also less subject to revision during a change. As requirements are expressed in more detail, they become more tightly associated with a specific solution or solution option...