Systems Analysis - Business Event Analysis Chapter 3

Front 1

The principal goal of information systems analysis is to

Back 1

to state accurately users’ requirements for a new information processing system.

Front 2

Event analysis treats the system as a...

Back 2

black box and views it from a stimulus-response perspective.

Front 3

An event is

Back 3

an occurrence which takes place at a specific time and triggers a predetermined response from the system. Because events occur independently of each other, event analysis is a powerful technique for breaking up a large or complex system into small, manageable, cohesive, independent parts.

Front 4

Event analysis...

Back 4

identifies the events to which the system is expected to respond, names the inputs and outputs, and identifies the actors – those who interact with the system by providing inputs and receiving outputs.

Front 5

The Primary Goal of Systems Analysis is

Back 5

To state accurately the users’ requirements for a new information processing system

Front 6

Secondary Goals of System Analysis are

Back 6

To understand the users’ requirements.
To communicate the current understanding of the proposed system
To prevent expensive mistakes
To state a design problem
To state the conditions for system acceptance

Front 7

5 Characteristics of a Statement of System Requirements

Back 7

Graphic: Uses diagrams
Partitioned: Organizes the system description into comprehensible parts
Non-redundant: A change can be made in a single place
Accurate: Rigorous, precise, clear, consistent, and complete
Minimal: Eliminates non-essentials, while including all critical details

Front 8

6 Step Procedure for Object-Oriented Systems Analysis

Back 8

Step 1. Identify the business events and make an event table.
Step 2. Identify the use cases and produce a use case diagram for the system.
Step 3. Write a use case narrative describing the system’s response to each business event.
Step 4. Draw a system sequence diagram for each use case scenario.
Step 5. Produce a domain model showing the concepts, attributes, and associations in the problem domain of the system.
Step 6. Write a contract for each system operation.

Front 9

Event-Driven Systems

Back 9

Event analysis takes a stimulus-response perspective

The system does nothing until it is triggered by an event.
When an event occurs, the system responds as completely as possible.
After the response is complete, the system waits until another event occurs.

Front 10

An event is

Back 10

an occurrence which takes place at a specific time and initiates or triggers a predetermined response from the system.

Front 11

An external event is

Back 11

an event which occurs outside the system boundary.

Front 12

An internal event is

Back 12

an event which occurs inside the system boundary.

Front 13

A temporal event is

Back 13

an event which occurs at a prespecified time.

Front 14

Event analysis creates a system description by identifying:

Back 14

The events to which the system is expected to respond
The incoming message (event flow or
data flow) associated with each event
The desired response
The actions or behaviors required to generate the response for each stimulus

Front 15

Hints About Event Analysis

Back 15

Ignore the technology of implementation – build an essential event model.
Model the system’s complete
response – don’t split a single event into fragments.
Isolate individual events – don’t combine events if the system must wait in between them.

Front 16

The initial step in object-oriented systems analysis is

Back 16

event analysis.

Front 17

Event analysis identifies ..

Back 17

external and temporal events and the system’s expected responses.

Front 18

Models for Object-Oriented Systems Analysis

Back 18

Models for Object-Oriented Systems Analysis

Front 19

Typical Models – Event List

Back 19

Typical Models – Event List
Event list for the university registration system

Front 20

Typical Models – Use Case Diagram

Back 20

Typical Models – Use Case Diagram

Front 21

Typical Models – Use Case Narrative

Back 21

Typical Models – Use Case Narrative

Front 22

Typical Models –System Sequence Diagram

Back 22

Typical Models – System Sequence Diagram

Front 23

Typical Models – Domain Model

Back 23

Typical Models – Domain Model

Front 24

Typical Models – System Operation Contract

Back 24

Typical Models – System Operation Contract

Front 25

Event Analysis

Back 25

Event Analysis

Front 26

Event Table

Back 26

Event Table