University of Sargodha - ShiningStudy · IT Hub Sargodha Version: 1.0 Accounts Management System Date: march 10.3.2017 IT-HUB 2

IT-Hub Sargodha Version: 1.0

Accounts Management System Date: July 10 2017

IT-Hub 1

Department of Computer Science &

Information Technology

University of Sargodha

Accounts Management System

version 1.0

IT Hub Sargodha Version: 1.0

Accounts Management System Date: march 10.3.2017

IT-HUB 2

Table of Contents

CHAPTER 1: FINAL PROJECT PROPOSAL ......................................................................... 5

1.1. PROJECT TITLE: ..................................................................................................................... 5 1.2 INTRODUCTION ...................................................................................................................... 5 1.3. PROJECT OVERVIEW STATEMENT: ......................................................................................... 5 1.4. PROJECT GOALS & OBJECTIVES: ........................................................................................... 6

1.5. HIGH-LEVEL SYSTEM COMPONENTS: ..................................................................................... 6 1.7. EXCLUSIONS: ........................................................................................................................ 7 1.8. APPLICATION ARCHITECTURE: .............................................................................................. 7

1.10.1. Hardware and Software Requirements:...................................................................... 7

1.11. TOOLS AND TECHNOLOGIES USED WITH REASONING: .......................................................... 7 1.11.1 Front-End /Back-End technologies.............................................................................. 7

1.11.2. Tools ............................................................................................................................ 8

CHAPTER 2: FIRST DELIVERABLE ...................................................................................... 9

2.1. PROJECT/PRODUCT FEASIBILITY REPORT .............................................................................. 9 2.1.1. Technical Feasibility ..................................................................................................... 9 2.1.2. Operational Feasibility ................................................................................................. 9

2.1.3. Economic Feasibility .................................................................................................... 9 2.1.4. Schedule Feasibility ...................................................................................................... 9

2.1.5. Specification Feasibility................................................................................................ 9 2.1.6. Information Feasibility ................................................................................................. 9

2.1.7. Motivational Feasibility ................................................................................................ 9 2.1.8. Legal & Ethical Feasibility ........................................................................................... 9

2.2. PROJECT/PRODUCT SCOPE .................................................................................................... 9 2.3. PROJECT/PRODUCT COSTING .............................................................................................. 10

2.3.1. Project Cost Estimation by Function Point Analysis .................................................. 10

2.3.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model) ............ 11 2.3.3. Activity Based Costing ................................................................................................ 12

2.4. TASK DEPENDENCY TABLE ................................................................................................. 12 2.5. CPM - CRITICAL PATH METHOD ......................................................................................... 13

2.6. GANTT CHART ..................................................................................................................... 15 2.7. INTRODUCTION TO TEAM MEMBER AND THEIR SKILL SET .................................................... 15 2.8. TASK AND MEMBER ASSIGNMENT TABLE ........................................................................... 15

2.10. TOOLS AND TECHNOLOGY WITH REASONING .................................................................... 16 2.11. VISION DOCUMENT ........................................................................................................... 17

Introduction: ......................................................................................................................... 17 Scope and vision: .................................................................................................................. 17

2.12. RISK LIST .......................................................................................................................... 17 2.13. PRODUCT FEATURES/ PRODUCT DECOMPOSITION ............................................................. 17

CHAPTER 3: SECOND DELIVERABLE FOR OBJECT ORIENTED APPROACH ...... 18

3.1. INTRODUCTION: .................................................................................................................. 18 3.2. EXISTING SYSTEM: .............................................................................................................. 18



IT-HUB 3

3.3 SCOPE OF THE SYSTEM: ........................................................................................................ 18 3.4 SUMMARY OF REQUIREMENTS: (INITIAL REQUIREMENTS): .................................................. 18

3.5 EXTERNAL ENTITIES ............................................................................................................ 19 3.10 HIGH LEVEL USE CASE DIAGRAM: ..................................................................................... 22 3.11 ANALYSIS LEVEL USE CASE DIAGRAM: ............................................................................. 23 3.12USECASE DESCRIPTION ....................................................................................................... 24

CHAPTER 4: THIRD DELIVERABLE FOR OBJECT ORIENTED APPROACH .......... 29

4.1. DOMAIN MODEL ................................................................................................................. 29 4.2. SYSTEM SEQUENCE DIAGRAM ............................................................................................ 30 4.3. SALESMAN SEQUENCE DIAGRAM: ....................................................................................... 31 4.4. ADMIN SEQUENCE DIAGRAM .............................................................................................. 32

4.5. DESIGN CLASS DIAGRAM .................................................................................................... 33 4.6. STATE CHART DIAGRAM ...................................................................................................... 34 4.7. ACTIVITY DIAGRAM ............................................................................................................ 35

