Group members Id Number

1. Nigussie Hailu 00657/02

2. Shiferaw Tegen 00713/02

Advisor: T. Murali Krishna (PHD)

Co-advisor: Tsigab Gebre (BSC)

January, 2013

Jimma, Ethiopia

Page i
 Requirement analysis and system design document

Advisor Name Signature

1. T. Murali Krishna (PHD) __________
2. Tsigab Gebre (BSC) __________

Examining board

Name Signature Date

1._______________ ___________ _________

2._______________ ___________ _________

3._______________ ___________ _________

4._______________ ___________ _________

Acknowledgement

Page ii
First of all we would like to extend our heartfelt gratitude to our advisor Mr. T. Murali Krishna
and co-advisor Mr. Tsigab Gebre for their constructive advises, guiding and correcting our
documents with attention and care as well as follow ups. We never forget also to extend a word
of thanks to Mr. Ahadu Tsegaye and Mrs. Saba Mekuria employers in Omedad Company for
their help by giving necessary information and support while gathering information about the
company financial related information.

Abstract

Page iii
The finance management system developed for Omedad Company financial department can
manage the tasks related to financial activities like ensuring data integrity and security, keeping
all records up to date, and minimizing overall paperwork. The possible users are financial
manager, accountant and clerk of the financial department. The system would provide basic set
of features to oversee and govern its income, employee payroll system, expenses, credit interest,
profit and loss, day book and assets or capital with the objectives of maximizing profits and
ensuring sustainability. The goal of this document is to clearly specify the requirements for the
system to be developed.

Abbreviations

Page iv
An abbreviation is a shortened form of something used to represent a longer whole. There are
few abbreviations that are used throughout our document.

UML: - Unified modeling language

CRC: - Class responsibility collaboration

OOP: - Object oriented programming

GUI: - Graphical user interface

OODBMS: - Object oriented database management system

RAM: - Random access memory

JDK: - java development toolkit

Page v
 Table of Contents
List of tables..............................................................................................................................viii
List of figures................................................................................................................................x
Chapter one...................................................................................................................................1
Introduction...................................................................................................................................1
1.1Background..........................................................................................................................1
1.2 Statement of the problem....................................................................................................2
1.3 Objective.............................................................................................................................2
1.3.1 General objective.........................................................................................................2
1.3.2 Specific objective.........................................................................................................2
1.4 Methodologies....................................................................................................................3
1.4.1 Data collection methodologies....................................................................................3
1.4.2 System development methodologies and tools............................................................3
1.5 Feasibility study..................................................................................................................5
1.5.1 Operational feasibility.................................................................................................5
1.5.2 Schedule feasibility......................................................................................................5
1.5.3 Technical feasibility.....................................................................................................6
1.5.4 Behavioral feasibility...................................................................................................6
1.5.5 Economic feasibility....................................................................................................6
1.6 Scope and limitation of the project.....................................................................................7
1.6.1 Scope............................................................................................................................7
1.6.2 Limitation....................................................................................................................7
1.7 Significance of the project..................................................................................................7
1.8 Time scheduling diagram...................................................................................................8
Chapter two.................................................................................................................................10
2 System analysis........................................................................................................................10
2.1 Existing system.................................................................................................................10
2.1.1 Problem with the existing system..............................................................................10
2.1.2 Business rule..............................................................................................................11
2.2 New system.......................................................................................................................12
2.2.1 Functional requirements............................................................................................12
2.2.2 Non functional requirements.....................................................................................12
2.2.3 Use case diagram.......................................................................................................13

Finance Management System For Omedad Company Page vi

 2.2.4 Use case description..................................................................................................16
2.2.5 Sequence diagram......................................................................................................25
2.2.6 State diagram.............................................................................................................32
2.2.7 Activity diagram........................................................................................................37
2.2.8 Class responsibility collaboration (CRC)..................................................................46
2.2.9 Change in case...........................................................................................................49
2.2.10 Class diagram...........................................................................................................49
2.2.11 User interface prototyping.......................................................................................50
Chapter three...............................................................................................................................61
System design.............................................................................................................................61
3.1 Introduction.......................................................................................................................61
3.1.1. Overview of the system design.................................................................................62
3.1.2 Design goals...............................................................................................................62
3.2 Current software architecture...........................................................................................64
3.3 Proposed software architecture.........................................................................................64
3.3.1 Subsystem decomposition.........................................................................................65
3.3.2 Component diagram...................................................................................................67
3.3.3 Deployment diagram.................................................................................................68
3.3. 4 Persistence modeling for object oriented database...................................................69
3.3.5 Access control............................................................................................................70
3.4 Conclusion and recommendation.....................................................................................72
3.4.1 Conclusion.................................................................................................................72
3.4.2 Recommendation.......................................................................................................72
Reference....................................................................................................................................73

Finance Management System For Omedad Company Page vii

List of tables
Table 2.1 Use case description for authentication ………………………………………….. 16

Table 2.2 Use case for employee registration ……………………………………………..... 17

Table 2.3 Use case for update employee details ……………………………………………. 18

Table 2.4 Use case for managing accounts …………………………………………………. 19

Table 2.5 Use case for payroll……………………………………………………………….. 20

Table 2.6 Use case for income ……………………………………………………………… 21

Table 2.7 Use case for expenditure …………………………………………………………. 21

Table 2.8 Use case for generate financial report ……………………………………………. 22

Table 2.9 Use case for calculate interest ……………………………………………………. 22

Table 2.10 Use case for calculate profit and loss …………………………………………… 23

Table 2.11 Use case for capital ……………………………………………………………… 23

Table 2.12 Use case for day book …………………………………………………………… 24

Table 2.13 Use case for invoice ……………………………………………………………… 24

Table 2.14 CRC analysis for Employee registration…………………………………………. 46

Table 2.15 CRC analysis for Employee payroll ……………………………………………... 46

Table 2.16 CRC analysis for Expense………………………………………………………... 47

Table 2.17 CRC analysis for Income………………………………………………………… 47

Table 2.18 CRC analysis for Invoice ………………………………………………………... 47

Table 2.19 CRC analysis for Generate report ……………………………………………….. 48

Table 2.20 CRC analysis for Profit and loss ………………………………………………… 48

Finance Management System For Omedad Company Page viii

Table 2.21 CRC analysis for capital ………………………………………………………..... 48

Table 2.22 CRC analysis for Day book ……………………………………………………… 48

Table 2.23 CRC analysis for credit interest ………………………………………………...... 49

Table 3.1 Access control represents level of access privileges ……………………………… 71

Finance Management System For Omedad Company Page ix

