PUCIT Documentation

Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

PUCIT

Punjab University College of Information Technology

Submitted By:
BCSF13M505
Syeda Maham Noor
BCSF13M515
Anha Shehzadi
BCSF13M539
Nigar Zahid

Submitted to:
Mam Fakhra Jabeen

First Deliverable
Book Store and Sale Management System

1
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

FIRST DELIVERABLE GUIDE...........................................................................................................................3

1 INTRODUCTION..........................................................................................................................................3
1.1 PROJECT/PRODUCT FEASIBILITY REPORT..............................................................................................3
1.1.1 Technical Feasibility......................................................................................................................4
1.1.2 Operational Feasibility.................................................................................................................4
1.1.3 Economic Feasibility.....................................................................................................................4
1.1.4 Schedule Feasibility.......................................................................................................................4
1.1.5 Specification Feasibility................................................................................................................5
1.1.6 Information Feasibility..................................................................................................................5
1.1.7 Motivational Feasibility................................................................................................................5
1.1.8 Legal & Ethical Feasibility...........................................................................................................5
1.2 PROJECT/PRODUCT SCOPE.....................................................................................................................5
1.3 PROJECT/PRODUCT COSTING.................................................................................................................5
1.3.1 Project Cost Estimation By Function Point Analysis....................................................................6
1.3.2 Project Cost Estimation by using COCOMO81 (Constructive Cost Model)...............................8
1.4 CPM - CRITICAL PATH METHOD...........................................................................................................9
1.5 GANTT CHART......................................................................................................................................12
1.6 INTRODUCTION TO TEAM MEMBER AND THEIR SKILL SET...................................................................13
1.7 TOOLS AND TECHNOLOGY WITH REASONING.......................................................................................13
1.8 VISION DOCUMENT..............................................................................................................................13
1.9 RISK LIST.............................................................................................................................................14
1 INTRODUCTION........................................................................................................................................15
1.1 Systems Specifications....................................................................................................................16
1.2 Identifying External Entities...........................................................................................................17
1.3 Context Level Data Flow Diagram................................................................................................17
1.4 Capture "shall" Statements.............................................................................................................17
1.5 Allocate Requirements....................................................................................................................18
1.6 Prioritize Requirements..................................................................................................................18
1.7 Requirements Trace-ability Matrix.................................................................................................18
1.8 EXAMPLE..............................................................................................................................................18
1.8.1 Introduction.................................................................................................................................18
1.8.2 Existing System Business Organization.......................................................................................18
1.8.4Scope of the System......................................................................................................................19
1.8.5 Summary of Requirements:(Initial Requirements)......................................................................20
1.8.6 Identifying External Entities........................................................................................................22
1.8.9 Capture "shall" Statements and External Entities.......................................................................23
1.8.10 Allocate Requirements...............................................................................................................23
1.8.11 Priorities Requirements.............................................................................................................25
1.8.12 Requirements Traceability Matrix.............................................................................................28
1.9 High Level Usecase Diagram.........................................................................................................30

First Deliverable Guide

Our project is Book Sale and Store Management System.

2
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

1 Introduction
1.1 Project/Product Feasibility Report
Book shop management system will help both purchaser and seller to purchase and
sell the books in an easy manner. Purchaser will able to search any book on various
criteria such as using writer and book name, using ISBN number, using subject wise
and many order. He or She can order that particular book.
Return book, request for any book which are not available in the book shop. Upon
placing order, buyers will get an order Id by which they can track their order. Buyers
can pay online or select other payment options. To use this system, buyers have to
setup their profile first and choose their username and password. Upon successful
registration, their username and password will be forwarded to their registered email
Id.
There are many types of feasibilities:

Technical
Operational
Economic
Schedule
Specification
Information
Motivational
Legal and Ethical

1.1.1 Technical Feasibility

The Online Bookstore is feasible technically, although there is some risk. The project
team likely will include 3 people. Business user involvement will be required. The
project timeframe cannot exceed 3 Months. The current Order System is a clientserver system built using open standards. An interface with the Web should be
possible. Retail stores already place and maintain orders electronically.

1.1.2 Operational Feasibility

