Chapter # 1

Introduction

This document briefly describes the sale system of 4B(four Brothers)Groups Pakistan in a business view .Currently the sale system of 4B(four Brothers) Groups Pakistan is almost manual . Pakistan. Our products deals with all transactions related with sale system. Our main target is to transfer the current sales system of 4B(four Brothers) Groups Pakistan into a computerized system, so that most of the transactions can be performed through computer Sales management system of 4B group is used for sales. The main steps involve in sales processes are Policy Definition, Collection against Policy, Customer Demand, Product ,Sale Return and CrDrNotes

1.1: Introduction about Website:

4B(Four Brother Company) deals with seeds and pestisides the worker or employee work on different branches of different cities. We develop a website to show time sheet management system about employee, employers and administrator. The whole record about employee such as their attendances, their leaves, their working period show by this website of the company. This site basically handles time sheet of all project and their Employees including Admin, Supervisors, Legal Supervisors, Managers and Employees. 2.1 Functional Requirements:This document briefly describes the sale system of 4B(four Brothers)Groups Pakistanin a business view .Currently the sale system of 4B(four Brothers)Groups Pakistan is almost manual . We are going to develop computerized sale system of 4B(four Brothers)Groups Pakistan.Our products deals with all transactions related with sale system. Our main target is to transfer the current sales system of 4B(four Brothers)Groups Pakistan into a computerized system, so that most of the transactions can be performed through computer

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11)

Improved GUI (Graphical User Interface) Better data reliability Better data security Improved searching mechanisms Better report generation Generate fast reporting Automate all account Record all the items Records customer accounts Easy to create fast invoicing Manage customers order

1.4 Limitations:Our Product is related to Sale System of 4B(Four Brothers ) Groups Pakistan. The purpose of limitations is to specify all the limitations by which our projects can be affected. So all the limitations and their remains that can be involved in the development of our Product are described in the limitation. Our Product is limited to handle only those transactions that are related to Sale Sections in Store. Our Product is not deal with any other section in the Collection,Sales, sale Return and DrCrNotes or Adjustments Our Product will keep the records related to Sales ,sales return and DrCrNotes. Our Product is a web site. Our product will follow the rules and regulation of only (Four Brothers ) Groups Pakistan Sales management system. All Sales transactions are done on Collection policy, cradit Policy, cash policy,Switch policy and Foc policy .

1.1.5Design and Development:

1) 2) 3) 4) Unified modeling language (UML) will be designing architecture. Visual Studio will be used designing architecture. Develop on initials user interface concept. Develop the web site according to requirements Identify the component of development and implementation.

1.1.6Database design:
The activities in this design are: 1) Identify the persistent table in the data base design. 2) Designing appropriate data base structure to store those identified persistent tables. 3) Define mechanisms and strategies in order to implement these persistent tables in such a way that meet the project requirements. 1.1.7Component Implementation: During this phase we will implement the component/table needed in the development of different phases of the project.

1.2Development Approach: 1.2.1Requirement Definition phase:

We will review the requirements for all solution module component and we will use UML modeling to: 1) we want to verify that UML meet the requirements of our web site . 2) Develop high level information architecture. 3) Identifying different systems object and develop their use case sequence diagrams, activity diagram and collaboration diagrams.

4) Identify user input and outputs and develops design architecture. 5) Describe high level system use cases.

1.2.2Testing:
We will test the system in accordance with test plan that specify the following:

1) 2) 3) 4)

Testing techniques and tools to be applied. User acceptance test. Type of testing to be done i.e. unit testing, system tests. Verification of interaction between objects, integration of all Modules and insure that effect are identified prior to the Implementation of the software.

1.1.1: Project Fundamentals: Our website facilitate to all user from any where can submit their attendance only at once. We choose online time management system of Descon as administer. Administrator can search employee information. This site basically handles all Descon project and their Employees including Supervisors, Managers and Employees. 1.1.2: Basic Structure of Website: The website Contain two interface An Employee side A Administrator side/ company side

