Lecture 4

Analyzing the Problem

Problem Analysis
Process of understanding the real world problems and users needs and proposing solutions to meet those needs. The goal of problem analysis to gain better understanding of the problem before the development begins. To identify the root cause or problem behind the problem Identifying the actors on the system.

 System built to
Solve a problem Take advantage of opportunities
2 sides of same coin, matter of perspective.

Problem/Problem Analysis
Problem
Defined as a difference between things as perceived and things derived.
If user perceives something as problem it should be addressed.

Problem Analysis
The process of understanding real world problems and user needs and proposing solutions to meet those needs.

Problem Analysis
It consist of 5 steps
Gain agreement on the problem definition Understand the root causes, the problem behind the problem Identify the stakeholders and the users Define the solution system boundary Identify the constraints to be imposed on the solution.

Step 1:Gain Agreement on the Problem Definition

Write the problem down Problem Statement Format Element Description
The problem of Affects And results in Describe the problem. Identify stakeholders affected by the problem. Describe the impact of this problem on stakeholders and business activity. Indicate the proposed solution and list a few key benefits

Benefits of a solution

Step 2: Identify root cause

Fish Bone Diagram for understanding root cause

Step 3:Who are the Stakeholders

Who are the users of the system? Who is the customer (economic buyer) for the system? Who else will be affected by the outputs the system produces? Who will evaluate and approve the system when it is delivered and deployed? Are there any other internal or external users of the system whose needs must be addressed? Who will maintain the new system? Is there anyone else who cares?

 Keeping in mind
Understanding of problem Consideration of potential solution

Define system boundary

Border between solution and the real world that surrounds the solution. Input and output pass back and forth from system to outside Environment interacts with system via interfaces

 2 parts
Our system (goals) Things that interact with our system (actor)

Answers to questions like

Who will operate the system Who will perform any system maintenance Where will the system be used etc? can help define boundary

Usually boundary shown by dotted line.

A restriction on the degree of freedom we have in providing a solution. Constraints can be known in the start or as the development proceeds. Certain questions help to find out constraints Major constraints sources
Economic Political Technical System Environmental Schedule and resources

 It is a problem analysis technique Before understanding problem we need to understand the environment which consists of
Organizations Business units Departments Functions Wide area network Corporate internet or extranet, Customers/users etc. etc.

 To understand the structure and dynamics of the organization To ensure that customers, end users and developers have a common understanding of the organization.
Done through UML, key modeling constructs
Business use case model Business object model

 Use-cases are now very widely used as the basic concept for specifying requirements of commercial information systems. Consist of
Actor User System

 Two types
Business Use cases System Use cases
A System Use-Case is a way in which a user of a computer system can make use of the system to get the result they want. This will typically be something we can readily imagine as being done in a single sitting on a single PC or other device such as an ATM or a mobile/cell phone, usually with a single UI, or a small number of closely-related screens such as a wizard, and taking maybe between a couple of minutes and a half-hour at most.

A Business Use-Case is to do with using a business: this recognises that businesses are created and organised in order to do things for people mainly customers, but also other actors. So a Business Use-Case is a way in which a customer or some other interested party can make use of the business to get the result they want whether its to buy an item, to get a new driving licence, to pay an invoice, or whatever.

Business Use-Case

An important point is that a single execution of a Business Use-Case should encompass all the activities necessary to do what the customer (or other actor) wants, and also any activities that the business needs to do before the process is complete from its point of view. So the duration of a BUC execution can vary greatly, depending on its nature. Some BUCs, like withdrawing cash from an ATM, can be done in less than a minute; others, like ordering goods for delivery, or getting a new phone line installed, can take days, weeks or even longer.

Business Use-Case
So BUCs define who is involved in the business activities and how they take place Actors are roles external to the business

Reading for next class: Business vs. System Use Cases Author: Martin Langlands and Charles Edwards