CHAPTER6: 4TH DELIVERABLE (USER INTERFACE DESIGN) ................................... 39

6.1. SITE MAPS .......................................................................................................................... 39

6.29 TRACE-ABILITY MATRIX .................................................................................................... 54

CHAPTER 7: 5TH DELIVERABLE (SOFTWARE TESTING) ............................................ 55

7.1 TEST PLAN ............................................................................................................................ 55

7.2.1....................................................................................................................................... 55



IT-HUB 4

List of Figures

Figure 1 Gantt Chart ...................................................................................................................... 7

Figure 2 Draw the Network Diagram .......................................................................................... 13

Figure 3 Newtwork diagram ........................................................................................................ 14

Figure 4 Gantt Chart .................................................................................................................... 15

Figure 5 High Level Use Case Diagram ...................................................................................... 22

Figure 6 Analysis Level Use Case Diagram ................................................................................ 23

Figure 7 Domain Model ............................................................................................................... 29

Figure 8 System Sequence Diagram ............................................................................................ 30

Figure 9 Salesman Sequence Diagram ........................................................................................ 31

Figure 10 Admin Sequence Diagram ........................................................................................... 32

Figure 11 Design Class Diagram ................................................................................................. 33

Figure 12 State Chart diagram ..................................................................................................... 34

Figure 13 Activity Diagram ......................................................................................................... 35

Figure 14 Activity Diagram 2 ...................................................................................................... 36

Figure 15 Activity Diagram 3 ...................................................................................................... 37

Figure 16 Entity Relationship Diagram ....................................................................................... 38

Figure 17 Site Maps ..................................................................................................................... 39



IT-HUB 5

Chapter 1: Final Project Proposal

1.1. Project Title:

Account Simple

1.2 Introduction

Account Simple is designed to facilitate the business to manage its accounts in an efficient way.

It could be any type of business who wants to manage its account.

This project can manage accounts, expenses, income, employee payrolls, bank accounts and can

generate profit and loss reports on annually, monthly and daily basis. It is an online account

management solution and any businessman can Sign up there and he will be able to manage its

accounts. After Sign up and he will get username and password and after logging in he can add

employee data, suppliers data, customer data, banks data and afterwards can manage all the

business transactions throughout the business

1.3. Project Overview statement:

Project Title: Departmental store management system Project Manager: Muhammad Muntazir Mehdi Bukhari

Project Members: WaqarAdil, Hassan Ali Shah, Usama

Name Registration # Email Address Signature

WaqarAdil [email protected]

Hassan Ali Shah [email protected]

Usama [email protected]

Project Goal:

The goal of this system is to develop Account management system. It will handle all the

accounts related operations of the business Objectives:

Sr.#

1 The system will manage accounts of many businesses at the same time

2 Any businessman can sign up online and he will be able to manage the accounts online

3 Manage expense and check profit and loss.

4 Generate annual report, customer report and project reports.

5 Generate invoices

6 Manage bank accounts

7 Manage Employess payrolls.

8 Add delete or update expenses

9 Add delete or update income

Project Success criteria:

The project’s success is based on following criteria:

• Adaptability: The system should be able to adjust to new conditions.

• Availability: The system ensures 24/7 availability.

• Reliability: The system functions according to the stated conditions.

mailto:[email protected]

mailto:[email protected]



IT-HUB 6

• Response time: The system must have a fast response time.

• Usability: The system provides ease of use, effectiveness, efficiency, learn ability and an overall

users’ satisfaction in addition to these all system will perform all the task mentioned above.

Assumptions, Risks and Obstacles:

• It is assumed that the team members will cooperate and work seriously on this project.

• It is assumed that the system would be accessible across all global locations through the Internet.

Non availability of the Internet would be one of the major obstacles.

• It is assumed that the user is familiar with Internet and World Wide Web navigational tools. The

users who are not familiar with these tools would face difficulty to use the system.

Users will require special training how to use the functionalities of the system. The level of training

depends on the role of the users.

Organization Address (if any):

IT-hub, 113/3, Stadium road, Sargodha

Type of project: Research Development

Target End users:

• Managers and administrator of company/organization

Development Technology: Object Oriented Structured

Platform: Web based Distributed

Desktop based Setup Configurations

Other_____________________

Approved By:

Date:

1.4. Project Goals & Objectives:

1.4.1. Goals: Main goal of this system is to provide an online account management solution to any business.

Business owner doesn't need to install any software or buy expensive systems he can manage his

account with any system having internet and web browser any time any where.

1.4.2. Objectives: To develop an effective and transparent departmental store management system for achieving

following objectives:

i. To manage and maintain Accounts of business

