In this business analysis training, you will learn Zachman Analysis. Topics covered in this session are:
• Introduction to OOA and UML
• Stated vs Un-stated
• Software Analysis and Design
• Modeling
• UML
• Why UML
• Overview
• Types
• Use Case Diagram
For more information, visit this link: https://www.mindsmapped.com/courses/business-analysis/business-analyst-training-for-beginners/
4. Page 3Classification: Restricted
A simple framework that is used for planning or analyzing what an organization
does. It is useful for BA’s, especially those in a consultancy role, to help ensure you
are asking the right questions and to provide a logical connection between the
high-level mission of the business and the everyday activities being carried out.
Mission: This is the organization's purpose for operating. It will usually outline
some form of key measurement.
Objectives: These are specific goals that the organization needs to meet in order
to fulfil the mission.
Strategy: This is the overall plan for how the organization will achieve the
objectives.
Tactics: This offers a greater level of detail and is concerned with the actions
required to execute the strategy.
What is a MOST analysis? Cont’d…
17. Page 16Classification: Restricted
Architectural Frameworks
• A variety of frameworks, tools and techniques are employed to create and
maintain the Business Architecture
• The value of a framework is that it provides compartments in which to
place predefined architectural products or outputs, thus providing order
and structure to the components
• Examples of architectural frameworks include the following
The Zachman Framework
It is helpful to use a defined framework that provides a common structure
and classification scheme for descriptive representations of an enterprise.
One such framework that has been widely adopted by organizations both
public and private is the Zachman Framework for Enterprise Architecture
developed by John Zachman.
21. Page 20Classification: Restricted
POLDAT
The framework provides common language and common structure for describing an
enterprise. Without a unifying framework, the fundamental design of an organization
may not result in an integrated, well functioning enterprise, which leads to
redundancies, inefficiencies and integration issues. The Zachman Framework is both
complex and comprehensive, and is presented in a matrix format, where: The columns
represent the questions that must be answered to design a business entity:
• What (data and entities)
• How (process or function)
• Where (location and network)
• Who (people)
• When (time)
• Why (motivation)
Whereas, the rows of the framework describe the different perspectives of the enterprise:
• Scope
• Business Model
• System Model
• Technology Model
• Detailed Representations
22. Page 21Classification: Restricted
The POLDAT Framework
Another, simpler structure that is often used in business process re-engineering projects is
the POLDAT framework. This model develops documents, tables, matrices, graphs, models
and organizes them in the following categories:
Process – the business processes that flow value from the organization to the customer.
Organization – the organizational entities that operate the business processes, including
the management teams, staff positions, roles, competencies, knowledge and skills.
Location – the location of the business units and other organizational entities, e.g., call
centers, distribution centers, etc.
Data – the data and information that is the “currency” of the organization, flowing through
the processes to accomplish the business functions.
Applications – the information technology (IT) applications that enable the business
processes to operate efficiently and provide decision-support information to the
management team.
Technology – the enabling technology that supports the operation of the processes and
applications.
25. Page 24Classification: Restricted
What is a Problem Statement
• A problem statement is a clear concise description of the
issue(s) that need(s) to be addressed by a problem solving
team. It is used to center and focus the team at the beginning,
keep the team on track during the effort, and is used to
validate that the effort delivered an outcome that solves the
problem statement.
26. Page 25Classification: Restricted
Questions a Problem Statement Should Answer
1.What is the problem?
This should explain why the team is needed.
2.Who has the problem or who is the client/customer?
This should explain who needs the solution and who will
decide the problem has been solved.
3.What form can the resolution be?
What is the scope and limitations (in time, money,
resources, technologies) that can be used to solve the
problem?
31. Page 30Classification: Restricted
• Root cause analysis (RCA) is a method of problem solving used for
identifying the root causes of faults or problems.
• The Root Cause Analysis process is also known as the “Ishikawa
Diagram” or “Fishbone Diagram.”