The project feasible within the limits of current technology. Our performance current
mode of operation provide adequate throughput and response time. Provide end users
and managers with timely, pertinent, accurate and usefully formatted
information.ourcurrent mode of operation provide cost-effective information services
to the business. There be a reduction in costs and/or an increase in benefits.
This system provide end user feel about role in new system and also provide the
management support. If end user resist to any change then this problem can
overcome.

3
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

1.1.3 Economic Feasibility

This project justified because benefits weigh cost.
Project be done, within given cost constraints. The task can be achieved in minimal
possible cost. We preferred to alternative solution, among candidate solution. We
build this system not purchase it .this system is PC based information system.

1.1.4 Schedule Feasibility

Our project is complete within time duration .our staff and resources within time is
very essential and complete our work with these limits. Our meetings is conducted
after every evolution of task. Project complete before technology becomes
unnecessary.

1.1.5 Specification Feasibility

The scope of our system for all end user who want to purchase or sale book.it deals
with purchasing book selling book ,it not concern with those requirement of
customer who find those books whose not available in shop, or unauthorized person
have constraint.

1.1.6 Information Feasibility

The project is time depend so our team member complete within time limit. Our
system is reliable for all end user and have all information about reserve book.so
each user can desire book from this system.

1.1.7 Motivational Feasibility

We formulate the goals to be met by the information system to be designed. We
quantify the goals. Obtain alternative solutions to satisfy the goals. Assess the
feasibility of implementing alternative solutions. Cost vs. benefits of each alternative
feasible solution.

1.1.8 Legal & Ethical Feasibility

Our goals and aims at ensuring that the business continuity project and the produced
plane do not violate any organizational policies, local,state,or federal laws, or any
adopted ethical codes.

1.2 Project/Product Scope

The project consists of following module
i. This project will help to maintain the records of books.
ii. This project will help the customer in searching of books.
4
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

iii. This project will help the Salesman in sale.

iv. This project will help the customer and salesman in payment system.
v. This project will help the Salesman in updating of stock.

1.3 Gantt chart

1.4 Introduction to Team member and their skill set

Maham Noor (BCSF13M505):
Coding
Anha Shehzadi (BCSF13M515):
Designing
Nigar Zahid (BCSF13M539):
Designing

1.4 Tools and Technology with reasoning

Tool
Reason
C++ Language
Better Understanding of language
Technology
Reason
Touch Screen
View

5
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

1.6 Vision Document

1.7 Risk List
The project may be affected with the following risks;
1. Technical risk:
This is a type of risks that may cause failure of the systems functionalities, which may
also affect its performance. Some of technical risks are;

System security risks where unauthorized person may gain access to the system
where they may violate data confidentiality, integrity and availability.
The system may have nonfunctional requirements risk failure such as lack of
multithreading functionality, lack of survivability functionality which may cause
the system to crash if accessed by many users concurrently.

2. Operational risk:
Failure of the information not being delivered on time which can be caused due to
The project may fail to be delivered on time due to poor or lack of senior
management support hence delaying in the decision making processes which may
delay the project.
The project my fail to be delivered on time due to lack of standardized project
management methodologies which may lead to improper management of the
system.
The system may fail to be delivered on time due to overworked or undertrained
project team.
3. Financial risk:
The project may be at a risk of not being delivered within the planned budget. For
example, if the project is faced with a risk of being behind the schedule, the project
manager may decide to add more team member, recruit other team members or even
add overtime hours which must cost more than it was allocated. In this case, the
project is at a risk of not being completed on the allocated budget since the cost to
cater some milestones that could have been covered has been used as mislenious
costs.
4. Member risk:
The project may be at a risk of the project team not meeting the requirements of the
user. The requirements may not be met either by having a non-qualified team who
may not have adequate knowledge about software development. Also, the project may
be at a risk of not meeting the clients requirements due to poor participation in the
development process.
5. Customer risk:
The project may be at a risk of the customer changing the project requirements.
6
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

6. Other risk:
In working there should be many risks. Sale may b freeze
If the system faces any problem. There should be a customer who did not know how
to use the system.

*********************REQUIREMENTS ENGINEERING*********************

