AL-Jabbal Manager - Finall

AL-JABBAL CORPORATION PROJECT
BSCS Session 2014-2018

Submitted By:
M. Adnan Shan
(Reg # 2014-BSCS-130)
M. Hanif Khan
(Reg # 2014-BSCS-148)
Semester: BSCS 8th
Supervisor
Mr. Imran Farooq
Lecturer
Date: January 10th, 2019
The University Of Poonch Rawalakot

Declaration
Declaration
Head and footer size should be 10pp
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 I

Final Approval
Final Approval
The University of the Poonch Rawalakot
Department of Computer Science and
Information Technology
FINAL APPROVAL
This is to certify that we have read the project report submitted by M. Adnan Shan(2014-BSCS-130) and M.
Hanif Khan(2014-BSCS-148) and it is our judgment that this report is of sufficient standard to warrant its
acceptance by The University of Poonch, Faculty of Basic & Applied Sciences Rawalakot for BS (hons) in
Computer Sciences.
COMMITTEE:
1. External Examiner ___________________________

Muhammad Yasir Shabir
Lecturer
Department of Computer Sciences & IT
University of Kotli AJK
2. Supervisor ___________________________
Mr. Imran Farooq
Lecturer,
Department of Computer Science & IT.
University of the Poonch Rawalakot
3. Chairman ___________________________
Dr. Adnan Idris
Chairman,
Department of Computer Science & IT
University of the Poonch Rawalakot
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 II

Dedication
Dedication
Dedicated to Our
Beloved Parents
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 III

Acknowledgement
ACKNOWLEDGEMENT
All acclamations and appreciation are for the Almighty ALLAH, the most merciful and
Prophet Hazrat Muhammad (PBUH), who is a permanent source of guidance for us and
humanity. Billions of “Darood-o-Salam” to Hazrat Muhammad (PBUH) who is symbol of
guide for humanity.
In the designation of ALLAH, The empathetic and the compassionate, whose ample blessings
empower us to complete our degree project.
We are highly grateful and express our honest thanks to our project Supervisor Mr. Imran
Farooq Lecturer, Department of CS&IT, for his profound interest, sympathetic and inspiring
guidance, and consistent encouragement & immense helped throughout the accomplishment
of our project.
I (Muhammad Adnan Shan) pay my thanks to my great Father and beloved Mother for
everything as they made me into who I am, and also warm thanks for all those relations who
helped me to complete my degree.
My (Muhammad Hanif Khan) humbly gratitude to my Father and Mother for her implacable
love, prayers encouragement & best wishes, which helped me to face the difficulties for life
& enabled me to complete my degree.
And we cordially thanks to All Teachers who made us able to do this project , due to their
keen interest we are able to learn programming skills in such a way so that we done our
degree project. We would like to mention the contribution of those who helped us at times
when we faced problems during the project. Dr. Adnan Idris’s, Dr. Zahid Mehmood’s, Mr.
Irteza’s, Mr. Imran Farooq’s and Mr. Irfan Javed’s insightful advices and attempts to solve
the problems have been precious. In the last but not least I am also thankful to my all
Colleagues.
Muhammad Adnan Shan
Muhammad Hanif Khan
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 IV

Project in Brief
Project Title Al-Jabbal Manager
Objective This application will be one of the best ways to
keep track of products, customer and also
finical transactions. Use of this application will
make the user confidential and calm from
anxiety of their data. This application will allow
users to automate all its business to get
reliability, consistency and efficiency. This
application will concentrate on automation of
business of Al Jabbal Corporation by using
desktop application.
Using this application user will be free from
worrying about stock, debtor information. This
application will notify the user if any product
getting short or any debtor has to pay amount in
current date. Proper backup can provide the
facility to recovery of data in any case of loss or
damage
Developed By Muhammad Adnan Shan 05
Muhammad Hanif Khan 23
Supervised By Mr. Imran Farooq.
Tool Used Visual studio 2010, SQL.
Operating system Microsoft Windows.
System Used Core i3 4 GB RAM , 500 GB H/D.
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 V

ABSTRACT
The degree project aims to introduce desktop app Al-Jabbal Manager and the purpose of this
project to allow users to store sensitive data on their Pc’s or laptops without having to worry
about confidentiality.
Al-Jabbal Manager will be one of the best ways to keep track of products, customer and also
finical transactions. Use of this application will make the user confidential and calm from
anxiety of their data. This application will allow users to automate all its business to get
reliability, consistency and efficiency. This application will concentrate on automation of
business of Al Jabbal Corporation by using desktop application.
This application will store whole data in database. Application will store the data offline.
User can access the sensitive data of application by login to the using his\her user ID and
password than the data will be displayed to the user. Other malicious user can’t access the
data
Using this application user will be free from worrying about stock, debtor information. This
application will notify the user if any product getting short or any debtor has to pay amount in
current date. Proper backup can provide the facility to recovery of data in any case of loss or
damage.
Computers and devices have become such a ubiquitous part of our everyday lives. As time
has passed, Computers have moved far beyond acting as a proxy for data saving and are now
different applications can reduce human work load and also predict for future. People needs
application’s in business to improve their business strategy as well to improve their income.
Our target is to allow user to make all business transactions by using this application safely.
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 VI

Table of Content
Table of Content
Chapter 1. Introduction ............................................................................................................. 11

1. Introduction: ...................................................................................... 1
1.1 Purpose ..................................................................................................................................... 1
1.2 Scope ......................................................................................................................................... 1
1.3 Problem Statement ................................................................................................................... 1
1.3.1 Problem Scenario ................................................................................................................... 1
1.4 Propose Solution ....................................................................................................................... 2
1.4.1 Scenario.................................................................................................................................. 2
1.5 References ................................................................................................................................ 3
Chapter 2. System Analysis .......................................................................................................... 4
2. System Analysis: ............................................................................... 5
2.1 Functional Requirement: .......................................................................................................... 5
2.2 Non Functional Requirement: ................................................................................................... 6
2.3 Software and hardware requirements ..................................................................................... 7
2.4 Use Case Diagram ..................................................................................................................... 8
2.5 Use Case Description................................................................................................................. 9
Chapter 3. System Design........................................................................................................... 20
3. System Design: ................................................................................ 21
3.1 Activity Diagrams .................................................................................................................... 22
3.2 Sequence Diagrams ................................................................................................................. 27
3.3 Class Diagram .......................................................................................................................... 31
3.4 Entity Relation Diagram .......................................................................................................... 33
Chapter 4. Implementation ........................................................................................................ 34
4. Implementation:.............................................................................. 35
4.1 Operating system selection..................................................................................................... 35
4.2 Programming Language Selection .......................................................................................... 35
4.3 Commenting Code .................................................................................................................. 35
4.4 Naming Convention ................................................................................................................ 35
Chapter 5. System Testing ......................................................................................................... 37
5. Testing: ............................................................................................ 38
5.1 Unit Testing ............................................................................................................................. 38
5.2 Interface Testing ..................................................................................................................... 38
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 VII

Table of Content
5.3 Module testing ........................................................................................................................ 38

5.4 Integration testing .................................................................................................................. 38
5.5 Evaluation................................................................................................................................ 39
5.6 Achievements.......................................................................................................................... 39
5.7 System Testing: ....................................................................................................................... 39
Chapter 6. Appendix................................................................................................................... 42
6. Screen Shots: ................................................................................... 43
Chapter 7. Conclusion ................................................................................................................ 55
7. Conclusion: ...................................................................................... 56
Chapter 8. References ................................................................................................................. 57
8. References: ...................................................................................... 58
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 VIII

List of Figures
List of Figures
Figure 1.3.1 Problem Scenario ..................................................................................................... 2
Figure 1.4.1 Solution Scenario ..................................................................................................... 2
Figure 2.4 Use Case Model ........................................................................................................... 8
Figure 3.1.1 Activity Login ......................................................................................................... 22
Figure 3.1.2 Activity Make Invoice ........................................................................................... 23
Figure 3.1.3 Activity Add Purchases ......................................................................................... 24
Figure 3.1.4 Activity Add Product............................................................................................. 25
Figure 3.1.5 Activity Update Stock ............................................................................................ 25
Figure 3.1.6 Activity Add Employee ......................................................................................... 26
Figure 3.1.7 Activity Add Shareholder ..................................................................................... 26
Figure 3.1.8 Activity Logout ...................................................................................................... 27
Figure 3.2.1 Sequence Login ...................................................................................................... 28
Figure 3.2.2 Sequence Make Invoice ......................................................................................... 28
Figure 3.2.3 Sequence Add Purchases....................................................................................... 29
Figure 3.2.4 Sequence Add Product .......................................................................................... 29
Figure 3.2.5 Sequence Add Stock .............................................................................................. 30
Figure 3.2.6 Sequence Add Shareholder ................................................................................... 30
Figure 3.2.7 Sequence Add Employee ....................................................................................... 31
Figure 3.3 Class Diagram ........................................................................................................... 32
Figure 3.4 ER- Diagram ............................................................................................................. 33
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 IX

List of Tables
List of Tables
Table 2.1 Use case-01 ................................................................................................................... 9
Table 2.2 Use case-02 .................................................................................................................. 10
Table 2.3 Use case-03 .................................................................................................................. 11
Table 2.4 Use case-04 .................................................................................................................. 13
Table 2.5 Use case-05 .................................................................................................................. 14
Table 2.6 Use case-06 .................................................................................................................. 16
Table 2.7 Use case-07 .................................................................................................................. 16
Table 2.8 Use case-08 .................................................................................................................. 18
Table 2.9 Use case-09 .................................................................................................................. 19
Table 5.1 Login ............................................................................................................................ 41
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 X

Chapter 1. Introduction
__________________________________________________________
Chapter 1 Introduction
1. Introduction:
has passed, our Computers have moved far beyond acting as a proxy for data saving and are
now different applications can reduce human work load and also predict for future. People
needs application’s in business to improve their business strategy as well to improve their
income.
1.1 Purpose
This application will allow users to automate all its business to get reliability, consistency and
efficiency. This application will concentrate on automation of business of Al Jabbal
Corporation by using desktop application. This application will store whole data in database.
Application will store the data offline. User can access the sensitive data of application by
login to the using his\her user ID and password than the data will be displayed to the user.
Other malicious user can’t access the data. Using this application user will be free from
worrying about stock, debtor information. This application will notify the user if any product
getting short or any debtor has to pay amount in current date. Proper backup can provide the
facility to recovery of data in any case of loss or damage.
1.2 Scope
has passed, our Computers have moved far beyond acting as a proxy for data saving and are
now different applications can reduce human work load and also predict for future. People
needs application’s in business to improve their business strategy as well to improve their
income.
This application will be one of the best ways to keep track of products, customer and also
finical transactions. Use of this application will make the user confidential and calm from
anxiety of their data.
1.3 Problem Statement
The existing system is manual system. Data can be stored in different registers that create a
problem known as Inconsistency of data. If we want to find some sort of information, it can
take more time and may have some error in finding the result. It is difficult to maintain and
manage the stock, customer and company record as well as difficult to maintain finical
investment by each stakeholder.
1.3.1 Problem Scenario
In manual system there are many problems. It is difficult to maintain and manage the stock,
customer and company record as well as difficult to maintain finical investment by each
stakeholder. Following Figure shows some problems in manual system. This figure shows
that there is lot of books to maintain different records it very difficult to find specific record
in any emergency.
Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 1

Figure 1.3.1 Problem Scenario
1.4 Propose Solution

Our System will provide user friendly environment that make our system easy to use and
save time, money and stationary. It can protect the confidential data to reduce the chance of
illegal access and loss or damage. Due to central database it can remove the redundancy of
data and provide the consistency. It will easy to maintain and have ability to maintain finical
transaction of user.
1.4.1 Scenario
In this Figure we clearly see that customer just place its order and make payment to get
products the record of the system easy maintain by the system and will saving time. The
entrepreneur will be able to manage the stocks.
Figure 1.4.1 Solution Scenario

1.5 References
This application has been prepared on the basis of discussion with Group member, teacher
and also taken information from different apps.

Chapter 2. System Analysis
__________________________________________________________
Chapter 2 System Analysis
2. System Analysis:
In the life of the software development, problem analysis provides a base for design and
development phase. The problem is analyzed so that sufficient matter is provided to design a
new system. Large problems are sub-divided into smaller once to make them understandable
and easy for finding solutions. Same in this project all the task are sub-divided and
categorized
2.1 Functional Requirement:
The functional requirements of the system describe the functionality or services that the
system is expected as provide.
ID Requirements Justification
REQ-1 Login Login provides facility to proceed to the Main
page.
REQ-2 Make Invoice User can make invoice as per customer need.
REQ-3 Sales Return User can add products that’s can be returned by
customer after purchasing.
REQ-4 Add Product User can add new product details.
REQ-5 Add Stock User can add stock detail of a particular product.
REQ-6 Update Stock User can update existing stock details.
REQ-7 Delete Product User can delete product if there is no stock of that
product.
REQ-8 View Stock User can view all stock details.
REQ-9 Add Purchases User can add new purchases from different
companies.
REQ-10 Manage Employees User can add, update and view employees.
REQ-11 Manage Shareholders User can add, update and view shareholders.
REQ-12 Manage System Users User can add, update and view users that can
access application functionalities.
REQ-13 Daily Expenses User can add, view and print daily expenses like
food expenses.
REQ-14 Monthly Expenses User can add, view and print Monthly expenses
like building rant, telephone bill etc.
REQ-15 Wages User can add and view the salaries paid to
employees.
REQ-16 Drawings. User can add and view the products withdraw by
the shareholder for its personal use.
REQ-17 Generate Repots User can generate sales report include weekly,
monthly and yearly sales. User can also generates
the report of products and stock.
REQ-18 Make Payments User can paid payments against the debit of
companies and received payments form debater
customers.
REQ-19 Generate Income User can generate the income statement to view
Statement the profit and loss of business.
REQ-20 Generate Shareholder User can generate the profit of all shareholders
equity after generating the income statement.
REQ-21 Maintain Balance sheet User can also make balance sheet to check
equality of assert and liabilities.

2.2 Non Functional Requirement:

Non-functional requirements are the quality requirements that stipulate how well software
does what it has to do. These are Quality attributes of any system; these can be seen at the
execution of the system and they can also be the part of the system architecture.
Accuracy:
The system will be accurate and reliable based on the design architecture. If there is any
problem in the accuracy then the system will provide alternative ways to solve the problem.
Usability:
The proposed system will be simple and easy to use by the users. The users will comfort in
order to communicate with the system. The user will be provided with an easy interface of
the system.
Accessibility:
The system will be accessible through application and there should be no any known
problem.
Performance:
The system performance will be at its best when performing the functionality of the system.
Reliability:
The proposed system will be reliable in all circumstances and if there is any problem that will
be affectively handle in the design.
Security:
The proposed system will be highly secured; every user will be required registration and
username/password to use the system. The system will do the proper authorization and
authentication of the users based on their types and their requirements. The proposed system
will be designed persistently to avoid any misuse of the application.

2.3 Software and hardware requirements

2.3.1 Software:
Following software are used in development of Al-Jabbal Manager.
 Visual Studio 2010
 SQL Database of Visual Studio 2010
 C# Language of Visual Studio 2010
2.3.2 Hardware
The recommended hardware specified by the respective software would suffice the needs.
The memory and processing power needed would increase as the number of users increase.
The estimated hardware requirements are as specified.
Following hardware are required to install for this application.
 Processor – i3
 Hard Disk – 500 MB
 Memory – 512 MB RAM

2.4 Use Case Diagram

Use Case Diagram is a graphical representation that describes how users will interact
with the system.
Figure 2.4 Use Case Model

2.5 Use Case Description
Table 2.1 Use case-01
Use Case ID UC-01
Use Case Name Login
Scope Al-Jabbal Manager
Level User Goal
Primary Actors Director, Administrator, Sales Man

Pre-Condition Actors should have accessed the system.
Post-Condition Actors successfully perform their operations.
Scenario-01 The user has the ability to logon to the system to be able use it.
Main success-scenarios Actor Action System Action

1) User presses login to Enter 2) System asks for following
the system. information
3) User provides asked Username
information. Password
4) User hits the “ok” button. User type
Extension and Alternatives 1a) If Username or Password or user type is incorrect.

1a.1) Re-enter username/password/user type.
Frequency Frequent.

Use Case ID UC-02
Use Case Name Manage Sales
Level User Goal
Scenario-01 User can Make Invoice.
1) User can start 2) System ask about

sales. Customer Information
3) User can provide Product Information
the asked Payment Information
information.
Extension and Alternatives 2a) If Invalid information provided.
2a.1) Re-enter asked information.
Frequency Frequent
Scenario-02 User can enter the products returned by the customer

after purchasing.
1) User can press 2) System ask about
“Sales Return” Customer Information
button. Product Information
Payment Information
3) User can provide
the asked
information.
Extension and Alternatives 2b) If Invalid information provided.
2b.1) Re-enter asked information.
Frequency Frequent

Use Case ID UC-03
Use Case Name Manage Products
Level User Goal
Primary Actors Director, Administrator

Scenario-01 The user has ability to add new Purchases.

1) User presses the

“Add Purchases”
button 2) System will open the
“Purchases info” screen
and ask for following
3) User provides information.
asked information. Company Detail
Product Detail
Payment Detail
4) User hits the

“Save” button.
Extension and Alternatives 3a) If Information is not valid.

3a.1) Relevant exception occurs.
Frequency Frequent
Scenario-02 The user has ability to add new Product.
1) User presses the

“Add Product” button
2) System will open

3) User provides the “Product info”
asked information. screen and ask for
following information.
Product Name
Product Category

Product Unit
4) User hits the
“Save” button.
Extension and Alternatives 3b) If Information is not valid.

3b.1Re-enter information again.
Frequency Frequent
Scenario-03 The user has ability to add new Stock.
1) User presses the

“Add Stock” button
2) System ask for
3) User provides Product Code
asked information. Quantity
Price
Shortage Limit
4) User hits the

“Save” button.
Extension and Alternatives 3c) If Information is not valid.

3c.1Re-enter information again.
Frequency Frequent
Scenario-04 The user has ability to Update Stock.
1) User presses the

“Update Stock”
button
2) System ask for

3) User provides following
asked information. information.
Product Code
Quantity
Price
4) User hits the Shortage Limit
“Update” button.
Extension and Alternatives 3c) If Information is not valid.

3c.1Re-enter information again.
Frequency Frequent

Use Case ID UC-04
Use Case Name Manage Users
Level User Goal
Primary Actors Director

Scenario-01 The user has ability to add new User.

1) User presses the

“Add New User”
button 2) System will open the
“User info” screen and
ask for following
asked information. First Name
Last Name
Email
Phone number
User Name
4) User hits the Password.
“Save” button.

Frequency Frequent
Scenario-02 The user has ability to add Update User.
1) User Click on the 2) System will open

User info the “User info” screen
and ask for following
asked information. First Name
Last Name
Email
4) User hits the Phone number
“Update” button. User Name

Password.
Conform Password
Frequency Frequent
Scenario-03 The user has ability to View.
1) User presses the

“View” button
2) System shows the
list of users
Extension and Alternatives Not defined.
Frequency Frequent
Use Case ID UC-05
Use Case Name Manage Expenses
Level User Goal

Scenario-01 The user has ability to add Daily Expenses.

1) User presses the

“Daily Expenses”
button 2) System ask for
3) User provides Office Expenses
asked information. Advertisement
Other Expense
Days
4) User hits the

“Save” button.

Frequency Frequent
Scenario-02 The user has ability to add Monthly Expenses.
1) User presses the

“Monthly Expenses”
button 2) System ask for
3) User provides Telephone Bill
asked information. Electricity Bill
Building Rent
Internet Charges
4) User hits the Month
“Save” button. Year

Frequency Frequent
Scenario-03 The user has ability to add Drawings.
1) User presses the

“Drawings” button
2) System asked for
3)User Provide the following information
asked information Shareholder Name
Drawing Amount
4)User hit “Save”
button
Extension and Alternatives Not defined.
Frequency Frequent

