Chapter Three: System Analysis (Modeling of the Existing and Proposed System using

the chosen methodology)

Introduction

System analysis is a process of collecting and interpreting facts, identifying the problems, and
decomposition of a system into its components. System analysis is conducted for the purpose of
studying a system or its parts in order to identify its objectives. It is a problem-solving technique
that improves the system and ensures that all the components of the system work efficiently to
accomplish their purpose. This document presents the system analysis for the development of a
web-based saving and credit service for Chincha, a microfinance organization dedicated to
empowering underserved communities through financial inclusion. The purpose of this analysis
is to thoroughly understand Chincha's existing processes, identify pain points, and propose a
comprehensive solution that leverages technology to streamline operations, enhance efficiency,
and improve service delivery. Chincha recognizes the importance of adopting modern
technologies to overcome the challenges associated with manual and paper-based processes. The
proposed web-based saving and credit service aims to provide Chincha with a robust platform
that enables efficient management of savings and credit operations while offering a seamless and
accessible experience for their clients. During the system analysis phase, a detailed examination
of Chincha's current workflows, data management practices, and customer interactions will be
conducted. This will involve close collaboration with Chincha's stakeholders, including
management, loan officers, and customer service representatives, to gain a comprehensive
understanding of their needs, pain points, and goals. The analysis will encompass various aspects
of Chincha's operations, including account management, loan application and approval
processes, interest calculations, reporting, and communication channels. By identifying
inefficiencies, bottlenecks, and areas for improvement, the analysis will inform the design and
development of a tailored web-based solution that addresses these challenges and aligns with
Chincha's specific requirements. Throughout the system analysis process, collaboration and
communication with Chincha's stakeholders will be paramount. Regular meetings, interviews,
and workshops will be conducted to gather requirements, validate assumptions, and ensure that
the proposed solution meets the organization's unique needs and objectives. Feedback loops will
be established to iterate on the design and development of the system, ensuring a successful
implementation.

---
 3.1 System Requirement Specifications (SRS)
\
System Requirement Specifications (SRS) refer to a document that outlines the detailed
description of the requirements and functionalities of a software system. It provides a
comprehensive understanding of what the system should do, its features, functionalities, and
constraints.

We have used Use case diagram to typically define interactions between a role (known in
Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. The actor can
be a human or an external system. We have used it as a blueprint for the system especially for the
interface design. It is also used to describe what a system does and to reflect the view of the
system from the perspective of a user outside of the system. We used UML to design the use
case model and derive system’s object and their interaction with each other with the users of the
system.

3.2.Actors
An actor represents a role in essential use case modeling. A person, organization, or external
system that interacts with the system is referred to as an actor. Actors are always outside of the
system being modeled; they are not a part of it. The followings are a list of actors in the proposed
system.

1.manager
2.accountant
3.loan committee
4. customer
5. System Manager:
6. Audit

Use case identification

A use case describes a sequence of actions that provide something of measurable value to an
actor.

Actor: manager:

➢ Manage account
➢ Manage employee
➢ Deactivate users
➢ approve loan
➢ View monthly report
➢ View and approve new customer
➢ Back up DB
➢ View log file
➢ send report
➢ View feedback
➢ Post meeting date
➢ Change password

Actor: accountant:

➢ Create account for customer

➢ register repay money
➢ Deposit money for customer
➢ Withdraw money
➢ transfer money
➢ view monthly report
➢ Accept new customer
➢ view approved request
➢ view receipt
➢ send report
➢ view reported response
➢ view meeting date
➢ view feedback
➢ change password

Actor: loan committee:

➢ view loan request

➢ approve loan request
➢ reject loan request
➢ view meeting date
➢ register debtor
➢ view debtor
➢ send report to manager \
➢ change password

Actor: customer:
➢ send request for loan
➢ view response
➢ view balance
➢ send feedback
➢ view meeting date
➢ change password
➢ transfer his/her money

Actor System Manager:

  Maintain system functionality
 Implement updates and enhancements
 Ensure data security
 and privacy complain

Actor Auditor: Role:

 Ensures compliance
 Conduct periodic audits
 Verify financial transactions
 Report any discrepancies or irregularities

3.3. Use Case Description

 A) Use case description for login

Section Purpose
Use case name Login
ID UC1
Actor Manager, Accountant, Customer, Loan Committee
Description The user enters authorized username and password in order to access the
system.
Precondition The user should have username and password
Post condition The user successfully login to the system
Basic course action User action System response
1. Open home page.
2. Display the login page with login form.

3. Enter the
authorized username,
password in the login
form.
4. Click on login
button
5. Check the authorized username and
password.
6. If the username and password correct login
in the system.
Alternative course A3: if input user name and password are invalid
of action A6: displays the user name and password is not found

B) Use case description for register customer

 Section Purpose
Use case name Create account for customer
ID UC17
Actor Accountant
Description The accountant create new account of customer
Precondition The customer must fulfill all requirement
Post condition Display message that indicates the success of the operation
Basic course action User action System response
1. Login in the system.
2 Display accountant page.
3. Open create account
page. 4. Display create account page.
5. Enter the appropriate .
information on the form. 6.
Click on create button

7. Check the filled information.

8. If the filled information is correct the
system create the new account for customer in
the system database and display successful
message

Alternative course of A5:If input vale is invalid

action
A8: System display ‘’account is not created message’’

C)Use case description for send loan request

 Section Purpose
Use case name Approve loan request
ID UC26
Actor Loan committee
Description Receive customer requests, the system check the conditions and accept or
reject the request

Precondition The request must be exist

Post condition Successfully see the request
Basic course User action System response
action
1. Login in to the system.
2 Display the loan committee page.
3. Open view loan request
page.
4. Display the loans request table.
5. loan committee click
status button
6. If the request
information is fulfilling the
criteria the Loan committee
accepts the request.
7:the system sends accepted message in to
sender

