Documentation

SUPERIOR UNIVERSITY LAHORE
Faculty of Computer Science & IT

Final Year Project
PROJECT REPORT (Part-1)

point of sale (POS)
Project ID:
Project Team
Student Name Student ID Program Contact Number Email Address
Muhammad Azeem MCSM-F17-046 MCS-3A 0322-2856719 Muhammadazeem7782@gmail.com
Sofia Sarwar MCSM-S18-007 MCS-3A 0303-7852297 Sofiasarwar0073@gmail.com
Rida Naseem MCSM-S18-006 MCS-3A 0305-9971331 Rida17285@gmail.com
Mr. Rohail Shehzad

(lecturer)
Project Report: point of sale (POS)
Project Report
Point of sale (POS)
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0 <Original Draft>
<Changes Based on
Feedback from
Supervisor>
<Changes Based on
Feedback From Faculty>
<Added Project Plan>
<Changes Based on
Feedback from
Supervisor>
Faculty of CS&IT, Superior University Lahore, Pakistan ii

APPROVAL
PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________
PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
HEAD OF THE DEPARTMENT

Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
Faculty of CS&IT, Superior University Lahore, Pakistan iii

Dedication
“This report is dedicated to our respected to our beloved parents whose sacrifice has no match;
it’s because of them that we’re here pursuing our degree of computer science; without their
financial and emotional support we couldn’t have done it any better. “
Faculty of CS&IT, Superior University Lahore, Pakistan iv

Acknowledgements
“We express our sincere respect to and gratitude to our supervisor Mr. Rohail Shehzad Who has
given us valuable support cooperation and Suggestions from time to time in successfully
completing this report.”
Faculty of CS&IT, Superior University Lahore, Pakistan v

Executive Summary
A point of sale system is the heart of a business and used for many essential tasks such as
inventory management, labor reporting, menu customizations, price adjustments, staff
management, sales reporting, customer management, marketing initiates, and so much more.
There can be hundreds of features that can streamline your operations and make your make
more efficient. we want to introduce new point of sale management system which will be
introduce all the working of supply chain management system (SCM) and Corporate social
responsibility (CSR). Through our POS systems, your organization can analyze sales data, figure
out how well all the items on your shelves sell, and adjust purchasing levels accordingly. You can
maintain a sales history to help adjust your buying decisions for seasonal purchasing trends.
Supply chain management has been defined as the "design, planning, execution, control, and
monitoring of supply chain activities with the objective of creating net value, building a
competitive infrastructure, leveraging worldwide logistics, synchronizing supply with demand
and measuring performance globally. In our pos system CSR also help to keep track retailer and
distributor problems. the biggest benefit is that our pos system also will take the customer
feedback and provide the best solution to the company.
Faculty of CS&IT, Superior University Lahore, Pakistan vi

Table of Contents
Dedication .......................................................................................................................................iv
Acknowledgements..........................................................................................................................v
Executive Summary.........................................................................................................................vi
Table of Contents ........................................................................................................................... vii
List of Figures ...................................................................................................................................x
List of Tables ................................................................................................................................... xi
Chapter 1......................................................................................................................................... 1
Introduction .................................................................................................................................... 1
1.1. Background....................................................................................................................... 2
1.2. Motivations and Challenges ............................................................................................. 2
1.3. Goals and Objectives ........................................................................................................ 2
1.4. Literature Review/Existing Solutions ............................................................................... 2
1.5. Gap Analysis ..................................................................................................................... 3
1.6. Proposed Solution ............................................................................................................ 3
1.7. Project Plan ...................................................................................................................... 3
1.7.1. Work Breakdown Structure .......................................................................................... 3
1.7.2. Roles & Responsibility Matrix ....................................................................................... 4
1.7.3. Gantt Chart ................................................................................................................... 4
1.8. Report Outline .................................................................................................................. 5
Chapter 2......................................................................................................................................... 7
Software Requirement Specifications ............................................................................................ 7
2.1. Introduction...................................................................................................................... 8
2.1.1. Purpose ......................................................................................................................... 8
2.1.2. Document Conventions ................................................................................................ 8
2.1.3. Intended Audience and Reading Suggestions .............................................................. 8
2.1.4. Product Scope ............................................................................................................... 9
2.1.5. References .................................................................................................................. 10
2.2. Overall Description ......................................................................................................... 10
Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.2.1. Product Perspective.................................................................................................... 10