1.1.3: Project Hierarchy:

Project Manager

Analyst & Designer

Developer & Tester

1.1.4: Project Goals / Objectives: The proposed system is required to fulfill the following objectives: To creates and utilize an able and motivated workforce, to accomplish the basic organizational goals. To increase the reliability of the system to an extent meeting the actual requirement of the organization. The basic purpose of this site is, to provide an interface between employee and company through which they can communicate with each other. The Data base will be responsible of all the communication between Employees and company/Administrator. To assure the availability of the information at the right time. To increase the performance of the company. To remove the drawbacks of the existing system. To make the information storage, processing and retrieving efficient. Administrator can search the existing record according to their requirement To establish and maintain sound organizational structure and desirable working relationships among all the members of the organization

1.1.5: Functional Boundaries: We have defined the following functional boundaries To provide an interface to the entire employee to post their attendances. To provide an interface to the administrator to check all employees record. To provide an interface to administrator to search the employees according to their requirements To provide an interface to employees communicate to company. 1.1.6: Scope of Project: This document describes: Setting up the website and the hardware at the Hosting Facility or another reliable data center. Setting up a process to maintain and support the website in production environment.

To provide an interface to the entire employee to post their attendances. Provide an interface for customers to view the status of their orders Provide an admin interface to administrate the attendance and obtaining reports

1.4 1.1.9: Component Implementation: During this phase we will implement the component / tables needed in the development of different modules of the project.

CHAPTER # 2

Project Feasibility Report

There are given setup/input/listing forms 1. REGION 2. ZONES 3. TERRITORY 4. BUSINESS TYPE 5. BUSINESS CATEGORY 6. BUSINESS ZONE 7. GENRAL BANK 8. PRODUCT CATEGORY 9. UNIT OF MEASURMENT (UOM) 10. PRODUCT DEFINATION 11. PRODUCET SPECIFICSTION 12. EMPOLYEE DESIGINATION 13. EMPOLYEE DEFINATION 14. PARTY MAIN 15. POLICY MAIN

Reports the project data required are 1. SETUP LISTING REPORT 2. BANK DEPOSITE REPORT 3. COLLECTION REGISTER REPORT 4. SALE INVOICE REPORT 5. PARTY CRADIT LIMIT REPORT 6. CUSTOMER LEGDER REPORT 7. ZONEWISE POSITION SUMMARY REPORT 8. PERIODIC SALE AND COLLETION REPORT 9. PRIODIC REPORT 10. SALE REGISTER REPORT 11. NATIONAL /ZONE PRODUCT WISE SALE REPORT

Requirement Analysis & definition

System and Software design

Implement and system testing

Implement of unit Testing

Operation and Maintenance

Problem discovered in the phase of system of testing. return back to the perivious phase for problem rectification

CHAPTER # 5

System Design

5.1: Use Cases With Respect To user (Super Admin)

5.1.1: Use case1: Users (Super Admin , Admin , Sale-M ) Description This use case is used to login into this site. Actor: Users Use Case diagram:

Users

Login

Precondition: Users must open login page. Flow of Events: Primary Scenario: Open Login page Users will enter login name Users will enter password Press login[Exceptions] System response: Users can visit own account.

Exceptions Required field are empty Invalid Users name or password

Secondary Scenario: Users focus on password field

Post condition: A Users with the specified Supervisor login name has been login. And all this information saved

Users Diagram of Supervisor Login

Browser : users Enter URL 1

User Account

DataBase

open Login Page 2 Enter Login Name And password 3

Send Data 4

5 User Visit his own Account 6

Verify

Activity diagram of Supervisor Login

5.2 Use Cases With Respect To Users

5.2.1 Use case1: Users( super admin , Admin, sale-m) Change Password This use case is used to describe the process of changing passward Actor: Admin Use Case diagram:

User

Change password

Precondition:

User must open login page

Flow of Events: Primary Scenario: Open Login page User will enter login name User will enter password User will open administrator tab and sub tab change password for changing password Type old password

Type new password and confirm password Click the save button System response: user changed password successfully This use case end here

Exceptions

Required field are empty Old Password not correct Password did not match
Secondary Scenario: User can go back to home page Post condition: An User with the specified Admin user name has been login. And all this information saved

Sequence Diagram of User Change password

: User

Browser

Login Page

Data Base

Enter URL 1 Open Login Page 2

Enter Login name And Password 3

4 Enterr New Password 5 Enter confirm password 6 7

Verify

Verify

Admin Visit Site 8

Activity Diagram of Admin Login Retype Password

Enter URL

Open Login Page Enter Login Name And Pas s word Pres s Login empty or invalid entery

Retype Pas s word

pres s Login

Admin Vis it Site

5.2.2 Use Case2: Add New Designation

This use case is used for add new Designation. Actor: Admin Use Case Diagram

Admin

Add Designation

Preconditions: Admin must open login page. Admin must sign in as admin.

Flow of Events: Primary Scenario: Click on add new Designation. Enter Designation. Click on Submit button[Exception]

Exception: Designation already exists Secondary Scenario: Admin can go back on home page

Post Condition: Designation added sheet open

Sequence Diagram of Add New Designation

: Admin

Company account

Data Base

Click on New Designation 1

Page Open 2

Enter Designation 3

Send Data 4

5 Verify New Designation 6

Activity Diagram of Add New Designation

Open Login Page Login as Admin See Login Activity Diagram

Click on New Designation Enter Designation

Designation Added

5.2.3 Use Case3: Appoint New Employee

Description: This use case is used for appoint new employee Actor: Admin Use Case Diagram:

Admin

Appoint New Employee

Preconditions: Admin must open login page. Admin must Login as Admin.

Flow of events: Primary Scenario: Click on New Employee Enter the required information Click submit information

Secondary Scenario: Admin must go back on account main page

Post condition: Form will be opened for appoint new employee

Sequence Diagram of Appoint New Employee

Admin Account

Data Base

: Admin Click on new Employee

Open Employee form 2

Fill Form 3 Send data 4

5 Verify Appoint Employee 7

Activity Diagram of Appoint New Employee

Enter URL

Open Login Page

Login as Adm in

See Login As Admin

Click on New Employee

Enter required inform ation

Appoint New Employee

5.2.4 Use Case 4: Update Employee Information

Description: This use case is used to update employee information Actor: Admin Use Case Diagram:

Admin

Update Employee information

Preconditions: Admin must open login page. Admin must sign in as admin

Flow of events: Primary Scenario: Click on Update Employee Enter the required information Click submit information

Secondary Scenario: Admin must go back on account main page

Post condition: Form will be opened to update employee

Sequence Diagram of Update Employee Information

Admin Account

DataBase

: Admin Click on update employee information 1

Page open 2

Enter updation 3 Send Data 4

5 Verify Update Employee Information 6

Activity Diagram of Update Employee Information

Enter URL

Login As Adm in

See Login Activity Diagram

click on update Em ployee info Page open

Enter updation

Updated info

5.2.5 Use Case5: Search Employee

Description: This use case is used for search employee. Actor: Admin Use Case Diagram:

Admin

Search Employee

Preconditions: Admin must open login page. Admin must sign in as Admin

Flow of events: Primary Scenario: Click on Search Employee Choose Search By Name Or Login information Search page open[Exception]

Exception: not found Secondary Scenario: Admin must go back on account main page

Post condition: Employee Information Will be shown

Sequence Diagram of Search Employee

: Admin

Admin account

Data Base

Click on Search Empoyee 1

Page Open 2 Click on Search By name/ Login info 3

Choose Page Open 4