List of figures
Fig 1.1 Gantt chart for work breaks down structure ………………………………………….. 9
Fig 2.1 Use case diagram …………………………………………………………………….. 15
Fig 2.2 sequence diagram for login …………………………………………………………... 25
Fig 2.3 sequence diagram for create account ………………………………………………... 26
Fig 2.4 sequence diagram for employee registration ………………………………………… 27
Fig 2.5 sequence diagram for update employee details ……………………………………… 27

Fig 2.6 sequence diagram for income ………………………………………………………... 28

Fig 2.7 Sequence diagram for payroll ………………………………………………………... 29
Fig 2.8 sequence diagram for expenditure …………………………………………………....30
Fig 2.9 sequence diagram for profit and loss ………………………………………………… 30
Fig 2.10 sequence diagram for invoicing …………………………………………………….. 31
Fig 2.11 sequence diagram for generate report …...…………….…………….……………… 31
Fig 2.12 State diagram for login …………………………………………………………...32
Fig 2.13 State diagram for update employee details …………………………………………. 32
Fig 2.14 State diagram for create account ……………………………………………… 33
Fig 2.15 State diagram for expenditure ………………………………………….…………… 33
Fig 2.16 State diagram for payroll ………………………………………………………….. 34
Fig 2.17 State diagram for profit and loss ……………………………………………………. 34
Fig 2.18 State diagram for employee registration …………………………………………..…35
Fig 2.19 State diagram for invoice ………………………………………….………………... 35
Fig 2.20 State diagram for generate report …………………………………………………... 36
Fig 2.21 Activity diagram for login to account ………………………………………………. 37
Fig 2.22 Activity diagram for account creating ……………………………………………… 38
Fig 2.23 Activity diagram for expenditure …………………………………………………. 39
Fig 2.24 Activity diagram for update account ………………………………………….…… 40
Fig 2.25 Activity diagram for registering employees………………………………………… 41

Finance Management System For Omedad Company Page x

Fig 2.26 Activity diagram for payroll ……………………………………………………… 42
Fig 2.27 Activity diagram for profit and loss ………………………………………………. 43
Fig 2.28 Activity diagram for invoicing ……………………………………………………... 44
Fig 2.29 Activity diagram for report ………………………………………………………… 45
Fig 2.30 Detailed class diagram …………………………………………………………….... 50
Fig 2.31 user interface for login to the system ……………………………………………. 51
Fig 2.32 user interface for the main window ……………………………………………….. 52
Fig 2.33 user interface for the employee payroll …………………………………………… 53
Fig 2.34 user interface for the employee registration ………………………………………... 54
Fig 2.35 user interface for income ………………………………………………………….. 55
Fig 2.36 user interface for expenditure …………………………………………………….. 56
Fig 2.37 user interface for profit and loss ……………………………………… …………… 57
Fig 2.38 user interface for credit interest …………………………………………………….. 58
Fig 2.39 user interface for day book …………………………………………………………. 59
Fig 2.40 user interface for summary report ………………………………………………….. 60
Fig 3.1 layered representation of the system ……………………………………………….... 66
Fig 3.2 Decomposition of finance manager ………………………………………………….. 66
Fig 3.3 Decomposition of accountant ………………………………………………………... 67
Fig 3.4 Decomposition of clerk ……………………………………………………………… 67
Fig 3.5 component modeling ……………………………………………………………….... 68

Fig 3.6 deployment diagram …………………………………………………………………. 69

Fig 3.7 persistence model diagram…………………………………………………………… 70

Finance Management System For Omedad Company Page xi

 Chapter one

Introduction
1.1Background

A financial management system is the methodology and software that an organization uses to
oversee and govern its income, expenses, and assets with the objectives of maximizing profits
and ensuring sustainability. An effective financial management system improves short and
long term business performance by streamlining invoicing and bill collection, eliminating
accounting errors, minimizing record keeping redundancy, ensuring compliance with tax and
accounting regulations, helping personnel to quantify budget planning, and offering flexibility
and expandability to accommodate change and growth. Other significant features of a good
financial management system are keeping all payments and receivables transparent, amortizing
prepaid expenses, depreciating assets according to accepted schedules, keeping track of
liabilities, Coordinating income statements, expense statements, and balance sheets, ensuring
data integrity and security, keeping all records up to date, maintaining a complete and accurate
audit trail, minimizing overall paper work. Financial management software should include
features that support creation of ad-hoc reporting as well as month end closing, quarter closings
and year end reporting.

Omedad Company is a huge organization which found in Addis Ababa and other cities like
Mekele, Jimma, Gondar, Baherdar, Axum, Arbaminch and other city. The main branch of this
company is found in Addis Ababa. It has more than 20 branches and in each branch has more
than 50 employees. The main branch has 60 employees. The company has main services such
as import and distributes electronic devices like photocopy machines, printers, household
electronic devices and computers, maintain electronic devices and give technical services.

Finance Management System For Omedad Company Page 1

 1.2 Statement of the problem

Omedad company the finance work system works manually, unsatisfactory and very difficult
to work because their current work system has many problems such as lack of security of data,
needs manual calculations using paper, excel and calculator, no fast retrieval of data time,
consume large volume of paper work and more man power, waste of too many hardware
materials and lose of their files. The payroll system of their employee works using paper and
ms excel. All the necessary records of the above management activities are kept manually on
papers and stored in file cabinet. Due to manual way of handling files error are occurs which
lead to unnecessary rework.

Those problems stated above may cause finding some specific data from the file in cabinets
which resulted in slow retrieval of data; difficulty in updating information, encountered
problem when report is generated and it is time consuming, the mechanism of data handling is
unsecured may cause the loose of data by several kinds of problems like rats, theft by workers
and others.

1.3 Objective

1.3.1 General objective

The main objective of this project is to develop a new system which solves the above
mentioned problems with the existing system. This is achieved by designing software that will
change the actual manual work to an automated environment.

1.3.2 Specific objective

The specific objectives of our project are:-

 To design a user friendly system.

 To make the office works in simple way.
 To increase the time to generate the report of the work.
 To give the service to the employees in short period of time.
 To reduce the human resource of the office.

Finance Management System For Omedad Company Page 2

  To increase to the work efficiency of the department.
 To minimize the loss of records or data.
 To minimize the time consuming to search for records from the file and make it
easy to search what we want.
 Increase the security of the data by authentication.
 To increase the employees motivation on their work without tiredness from the
manual system work.

1.4 Methodologies

1.4.1 Data collection methodologies