2.2.2. Product Functions ....................................................................................................... 10
2.2.3. User Classes and Characteristics ................................................................................ 10
2.2.4. Operating Environment .............................................................................................. 10
2.2.5. Design and Implementation Constraints .................................................................... 11
2.2.6. User Documentation .................................................................................................. 11
2.2.7. Assumptions and Dependencies ................................................................................ 11
2.3. External Interface Requirements ................................................................................... 11
2.3.1. User Interfaces............................................................................................................ 12
2.3.2. Hardware Interfaces ................................................................................................... 12
2.3.3. Software Interfaces .................................................................................................... 12
2.3.4. Communications Interfaces ........................................................................................ 12
2.4. System Features ............................................................................................................. 13
2.4.1. System Feature 1 ........................................................................................................ 13
2.4.1.1. Description and Priority .......................................................................................... 13
2.4.1.2. Stimulus/Response Sequences ............................................................................... 13
2.4.1.3. Functional Requirements ........................................................................................ 13
2.4.2. System Feature 2 ........................................................................................................ 13
2.4.2.1. Description and Priority .......................................................................................... 13
2.4.2.2. Stimulus/Response Sequences ............................................................................... 13
2.4.2.3. Functional Requirements ........................................................................................ 14
2.4.3. System Feature 3 (and so on) ........................................ Error! Bookmark not defined.
2.5. Other Nonfunctional Requirements .............................................................................. 14
2.5.1. Performance Requirements ....................................................................................... 14
2.5.2. Safety Requirements .................................................................................................. 14
2.5.3. Security Requirements ............................................................................................... 14
2.5.4. Software Quality Attributes ........................................................................................ 15
2.5.5 bussiness ruless………………………………………………………………………………………………………..12
Chapter 3....................................................................................................................................... 17
Faculty of CS&IT, Superior University Lahore, Pakistan viii

Use Case Analysis .......................................................................................................................... 17

3.1. Use Case Model .............................................................................................................. 18
3.2. Fully Dressed Use Cases ................................................................................................. 19
Chapter 4....................................................................................................................................... 20
System Design ............................................................................................................................... 20
4.1. Architecture Diagram ..................................................................................................... 21
4.2. Domain Model ................................................................................................................ 21
4.3. Entity Relationship Diagram with data dictionary ......................................................... 22
4.4. Class Diagram ................................................................................................................. 23
4.5. Sequence / Collaboration Diagram ................................................................................ 24
4.6. Operation contracts ....................................................................................................... 24
4.7. Activity Diagram ............................................................................................................. 25
4.8. State Transition Diagram................................................................................................ 26
4.9. Component Diagram ...................................................................................................... 27
4.10. Deployment Diagram.................................................................................................. 27
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1] .................. 28
Chapter 5....................................................................................................................................... 29
Implementation ............................................................................................................................ 29
5.1. Important Flow Control/Pseudo codes .......................................................................... 30
5.2. Components, Libraries, Web Services and stubs ........................................................... 30
5.3. Deployment Environment .............................................................................................. 30
5.4. Tools and Techniques ..................................................................................................... 31
5.5. Best Practices / Coding Standards.................................................................................. 31
5.6. Version Control .............................................................................................................. 31
Appendices.................................................................................................................................... 32
Appendix A: Information / Promotional Material ........................................................................ 33
Reference and Bibliography .......................................................................................................... 36
Index.............................................................................................................................................. 38
Faculty of CS&IT, Superior University Lahore, Pakistan ix

List of Figures
1.1 Gantt chart of first chapter 6

1.2 second figure of first chapter 7
2.1 first figure of second chapter 14
2.2 second figure of second chapter 22
2.3 third figure of second chapter 26
5.1 first figure of fifth chapter 49
5.2 second figure of fifth chapter 49
Faculty of CS&IT, Superior University Lahore, Pakistan x

List of Tables
1.1 first table of first chapter 6

1.2 second table of first chapter 7
2.1 first table of second chapter 14
2.2 second table of second chapter 22
2.3 third table of second chapter 26
5.1 first table of fifth chapter 49
5.2 second table of fifth chapter 49
Faculty of CS&IT, Superior University Lahore, Pakistan xi