ii. To maintain bank accounts details

iii. To manage customer’s transactions

iv. To manage and maintain suppliers transactions

v. To maintain annual, customer and expense reports

vi. To generate profit and loss reports

1.5. High-level system components:

i. Manage and maintain bank accounts

ii. Manage and maintain expenses

iii. Generate customer receipts

iv. Manage accounts

v. Generate and maintain reports

vi. Manage employee payrolls, customers and suppliers transactions



IT-HUB 7

1.6. List of optional functional units: Purchasing management

1.7. Exclusions:

It is only an account management system. Which can only maintain and manage accounts related

tasks of any business.

1.8. Application Architecture:

3 Tier Architecture is being used in our system.

1.9. Gantt chart:

Figure 1 Gantt Chart

1.10. Hardware and Software Specification:

1.10.1. Hardware and Software Requirements:

• Operating System: Windows 10, 7, Vista

• Web browser with internet connections

1.10.2. Hardware Specification:

• Processor: x86 compatible processor

• RAM: 512 MB or greater

• Hard Disk: 20 GB or greater

• Monitor: VGA/SVGA

• Keyboard: 104 keys standard

• Mouse: 2/3 button. Optical/ Mechanical.

1.11. Tools and technologies used with reasoning:

1.11.1 Front-End /Back-End technologies

1.11.1.1. Front-End:

i. HTML

a. It is used to generate web pages. HTML, an initialism of Hypertext Markup

Language, is the predominant markup language for web pages. It provides the



IT-HUB 8

means to describe the structure of text based information in a document by

denoting certain text as headings, paragraphs, list and so on.

ii. JAVASCRIPT

a. It is a scripting language most often used for client side web development. It is a

dynamic, weakly typed, prototype based language with a lot of functions.

iii. CSS

a. CSS is used to design for front end designing. With the help of CSS we can make

our webpages more attractive and eye catching.

1.11.1.2Back-End:

• My SQL

My SQL is used to access the database. SQL stands for structured query language and is

used to perform different operations on the data stored in database.

• PHP

PHP is a technology that lets you mix regular, static HTML with dynamic generated

HTML. PHP receive any process request from HTML and give the result to HTML after

processing to show the result.

1.11.2. Tools

• PHP Storm

• XAMPP

• Google chrome



IT-HUB 9

Chapter 2: First Deliverable

2.1. Project/Product Feasibility Report

There are many types of feasibilities:

2.1.1. Technical Feasibility Our project is technically feasible because it is an account management system which can

manage accounts of any business. We have all technical skills needed to design this system. We

have the ability to design an attractive front end for the end user and a proper back end to make

the system efficient.

2.1.2. Operational Feasibility

The system we are going to design is operationally feasible.

2.1.3. Economic Feasibility

Economic feasibility can be divided into two parts; cost estimates and benefit estimates. Cost

estimates can further be alienated into development or acquisition costs (one time) and

maintenance and operation costs (ongoing). Benefit estimates enclose tangible benefits and

intangible benefits. Tangible benefits would include reduced costs and increased revenues.

However, information quality, job satisfaction, and external standing are examples of intangible

benefits. According to the skill cost of team members and cost estimation our project is

economically feasible.

2.1.4. Schedule Feasibility

We have much time to develop this project. To efficiently utilize our time we have assigned a

limited time to each task/phase to complete out project on time.

2.1.5. Specification Feasibility

All requirements are clear. All features and components are well known.

2.1.6. Information Feasibility

System is very reliable. It can properly manage departmental store and generate accurate reports

of each transaction.

2.1.7. Motivational Feasibility

All information about the system is available. We can motivate the team members to develop an

acceptable and efficient management system.

2.1.8. Legal & Ethical Feasibility

It is a management system that is designed to manage departmental stores. This will be a useful

system. So there are no legal or ethical issues.

2.2. Project/Product Scope

Scope of this system can be defined by mentioning the system requirements. This system is

beneficial for maintaining and managing accounts of any business. The system will keep record

of all transactions. It will manage income ,expenses, bank accounts and customer transaction.



IT-HUB 10

End user of the system will be an admin who has to register himself and then login to work with

the system.

The admin will be given privileges to view accounts, add new customer and supplier, add bank

accounts details and manage income and expense of the business. The system will generate

customer receipts and profit and loss reports.

2.3. Project/Product Costing

2.3.1. Project Cost Estimation by Function Point Analysis

Information domain values are defined in the following manner:

To compute function points (FP), the following relationship is used:

FP est. = 91 * [0.65 + 0.01 * (28)]

FP est. = 91 * [0.65 + 0.01 * 28]

FP est. =84.63

Type of

component

Low Average High Total