We use observation, interview and work on the company as apparent ship in order to obtain the
information about the practices and problems of the Omedad Company finance department
which ultimately assists us in developing the automated system.

 Observation: - Observation is common methods of scientific research to collect the

data. We use observation to know the existing system, the location of Omedad finance
department company office, different sub offices and how office members are handling
the work in the office.
 Interview: - Interview is particularly useful for getting the history behind the
participant’s experiences. We used interview to get information about the existing
system for developing our project. The interview will be conducted on the staff
member.
 Work on the company as apprenticeship: - working on the company for three months
as apprenticeship. As we have seen the problem in addition to observation and
interviewing work on the company it give us more knowledge on the current system
and which lead us to the proper solution.

1.4.2 System development methodologies and tools

To develop the system different software, hardware tools and programming language are very
important. Hardware tools such as computer, flash disk, network cable and CD, software tool
such as Netbeans, Microsoft office word and PowerPoint, JDK and other are listed below.

Finance Management System For Omedad Company Page 3

We use OOP language in our implementation of our project. Because of our title has a lots of
objects which coherently Organized and built the system and also to show their inheritance and
plat form independent of the system in detail. In addition, the GUI of the object oriented
programming language is too easy to the end user of the system as well as it is easy to program
and handle exceptional thrown.

Software tools

 Microsoft office word: - It is very useful because it takes less time to write and format
the text, communicative effectively smart diagram and chart tools, quickly assemble
document. By looking its useful properties we use Microsoft office word to type our
project work to get all the above benefits of it.
 Microsoft Power point: - use to present the document in abstract forms. We use it to
present our presentation in short and brief way.
 JDK: - a java development toolkit is a program development environment for writing
java applet and application. It is a tool used to compile, debug, and run applets and
applications written in the Java language.
 Net beans: - open - source integrated development environment (IDE) for developing
with Java, PHP, C++, and other programming languages. 
 Visual paradigm for UML: - a software that used to develop a UML.
 Microsoft office Visio: - a software that used to develop a UML.
 Smart sheet: -a web site that used to draw the time scheduling diagram for and its link
is https://www.smartsheet.com/

Hardware tools

Different hardwires used to develop our project.

 Computer: - used to install software that are necessary for our work like Netbeans
and to do other tasks related to our work.
 Network cable: - we used twisted pair cable to get the internet access which is used us
to get many information about our project.
 Flash disk and CD: - used for the movement of data from one machine to another. We
use both of them when we move our data from one machine to another.

Finance Management System For Omedad Company Page 4

  Printer: - for printing the documents.

1.5 Feasibility study

Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibility study of a
system proposal is according to its workability, which is the impact on the organization, ability
to meet their user needs and effective use of resources. Thus when a new application is
proposed it normally goes through a feasibility study before it is approved for development.

The document provide the feasibility of the project that is being designed and lists various
areas that were considered very carefully during the feasibility study of this project such as
operational, scheduling, technical, behavioral and economical feasibilities. The following are
its features:

1.5.1 Operational feasibility

We expect that the system which is in development is to be operational. That is once the
system is deployed, it can operate on any of the operating systems which have a java
framework installed. Therefore, the system will be designed to be operationally feasible that if
it is deployed, the system will operate in any kind of platforms without any mal functionalities.

1.5.2 Schedule feasibility

We expect that the project will be completed within the time frame stated, so that the system
will be feasible regarding schedule.

Finance Management System For Omedad Company Page 5

1.5.3 Technical feasibility

We expected the system to be technically feasible. The system is going to be developed by

following the Object Oriented System Development technique and we have the ability to
develop this system without any difficulty since the team has studied the required
methodologies and tools. So the system will be technically feasible.

1.5.4 Behavioral feasibility

This includes the following questions:
 Is there sufficient support for the users?
 Will the proposed system cause harm?
The project would be beneficial because it satisfies the objectives when developed and
installed. All behavioral aspects are considered carefully and conclude that the project is
behaviorally feasible.

1.5.5 Economic feasibility

The developing system must be justified by cost and benefit. Criteria to ensure that effort is
concentrated on project, which will give best, return at the earliest. One of the factors, which
affect the development of a new system, is the cost it would require.
The following are some of the important financial questions asked during preliminary
investigation:
 The costs conduct a full system investigation.
 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.
Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also all the resources are already available, it give an indication of the
system is economically possible for development.

Finance Management System For Omedad Company Page 6

 1.6 Scope and limitation of the project

Since Omedad company finance department performs its basic tasks manually the scope of this
project is to develop and implement a new System which will avoid the problems associated
with the manual processing.

1.6.1 Scope

The new system implements for Omedad Company finance department to oversee and govern
its income, employee payroll system, expenses, credit interest, profit and loss, day book and
assets or capital with the objectives of maximizing profits and ensuring sustainability.

1.6.2 Limitation

This project is limited only to those activities and operations related to the finance management
system for the Addis Ababa branch which the team is intended to deal with and it calculate
only the interest of the credit not the debit interest. We do not add the bill collection of the
companies.

1.7 Significance of the project

There are different bodies that will be benefited from this system. The main beneficiary of this
system is the company itself in which, first, the environment is changed to a computerized
environment, which improves the quality of internal operations like accuracy, timeliness,
reliable, secured, relevant and valuable data usage for the finance department. Secondly they
can reduce the human resource of the office which resulted in minimizing the companies’
expense for paying for them. Thirdly the problem associated with manual processing is
minimized and the quality of work and services became improved. It also increases the

Finance Management System For Omedad Company Page 7

efficiency of the worker on the new system because it is user friendly and they can work their
work effectively.

The other beneficiaries of the system are employees. Ones the new system is implemented,
firstly employees are benefited from the system in such a way that the quality and performance
of their work is improved, the time they spent for manual operation is significantly reduced and
their management and control of their job is improved. In addition to this the employees
efficiency became increased because of they take few time for some as they were using in
manually.

Generally this project reduces work over load, security of data, use of many man power,
Ensure data accuracy, and proper control of the higher officials, reduce the damage of the
machine, minimize, manual data entry, minimize time needed for the various processing,
greater efficiency, better service for Omedad company financial department office workers.
The system generally helps the Omedad company financial department office workers to
clarify their work and automate their work. The system increase document preservation
without need of large area.

1.8 Time scheduling diagram

The time schedule of the project is show below. It includes the phases of requirement analysis,
design, implementation, and testing.

Finance Management System For Omedad Company Page 8

 Fig 1.1 Gantt chart for work breaks down structure

Finance Management System For Omedad Company Page 9

 Chapter two