Chapter 1
Introduction
Chapter 1: Introduction
In this chapter, we discuss the History of point of sale, the problems facing in market and discuss
the major factor of previous point of sale system, through this system we decrease market gap.
1.1. Background
For small businesses, trends like mobile payments and mobile loyalty programs are especially
relevant to product selection. For large businesses, the POS system will often be part of a larger
retail management suite. New investors entered into the industry and adopted modern
technologies such as (Square POS, Toast, We Pay, Epicor Eagle, N Series, Touch Bistro, Sally,
PayPal Here, Shopkeeper and STORIS POS etc.
In our pos system CSR also help to keep track retailer and distributor problems. the biggest
benefit is that our pos system also will take the customer feedback and provide the best solution
to the company.
1.2. Motivations and Challenges

We get motivation from POS desktop system then we decide to make it change in mobile app,
either we are in office and outside of office at any place, we operate our business and proper
check.
1.3. Goals and Objectives

 Android mobile app
 Existing system is desktop now we develop mobile app
 Through this system our payments online and we get customers feedback
1.4. Literature Review/Existing Solutions

Candela is designed with POS and inventory management features that provide automated
operations, integrated information, and real-time reports that help streamline the entire
retail process. But still no one added the functionality of supply chain and CSR in point of
sale that are most important think for business. In our pos system CSR also help to keep
track retailer and distributor problems. the biggest benefit is that our pos system also will
take the customer feedback and provide the best solution to the company.
Faculty of CS&IT, Superior University Lahore, Pakistan 2

1.5. Gap Analysis

 Desktop system to Android mobile app
 Existing system is desktop now we develop mobile app
 Through this system our payments online and we get customers feedback
1.6. Proposed Solution

The Expert pos system for the any company to reduce the market gap also an app for the
convenience of the user through which they control the Climate. it helps all the employee and
business man to keep track their business and check the activities of business on the daily basis.
it also helps to the employee that are working in the fields that are taking the order from the
customers they can also insert an order and increase the production demand on the time to time.
the customers and employee can also share any point through CSR that are the main purpose to
invent the new pos system. the pos system will also show many reports that help to employee
like (stock and sale report, daily sale report, weekly and monthly all reports) and also check the
customers and employee behavior.
1.7. Project Plan

Project Plan includes two things.
 Work breakdown structure (WBS) and
 Gantt chart consisting of Timeline with milestone.
1.7.1. Work Breakdown Structure

1.7.2. Roles & Responsibility Matrix

WBS WBS Deliverable Activity # Duration Responsible Team Member(s) & Role(s)
# (# of Days)
1 Requirement 01 22days M azeem
2 Analysis 02 22days Sofia sarwar,
Rida naseem
M azeem
3 Design 03 25days Sofia sarwar
Rida Naseem
4 Implementation 04 39days Sofia sarwar,Rida Naseem
.MAzeem
5 Testing 05 26days M.azeem
6 Documentation 06 37days Sofia sarwar, Rida Naseem
7 Deployment 07 66days All members
1.7.3. Gantt Chart

1.8. Report Outline

This report is divided into numerous sections that include: background which analyses overall
mobile application development. Requirement analysis that covers user requirements for the
mobile app, Design and implementation chapters that cover mobile development. User testing
and evaluation. Future work and conclusion which includes a discussion of certain problems
encountered in the project.
 Introduction
 Existing System / Competitive Analysis
 Introduction
 Existing System / Competitive Analysis
 Problem Statement:
 Proposed Solution:
 Scope of the Project:
 System Architectural Design
 Implementation Tools and Techniques
 Project Plan
 System Architectural Design
 Implementation Tools and Techniques
 Project Plan
o Work Breakdown Structure
 Project Management
o System Design
o Roles & Responsibility Matrix
o Gantt Chart


Chapter 2
Software Requirement
Specifications

Chapter 2: Software Requirement Specifications
2.1. Introduction
2.1.1. Purpose
The purpose of this Software Requirements Specification (SRS) document is to proposal a
complete Point of sale (POS) of the functionalities of the online android application. This
document resolves each of the system’s intended features, as well as offer many features of the
software application’s User Interface (UI). This document will cover software, and various other
technical needs.
2.1.2. Document Conventions

This document structures some terminology which readers may be unaware with. See Appendix
for a list of these relations and their descriptions.
2.1.3. Intended Audience and Reading Suggestions
This document is proposed for all point of sale employees participating in running the Mobile
application. Person who reads involved in a brief outline of the application should focus on the
rest of (Introduction), as well as the document (Overall Description), which provide a brief
summary of each feature of the project as a whole. (External Interface Requirements) offers
further technical details, with information on the user interface as well as the hardware and
software platforms on which the application will run. Reader’s complex in the non-technical
features of the project must read which covers performance, safety and security, or various other
attributes that will be important to users. Readers who have not found the information they are
looking for should check (Other Requirements), which includes any additional information which
does not fit logically into the other sections.

2.1.4. Product Scope

Import and Export Record management:
In our pos system CSR also help to keep track retailer and distributor problems. the biggest
benefit is that our pos system also will take the customer feedback and provide the best
solution to the company. keep eye on all the record and current situation of the business.
Android APP:
An app is developed for the Expert Pos System, through which the user control and show all
the records of the sale, stock, purchase, and customer behavior.
Past history Record:
The now POS only keep track the inventories and receiving which company employee and
owner not involve only cashier involve. The old designed with POS and inventory
management features that provide only automated operations, integrated information, and
real-time reports that help streamline the entire retail process only.
Connectivity:
A solid Wi-Fi network is an essential part of your business plan. After all, businesses in
industries like retail and hospitality depend on strong connectivity throughout to complete
day-to-day tasks on their POS systems. The move to a strong connected environment
benefits large and small businesses alike. Wi-Fi is at the heart of successful operations. Don’t
make the mistake of using generic, out-of-the-box Wi-Fi for your business. A strong, reliable
connection on-site and mobile visibility is key to any wireless network setup.
Tracking Promotions:
Another reason to upgrade to a new POS system is for optimal tracking and reporting on
sales and promotions. However, some point-of-sale systems fail to do this properly, and if
bad analytics are hurting your business, you need to speak with a POS professional about
upgrading your system to one that meets your needs. Promotions are a must for any retailer
and your POS system should not have any issues handling sales, coupons and other daily
discounts.

2.1.5. References
Nothing
2.2. Overall Description

2.2.1. Product Perspective
Our App is a new, self-sufficient invention planned for usage on the Android platform. While the
Daily point of sale activities done with mobile app is the main focus of the project. There is also
many features which includes, showing daily activities according to product so that a
Stores/employees can do it in right way according the product.
2.2.2. Product Functions
The following list offers a brief summary of the main features and functionalities of
Point of sale application.
 Online payment.
 Manage day by day business.
 record of reports includes stock and sale report.
 Feedback
2.2.3. User Classes and Characteristics
There are two types of users that relate with the system: users of the mobile application, and
administrators. Each of these two types of users has different use of the system so each of them
has their own requests. The mobile application users can use the application to learn daily
activities according to point of sale system. This application is helpful for business men to keep
track all business activities and manage day by day product. The administrators manage the
information of Mobile App, for example a description of the app, contact information and their
product. They are dealing the overall system so there is no incorrect information within it.
2.2.4. Operating Environment
The main part of the project is the android application, which will be limited to the Android
operating system. The application is not resource or graphics-intensive, so there are no useful
hardware constraints. The app will depend on different functionalities assembled into Android’s

Application Programming Interface (API), so certifying proper usage of the API will be a main
concern.
Software and Hardware
Tools Android studio
Languages java, xml
Database SQLite, firebase
2.2.5. Design and Implementation Constraints
The major design constraint is the mobile platform. Since the application is selected for mobile
phones, limited screen size and resolution will be a major project consideration. Creating a user
boundary which is both active and easily controllable will pose a difficult challenge. Point of sale
Application is meant to be fast and responsive, even when displaying large activity, so each
feature must be designed and executed with efficiency in mind.
2.2.6. User Documentation
The main goal of point of sale android application is to facilitate the process of dealing shared
expenses. Consequently, the application will be designed to be as simple to use as conceivable.
However, users may still require some extra information about each component of the
application. The application will contain many features that offer this
 Online payment.
 Manage day by day business.
 record of reports includes stock and sale report.
 Feedback
2.2.7. Assumptions and Dependencies

any assumption about the app is that it will always be used on mobile phones that have sufficient
performance. If the phone does not have enough hardware resources existing for the application,
for example the users might have distributed them with other applications there may be setups
where the application does not work as planned or even at all.

External Interface Requirements
2.2.8. User Interfaces

Android Mobile convenient to use for users easy to operate it.
2.2.9. Hardware Interfaces
Android Mobile phone and tablets.
2.2.10. Software Interfaces
The mobile application communicates with the internet application in order to get information
about where the employees is placed, and with the database in order to get the information
about the App. The communication between the database and the application involve operation
concerning both reading and modifying the data, while the communication between the
database and the mobile application consists of only reading operations.
Software used Description
We have chosen android studio for its best support and user-
Android studio friendliness.
To save the data and user records we have chosen SQLite, firebase
Database with database.
2.2.11. Communications Interfaces

The communication between the different parts of the system is significant since they depend
on each other. But the communication is completed is not important for the system and is
therefore, handled by the basic operating systems for mobile application.
This project supports all types of android mobile phone. Communication will be maintained
through internet and web servers.

2.3. System Features
2.3.1. System Feature 1
2.3.1.1. Description and Priority
2.3.1.2. Stimulus/Response Sequences
2.3.1.3. Functional Requirements

 Online payment
 Costumers feedback
2.3.2. System Feature 2

Point of sale system
2.3.2.1. Description and Priority
In our application the user can pay their payments online.
2.3.2.2. Stimulus/Response Sequences

2.3.2.3. Functional Requirements
2.4. Other Nonfunctional Requirements

2.4.1. Performance Requirements
 The point of sale system must be very efficient.
 The records in the database will continuously back-up at the end
 Usability factor will be the first and foremost priority.
2.4.2. Safety Requirements

 All the data of the user will remain safe and secured.
 Only the admin will be able to access his account.
 The password comprises encryption.
 The user will be able to see his chicken order details and won’t be allowed to make
any changes.
 In case if the user forgets his password or wants to change the password, the option
of “forget password” is available through which he can reset his password and all
the backups are available of his account that are used for his account recovery.
 The session will be destroyed after 10 minutes, in case if user forgets to logout his
account.
2.4.3. Security Requirements
 Security systems need database storage just like many other applications.
 However, the special requirements of the security market mean that vendors must choose
their database partner carefully.
 The encryption factor will be used to maintain the security.

2.4.4. Software Quality Attributes

These are some of the most imperative quality factors that can affect the whole project:
 Availability:
App should be available at 24/7 hours and provides services to clients.
 Efficiency:
App should have efficiency in its performance/response time.
It can work properly without any failure.
 Flexibility:
App should be flexible enough to adapt the new changes with the passage of time.
If any change is required in future it should be able to manage the changes gracefully.
 Security:
App should be secure enough that no one can access personal data.
Security of the system is improved by installing firewalls and authorization processes.
 Portability:
App should be portable enough that it can easily be install on another platform.
It can easily be run on other platform/devices.
 Interoperability:
App should have interoperability that it can exchange the data among internal components
and outside components.
 Scalability:
App should be scalable enough that it can adapt to increase in user request.
 Reliability:
App should be reliable enough that it can maintain its performance over time.
It can adapt changes and maintain itself in near future.
 Usability:
App should be user-friendly and easy to understand.
Clients should be fully satisfied with it performance and its functionality.

 Maintainability:
App should be self- maintained and efficient.
It can maintain the new changes.
It can maintain all the records.
 Reusability:
App components/features should be designed in such a way that they can be used in other
applications too.
Reusability reduces the time and complexity.
 Robustness:
App should have the ability to handle the error conditions gracefully without any failure.
It should be uptime or available for use. It has limited downtime.
2.5. Business Rules

 In requirement phase all the requirements are gathered and understand. User can also
change the requirements but there comes a point when all the requirements are freeze i.e.
no changes in requirements occur this phase is called the crystal requirements.
 Each develop conduct the meeting before implementing the functionality.
 Each developer must document after each phase.
 Hybrid approach follows i.e. waterfall and agile model.
 After each module implementation unit testing occurs.
 User satisfaction must be fulfilling.
 Review meeting occurs in which problems and errors are identifying and fix.

Chapter 3
Use Case Analysis

Chapter 3:
System Analysis
Point of sale system is developed for the android mobile application. It can manage all the records
of the system and also describe the current status of the customers feedback. The system has
the multiple functionalities which can be better understand through use case models. Each
functional requirement is described through use case model which can describe its working in a
better way and is more understandable.
3.1. Use Case Model

3.2. Fully Dressed Use Cases

Chapter 4
System Design

Chapter 4: System Design

4.1. Architecture Diagram
4.2. Domain Mode

4.3. Entity Relationship Diagram with data dictionary

4.4. Class Diagram

4.5. Sequence / Collaboration Diagram
4.6. Operation contracts

4.7. Activity Diagram

4.8. State Transition Diagram

4.9. Component Diagram
4.10. Deployment Diagram

4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1]