1 Introduction
The inputs consist of the query to the database and the output consists of the solutions for
the query. The output also includes the user receiving the details of their accounts. In this
project the inputs will be the queries as fired by the users like create an account, selecting
books and putting into account. Now the output will be visible when the user requests the
server to get details of their account in the form of time, date and which books are
currently in the account.

Functional Requirements
System must not generate the same customer id.
When customer click on list view, system should show out the customer
information on textbox provided.
System should not allow customer ID to be change when user clicks
Edit.
System must be able to verify the information.
System must enter the correct copies quantity into book copies table.
The repeated ISBN number should not be allowed to enter into
database.

Non-functional Requirements
1. Safety Requirement
The database may get crashed at any certain time due to virus or operating system
failure. Therefore, it is required to take the database backup so that the database is not
lost. Proper UPS/inverter facility should be there in case of power supply failure.

2. Security Requirement
System will use secured database
Normal users can just read information but they cannot edit or modify anything
except their personal and some other information.
System will have different types of users and every user has access constraints
7
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

Proper user authentication should be provided

No one should be able to hack users password
There should be separate accounts for admin and members such that no member
can access the database and only admin has the rights to update the database.
3. Requirement attributes

There may be multiple admins creating the project, all of them will have the right
to create changes to the system. But the members or other users cannot do
changes
The project should be open source
The Quality of the database is maintained in such a way so that it can be very user
friendly to all the users of the database
The user be able to easily download and install the system

1.1 Systems Specifications

Introduction
The users of the system should be provided the surety that their account is secure.
This includes:

Authentication of members
Validation of members
Monitoring
Updating of records
Accountability
Integrity

Existing System
The brief description of the above clause is that:
1. User authentication and validation of members using their unique member ID
2. Proper monitoring by the administrator which includes updating account status,
showing a popup if the member attempts to issue number of books that exceed the
limit provided by the book shop, assigning fine to members who skip the date of
return
3. Proper accountability which includes not allowing a member to see other
members account. Only administrator will see and manage all member accounts
4. It will provide security on the data of a member.
Organizational Chart

8
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

Scope of the System

The system was developed to overcome the current problem occurred in
Book store.
The system must be able to validate the user, store the record and bug free.
System should be save timer.
It should be cost saver.

9
Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

Summary of Requirements (Initial Requirements)

Online bookstore website the websites must meet specific requirements standards. The
requirements that the bookstore websites must meet to ensure customers satisfaction are;
1. Only registered customer could place order for goods. So a customer must be able
to register himself to the system by requesting for registration. The system must
implement information confidentiality and integrity by ensuring that the entire
customers information is kept away from unauthorized personnel. A complete
order must contain personal details of the customer, information, book name
along with writer name and payment details. A customer shall login to the
system and can change his password
2. The system should be light when loading in computers and mobile phones so that
customers using different types of devices to access the system can access it
without experiencing any delays due to the devices they are using to access the
system. The system should have backup facilities such as onsite and offsite
servers which can help in restoring the system to its previous state before any kind
of attack happens. This increases the confidence of customers on the system due
to maintenance of consistent records. The system should have reliability nonfunctional requirements where they should be able to provide reliable information
to its customers at all times. The system should be easy to update so that
customers can be having updated products details which will increase their
effectiveness. The system should have adequate and effective search criteria
mechanism that can help the customers to easily find and choose the books that he
or she wishes to order. The systems should have adequate customer service
functionalities such as integrated live chat services for handling urgent customer
issues and email services for handling customers issues that are not urgent.
3. Customer could make payment either through cash or through a credit card.He
can also see the prices of the books. The systems graphical user interface should
be simple which allows customers to navigate through without experiencing any
difficulties in viewing the various books that the site offers, the means of
payment, and how the order can be traced.

1.2 Identifying External Entities

The software provides good graphical interface for the user and the administrator can
operate on the system, performing the required task such as create, update, viewing the
details of the book.

It allows user to view quick reports like Book Issued/Returned in between

particular time.
It provides stock verification and search facility based on different criteria.
10

Book Store and sale management system

PUCIT Documentation
Final Project Deliverable Guide