2 System analysis
System analysis is the way of studying a system with an eye on solving its problem using
computers. It is the most essential part of the development of a project of a system analysis.
System analysis consists of system element, process and technology. It is the detailed study of
the various operations performed by a system and their relationships within and outside of the
system. A key question is: What must be done to solve the problem? One aspect of analysis is
defining the boundaries of the system and determining whether or not candidate system should
consider other related systems.

2.1 Existing system

In the existing system the transactions are done only manually and there are errors due to
carelessness or oversight that may result in loss to the data and as to the organization. For an
organization, time is very important factor. They works manually, unsatisfactory and very
difficult to work because their current work system has many problems such as lack of security
of data, needs manual calculations using paper, excel and calculator, no fast retrieval of data
time, consume large volume of paper work and more man power, waste of too many hardware
materials and lose of their files. All the necessary records of the above management activities
are kept manually on papers and stored in file cabinet.

2.1.1 Problem with the existing system

 Lack of security of data: - all files are kept on cabinets by a box file they are exposed
to theft and other environmental disaster.
 More man power is needed: - requires many numbers of peoples to calculate the
transactions like employees overtime work payment during salary time.

Finance Management System For Omedad Company Page 10

  Time consuming: - as it was manual using paper and Excel it is difficult to generate
daily, monthly and annually report on timely and it may have errors as they work in
quickly.
 Consumes large volume of pare work: - as they were use manual working conditions
the use large number of paper to do all requires tasks.

 Needs manual calculations: - use calculator to calculate then write it on word or in

Excel to file all the data. Due to manual way of handling files. We can’t asses the
calculations accurately. To get the correct result they do a single computation
repeatedly and error are occurs which lead to unnecessary rework.

 Week retrieval of data: - Searching or retrieving for financial information like

employee’s details, expenditures, revenues and others is too much, Time consuming to
get from files on the shelves and file cabinets.

 Tiredness of employees: - as they work manually searching some data is takes too
much time for the employees who assigned on this work and they are unsatisfactory on
the existing system which leads to endanger on the sustainability of the company.

 Work Delay: - mostly to generate the reports like profit and loss, expense, income and
others it takes them too much time. They do not finish on time.

2.1.2 Business rule

The business rules associated with the existing system are as follows.

 Only a unique id is given to the employees.

 Only full time employees can get insurance for their accidental harm that cause their
life endanger when they are working.

Finance Management System For Omedad Company Page 11

  When employees are sick the company covers 80% of their expense and the other 20%
are covered by them.

 If the employees want to join the saving at minimum they should have to save their 5%
of their salary.

 Employees that join the company after 23/ 06 / 2012 can get have only a choice of
pension rather than provident fund. Those who join the company can get the provident
fund or they can change into pension if they want.

2.2 New system

The following are functional and nonfunctional requirements of the proposed new system that
we identified from requirement.

2.2.1 Functional requirements

Functional Requirements are those that refer to the functionality of the system, i.e., what
services it will provide to the user. Statements of services the system should provide how the
system should react to particular inputs and how the system should behave in particular
situations. Our new system performs the following tasks.

 Register employees and handle their details.

 Calculate for the expenses, income, credit interest, and assets or capital of the company
monthly, quarterly and annually.
 Generate reports.
 Compute employee payroll.
 Analyze profit and loss.

 Make day book for each day transactions. Transactions can be income, expenditure,
profit and loss and others.

Finance Management System For Omedad Company Page 12

2.2.2 Non functional requirements
Non functional requirements pertain to other information needed to produce the correct system
and are detailed separately. Constraints on the services or functions offered by the system such
as timing constraints, constraints on the development process, standards, etc.

 User interface: - The system will be implemented using the users interface. The users
are familiar to the system easily.
 Hardware consideration: - the organization should have computers having typical
storage capacity and processing speed.
 Error handling: - When the users of the system interact with the system errors may
appear. To control these inaccuracies the system will generate different messages. Data
errors which are entered in to the system may not be completely avoided but they can
be minimized. To do this, most of the system execution buttons will be controlled
according to the sequence which the user is expected to follow. Or this can be done by
generating different system responses to the input of the users.
 Security: - the system should have a security privilege that secures the system. That
means the system can only accessed by authorized persons and on their privileges. The
administrator of the system monitor over all activity.
 Performance characteristics: - the end user computers should have medium processor
and the server computers should have large processor. It’s measured by its speed of
processor.
 Usability:-The system ability to provide search help is user friendly.
 Performance: -The system works in efficient manner.
 Supportability: - The system ability to make easily to install and maintenance.
 Modifiability or Extensibility: - The system ability to add (unspecified) future
functionality.
 Compensability: - The system ability to compose systems from plug-and-play
components
 Reusability: - The system ability to (re)use in future system.

Finance Management System For Omedad Company Page 13

2.2.3 Use case diagram
The Use case diagram is used to define the core elements and processes that make up a system.
The key elements are termed as "actors" and the processes are called "use cases." The Use case
diagram shows which actors interact with each use case. Actors and their general work
description are listed below:-

 Finance Director
Working closely with his Deputy and the Finance Team, Finance Director has direct
oversight and responsibility over all finance operations. The emphasis of the
departmental director is made in rendering proper financial services and getting
accuracy and integrity in financial status reports including. The major operations in the
system are:
Admin login, Add/Delete/Update/View/Save Employee, Expenditures, Incomes,
Daybook module, Profit and Loss, Summary module

 Accountant
this is the person who is in charge of processing accounts receivable, accounts payable,
and payrolls. Accountants assist in the preparation of financial reports, auditing
documents, revision memorandum, and the monthly closing of the books.

 Clerk

This module performs the following operations in the system. Cashier ensures that all
cash money records are in line with existing cash in the cash desk. This employee
reports to Accountant. The operations of the clerk is Invoicing.

Finance Management System For Omedad Company Page 14

 Finance Management System on Omedad Company

employees
Regestration
*

upadte emloyees
information
*

«uses»
*
manage accounts
*
* *

«uses»

finance manager

«uses»
Employee payroll
*

«uses»

calculate income
«uses»
*

login
«uses»
calculate expense
* «uses»
** *
**
**

generate financial «uses»

accountant reports
*
«uses»

calculate credit «uses»

* interst
«uses»

*
calculate profit «uses»
and loss

*
*
capital
*

*
Clerk

day book

invoice

Fig 2.1 Use case diagram

Finance Management System For Omedad Company Page 15

2.2.4 Use case description

Use case describes a way in which a real world actor interacts with the system. We use the
table format for the interaction between actor and system.

Use Case Login[01]

Name:
Actor: Finance Manager ,Accountant , clerk
Scenario: Login into the system.
Precondition: The account level, user name and password must be correct.
Flow Event: Actor System