Chapter 5
Implementation

Chapter 5: Implementation
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this chapter all about]
5.1. Important Flow Control/Pseudo codes

5.2. Components, Libraries, Web Services and stubs

5.3. Deployment Environment


5.4. Tools and Techniques

5.5. Best Practices / Coding Standards

5.6. Version Control


Appendices

Appendix A: Information / Promotional Material

[Between 4 to 8 lines describe what is this appendix all about]
A.1. Broacher
A.2. Flyer
A.3. Standee
A.4. Banner

A.5. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.5.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]

Appendix [no.]: Appendix Title

[Between 4 to 8 lines describe what is this chapter all about]
A.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.2. Third level heading [12 pt, Calibri, Bold, Left aligned]

Reference and
Bibliography
Reference and Bibliography

[1] M. Sher, M. Rehman, “Title of the Paper” Conference name/Journal Name, Edition,
Volume, Issue, ISBN/ISSN, PP, Publisher/City-Country, Year.
[2] ……

Index

Index
[A]
[B]
[C]



Documentation

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Documentation

Hochgeladen von

Copyright:

Verfügbare Formate

SUPERIOR UNIVERSITY LAHORE

Faculty of Computer Science & IT

PROJECT REPORT (Part-1)

Muhammad Azeem MCSM-F17-046 MCS-3A 0322-2856719 Muhammadazeem7782@gmail.com