External Input 0*4=0 5*0=0 5*6=30 30

Internal Output 6*0=0 0*3=0 6*3=18 18

External Inquire 2*5=10 0*5=0 4*0=0 10

Internal logical

Files

0*6=0 1*17=17 0*14=0 17

External

Interface

File

0*2=0 2*8=16 0*12=0 16

Total 91

Serial # Complex Technology Term Scale

1 Data Communication 0

2 Distributed data processing 0

3 Performance 4

4 Heavily used configuration 2

5 Transact rate 1

6 Online data entry 0

7 End-user Efficiency 4

8 Online update 0

9 Complex Processing 3

10 Reusability 3

11 Installation ease 4

12 Operational ease 4

13 Multiple Sites 0

14 Facilitate change 3

Sum(Fi) 28



IT-HUB 11

2.3.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model)

Basic COCOMO

Type Effort Schedule

Organic PM= 2.4 (KLOC)1.05 TD= 2.5(PM)0.38

Semi-Detached PM= 3.0 (KLOC)1.12 TD= 2.5(PM)0.35

Embedded PM= 2.4 (KLOC)1.20=2.4(6)1.05=15.12

TD= 2.5(PM)0.32=2.5(15.12)0.38=14.364 PM= person-month (effort)

KLOC= lines of code, in thousands

TD= number of months estimated for software development (duration)

Intermediate COCOMO

Type Effort Organic PM= 2.4 (KLOC)1.05 x M

Semi-Detached PM= 3.0 (KLOC)1.12 x M

Embedded PM= 2.4 (KLOC)1.20 x M

PM= person-month

KLOC= lines of code, in thousands

M.- reflects 15 predictor variables, called cost drivers

The schedule is determined using the Basic COCOMO schedule equations.

People Required = Effort / Duration



IT-HUB 12

2.3.3. Activity Based Costing

Activity Cost

Feasibility Report

1000

Cost Estimation by Function Point Analysis 2000

Cost Estimation by COCOMO Model 2000

Activity based Costing 2000

Critical Path Method

3000

Task Dependency and Duration

2000

Vision Document

1000

Risk List

500

Allocate Requirement

500

Design Interface

10000

Modeling

15000

Test and Evaluate

5000

Improve Test

3000

Show Result

4000

Total Cost 49000

2.4. Task Dependency Table

Task# Task Dependencies

T1 Proposal None

T2 Feasibility Report T1

T3 Cost Estimation T2

T4 System Specification and

Analysis

T2

T5 Domain Model T1,T2

T6 Allocate Requirements None

T7 Application Development T4.T5

T8 User T7

T9 Processing T7,T8

T10 Testing T9

T11 Showing T7,T8,T9,T10



IT-HUB 13

2.5. CPM - Critical Path Method

2.5.1. Specify the Individual Activities

Individual activities are as follow:

2.5.1.1. Planning

2.5.1.2. Analysis

2.5.1.3. Logical design

2.5.1.4. Physical design

2.5.1.5. Testing

2.5.1.6. Implementation

2.5.1.7. Deployment

2.5.2. Determine the Sequence of the Activities

All activities are dependent on each other like, first planning and then go to second activity

which is named as Analysis. And then logical designing after it physical designing, then testing it

all and then deployment.

2.5.3. Draw the Network Diagram

4. Estimate Activity Completion Time

Activity Duration ES EF LS LF TS FS

Planning

(A) 5 0 5 0 5 0 0

Analysis

(B) 4 0 4 4 8 4 3

Logical

designing

(C)

8 5 13 5 13 0 0

Physical

designing

(D)

7 5 12 6 13 1 1

Testing

(E) 7 0 7 6 13 6 6

Deploy-

ment (F) 4 13 17 13 17 0 0

B C D E F A

Figure 2 Draw the Network Diagram



IT-HUB 14

2.5.4 Identify the Critical Path

The critical path is the longest-duration path through the network. The significance of the critical

path is that the activities that lie on it cannot be delayed without delaying the project. Because of

its

impact on the entire project, critical path analysis is an important aspect of project planning.

Critical path is: (A,B,C,D,E,F)

6. Update CPM Diagram

Activity Immediate Predecessor Duration (Weeks)

A None 1

B None 1

C A 3

D A, B 4

E None 4

F C, D, E 5

G F 3

The critical path is:

A, C, F, G

D

E

B

A C

F G End Start

Figure 3 Newtwork diagram



IT-HUB 15

2.6. Gantt chart

Figure 4 Gantt Chart

2.7. Introduction to Team member and their skill set

Name Roll No Skill

WaqarAdil MITF15M99 • HTML,

CSS,PHP,java script

Hassan Ali Shah MITF15M05 • HTML,

