Scope modelling describes scope of analysis or scope of a solution. They serve as a basis for defining and limiting scope of business analysis and project work.
Scope models show:
While considering scope of change and context, determine:
·Business processes, functions, capabilities to be defined or modified.
·Use cases to be supported.
·Technologies to be changed.
·Organizational roles and units impacted.
·Events to be responded to and impacted.
·Systems, tools, assets required for change or impacted by change.
In order to ensure completeness and integrity of scope models, identify relationships between potential scope elements.
Scope Modeling Technique #1 Hierarchical decomposition.
Functional decomposition is a technique used to break down a complex system into smaller, more manageable parts. By breaking the system down into smaller pieces, it is easier to understand how the system works and identify potential areas of improvement. Additionally, functional decomposition can be used to create detailed plans for designing, developing, and testing complex systems.
Functional decomposition can be used to indicate which functionalities are in scope of the solution and which are outside the solution scope.
Scope Modeling Technique #2 Use Case Diagram
A use case diagram is a graphical representation of the steps that need to be taken in order to complete a process. It is typically used in software development to map out the functionality of a system. Use case diagrams can be very helpful in understanding the requirements of a system. They can also be used to identify potential areas for improvement. By clearly mapping out the steps involved in a process, use case diagrams can help to improve efficiency and optimize performance.
When creating a use case diagram, it is important to consider the different actors that will be involved in the process. Each actor should have their own individual goals and objectives. The use case diagram should also include a description of the interactions between each actor. Whatever exists inside the System Boundary is considered as In-scope.
Recommended by LinkedIn
Scope Modeling Technique #3 Process Model
A process model is a graphical representation of a business process. It is used to document, visualize, and analyze the steps in a business process. A process model can be used to improve the efficiency of a business process by identifying bottlenecks and opportunities for improvement. One can indicate which part of the project is in scope and which part will remain out of the scope.
A process model can be created using different notation systems, such as the Business Process Modeling Notation (BPMN) or the Unified Modeling Language (UML). In addition, a variety of software tools can be used to create process models, such as Microsoft Visio or BizAgi BPM.
Scope Modeling Technique #4 3-Box Diagram
A 3-box diagram is a very simple technique. It is a table with 3 columns: In-Scope, Out-of-scope and Doubtful-scope.
Scope Modeling Technique #5 Pareto Diagram
Pareto diagrams are a type of process model that is used to identify the most important factors in a process. Pareto diagrams are based on the principle of 80/20, which states that 80% of the effects come from 20% of the causes. Pareto diagrams are often used in quality improvement initiatives, such as Six Sigma or Lean. The purpose of a Pareto diagram is to help identify the most important factors in a process so that resources can be focused on those factors.
Using the Pareto diagram, one can find key causes of the problem and keep them as part of the scope.
Usefulness of Scope Modeling
Limitations of scope modeling
About Adaptive US
Adaptive US is world's Go to Provider of IIBA Certifications Training (CBAP, CCBA, ECBA, CBDA, AAC, CPOA, and CCA) and Study Aids. Get 100% Success or 100% Refund guarantee for all IIBA certifications Training. Adaptive US provided business analyst training, templates, tools for it’s clients throughout the world.