Sofia Sarwar MCSM-S18-007 MCS-3A 0303-7852297 Sofiasarwar0073@gmail.com

Rida Naseem MCSM-S18-006 MCS-3A 0305-9971331 Rida17285@gmail.com

Mr. Rohail Shehzad

1.0 <Original Draft>

<Added Project Plan>

Faculty of CS&IT, Superior University Lahore, Pakistan ii

HEAD OF THE DEPARTMENT

Faculty of CS&IT, Superior University Lahore, Pakistan iii

Faculty of CS&IT, Superior University Lahore, Pakistan iv

Faculty of CS&IT, Superior University Lahore, Pakistan v

Faculty of CS&IT, Superior University Lahore, Pakistan vi

Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.2.1. Product Perspective.................................................................................................... 10

Faculty of CS&IT, Superior University Lahore, Pakistan viii

Use Case Analysis .......................................................................................................................... 17

Faculty of CS&IT, Superior University Lahore, Pakistan ix

1.1 Gantt chart of first chapter 6

Faculty of CS&IT, Superior University Lahore, Pakistan x

1.1 first table of first chapter 6

Faculty of CS&IT, Superior University Lahore, Pakistan xi

1.2. Motivations and Challenges

1.3. Goals and Objectives

1.4. Literature Review/Existing Solutions