1. Fill user name and password

2. Click login button. 2.1 Display login successful
or failed.
3. Repeat step 1 and 2 until 3.1 Repeat step 2.1 until step
Login successful. 2 is over.
4 Enter the page.
Exception If the user name does not exist the system stop login.
Condition
Post condition Main window displayed.

Table 2.1 Use case description for authentication

Finance Management System For Omedad Company Page 16

Use Case Employees Registration [02]
Name:
Actor: Finance Manager
Scenario: To use their as an input in other transactions
Precondition: Use case [01]
Presence of new employees to be registered
Flow Event: Actor System

1.Fill all information of

employees details
2.Save
3. Display registration is
successful

4. failed
4.1 Repeat step 1 until step
2 are over.

Exception The data you entered is incorrect.

Condition
Post condition Main window displayed.

Table 2.2 Use case for employee registration

Use case Name: Update employees detail [03]

Actor : Finance manager
Scenario : To manage the employees details
Precondition : Use case [01] and Use case [02]
Presence of registered employees
Flow event : 1. Update employees’ 2. Display registration is

Finance Management System For Omedad Company Page 17

 data that is needed. successful
3. failed
3.
1 Repeat step 1 until step
2 is displayed.
Exception The data you entered is incorrect.
condition :
Post condition : Main window displayed.

Table 2.3 Use case for update employee details

Use case Name: Manage accounts [04]

Actor : Finance manager
Scenario : To manage accounts that are created and create account on their
privileges
Precondition : Use case [01]
Flow event : 1. Create account by and 2. Display account
give their own privileges and registration is
password. Successful created
Exception

Finance Management System For Omedad Company Page 18

condition : You should fill all blank spaces give a message
Post condition : Main window displayed.

Table 2.4 Use case for managing accounts

Use case Name: Payroll [05]

Actor : Accountant
Scenario : To calculate the employees net pay
Precondition : Use case [01]
Employees should be there in the database
Flow event : 1. Search the employee id 3. Display successfully saved
then get its basic pay, saving if it is saving or successfully
,family deduction ,tax, number updated if it is updating.
of presence in work ,additional
payments and the reduction
from payment to generate the
payroll

Finance Management System For Omedad Company Page 19

 2. Save or update.
Exception Display there is no such id in the database. And you should fill all
condition : blank spaces give a message for the incorrect data placed.
Post condition : Main window displayed.

Table 2.5 Use case for payroll

Use case Name: Income [06]

Actor : Accountant
Scenario : To calculate income
Precondition : Use case[01]
Flow event : 1. From nontax revenues 2. Display successfully saved
such as sales of goods if it is saving or successfully
services, charge and updated if it is updating.
commission.
Exception You should fill all blank spaces give a message for the incorrect
condition : data placed.
Post condition : Main window displayed.

Table 2.6 Use case for income

Use case Name: Expenditure [07]

Actor : Accountant
Finance Management System For Omedad Company Page 20
Scenario : To calculate expenditure
Precondition : Use case[01]
Flow event : 1. To estimate the total expenditure it 2. Display successfully
should get this information. the tax saved if it is saving or
,penalties , basic payment , employees successfully updated if
benefit ,cost of material , equipment it is updating.
expenditure, service expenditure
similar to pay for goods , water and
electric consumption bill
Exception You should fill all blank spaces give a message for the incorrect
condition : data placed.
Post condition : Main window displayed.

Table 2.7 Use case for expenditure

Use case Name: Financial report [08]

Actor : Accountant
Scenario : To generate financial report
Precondition : Use case[01]
It should get information about employee, expenditure, income,
interest, payroll, profit and loss and capital.
Flow event : 1. Generate the report for 2. Display the generated
what we wont records
3. There is no such date.
Return to step 1.
Exception There is no data found in the data base.
condition :
Post condition : Main window displayed.

Table 2.8 Use case for generate financial report

Use case Name: Interest [09]

Actor : Accountant
Scenario : To calculate interest

Finance Management System For Omedad Company Page 21

Precondition : Use case[01]
Flow event : 1. It uses the loans and saving 2. Display calculated results
when we enter save.
Exception You should fill all blank spaces give a message for the incorrect
condition : data placed.
Post condition : Main window displayed.

Table 2.9 Use case for calculate interest

Use case Name: Profit and loss [10]

Actor : Accountant
Scenario : To calculate profit and loss
Precondition : Use case[01]
Flow event : 1. From revenues and 2. Display successfully saved if
expenditure. it is saving or successfully
updated if it is updating.
Exception You should fill all blank spaces give a message for the incorrect
condition : data placed.
Post condition : Main window displayed.

Table 2.10 Use case for calculate profit and loss

Use case Name: Capital [11]

Actor : Accountant
Scenario : To calculate capital
Precondition : Use case[01]
Flow event : 1. From assets and cash. 2. Display successfully saved
if it is saving or successfully
updated if it is updating.
Exception You should fill all blank spaces give a message for the incorrect
condition : data placed.
Post condition : Main window displayed.

Finance Management System For Omedad Company Page 22

 Table 2.11 Use case for capital

Use case Name: Day book [12]

Actor : Accountant ,clerk
Scenario : To show day book
Precondition : Use case[01]
Flow event : 1. Daily transaction they perform 2. Display successfully saved
such as purchased, sales , if it is saving or successfully
profit, loose and other updated if it is updating.
activities
Exception You should fill all blank spaces give a message for the incorrect
condition : data placed.
Post condition : Main window displayed.

Table 2.12 Use case for day book

Use case Name: Invoice [13]

Actor : Clerk
Scenario : To generate invoice
Precondition : Use case[01]
Flow event : 1. Price of the good that are 2. Display successfully saved
received and pay. if it is saving or successfully
updated if it is updating.

Exception Give a message for the incorrect data placed.

condition :
Post condition : Main window displayed.

Table 2.13 Use case for invoice

Finance Management System For Omedad Company Page 23

2.2.5 Sequence diagram
A sequence diagram, in the context of UML, represents object collaboration and is used to
define event sequences between objects for a certain outcome. A sequence diagram is an
essential component used in processes related to analysis, design and documentation. A
sequence diagram is also known as a timing diagram, event diagram and event scenario.

Fig 2.2 sequence diagram for login

Finance Management System For Omedad Company Page 24

 Fig 2.3 sequence diagram for create account

Finance Management System For Omedad Company Page 25

 Fig 2.4 sequence diagram for employee registration

Fig 2.5 sequence diagram for update employee details

Finance Management System For Omedad Company Page 26

 Fig 2.6 sequence diagram for income

Finance Management System For Omedad Company Page 27

 Fig 2.7 Sequence diagram for payroll

Finance Management System For Omedad Company Page 28

 Fig 2.8 sequence diagram for expenditure

Fig 2.9 sequence diagram for profit and loss

Finance Management System For Omedad Company Page 29

 Fig 2.10 sequence diagram for invoicing

Fig 2.11 sequence diagram for generate report

Finance Management System For Omedad Company Page 30

2.2.6 State diagram
A state diagram is a diagram to describe the behavior of a system considering all the possible
states of an object when an event occurs. This behavior is represented and analyzed in a series
of events that occur in one or more possible states. Each diagram represents objects and tracks
the various states of these objects throughout the system.

Fig 2.12 State diagram for login Fig 2.13 State diagram for update employee details

Finance Management System For Omedad Company Page 31

Fig 2.14 State diagram for create account Fig 2.15 State diagram for expenditure

Finance Management System For Omedad Company Page 32

Fig 2.16 State diagram for payroll Fig 2.17 State diagram for profit and loss

Finance Management System For Omedad Company Page 33

Fig 2.18 State diagram for employee registration Fig 2.19 State diagram for invoice

Finance Management System For Omedad Company Page 34

 Fig 2.20 State diagram for generate report

Finance Management System For Omedad Company Page 35

2.2.7 Activity diagram
Activity diagram is a graphical representation of an executed set of procedural system activities
and considered a state chart diagram variation. Activity diagrams describe parallel and
conditional activities, use cases and system functions at a detailed level.

Fig 2.21 Activity diagram for login to account

Finance Management System For Omedad Company Page 36

 Fig 2.22 Activity diagram for account creating

Finance Management System For Omedad Company Page 37

 Fig 2.23 Activity diagram for expenditure

Fig 2.24 Activity diagram for update account

Finance Management System For Omedad Company Page 38

 Fig 2.25 Activity diagram for employee registration

Finance Management System For Omedad Company Page 39

 Fig 2.26 Activity diagram for payroll

Finance Management System For Omedad Company Page 40

 Fig 2.27 Activity diagram for profit and loss

Finance Management System For Omedad Company Page 41

 Fig 2.28 Activity diagram for invoicing

Finance Management System For Omedad Company Page 42

 Fig 2.29 Activity diagram for report

Finance Management System For Omedad Company Page 43

2.2.8 Class responsibility collaboration (CRC)
CRC is collection of standard index cards that have been divided into three sections. A class
represents a collection of similar objects, a responsibility is something that a class knows or
does, and a collaborator is another class that a class interacts with to fulfill its responsibilities.
In other words it is a card is made for each class containing responsibilities (knowledge and
services) and collaborators (interactions with other objects). The cards provide an informal,
intuitive way for group members to work on object design together.

Employee registration
responsibility collaboration
Employee id Employee Payroll
First name Generate report
Middle name
Last name
Gender
Date of Join
Age
Region
Address
Phone no
Basic Salary
Designation

Table 2.14 CRC analysis for Employee registration

Employee Payroll
responsibility collaboration
Employee id Attendance
Basic Pay Employee
Saving Expense
Family Deduction Invoice
Health Deduction Generate report
Tax
No of Presence
Bonus
Over time type
Over time hour
Over time pay
Other additional pay
Additional pay kind
No of Hours

Finance Management System For Omedad Company Page 44

Health Deduction
Penalty Deduction
Other Deductions
Net pay

Table 2.15 CRC analysis for Employee payroll

Expense
responsibility collaboration
Expense Type Employee Payroll
Expense To Cash Invoice
Expense To Check Generate report
Total expenditure

Table 2.16 CRC analysis for Expense

Income
responsibility collaboration
Income Type Employee Payroll
Income by Cash Invoice
Income by Check Generate report
Total income

Table 2.17 CRC analysis for Income

Invoice
responsibility collaboration
Invoice type Employee Payroll
Amount Invoice
Date Generate report

Table 2.18 CRC analysis for Invoice

Finance Management System For Omedad Company Page 45

Generate report
responsibility collaboration
Total employees Employee Payroll
Total income Invoice
Total expenditure Generate report
Total credit Interest
Total capital
Net profit
Description

Table 2.19 CRC analysis for Generate report

Profit and loss

responsibility collaboration
Income Income
Expenditure Expenditure

Table 2.20 CRC analysis for Profit and loss

Capital
responsibility collaboration
Amount by cash
Amount by Asset
Total Amount

Table 2.21 CRC analysis for capital

Day book
responsibility collaboration
Date Income
Income type Expenditure
Income Profit and loss
Expenditure type
Income
Expenditure

Table 2.22 CRC analysis for Day book

Finance Management System For Omedad Company Page 46

 Credit Interest
responsibility collaboration
Date Income
Credit Id
Interest Rate
Interest type
Beginning date
Return date
Interest

Table 2.23 CRC analysis for Interest

2.2.9 Change in case

As we are doing on this project we try to add employee’s image in addition to their other
information. It makes to identify the employees easily in addition to their id. The impact of this
is the workers who work on this system can identify the employees easily. As the number of
the employees increased it is good solution.

2.2.10 Class diagram

A Class diagrams show the classes of the system, their interrelationships (including
inheritance, aggregation, and association), and the operations and attributes of the classes.

In this context, a class defines the methods and variables in an object, which is a specific entity
in a program or the unit of code representing that entity. Class diagrams are useful in all forms
of OOP. The concept is several years old but has been refined as OOP modeling paradigms
have evolved.

In a class diagram, the classes are arranged in groups that share common characteristics. A
class diagram resembles a flowchart in which classes are portrayed as boxes, each box having
three rectangles inside. The top rectangle contains the name of the class; the middle rectangle
contains the attributes of the class; the lower rectangle contains the methods, also called
operations, of the class. Lines, which may have arrows at one or both ends, connect the boxes.
These lines define the relationships, also called associations, between the classes.

Finance Management System For Omedad Company Page 47

Fig 2.30 Detailed class diagram

2.2.11 User interface prototyping

User interface is the junction between a user and a computer  program. An interface is a set
of commands or menus through which a user communicates with a program. The user interface
is one of the most important parts of any program because it determines how easily you can
make the program do what you want.

Finance Management System For Omedad Company Page 48

 Fig 2.31 user interface for login to the system

Finance Management System For Omedad Company Page 49

 Fig 2.32 user interface for the main window

Finance Management System For Omedad Company Page 50

 Fig 2.33 user interface for the employee payroll

Finance Management System For Omedad Company Page 51

 Fig 2.34 user interface for the employee registration