Use Case ID UC-06
Use Case Name Generate Reports
Level User Goal
Scenario-01 User can generate sales reports.
1) User can press 2) System will show

“Sale Reports” weekly, monthly,
button: yearly sale report
Extension and Alternatives Not defined
Frequency Frequent
Use Case ID UC-07
Use Case Name Make Payments
Level User Goal
Primary Actors Director, Administrator

Scenario-01 User can add debtor’s payment details.
1) User Press 2) System can asked

“Payments by for the following
customer” information.
Customer Name
2) User provides Bill No
the asked Discount
information. Amount received
3) User hit “Save”

button

Frequency Frequent
Scenario-02 User can add payments to company details.
1) User Press 2) System can asked

“Payments to party” for the following
information.
2) User provides the Party Name
asked information. Invoice No
Discount
3) User hit “Save” Amount paid
button

7b.1) Relevant exception occurs.
Frequency Frequent

Use Case ID UC-08
Use Case Name Manage Financial Resources
Level User Goal
Primary Actors Director
Scenario-01 User can generate income statement.
1) User can press 2) System will asked

“Income for the following
Statement” button information
State date
3) User can Provide End Date
asked information
1) User can press

“Enter” button
Extension and Alternatives Not defined
Frequency Frequent

Use Case ID UC-09
Use Case Name Logout
Level User Goal
Scenario-01 The user has the ability to logout to the

