WEB PROCESS AND

SYSTEM ANALYSIS
CONTENT
Customer and journey maps
Business process and system modeling
 Use case modeling
 Event analysis
 Process mapping
CUSTOMER PROFILE
 CUSTOMER JOURNEY MAPS
a visual representation of a customer’s experience with your business. For example:
making a purchase, signing up for a newsletter or joining a loyalty program
outlines key events, customer motivations, and areas of friction within their
experience
often based on a timeline of events, visualizes the current process customers take,
from the first to final touchpoint (A display ad, an interaction with an employee, a 404
error…)
 CJM
Go to mural.co , create
a customer experience
journey map for your
group project
 MODELING BUSINESS
PROCESS AND SYSTEM
SYSTEM
MODELING
Modeling events
 Use cases
 Event tables…

Modeling data:
 ERD,
 Data dictionary…

Modeling process:
 DFD
EVENTS, ACTIVITIES, AND
USE CASES

Use Case Techniques for identifying use cases

An activity the system performs in response to a Identify user goals
user request • Each goal at the elementary business process
(EBP) level is a use case
• EBP – a task performed by one user, in one
place in response to a business event, that adds
measurable business value, and leaves system
and data in consistent state (e.g., create new
order)
Event decomposition technique (how the system
responds)
 USE CASE
MODELING
USE CASE MODELING
Part of the unified modeling language (UML)
Describes what a system does without describing how the
system works
A view of the system requirements
Analyst works with business experts to develop requirements
USE CASE DIAGRAM
Actor
 Refers to a particular role of a user of the system
 Similar to external entities; they exist outside of the system
Use case symbols
 An oval indicating the task of the use case
Connecting lines
 Arrows and lines used to diagram behavioral relationships
ACTOR
Divided into two groups
 Primary actors:
 Supply data or receive information from the system
 Provide details on what the use case should do
 Supporting actors:
 Help to keep the system running or provide help
 The people who run the help desk, the analysts,
programmers, and so on
A USE CASE ALWAYS
PROVIDES THREE THINGS
An actor that initiates an event
The event that triggers a use case
The use case that performs the actions triggered by the event
USE CASE RELATIONS
Behavioral relationships
 Communicates
 Used to connect an actor to a use case
 Includes
 Describes the situation in which a use case contains behavior that
is common to more than one use case
 Extends
 Describes the situation in which one use case possesses the
behavior that allows the new case to handle a variation or
exception from the basic use case
 Generalizes
 Implies that one thing is more typical than the other thing
FOUR TYPES OF BEHAVIORAL
RELATIONSHIPS AND THE LINES USED
TO DIAGRAM
ACTORS, USE CASES, AND RELATIONSHIPS
FOR A STUDENT ENROLLMENT EXAMPLE
BUSINESS USE CASE MODELING
Business use case reference
USE CASE
DESCRIPTI
ON
IDENTIFYING USE CASES
BASED ON USER GOALS
BUSINESS
REQUIREMENT
DOCUMENT
BUSINESS
REQUIREMENTS
VS FUNCTIONAL
REQUIREMENTS
 FUNCTIONAL
SPECIFICATION
DOCUMENTS
Depending on the project and the team, a functional specification could
include:

 Project scope -- the goals, features, tasks, deliverables, costs and

deadlines of the project.

 Risks and assumptions -- the considerations that could affect the

functional design of the product.

 Product overview -- the explanation of how the application will solve a

specific problem for the target audience.

 Use cases -- the functional requirements are placed in the context of a

user action. This shows what happens from the user perspective.

 Requirements -- essential features of the product that explain what it

does.

 Configuration -- steps needed to configure a product, such as user

account setup.

 Non-functional requirements -- the non-essential features that aren’t at

the core of the product.

 Error reporting -- an explanation of how the product will handle errors or

exceptions.

Read more
EVENT ANALYSIS
 External
• Outside system, initiated by external agent
• To identify external events, first identify all external agents
that might want something from the system (e.g.,
customer)
Temporal
TYPES OF • Occur as result of reaching a point in time; no external
agent is making demands of the system

EVENTS • Based on system deadlines (e.g., produce daily production

schedule)
State
• Something inside system triggers processing need
• e.g., inventory drops below a reorder point; time to
reorder
• Can be similar to temporal events, except the point in time
cannot be defined.
EVENTS AFFECTING A CHARGE ACCOUNT PROCESSING
SYSTEM THAT LEAD TO USE CASES
EXTERNAL EVENT CHECKLIST
TEMPORAL EVENT
CHECKLIST
IDENTIFYING
EVENTS
Can be difficult to determine

Often confused with conditions and responses

May be useful to trace a transaction’s life cycle

Certain events left to design phase

 System controls to protect system integrity: security and
privacy issues such as access control, integrity check

 Perfect technology assumption defers events: assumes that

system never crashes, never makes any errors
SEQUENCE OF ACTIONS THAT LEAD UP TO
ONLY ONE EVENT AFFECTING THE SYSTEM
SEQUENCE OF “TRANSACTIONS” FOR ONE
SPECIFIC CUSTOMER RESULTING IN MANY
EVENTS
An input flow from an external entity is
sometimes called a trigger because it starts
the activities of a process
EVENT
MODELING
Events cause the system to do something
and act as a trigger to the system AND DATA
FLOW
An approach to creating physical data flow
DIAGRAMS
diagrams is to create a data flow diagram
fragment for each unique system event
 An event table is used to
create a data flow diagram by
analyzing each event and the
data used and produced by the
event
Every row in an event table
represents a data flow
diagram fragment and is used
to create a single process on a
data flow diagram

EVENT TABLES
INFORMATION ABOUT EACH EVENT IN
AN EVENT TABLE: CATALOG OF
INFORMATION ABOUT EACH USE CASE
EXAMPLE OF EVENT TABLE
AN EVENT TABLE FOR AN INTERNET
STOREFRONT
Event
Customer logs on
Source
Customer
Trigger
Customer
number and
Activity
Find customer record and verify
password.
Response
Welcome
web page
Destination
Customer

password Send Welcome web page

Customer Customer Item information Find item price and quantity available. Item Customer
browses items Send Item Response web page. Response
at Web storefront web page

Customer places Customer Item purchase Store data on Order Detail Record. Items Customer
item into shopping (item number Calculate shipping cost using shipping Purchased
basket at Web and quantity) tables. Update customer total. Update web page
storefront item quantity on hand.

Customer Customer Clicks “Check Display Customer Verification Blank

checks out Out” button on Order web page. web page
web page
Obtain customer Customer Credit card Verify credit card amount with credit Credit card Credit card
Payment information card company. Send. data company
Customer Customer
feedback
Send customer Blank Temporal, Send customer an email confirming Blank Customer
email hourly shipment.
PROCESS MAPPING
PROCESS MAPPING
Process mapping is a
technique used to visually
map out workflows and
processes. It involves
creating a process map, also
referred to as a flowchart,
process flowchart, or
workflow diagram
PROCESS MAPPING
Types of process mapping
EXAMPLE OF FLOWCHART
WORKFLOW DIAGRAM
Types of workflow diagram
EXAMPLE OF PROCESS MAPPING
WITH SWIMLANE
EXAMPLE OF BUSINESS
SYSTEM DESIGN
Logical System Architecture