CSS,PHP,Java script

Usama MITF14M27 • HTML

• CSS,PHP,Java script

2.8. Task and Member Assignment Table

Task# Task Dependencies

T1 Proposal None

T2 Feasibility Report T1

T3 Cost Estimation T2

T4 System Specification and

Analysis

T2

T5 Domain Model T1,T2

T6 Allocate Requirements None

T7 Application Development T4.T5

T8 User T7

T9 Processing T7,T8

T10 Testing T9

T11 Showing T7,T8,T9,T10

Consider the set of activities shown in figure. This table shows activities, their duration, and

activity interdependencies. From figure, you can see that Task T3 is dependent on Task T2. This

means that T2 must be completed before T3 starts. For example, T1 might be the preparation of a



IT-HUB 16

component design and T3, the implementation of that design. Before implementation starts, the

design should be complete.

Activity bar Chart

Allocation of People to Activities:

T1 Hassan

T2 Waqar

T3 Hassan

T4 Usama

T5 Waqar

T6 Waqar

T7 Usama

T8 Hassan

T9 Hassan

T10 Usama

T11 Waqar

2.10. Tools and Technology with reasoning There are following tools and technologies that are used in our system:

Tools:

• MS Visio Professional:

We used Visio for ERD and Sequence diagram.

• MS Project Professional;

We used MS Project for Gantt chart.

• MS word

For project documentation

• Not pad++/Bracket( for coding)

• Web Server - Apache web server or other who concern with PHP codes or scripts. It is

basically used to run the PHP code or file on browser.

• Web-browsing software-Mozilla Firefox, Internet Explorer or other

• XAMPP- WIN-32-1.6.3a

Technologies:

PHP – It is used for back end tools for the system.

MYSQL - Used to maintain the database. So, you can call it to back-end of system.

HTML & CSS &Bootstrap-These are used for font end because they sport to produce good

front end .Bootstrap used for responsiveness.



IT-HUB 17

2.11. Vision Document

Introduction:

This account management system is designed to facilitate the business to manage its accounts in

an efficient way. It could be any kind of business who wants to manage his accounts.

Scope and vision:

The system will be utilized by any business owner. End user of the system is an admin who will

have the access to the system after logging in. The admin will be able to add new bank accounts

details, add new customer, supplier and employee . He can add delete or update income , and

expenses. He can add delete or update his interbank transactions and trace them. He can create

customers invoices and can generate reports of expense, profit and loss report. These reports will

contain all information in detail about each entity.

The system will minimize the problems of record keeping, reports generation and business

progress checking.

2.12. Risk List

We may encounter following risks:

• Short time

• Editing Cost

2.13. Product Features/ Product Decomposition

Our product features are as follows:

Accounts management system

• Easy to use

• Generate fine and accurate result

• Manages profit and loss reports

• Create customer invoices

• Manage bank transactions



IT-HUB 18

Chapter 3: Second Deliverable for Object Oriented Approach

3.1. Introduction:

Account Simple is designed to facilitate the business to manage its accounts in an efficient way.

It could be any type of business who wants to manage its account.

This project can manage accounts, expenses, income, employee payrolls, bank accounts and can

generate profit and loss reports on annually, monthly and daily basis. It is an online account

management solution and any businessman can Sign up there and he will be able to manage its

accounts. After Sign up and he will get username and password and after logging in he can add

employee data, suppliers data, customer data, banks data and afterwards can manage all the

business transactions throughout the business

3.2. Existing System:

On existing system all the accounts details are on records books and done manually including

invoices ,sales ,orders and etc.

3.3 Scope of the System:

Scope of the System

The system will be utilized by any business owner. End user of the system is an admin who will

have the access to the system after logging in. The admin will be able to add new bank accounts

details, add new customer, supplier and employee . He can add delete or update income , and

expenses. He can add delete or update his interbank transactions and trace them. He can create

customers invoices and can generate reports of expense, profit and loss report. These reports will

contain all information in detail about each entity.

The system will minimize the problems of record keeping, reports generation and business

progress checking.

3.4 Summary of Requirements: (Initial requirements):

The System will be operated by an admin or accountant. He will manage all activities performed

by the system.

3.4.1 Registration:

In order to perform further action admin or accountant will need to first register. Admin will

enter his credentials to register him.

3.4.2 Login: After registration admin or accountant will enter his user name and password to log in.

3.4.3 Admin Interface:

From admin interface, there will be a dashboard having information about sales, expenses,

banks accounts and profit and loss to perform. There will be buttons for creating new invoice,

new expense, new payment, new receipt and payrolls. He can check daily weekly and monthly



IT-HUB 19

sales reports of business. He can generate profit and loss reports and other reports for other

financial activities.

