Chapter Two

Analysis of Existing System

2.1 Overview of Existing System
2.2 Functions of Exiting System
2.3 Players of Existing System
2.4 Problems of Existing System
2.5 Supplementary Specification
2.5.1 Business Rules
2.6 Modeling the Existing System
2.6.1 Use Cases
2.6.2 Essential Use Case Modeling
2.6.2 Essential Use Case Documentation
2.6.3 CRC Model
2.6.4 Essential User Interface Prototype
2.6.5 User Interface(UI) Flow Diagram
 2.1 Overview of Existing System
 Clearly describe what you are going to done or
models at this part by one or two paragraphs:
For Example this part describe:
 Functions of existing system,
 Players of the existing system,
 Problems of the existing system,
 Supplementary Specification of the existing
system(include only the Business rule )
 Modeling the existing system.
 2.2 Functions of Exiting System
 List down and describe the functions of existing system
that you gather during requirement gathering.
 2.3 Players of Existing System
 Shortly List down the players(actors) of the existing
System with its corresponding responsibilities
 Example:
Actors Description
 2.4 Problems of Existing System
 List down clearly the problems of existing system you
identify during requirement determination or elicitation.
 It is not problem of statement but are problems of the
manual or existing system
 2.5 Supplementary Specification
2.5.1 Business Rules
 List down and describe those business rules that the
existing system may use to perform its required operation
as a procedures.
 Usually this part is taken directly from the directives or
legislation document of the manual system as it is with no
modification.
 Example: Student Fee Payment system business rule
might be describe as follows in the document.
1. Business Rule One
 Student fee payment is made within 5 days of each month
of the academic calendar otherwise additional 100 birr is
incurred as a penalty with in 15 days. 7
 2.6 Modeling the Existing System
 Describe about the models used to model the existing or
manual system of your project.

2.6.1 Use Cases

 List down use case that you identify in the existing

system.
 2.6.2 Essential Use Case Diagram
 Describe about Essential Use Case Diagram to model
the interaction between actors and the use cases.
 Use Pencil to draw the diagram to show the interaction
between the actors and the use cases.
 2.6.3 Essential Use Case Documentation
 Describe about Essential Use Case Documentation.
 Prepare separate use case documentation for each use
cases you identify in the exiting system.
Use the following standard format to prepare
essential use case documentation for each use
cases.
 Use Case Documentation Format
Actors: User
Use case:
Name:
Identifier:
Description:
Actor:
Precondition:
Post condition:
Extends:
Include:
Basic Course of Action:
1.
2.
3.
4.
5.

Alternative course of action: if the user did not get privilege

1.
2.
11
 2.6.4 CRC Model
 Describe about CRC Model shortly
 List down the things or classes that might be included in
the existing system
 Use the following Sample CRC format to model the
CRC

Class Name

Responsibilities Collaborators
 2.6.5 Essential User Interface Prototype
 Describe Essential User interface prototype shortly
 Use forms that is used by the organization to perform the
day to day operation of the business.
 2.6.6 User Interface(UI) Flow Diagram
 Describe shortly about the Essential UI flow diagram of the
existing system.
 The description shows all the relationships between each
formats in the exiting system.
 Use pencil to draw the Essential UI flow diagram.