Faculty of CS&IT, Superior University Lahore, Pakistan 2

1.5. Gap Analysis

1.6. Proposed Solution

1.7. Project Plan

1.7.1. Work Breakdown Structure

Faculty of CS&IT, Superior University Lahore, Pakistan 3

1.7.2. Roles & Responsibility Matrix

1.7.3. Gantt Chart

Faculty of CS&IT, Superior University Lahore, Pakistan 4

1.8. Report Outline

Faculty of CS&IT, Superior University Lahore, Pakistan 5

Faculty of CS&IT, Superior University Lahore, Pakistan 6

Faculty of CS&IT, Superior University Lahore, Pakistan 7

Chapter 2: Software Requirement Specifications

2.1.2. Document Conventions

Faculty of CS&IT, Superior University Lahore, Pakistan 8

2.1.4. Product Scope

Faculty of CS&IT, Superior University Lahore, Pakistan 9

2.2. Overall Description

Faculty of CS&IT, Superior University Lahore, Pakistan 10

2.2.7. Assumptions and Dependencies

Faculty of CS&IT, Superior University Lahore, Pakistan 11

External Interface Requirements

2.2.8. User Interfaces

Software used Description

2.2.11. Communications Interfaces

Faculty of CS&IT, Superior University Lahore, Pakistan 12

2.3. System Features

2.3.1. System Feature 1

2.3.1.1. Description and Priority

2.3.1.2. Stimulus/Response Sequences

2.3.1.3. Functional Requirements

2.3.2. System Feature 2

2.3.2.2. Stimulus/Response Sequences

Faculty of CS&IT, Superior University Lahore, Pakistan 13