Finance Management System For Omedad Company Page 52

 Fig 2.35 user interface for income

Finance Management System For Omedad Company Page 53

 Fig 2.36 user interface for expenditure

Finance Management System For Omedad Company Page 54

 Fig 2.37 user interface for profit and loss

Finance Management System For Omedad Company Page 55

 Fig 2.38 user interface for credit interest

Finance Management System For Omedad Company Page 56

 Fig 2.39 user interface for day book

Finance Management System For Omedad Company Page 57

 Fig 2.40 user interface for summary report

Finance Management System For Omedad Company Page 58

 Chapter three

System design

3.1 Introduction

Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.

Once the software requirements have been analyzed and specified the software design involves
three technical activities design, coding, generation and testing that are required to build and
verify the software.

The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are
made. These decisions have the final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s requirements into finished
software or a system.

Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software design is
conducted in two steps. Preliminary design is concerned with the transformation of
requirements into data.

As it has been stated in analysis phase the methodology used in developing software for
Omedad company finance department is object oriented methodology in which UML is a tool
used to design the system. This application will bring new sort of integration and flexibility of
financial management system as a result of a great potential application.

The purpose of the system is to store user’s information permanently, performing intended
manipulation on this information; avoid data redundancy when registration takes place. It

Finance Management System For Omedad Company Page 59

improves the quality of internal operations like accuracy, timeliness, reliable, secured, relevant
and valuable data usage for the department. Secondly they can reduce the human resource of
the office which resulted in minimizing the companies’ expense for paying for them. Thirdly
the problem associated with manual processing is minimized and the quality of work and
services became improved. reduces work over load, security of data, use of many man power,
Ensure data accuracy, and proper control of the higher officials, reduce the damage of the
machine, minimize, manual data entry, minimize time needed for the various processing,
greater efficiency, allow to give a better service and make a user friendly system for the
employers who do on the system.

3.1.1. Overview of the system design

This chapter describes the result of the design of the system design carried out during design
phase of the Omedad company finance department. The first section describes the desirable
design goal that the system strives to achieve and describing the quality of the system that we
shall use optimize derived from non functional requirements.

The design goal is stated clearly in such a way that making design decisions will be in light of
these goals. The second section which is the most important one describes the system under
development in terms of system decomposition, technology choices, deployment diagram, and
persistence modeling for object oriented database system and access control.

3.1.2 Design goals

The design goals represent the desired qualities that the system should have and provide a
consistent set of criteria that would be taken into consideration when making design decisions.
The following are outlined to be the design goals of Omedad company finance department
system development.

Robustness: - The system should be designed in such a way that users cannot proceed having
entered invalid input or data in all cases of interacting with the system.

Security: - The system should be designed in such a way that every user is prompted for
username and password to access the system’s database or some functionality with only
permission to the authorized body to use the system.

Finance Management System For Omedad Company Page 60

Extensibility: - The system should be able to entertain the addition of any new services related
to welfare distribution to the needy and management of the employees

Usability: - The system should have a simple and easy graphical interface that users can
understand quickly.

Availability: -The system should be available 100% of the time during all working hours.

Portability:-The system should be well suited to work on any machine running windows
operating system.

Performance: -

 The main users of the systems are finance manager accountant and clerk. The finance
manager can register the employees and give account and manage those accounts and
employees details. Accountants make employee payroll and day booking, generate
report, and calculate expense, income, profit and loss, credit interest and capital. The
clerk can make only invoicing for the receivable and payable tasks.
 Speed and space requirement:-The system needs a Desktop computer having
minimum of 256MB of RAM and minimum of 80GB hard disk capacity. And also a
database server computer having more than1GB of RAM size and high Storage
capacity and processing speed. In addition to this other fast network material is
needed to increase the performance of the system.

Compatibility: - Our system has compatible with windows because we get easily and users
are customizing with the software.

Maintenance Criteria:-

 Modifiability: - The system is modifiable when the organization become large and
its working style changed.

Finance Management System For Omedad Company Page 61

  Readability: - The code of the system is easily understood by only programmer
which knows programming languages like JAVA and others. And by reading
information inside comments of the code in system is easily understood.

3.2 Current software architecture

In spite of its organized administrative structure, Omedad finance department has no
computerized system for handling the data of support it to produce employee payroll, generate
reports, and calculate the income, expenditure profit and loss, credit interest, capital. In order to
handle or process the data for above mentioned categories of tasks there is the manual system
that is deployed within the organization. The description is disclosed as follows.

Whenever a company recruits new employees finance manager register the employee in the
system. The employee can get the id that describes his personal information. If the employee
information is needed to be changed the finance managers update their details. The finance
manager authenticates users by giving access privileges.

The accountant makes an employee’s payroll, calculate the companies’ income with their
details of the income such as from sales of goods and service. The expenditure of the company
expense is from the following tasks like purchasing goods, employee’s salary and other
expenses. They calculate the credit interest, profit and loss from the income and expenditure
that leads to estimate the company status in the business. The capital that the company holds
weather it is in asset or in cash. See the day book of the daily tail records.

3.3 Proposed software architecture

After identifying the problems of the current system of the current resident file handling
system and decentralization administrative system, the aim of proposed is to develop an
automated and desktop application which will resolve the problems of the current system. The
new system has connection stability. The system has centralized database and repository
architecture.

Finance Management System For Omedad Company Page 62

3.3.1 Subsystem decomposition
Subsystem decomposition will help reduce the complexity of the system. The subsystem can
be considered as package holding related classes or objects any system can be decomposed in
to different sub system based on the functional services. A subsystem is characterized by the
services it provides to other sub system. Services are a set of related operations that has a
common purpose. In order to make the implementation easy and manageable, the newly
developed system decomposed in to the following smaller subsystems.

Finance Management Subsystem: - In this subsystem manage all information, give the
service, control payment and fulfill infrastructure when needed.
Finance Manager: - Register the employees, update their details and manage accounts.
Accountant: - calculate employee payroll, calculate profit and loss, calculate income, calculate
expenditure, calculate credit interest
Clerk: - make an invoicing for the payment and receivables.

The following diagram gives an overview of the system decomposition together with the
relation of subsystems.

Finance Management System For Omedad Company Page 63

 Finance Management
System

«subsystem»
Employee Registration
«subsystem»
Day Book

«subsystem»
Emloyee Payroll
«subsystem»
Calculate Capital

«subsystem»
Login «subsystem»
Calculate Profit and
Loss

«subsystem» «subsystem» «subsystem» «subsystem»

«subsystem»
Calculate Income Calculate Generate Report Calculate Credit
Invoice
Expenditure Interest