system.
1) User pressed “X” 2) System will ask for

button: conformation and give
3) User will select following options
the option. Yes
No
Extension and Alternatives 09a) If “Yes” application exit.
09a.1) If “No” application not exist .
Frequency Frequent

Chapter 3. System Design
__________________________________________________________
Chapter 3 System Design
3. System Design:
System design is the process of expanding what was learned during domain analysis into a
working implementation. Design implementation that will carry out the system charter and
lead to reuse among many systems.
Designers have developed a set of design rules that can be reapplied during the design of new
applications.
Design Model (Interactive Model)
Interactive modeling emphasis on the illustration of software objects interaction via
messages. The interaction diagram/model is generalization of two UML diagrams types, both
can be used to express similar messages interaction. These are
 Sequence diagram
 Activity diagram
 Class diagram
 Entity relationship diagram

3.1 Activity Diagrams

Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.
So the control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. Activity diagrams deals with all type of flow control by using
different elements like fork, join etc.
3.1.1 Login:
Figure 3.1.1 Activity Login

3.1.2 Make Invoice:
Figure 3.1.2 Activity Make Invoice

3.1.3 Add Purchases:
Figure 3.1.3 Activity Add Purchases

3.1.4 Add Product:
Figure 3.1.4 Activity Add Product
3.1.5 Update Stock:
Figure 3.1.5 Activity Update Stock

3.1.6 Add Employee:
Figure 3.1.6 Activity Add Employee
3.1.7 Add Shareholder:
Figure 3.1.7 Activity Add Shareholder

3.1.8 Logout:
Figure 3.1.8 Activity Logout
3.2 Sequence Diagrams

UML sequence diagrams are used to show how objects interact in a given situation. An
important characteristic of a sequence diagram is that time passes from top to bottom: the
interaction starts near the top of the diagram and ends at the bottom (i.e. Lower equals later).
A popular use for them is to document the dynamics in an object-oriented system. For each
key collaboration, diagrams are created that show how objects interact in various
representative scenarios for that collaboration.
Sequence Diagram (SD) is one of the key notations of UML and serves as a well-accepted
media among software developers, stakeholders, and tool builders. The appeal can be
attributed to the intuitive nature of its graphical representation and its capability to capture
scenarios of how the system might be used or how entities interact by transmitting sequences
of Messages.

3.2.1 Login:
Figure 3.2.1 Sequence Login

3.2.2 Make Invoice:
Figure 3.2.2 Sequence Make Invoice

3.2.3 Purchases:
Figure 3.2.3 Sequence Add Purchases
3.2.4 Add Product:
Figure 3.2.4 Sequence Add Product

3.2.5 Add Stock:
Figure 3.2.5 Sequence Add Stock

3.2.6 Add Shareholder:
Figure 3.2.6 Sequence Add Shareholder

3.2.7 Add Employee:
Figure 3.2.7 Sequence Add Employee
3.3 Class Diagram

The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the constraints
imposed on the system. The class diagrams are widely used in the modelling of object
oriented systems because they are the only UML diagrams which can be mapped directly
with object oriented languages.
The class diagram shows a collection of classes, interfaces, associations, collaborations and
constraints. It is also known as a structural diagram.

Figure 3.3 Class Diagram

3.4 Entity Relation Diagram

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a
database. An entity in this context is a component of data. In other words, ER diagrams
illustrate the logical structure of databases.
At first glance an entity relationship diagram looks very much like a flowchart. It is the
specialized symbols, and the meanings of those symbols, that make it unique.
Figure 3.4 ER- Diagram