Bookstore
Date: 10-April-2015

The user interface must be customizable by the administrator

All the modules provided with the software must fit into this graphical user
interface and accomplish to the standard defined
The design should be simple and all the different interfaces should follow a
standard template
The user interface should be able to interact with the user management module
and a part of the interface must be dedicated to the login/logout module

Login Interface:
Incasetheuserisnotyetregistered,hecanenterthedetailsandregistertocreatehis
account.OncehisaccountiscreatedhecanLoginwhichaskstheusertotypehis
usernameandpassword.Iftheuserenteredeitherhisusernameorpasswordincorrectly
thenanerrormessageappears.
Search:
Thecustomercanenterthetypeofbookheislookingforandthetitleheisinterested
in,thenhecansearchfortherequiredbookbyenteringthebookname.
CategoriesView:
Categoriesviewshowsthecategoriesofbooksavailableandprovidesabilityto
add/editordeletecategoryfromthelist.
The Identification of External Entities or Actors is done in two phases.
a. Over Specify Entities from Abstract
On the basis of the Abstract, one might identify the following entities

Customer
Order
Books
ID
Publisher
Record
Payment
Account
Credit Card
Cheque
Request

b. Perform Refinement
After over specifying the entities, you have to refine them on the basis of your Business
Logic.
For example, in this example we found the following entities

11
Book Store and sale management system

PUCIT-Project Coordination Office

Final Project Deliverable Guide

Version: 1.0
Date: 10 May, 2005

Customer
Salesman
Books

1.3 Capture "shall" Statements

Para # External
Entity
1.0
Customer
1.0
Customer
1.0
Customer
1.0
Customer
1.0
System
1.0

2.0
2.0
2.0

System

3.0
3.0

Payment

Initial Requirements
A customer shall place order for goods
A customer shall register himself to the system
A customer shall view his details for verification purposes
A customer shall login to the system and can change his password
System shall update the customers Request
System shall process different types of updating e.g. updating of his
personal/shipping details, or upgrading of his status from registered to privileged
customer, or updating of his payment methodology
System shall search any customer details
System shall generate invoice, confirmation receipt and finally will place order
The System shall generate an action event for a corresponding administrator
when a request is placed for updating of orders or customer details etc.
Customer shall make payment; either through cash or through a credit card
Customer will view the prices of books.

Punjab University College of Information Technology, University Of The Punjab.

12

PUCIT-Project Coordination Office

Final Project Deliverable Guide

Version: 1.0
Date: 10 May, 2005

1.4 Allocate Requirements

Para# Initial Requirements
1.0
A customer will place order for book

Use Case Name

UC_ Order

1.0

A customer shall register himself to theUC_Registration_Request

system

1.0

A customer shall login to the system and can UC_Login

change his password

1.0

A customer shall view his details forUC_View_Customer_Details

verification purposes
System shall update the customers Request UC_Update_Request
System shall process different types ofUC_Change_Status
updating e.g. updating of his personal/shipping
details, or upgrading of his status, or updating
of his payment methodology
System shall search any customer details
UC_Search_Customer
System will generate invoice, confirmationUC_Invoice_Generation,
receipt and finally will place order

2.0
2.0

2.0
2.0
2.0

3.0
3.0

The System shall generate an action eventUC_Create_Action,

for a corresponding administrator when a
request is placed for updating of orders or
customer details etc.
Customer will make payment; either throughUC_Pay_For_Order
cash or through a credit card
Customer will view prices of books.

UC_View_Book_Order

Punjab University College of Information Technology, University Of The Punjab.

13

Project Deliverable 1

Date: 10 April, 2015

1.5 Prioritize Requirements

Par
1.0

1.0

2.0

2.0

3.0

1.0

1.0

Rank

Highest

Initial
Requirements

Use
Use Case Name
Case ID

A customer willUC_ 1
place order for
book
Highest A customer shallUC_2
register himself to
the system
Highest Customer
willUC_3
make
payment
either through cash
or through a credit
card
Highest System
willUC_4
generate invoice,
confirmation
receipt and finally
will place order
Medium The System shallUC_7
generate an action
event
for
a
corresponding
administrator when
a request is placed
for updating of
orders or customer
details etc
Medium System
shallUC_11
update
the
customers Request
Medium System
shallUC_12
process
differentUC_13
types of updatingUC_14
e.g. updating of his
personal details, or
upgrading of his
status or updating
of his payment

UC_Order

UC_Registration_Request

UC_Pay_For_Order

UC_Invoice_Generation,

UC_Create_Action

UC_Update_Request

UC_Change_Payment_Details,
UC_Change_Status,
UC_Change_Personal_Details

Punjab University College of Information Technology, University Of The Punjab.

14

Project Deliverable 1

1.0

1.0

1.0

Date: 10 April, 2015

methodology
Medium A customer shallUC_15 UC_View_Customer_Details
view his details for
verification
purposes
Medium System
shallUC_16 UC_Search_Customer
search
any
customer details
Lowest A customer shallUC_22 UC_Login,
login to the systemUC_23
and can change his
password

1.6 Requirements Trace-ability Matrix

Sr Para # System SpecificationBuild
#
Text
1 1.0
A customer willB1
place order for goods
2 1.0
A customer shallB1
register himself to the
system
5 1.0
A customer shallB1
login to the system
and can change his
password
6 1.0
System shall updateB1
the customers Request
7 1.0
System
shallB1
process different types
of
updating
e.g.
updating
of
his
personal details, or
upgrading
of
his
status or updating of
his
payment
methodology
8 1.0
A customer shallB1
view his details for

Use Case Name

Category

UC _Order

Business

UC_Registration_Request

Business

UC_Login,

Business

UC_Update_Request

Business

UC_Change_Payment_Details,
UC_Change_Status,
UC_Change_Personal_Details

Business

UC_View_Customer_Details

Business

Punjab University College of Information Technology, University Of The Punjab.

15

Project Deliverable 1

1.0

11 2.0

12 2.0

verification purposes
System shall searchB1
any customer details
Customer will makeB1
payment;
either
through
cash
or
through a credit card
System
willB1
generate
invoice,
confirmation receipt
and finally will place
order

Date: 10 April, 2015

UC_Search_Customer

Business

UC_Pay_For_Order

Business

UC_Invoice_Generation

Business

1.9 High Level Usecase Diagram

Use Case Name:
1. Login with registered id
2. Enter the choice
3. Enter book name
4. Enter writer name
5. Enter Email id
6. Receive the slip
7. Login for update record
Actor:
Primary:
Customer
Supporting:
Salesman
Off Stage:
Government/Tax Receiver
Precondition:
Salesman is identified and authenticated.
Customer having sufficient money for payment.
Post condition:
System saves the detail of book stock.
System records the registered customers.
Basic Flow:
1. Customer gives his/her identity.
2. Salesman login on the system.
Punjab University College of Information Technology, University Of The Punjab.

16

Project Deliverable 1

Date: 10 April, 2015

3. Salesman registers the customer.

4. Salesman assign customer id to customer.
5. Customer login through customer id on system.
6. System shows the details of services to the customer.
7. Customer enters his/her choice.
8. Customer searches a book on the bases of book name and Writer name.
9. System shows the view of book.
10. System records the customer order.
11. System shoes the detail of payment to the customer.
12. Customer enters Email id for the confirmation of payment.
13. System returns a slip to the customer with details of book and payment.
14. Customer receives book from salesman.
15. Customer returns the book to salesman.
16. Customer receives a return slip from system.
17. Customer pays bill to the Salesman.
18. Salesman check the details of book stock.
19. Salesman orders for new books.
20. Salesman update the records of books.
Alternative Flow:
2a. Invalid Id
Re-Enter Id
3a. Customer is already registered
4a. Id already exists
Re-Enter Id
5a. Invalid Id
Re-Enter Id
2a. Invalid choice
Re-Enter choice
8a. No book found
12a.Same Id already present
Enter different Id
13a.Slip is currently unavailable
Contact the salesman
Special Requirement:
Touch Screen

Punjab University College of Information Technology, University Of The Punjab.

17

Project Deliverable 1

Date: 10 April, 2015

Punjab University College of Information Technology, University Of The Punjab.

18