Alternative A6: If the request information is not fulfilling the criteria

course of action A7: the Loan committee reject the request

D) Use case description for view report

Section Purpose
Use case name view report
Id Uc16
Actor Accountant, manager, Loan committee
Description View monthly activity in the association
Pre-condition Accountant, manager and Loan committee login to the system
Post condition Display monthly report
Basic course action User action System response
1. login to the system
2.Display accountant, manager and Loan
3. Click view report committee page
button
4. Display report button
5. Click report button
6. Display monthly report
A3:If the report is not found
A6:Displaye the report is not found

E) Use case description for view balance

Section Purpose
User case name View balance
Id Uc38
Actor customer
Description customer wants to view their balance
Precondition customer first login to the system
Post condition View necessary balance
Basic course of User action System response
action
1.login to the system
2.display customer page
3.click view balance button
4. display balance

F) Use Case Documentation for Report Generation

Section Purpose
Use Case Name Report Generation
Participating actor Manager ,accountant and loan committee
Description Allow manager, accountant and loan
Goal To generate different kinds of report
Precondition Login in their respective user account
Post condition Generate report
Flow of event User Action System Response
1 The manager, 2 The system displays
accountant and loan the report
interacts with the 5 the system
system to generate displays generates
report report
3 the manager, 6 use case ends
accountant and loan
selects report they
want to be generate
4 they click
print button

Alternative course of action A3: the system notifies selected information is

invalid or not found
A5: the system display error message

G) Use Case Description for withdraw money

Section Purpose
Use case name Withdraw money
 Participating actor accountant
Description It allows the accountant to performer transaction
Goal To withdraw money for customer

Precondition The user must have available balance

Post condition The customer take money

Flow of event User action System response
1 Accountant interacts with system 2 The system displays
to withdraw the money Transaction login form.

3 Accountants fill the form and click login

button. 4 The system validates and
cheeks the username and
account then the System
5 Accountant performer’s transaction. displays Transaction page. 6
The system displays
transaction form

7 Accountants fill form and click withdraw 8 Displays withdraw

button. successfully message

9.Use case
end

Alternative course A3:The user name and password is not found

of action A4:the system displays error message
A7 The system notifies that accountant enter invalid entry and balance is not
available
A8: The system displays balance is not available.

G) Case Description for deposit money

Section Purpose
Use case name Deposit money
 Participating actor accountant
Description It allows accountant to perform the transaction
Goal To deposit money for customer
Precondition The user must have balance in the hand
Post condition Money is deposited in customers account
Flow of event User action System response
1 accountant interacts with system to 1 the system displays
perform transaction transaction

3 accountants fill the form and click login form.

login button. 4 the system validates

5 accountants click transaction button. and cheeks the
username and account
then the
System displays
Transaction page.

7 accountant fills form and click deposit 6 the system displays

button. transaction form

8 displays
successfully message

9 use case ends

Alternative course of A3:if user is not found
action A4:displayes error message
A7 the system notifies that accountant enter invalid entry A8
the system displays error message.

3.4. Sequence diagram

Sequence diagrams are used to formalize the behavior of this system and to
visualize the communication among objects. The diagrams show the flow of
messages from one object to another, and as such correspond to the methods and
events supported by a class/object. These typically show a user or actor, and the
objects and components they interact with in the execution of a use case. A
sequence diagram is a Unified Modeling Language (UML) diagram that illustrates
the sequence of messages between objects in an interaction. A sequence diagram
consists of a group of objects that are represented by lifelines, and the messages that
they exchange over time during the interaction.

A) Sequence diagram for withdraw money

B) Sequence diagram for create account for customer
C)Sequence diagram for send loan request
D) Sequence diagram for view balance
3.5. Activity Diagram
Activity diagram is UML behavior diagram which shows flow of control or object
flow with emphasis on the sequence and conditions of the flow. An activity diagram
visually presents a series of actions or flow of control in a system similar to a
flowchart or a data flow diagram. Activity diagrams are often used in business
process modeling Some of the activity diagrams of the project known as chincha
micro finance saving and credit association information management system are:

Sequence diagram for create account for customer

Sequence diagram for send loan request

Sequence diagram for create account for customer

Sequence diagram for send loan request
Sequence diagram for view balance
3.6. Activity Diagram

Activity diagram is UML behavior diagram which shows flow of control or object
flow with emphasis on the sequence and conditions of the flow. An activity diagram
visually presents a series of actions or flow of control in a system similar to a
flowchart or a data flow diagram. Activity diagrams are often used in business
process modeling Some of the activity diagrams of the project known as chincha
micro finance saving and credit association information management system are:

A) Activity diagram for login

B) Activity diagram for create account
C)Activity diagram for send loan request
 D) Activity diagram for view balance

3.7. Class Diagram

Class diagrams are the blueprints of system or subsystem. You can use class diagrams to model
the objects that make up the system, to display the relationships between the objects, and to
describe what those objects do and the services that they provide. The class diagram represents
the static view of an application. Class diagram is not only used for visualizing, describing and
documenting different aspects of a system but also for constructing executable code of the
software application. The class diagram describes the attributes and operations of a class and also
the constraints imposed on the system. The class’s diagrams are widely used in the modeling of
object-oriented systems because they are only UML diagrams which can be mapped directly
with object-oriented languag0es.
Class diagram
Introduction
3.2 System Requirement Specifications (SRS)
3.2.1 Use case diagrams
3.2.2 Use case documentation (for each use case identified)
3.2.3 Sequence diagram
3.2.4 Activity Diagram
3.2.5 Analysis level class diagram (conceptual modeling)
3.2.6 User Interface Prototyping
3.2.7 Supplementary specifications