Enter Updation Send Data 6

7 Employee information shown 8

Verify

Activity Diagram of Search Employee

Enter URL

Login A Adm in s

Click on s aerch by nam e or login info Choos e page open

Enter updation

pres s s ubm itt button

5.2.6 Use Case6: Add New Project

Description: This use case is used to added new project. Actor: Admin Use Case Diagram:

Admin

Add new project

Preconditions: Admin must open login page. Admin must sign in as admin

Flow of events: Primary Scenario: Click on New Project Enter the required information Click submit Project

Secondary Scenario: Admin must go back on account main page

Post condition: Form will be opened added new project

Sequence Diagram of Add New Project

: Admin

Admin Account

DataBase

Click on Add New Project 1

Page open 2

Enter Project 3 Send Data 4

5 Verify Project added 6

Activity Diagram of Add New Project

Enter URL

Login As Admin

See Login Activity Diagram

click on Add new project Page open

Enter Project

Project added

CHAPTER # 6

Database Design

6.1: Data Models :

6.1.1 : Security : It shows security heraricy .On the base company , then combranch, user , then according to user group it shows pages.

6.1.2 : Area : It shows structure and hararicy of area.And shows the division of areas.

6.1.3: Policy :
The main steps involve in sales & receivables processes are Policy Definition, Collection against Policy, Customer Demand & Supply creation, Delivery Order & Outward Gate Pass creation.

6.1.4: Customer Demand :

It shows the relation about the transction according to the part.

6.1.5: OPG

6.1.6: Product:
It shows the relationship that we select product main and product spc according tp policy and then select product category.

6.2: Database design:

Database design is the core of system development. By knowing the requirements of the user, developer designs the database. Database design is technical discipline that is applied once the information domain of the database design has been defined. Therefore, the role of the system developer is to define the information to b contained in the database, the type of queries to be submitted for processing the manner in which data will be accessed and the capability of the database. Database design is a set of different activities. The database for the under discuss system is the result of different intermediate activities. First we will see the design view in SQL server 2008

6.2.1: Final Database Tables:

Users: This table will contain the information about Users

User Groups: This table will divide user into groups.

Paages: This table will dynamoclly handle the menu or tree and also explain level of tree.

Usergroup page rel: This table will contain handle menu according to usergruops

Fyear: This table will tell about time of fyear Fyear is year used to calculate annual budgte

Com company: This table will handle company

Com branch: This table will handle branches of company

Region: This table will contain the information about regions.

Zones: This table will contain the information about zones of company

User zone: This table will contain the information about zones of custmores

Bankinfo: This table will contain the information about the accounts of office

Business Type: This table will contain business types of company

Product categary This table will contain the information categaries of the products

Policy main: This table will contain the information about pakges for customers

Policy Foc type: This table will contain the information about the free of cost products

Cdmain: This table will contain the information about customer demands and supply of products

Party opgmain: This table will contain the information about TimeSheetSUP

Partyopg tranz: This table will contain about trasactions of user

Collection Main: This table will contain about the

Collection details: This table will contain about the

Crdt Bebt type: This table will contain about credit and debit

CHAPTER # 7

Snap Shots of Input Design

Chapter # 7

Snap Shots of Input Designs

Login Form Description: This web page is used to login Admin, Supper, Sales-M Groups users into this site.

Switch Credentionals Form Description: This web page is used to swicthing in a specific Company,branch,Zone and Fiscal Year.

User Setup Form Description: This web page is used to Add the New User and asign Company,branch and zone.

User Change Password Form Description: This web page is used to change the password and also required the old password for assign the new password.

User Groups Form Description: This web page is used to make the user groups

User Groups Form Description:

This web page is used to make the new company .

Location Setup Form Description: This web page is used to set the location of Company

CHAPTER # 8

Snap Shots of Output Design

Chapter # 8

Snap Shots of Output Design

Reports: