Professional Documents
Culture Documents
being analyzed
Goal and business objectives Organizing and reflecting goals, business problems, business objectives, success
model metrics, and high-level features.
Business objectives are mapped to the requirements, scope control becomes much
easier
Ecosystem map Shows all the relevant systems, the relationships between them, and optionally, any
data objects passed between them.
This ecosystem map contains all of the systems, including external systems that
transfer data. Although some of the systems do not directly interact with the solution
Used to understand all of the systems that may be affected by or that will impact the
in-scope systems.
Context diagram A context diagram shows all of the direct system and human interfaces to systems
within a solution.
Specify the scope of the project, including any interfaces that have to be developed.
Context diagrams are also helpful in determining where there could be interface
requirements or data requirements.
Feature model Representation of all of the features of a solution arranged in a tree or hierarchical
structure.
Show how features are grouped together and which features are subfeatures of other
ones.
Organizational chart
(described in Business
Analysis Planning)
Use case diagram A use case diagram shows all of the in-scope use cases for a system.
Use case diagrams can be used to summarize the scope of a solution, highlighting the
main features to be added
These diagrams also show the stakeholders who directly interact with the solution
Decomposition model
(described in Business
Analysis Planning)
Fishbone diagram (described
in Needs Assessment)
Interrelationship diagram
(described in Needs
Assessment)
SWOT diagram (described in
Needs Assessment)
Process models : Models that describe business processes and ways in which stakeholders interact with those processes
Process flow Also called swimlane diagrams, process maps, process diagrams, or process flow
charts, visually depict the tasks that people perform in their jobs.
Typically, process flows describe the steps that people take, although they may
describe system steps and could be called system flows.
Facilitating conversations during elicitation , identify missing features or
requirements , discuss as-is processes
Use case A use case describes a set of scenarios. A scenario is any single pass through a system
to achieve a goal for the primary actor.
Includes: Name, Description, Actors, Organizational benefit, Trigger, Preconditions,
Normal flow, Alternate flows.
Use cases are used when there are complex back and forth interactions between users
and systems.
User story A user story is a statement, written from the point of view of the user, and describes
the functionality needed in a solution.
As an <actor>, I want to be able to <function>, so that I can <business reason>.
INVEST acronym: Independent, Negotiable, Valuable, Estimable, Small,
and Testable.
Rule models : Models of concepts and behaviors that define or constrain aspects of a business in order to enforce established business
policies
Business rules catalog Are not processes or procedures, but rather describe how to constrain or support a
behavior.
Decision tree Used to model business rules.
Decision table used to model complex branching logic
Uncovers a series of “if this, then that” statements
Decision trees are helpful to identify ways to reduce complex decision logic
Data models: Models of concepts and behaviors that define or constrain aspects of a business in order to enforce established business policies
Entity relationship diagram Also called a business data diagram, shows the business data objects or pieces of
information of interest in a project and the cardinality relationship between those
objects.
Represent the people, places, things, and concepts that the business cares about
Used to define the business data objects and their relationships to one another.
Data flow diagram Illustrates the relationships between systems, actors, and the data that is exchanged and
manipulated over the course of one or many processes.
Used to describe the movement of data between actors and systems over the course of
a process or several processes
Data dictionary Tabular format and shows data fields and attributes of those fields include name,
description, size
Used to specify very detailed aspects of data and to capture data fields and attributes
from the business stakeholder’s perspective.
State table Valid states of an object and any allowed transitions between those states
State diagram Specify the life cycle of an object in the solution , objects that go through workflow
(e.g., an approval process) are aided by using state models
Interface models: Models that assist in understanding specific systems and their relationships within a solution
Report table Captures the detailed level requirements for a single report. Common attributes of a
report include: name, description, decisions made from the report, objectives,
audience, trigger, data fields, data volume, frequency, display format, and calculations.
System interface table Is a model of attributes that captures all of the detailed level requirements for a single
system interface
Used to specify the details for each interface between the systems in the solution.
User interface flow Displays specific pages or screens within a functional design and plots out how to
navigate the screens according to various triggers.
Used in the solution definition stage of a project and help track all of the screens that
need to be further defined
Wireframes
Display-action-response