Chapter 4. Implementation
__________________________________________________________
Chapter 4 Implementation
4. Implementation:
The implementation phase of a project starts after design. During this phase a design is
converted into working software. The software is developed in such a way so that it can meet
the requirements and specifications of the users. The implementation of any system is
converted with the tool used in the development work and the component used to implement
the system.
The process of assuring that the system is operational and then allowing users to take over its
operation for the use and evaluation is called implementation. Here, system means new
system, which is going to be implemented. The new system needs to be implemented because
the old system was manual .therefore, there is always room for improvement of the system.
System implementation involves following key features:
• Operating system selection
• Tool selection
• Language selection
• Commenting code
• Naming conventions
4.1 Operating system selection
Windows 8.1 Professional selected as development platform as it is University’s standard and
later the system will be implemented on the windows operating system. So, it is better to use
it at development time for ease enhancement and later compatibility.
Microsoft Windows 8.1 Professional is a powerful multitasking operating system. Its ease of
use, flexibility and communication services increase its demand. Microsoft Windows 8.1
Professional delivers seamless integration with one platform for communication. It is the
most flexible operating system working with wide variety of client operating systems.
4.2 Programming Language Selection
For implementation of Al-Jabbal Manager we use C# language and SQL. We use Visual
studio 2010 as IDE and windows local server .
4.3 Commenting Code
Understanding of where and how to comment your code is important. Commenting code
describe the functions and statements properly that help others to understand the concept of
statements for further enhancements. Comments help us to understand what is to be done. It
is also very backward to write the code and then try to explain what it does. So, most of the
point is tired to make clear by explaining it in comments.
4.4 Naming Convention
It is necessary to follow a standard naming convention throughout the whole project during
the development, to make the code readable. The approach that is used is as follow:
Variable: First letter of variable name represent the name of value or data it holds and first
letter is small and ‘_’ for each word in variable name.
Functions: Function name start with the type of functionality it is doing and first letter of
each word in function name is small and ‘_’ for each word in function name.

Chapter 4 Implementation
Text boxes: The name of all text boxes represent the name of value or data it holds and first
letter is small and ‘_’ for each word in text box name.

Chapter 5. System Testing
__________________________________________________________
Chapter 5 System Testing
5. Testing:
Software testing is an empirical technical investigation conducted to provide stakeholders
with information about the quality of the product or service under test, with respect to the
context in which it is intended to operate.
System testing is an essentials step for the development of the reliable and error free system.
Testing is the process executing a problem with the explicit intention of finding errors i.e.
making the problem fail and test cases are devised with the purpose in mind. A test case is a
set of data items that the system processes as normal input. A successful test is one that has a
high probability of finding an as-yet undiscovered error. Testing involves exercising the
program using data like the real processed by the program.
Testing may be carried out during the implementation phase, to verify if the software behaves
as intended by its designer, or after the completion of its implementation phase. There are
many approaches to software testing.
 Unit testing
 Interface testing
 Integration testing
 Module testing
5.1 Unit Testing

Each and every module of the system was tested at individual component level to ensure that
system operates correctly. Testing of these modules involved various steps:
Validation checks were confirmed on each item after the data was entered.
Functionality of each button was successfully tested.
5.2 Interface Testing
Interface testing ensures that proper links are operational and everything is displayed
according to the requirement of the system. Interface testing involved many steps:
Fonts size and font name were checked against the guidelines laid by the University.
It was checked that every meaningful word in prompt/any alert message displayed started
with a capital letter.
5.3 Module testing
A module is a collection of dependent components. In module testing, related units are
integrated in a module and tested for their proper functionality together. Various modules
were tested, by passing data/signal between them.
5.4 Integration testing
All the components module of the system were put to integrated testing and were found
working successfully.

5.5 Evaluation
Evaluation of the system means to examine what goals are achieved by the system and what
are the weaknesses and the deficiencies left behind. Evaluation is the final step in the
development by any system. This phase is for the purpose of reviewing whether objectives
and functional requirements of the Univ. are fulfilled are not.
5.6 Achievements
 Software provides the password protected GUI to facilitate the administrator to
manage this system.
 In all modules of the system, data is properly add, delete and update.
 All verification and validation checks work properly.
 System is satisfying almost all of its major specifications and functionality and it can