3.4.4 Company:

After clicking on Company on admin interface admin will be redirected here. It will be a form

through which admin can add all the details of the company Like business details, accounting

and tax details, Bank details and business owner details

3.4.5 Customer:

After clicking on Customer on admin interface admin will be redirected here. It will be a page on

which admin can see customer information like name, reference, Telephone etc. Admin can also

Add, delete or Update client from here.

3.4.6 Supplier:

After clicking on Supplier on admin interface admin will be redirected here. It will be a page on

which admin can see Supplier information like name, reference, Telephone etc. Admin can also

Add, delete or Update Supplier information from here

3.4.7 Bank:

After clicking on Bank on admin interface admin will be redirected here. It will be a page on

which admin can see Bank accounts information like Bank name, reference, Account Number,

SORT Code etc. Admin can also Add, delete or Update Bank information from here

3.4.8 Analysis List:


which admin can see the types of expenses here. Admin can also Add, delete or Update expenses

from here.

3.4.9 Payroll:

After clicking on Payroll on admin interface admin will be redirected here. It will be a page on

which admin can see Employees information like name, reference, start date and leaving date

Admin can also Add, delete or Update Employees information from here.

3.4.10 Income:

After clicking on Income on admin interface admin will be redirected here. It will be a page on

which admin can see all the business transactions with supplier and customers. He will create

invoices for clients. There will be buttons to add new transaction and Generate reports

3.4.11 Expense:


which admin can see expense report. Admin can also Add, delete or Update expenses from here

3.4.11 Generate report:

System will generate some reports from where admin can check the status of the company

account, expense, accounts and profit or loss.

• System will generate weekly monthly and annual sales report.

• System will generate reports of debt and credit of business

• System will generate annual report showing profit and loss year and month vise.

• System will generate expense report to show expense of business

3.5 External Entities

Main external entities is only one in this system:

• Admin

3.6 Capture “shall” Statement:



IT-HUB 20

Para# Initial Requirements

1.0 Shall system give user interface and log in option too.

1.0 Shall system Manage expense and check profit and loss.

1.0 Shall System Generate annual report, Monthly reports, Daily reports

1.0 Shall System Manage Bank Accounts

1.0 Shall System manage Income record

1.0 Shall system manage expense record

1.0 Shall system generate profit and loss reports

3.7 Allocate Requirements:

Para# Initial Requirements Use case name

1.0 Admin Shall register himself UC_Registration

1.0 Admin shall login UC_Login_Admin

1.0 He shall add company details UC_Company

1.0 He shall add, update and delete customer UC_Customer

1.0 He shall add, update and delete Supplier UC_Supplier

1.0 He shall add, update and delete Bank details UC_Bank

1.0 He shall add, update and delete expense Type UC_Analysis_list

1.0 System shall generate annual report showing profit and loss

year and month.

UC_ Generate_

Report

1.0 He shall create payroll and add, update and delete employee UC_Payroll.

1.0 He shall add, update and delete income details UC_Income

1.0 He shall add and update expense details UC_Expense

3.8 Priorities Requirements:

Para# Rank Initial Requirements Use case

ID

Use case Name

1.0 Highest Admin will register

himself

Uc.1 UC_Admin_Register

1.0 Highest Admin will login. Uc.2 UC_Admin_Login

1.0 Highest He will add Company

details

Uc.3 UC_Add_Company_Details

1.0 Highest He will update

Company details

Uc.3 UC_Update_Company_Details

1.0 Highest He will add customer

details

Uc.4 UC_Add_Customer_Details

1.0 Highest He will update

customer details

Uc.4 UC_Update_Customer_Details

1.0 Medium He will delete

customer details.

Uc.4 UC_Delete_Customer_Details

1.0 Highest He will add supplier

details.

Uc.5 UC_Add_Supplier_Details

1.0 Highest He will update supplier Uc.5 UC_Update_Supplier_Details



IT-HUB 21

details.

1.0 Medium He will delete supplier

details.

Uc.5 UC_Delete_Supplier_Details

1.0 Highest He will add bank

details.

Uc.6 UC_Add_Bank_Details

1.0 Highest He will update bank

details.

Uc.6 UC_Update_Bank_Details

1.0 Medium He will delete bank

details.

Uc.6 UC_Delete_Bank_Details

1.0 Highest He will add expense

type.

Uc.7 UC_Add_Expense_Type

1.0 Highest He will update expense

type

Uc.7 UC_Update_ Expense_Type

1.0 Medium He will delete expense

type

Uc.7 UC_Delete_ Expense_Type

1.0 Highest He will add Income

details

Uc.8 UC_Add_Income_Details

1.0 Highest He will update Income

details