Fig 3.1 layered representation of the system

Finance Manager

«subsystem» «subsystem» «subsystem»

Manage Accounts Register Employees Update employee Information

Fig 3.2 Decomposition of finance manager

Finance Management System For Omedad Company Page 64

 Accountant

«subsystem» «subsystem»
Employee Payroll Day Book

«subsystem» «subsystem»
Calculate Calculate
Expenditure Capital
«subsystem»
Calculate
Interest

«subsystem»
Calculate Income
«subsystem» «subsystem»
Generate Financial Calculate Profit
Report and Loss

Fig 3.3 Decomposition of accountant

Clerk

«subsystem»
Invoicing

Fig 3.4 Decomposition of clerk

3.3.2 Component diagram

A component is a container of logical elements and represents things that participate in the
execution of a system. Components also use the services of other components through one of
its interfaces. Components are typically used to visualize logical packages of source code

Finance Management System For Omedad Company Page 65

(work product components), binary code (deployment components), or executable files
(execution components).

The component model illustrates the software components that will be used to build the
system. We build it up from the class model and written from scratch for the new system.
Components are high level aggregations of similar software pieces, and help us in providing
provide a’ black box’ building block approach to software construction.

Empoloyee Registeration

Manage accounts
Finance Manager

Update Employee Information

Encryption
Security <<infrasracture>>
Access control

Employee Payroll

Calculate Income
Accountant

Calculate Expenditure

Calculate profit and Loss Persistance <<infrastructure>>

Persistance

Calculate Credit Interest

{JDBC}

Calculate Capital

Fnance <<Database>>

Generate Financial Reports

Database
* *

* *
Day Book

Clerk
Invocing

Fig 3.5 Component modeling

Finance Management System For Omedad Company Page 66

3.3.3 Deployment diagram
Deployment modeling is used to show the hardware of the system, the software that is installed
in the hardware and also the middleware that is used to connect the disparate machines to one
and other. It also shows how the software and the hardware components work together.

In this Diagram components of the system will be wired showing that there is relation among
components, management of the system, database and operations performed on databases such
security issue. This in some extent shows which component or objects will be accessed by
whom and what type of security infrastructures it is using. The diagram is simulated below.

 Node: represents a computer. Drawn as a 3-D box.

 Connection: represents a communication channel between machines. Drawn as a

straight line.

 Component: represents a software component. Drawn as a box with smaller boxes on

left edge.

 Dependency: indicates that one component makes use of another component. Drawn as
dashed line with a stick arrowhead.

User Database

JDBC
Database System
GUI

Fig 3.6 deployment diagram

Finance Management System For Omedad Company Page 67

3.3. 4 Persistence modeling for object oriented database

Object persistence is one of the most fundamental services provided by an object OODBMS. 
A persistent object is an object that is always available and an object's state will remain
unchanged from one invocation to the next, as opposed to an object that is no longer available.
OODBMS provide the recovery services that ensure persistence objects survive any kind of
system failure.  There are two methods that the OODBMS uses to access persistent objects,
virtual memory address pointers and hash tables.  A persistent object will always be ready to be
invoked, and its state can and will be preserved and survive any kind of system failure. 

Fig 3.7 persistence model diagram

Finance Management System For Omedad Company Page 68

3.3.5 Access control
There are users of the Omedad finance department system having different level of accessing
privileges. Accordingly to the following access control list is given for the system. Each
column name specifies the class whose functions are to be protected and the rows specify users
whose access is to be controlled. If there are operations (of the class specified in the
corresponding column) in a given cell (column and row intersection) then the user in that given
row is said to be given access to these operations.

Class Actors
Functionalities

Finance Manager Accountant Clerk

Account AddUser () Login() Login()
Changepassword() Changepassword()
Change Account()
RemoveAccount()
EmployeeRegestration Register()
Update() - -
EmployeePayroll - Calculate() View()
View()
Expenditure - Calculate()
View() View()
Income - Calculate()
View() View()
ProfitandLoss - Calculate()
View() View()
Report - - Generate()
Capital Add() View()
- View()
Update()
DayBook - View() View()
Invoice - - Print()

Table 3.1 Access control represents level of access privileges.

Finance Management System For Omedad Company Page 69

 3.4 Conclusion and recommendation

3.4.1 Conclusion
Omedad company financial management System is one of the main management system found
in the company management. After we have completed the project we are sure the problems in
the existing system would overcome. The Finance management system process made
computerized to design a user friendly system, reduce the human resource of the office,
minimize the loss of records or data, minimize the time consuming to search for records from
the file and make it easy to search what we want, to increase the security of the data by
authentication and to increase to the work efficiency of the department. The problems, which
existed in the earlier system, have been removed to a large extent. And it is expected that this
project will go a long way in satisfying users’ requirements.

Through various challenging, now we are coming to the end of this project. We face those
different challenges made possible by the cooperation. In developing this project we
contributed our full capability with maximum interest and get ways toward developing a
project.

3.4.2 Recommendation
The system we have developed is a desktop application it needs a skilled person to work with
the system. So, we recommend the system should be entitled to the responsible and skilled
person. We highly recommend the system should be kept in highly safe and favorable
condition.

Finance Management System For Omedad Company Page 70

Reference
The resources that we used in this project are listed below

1. Ivan Marsic, Software engineering book, pp 106 – 108, (2012)

2. Understanding about financial management system
http://searchfinancialapplications.techtarget.com/definition/financial-management-
system
3. Agile development for use case diagram
http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
4. Agile development for activity diagram
http://www.agilemodeling.com/artifacts/activityDiagram.htm
5. Agile development for user interface prototyping diagram
http://www.agilemodeling.com/artifacts/uiPrototype.htm
6. Agile development for class diagram
http://www.agilemodeling.com/artifacts/classDiagram.htm
7. Agile development for component diagram
http://www.agilemodeling.com/artifacts/componentDiagram.htm
8. Agile development for deployment diagram
http://www.agilemodeling.com/artifacts/deploymentDiagram.htm
9. Agile development for sequence diagram
http://www.agilemodeling.com/artifacts/sequenceDiagram.htm
10. Agile development for business rule
http://www.agilemodeling.com/artifacts/businessRule.htm
11. Agile development for change cases
http://www.agilemodeling.com/artifacts/changeCase.htm

Finance Management System For Omedad Company Page 71

 12. Agile development for CRC modeling
http://www.agilemodeling.com/artifacts/crcModel.htm
13. Others for UML http://creately.com/blog/diagrams/uml-diagram-types-examples/

Finance Management System For Omedad Company Page 72