be concluded that system is satisfying its more than 90% scope.
5.7 System Testing:

System testing is an essential step for the development of the reliable and error free system.
Testing is the process executing a problem with the explicit intention of finding errors i.e.
making the problem fail and test cases are devised with the purpose in mind. A successful test
is one which does not find an error.

TEST CASES
5.8 Test Case:
Table 5.1 Login
Test Case ID: TC-001 Test Item: User authentication

Author: Adnan shan Doc-Date: 20-DEC-2018
Test Type: Manual-black box. Test Case Name: Login
Component: User authentication facility Release Version: 1.0
Test Case Description: The test case will determine the current functionality of user
authentication
Pre-Condition Post Condition
User should have their own user name, user type and System successfully authorized the user
password to use system.
Input Data/Event Expected output Data
In case of AL-Jabbal Login
Enter User type, User Name and password. Successfully Login
Test Case Result Test is performed successfully.
Actual Input Data/Event Actual Output Data/Event
1. Enter “Director(MD)” as user type “Admin”
as user name and “Admin” as password.
2. Click on “Login” button. Successfully login.
1. Enter “Administrator” as user type “Admin”

as user name and “Admin” as password.
2. Click on “Login” button. Login failed.
1. Enter “Sales Man” as user type “Admin” as

user name and “Admin” as password.
2. Click on “Login” button. Login failed.
Test Case Result Test is performed successfully.

Chapter 6. Appendix
__________________________________________________________
Chapter 6 Screen Shots
6. Screen Shots:












Chapter 7. Conclusion
__________________________________________________________
Chapter 7 Conclusion
7. Conclusion:
Using this application user will be fully confidential of his stock detail, company detail and
for debtor’s information. Proper backup of data makes sure the recovery of data in any case
of loss.
The user will free of doing complex calculations. The time will be saved, and mistakes of
user should be less.

Chapter 8. References
__________________________________________________________
Chapter 8 References
8. References:
1. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and
Iterative Development (3rd Edition)
2. Sql database developer: ISO/IEC
3. Sql database standard: ISO/IEC 9075
4. https://Microsoft-Visual-Studio-2010-Ultimate/3000-2383_4-75450998.html

AL-Jabbal Manager - Finall

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

AL-Jabbal Manager - Finall

Enviado por

Direitos autorais:

Formatos disponíveis

AL-JABBAL CORPORATION PROJECT

BSCS Session 2014-2018

Date: January 10th, 2019

The University Of Poonch Rawalakot

Head and footer size should be 10pp

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 I

1. External Examiner ___________________________

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 II

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 III

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 IV

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 V

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 VI

Chapter 1. Introduction ............................................................................................................. 11

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 VII

5.3 Module testing ........................................................................................................................ 38

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 VIII

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 IX

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 X

1.3 Problem Statement

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 1

Figure 1.3.1 Problem Scenario

1.4 Propose Solution

Figure 1.4.1 Solution Scenario

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 2

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 3

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 5

2.2 Non Functional Requirement:

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 6

2.3 Software and hardware requirements

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 7

2.4 Use Case Diagram

Figure 2.4 Use Case Model

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 8

2.5 Use Case Description

Table 2.1 Use case-01

Use Case ID UC-01

Use Case Name Login

Scope Al-Jabbal Manager

Level User Goal

Primary Actors Director, Administrator, Sales Man

Post-Condition Actors successfully perform their operations.

Main success-scenarios Actor Action System Action

Extension and Alternatives 1a) If Username or Password or user type is incorrect.

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 9

Table 2.2 Use case-02

Use Case ID UC-02

Use Case Name Manage Sales

Scope Al-Jabbal Manager

Level User Goal

Primary Actors Director, Administrator, Sales Man

Pre-Condition Actors should have accessed the system.

Post-Condition Actors successfully perform their operations.

Scenario-01 User can Make Invoice.

Main success-scenarios Actor Action System Action

1) User can start 2) System ask about

Scenario-02 User can enter the products returned by the customer

Al-JABBAL CORPORATION PROJECT Roll Number 05 & 23 BSCS 2014-2018 10

Table 2.3 Use case-03

Use Case ID UC-03

Use Case Name Manage Products

Scope Al-Jabbal Manager

Level User Goal

Primary Actors Director, Administrator