Uc.8 UC_Update_ Income_Details

1.0 Medium He will delete Income

details

Uc.8 UC_Delete_ Income_Details



IT-HUB 22

3.10 High Level Use case Diagram:

Figure 5 High Level Use Case Diagram



IT-HUB 23

3.11 Analysis Level Use case Diagram:

Figure 6 Analysis Level Use Case Diagram



IT-HUB 24

3.12Usecase Description

1: Admin Registration:

2: Admin Login:

3: Add Company details:

4: Update Company details:

Use case name: UC_Admin_Login Use case ID: 2

Pre-Conditions: System is on.

Basic flow: Enter admin email and Password.

Alternative flow : Enter again Email and Password.

Post -Conditions: Login Successfully.

Use case name: UC_Admin_Register Use case ID: 1

Pre-Conditions: System is on.

Basic flow: Enter admin detail.

Alternative flow : Not done.

Post -Conditions: Registered.

Use case name: UC_Add_Company_Details Use case ID: 3

Pre-Conditions: Login admin

Basic flow: Enter company details.

Alternative flow : Again enter company details.

Post -Conditions: Enter company details Successfully.

Use case name:

UC_Delete_Customer_Details

Use case ID: 4


Basic flow: delete Customer details.


Post -Conditions: delete Customer Details Successfully.



IT-HUB 25

5: Add Customer Details:

6: Update Customer Details

7: Delete Customer Details

8: Add Supplier Details

Use case name:

UC_Update_Supplier_Details

Use case ID: 5


Basic flow: Update Supplier details.


Post -Conditions: Update Supplier Details Successfully.

Use case name: UC_Add_Bank_Details Use case ID: 6


Basic flow: Add Bank details.


Post -Conditions: Add Bank Details Successfully.

Use case name: UC_Add_Expense_Type Use case ID: 7


Basic flow: Add Expense Type.


Post -Conditions: Add Expense Type Successfully.

Use case name: UC_Update_

Income_Details

Use case ID: 8


Basic flow: Update Income Details.


Post -Conditions: Update Income Details Successfully.



IT-HUB 26

9: Update Supplier Details

10: Delete Supplier Details

11: Add Bank Details

12: Update Bank Details

13: Delete Bank Details

Use case name: UC_Add_Expense_Type Use case ID: 9


Basic flow: Add Expense Type.


Post -Conditions: Add Expense Type Successfully.

Use case name: UC_Update_ Expense_Type Use case ID: 10


Basic flow: Update Expense Type.


Post -Conditions: Update Expense Type Successfully.

Use case name: UC_Add_Bank_Details Use case ID:11


Basic flow: Add Bank details.


Post -Conditions: Add Bank Details Successfully.

Use case name: UC_Update_Bank_Details Use case ID: 12


Basic flow: Update Bank details.


Post -Conditions: Update Bank Details Successfully.

Use case name: UC_Add_Income_Details Use case ID: 13


Basic flow: Add Income Details.


Post -Conditions: Add Income Details Successfully.



IT-HUB 27

14: Add Expense Type

15: Update Expense Type

16: Delete Expense Type


Income_Details

Use case ID: 14





Use case name: UC_Delete_

Income_Details

Use case ID: 15


Basic flow: Delete Income Details.


Post -Conditions: Delete Income Details Successfully.

Use case name: UC_Delete_ Expense_Type Use case ID: 16


Basic flow: Delete Expense Type.


Post -Conditions: Delete Expense Type Successfully.



IT-HUB 28

17: Add Income Details

18: Update Income Details

19: Delete Income Details

Use case name: UC_Add_Income_Details Use case ID: 17


Basic flow: Add Income Details.


Post -Conditions: Add Income Details Successfully.


Income_Details

Use case ID: 18





Use case name: UC_Delete_

Income_Details

Use case ID: 19


Basic flow: Delete Income Details.


Post -Conditions: Delete Income Details Successfully.



IT-HUB 29

Chapter 4: Third Deliverable For Object Oriented Approach

4.1. Domain Model

Figure 7 Domain Model



IT-HUB 30

4.2. System Sequence Diagram

Figure 8 System Sequence Diagram



IT-HUB 31

4.3. Salesman Sequence Diagram:

Figure 9 Salesman Sequence Diagram



IT-HUB 32

4.4. Admin Sequence Diagram

Figure 10 Admin Sequence Diagram



IT-HUB 33

4.5. Design Class Diagram

Figure 11 Design Class Diagram



IT-HUB 34

4.6. State chart diagram

Figure 12 State Chart diagram



IT-HUB 35

4.7. Activity diagram

Figure 13 Activity Diagram



IT-HUB 36

4.8 Activity diagram2

Figure 14 Activity Diagram 2



IT-HUB 37

4.9 Activity diagram3

Figure 15 Activity Diagram 3



IT-HUB 38

4.9 Entity Relationship Diagram

Figure 16 Entity Relationship Diagram



IT-HUB 39

Chapter6: 4th Deliverable (User Interface Design)

6.1. Site Maps

Figure 17 Site Maps



IT-HUB 40

6.2 Front page

6.3 Enter email and password



IT-HUB 41

6.4 Wrong email or password entered:

6.5 Login successful. Owner panel shown.



IT-HUB 42

6.5 Scroll down to view next graph.

6.6 First Tab Is Dashbord Expand (Add New Invoice)



IT-HUB 43

6.7 Click on New Invoice to Add invoice

6.8 Add Data and click on Save Button



IT-HUB 44

6.9 Click on Expenses to Add expenses

6.10 Click on Expenses A page appear



IT-HUB 45

6.11 Click on second tab INCOME

6.12 All sales invoices are credits shown



IT-HUB 46

6.13 Click on Reports to generate reports

6.14 Click on reports and enter data and click on generate to generate report



IT-HUB 47

6.15 Third tab is Expenses all expenses are shown.

6.16 To generate report click on reports



IT-HUB 48

6.17 Add data and click on generate to generate reports

6.18 Click on Enter Button to enter expenses



IT-HUB 49

6.19 Add detail and click on add button for submission

6.20 Fourth tab is Bank click on bank to show bank page



IT-HUB 50

6.21 Click on add reports to generate reports

6.22 Add detail and generate reports



IT-HUB 51

6.23 Click on enter to enter reports

6.24 Enter data and click on Add button



IT-HUB 52

6.25 Next Sub tab is Transfer to transfer funds

6.26 Enter info and click on transfer to transfer Amount



IT-HUB 53

6.27 Next tab is payroll

6.28 Next tab is Settings



IT-HUB 54

6.29 Trace-ability Matrix

Features UC

ID

UI

ID

Priority DB

ID

Dependent classes

Authentication 1 1 High 10 Connection.php

authorization 1 1 High 10 Authentication

Signup 1 1 High 10 Authentication

login 2 2 High 10 Signup

Add new project

6 4 High 5 Login

Update project

information

6 5 low 5 Project added

View projects

6 6 low 5 Project added

Project approval

process

12 4 High 7 Added project

Project Assignment to

managers


Add new tasks




IT-HUB 55

Chapter 7: 5th Deliverable (Software Testing)

7.1 Test plan

7.2.1.

Test plane identifier: 1

Introduction: Sign Up system is used for authenticate users.

Test item: Registration and login

Feature: Authentication & authorization

Approach: Enter user name, password, email, phone,

address.

Result: Pass


Introduction: Add or Update information of company

Test item: Add and update information

Feature: Insertion & Updation

Approach: Enter company detail by fill form.

Result: Pass. Test plane identifier: 3

Introduction: Add, Delete, Update Customer information

Test item: Add, Delete and update information

Feature: Addition, Deletion and Updation Customer

record

Approach: Add customer Delete Customer and Update

customer using form and delete button

Result: Pass.


Introduction: Add, Delete, Update Supplier information


Feature: Addition, Deletion and Updation Supplier

information

Approach: Add Supplier Delete Supplier and Update

Supplier using form and delete button

Result: Pass.


Introduction: Add, Delete, Update Bank information


Feature: Addition, Deletion and Updation Bank record

Approach: Add Bank Delete Bank and Update Bank using

form and delete button


Introduction: Add, Delete, Update Analysis list



IT-HUB 56


Feature: Addition, Deletion and Updation of expense

type

Approach: Add, Delete and Update expense type using

form and delete button


Introduction: Add, Delete, Update payroll


Feature: Addition, Deletion and Updation of employee

info

Approach: Add, Delete and Update employee using form

and delete button

Result: Pass.


Introduction: Add, Delete, Update income details

Test item: Add, Delete and update income details

Feature: Addition, Deletion and Updation of income

Approach: Add, Delete and Update income using form and

delete button

Result: Pass.


Introduction: Add, Delete, Update Generate reports

Test item: Generate Annual, Monthly and weekly reports

Feature: Generating Annual, Monthly and weekly

reports

Approach: Generating reports by clicking on Reports

button and filling the form

Result: Pass.


Introduction: Add expense and Update expense

Test item: Addition and updation of expense details

Feature: Add and update of expense details

Approach: Adding and updating expense details by

clicking on Edit and add button and filling the

form

Result: Pass.

Documents

University of Sargodha - ShiningStudy · IT Hub Sargodha Version: 1.0 Accounts Management System Date: march 10.3.2017 IT-HUB 2