The document describes a project titled 'online shopping system,' a web-based application for managing sales, online purchases, and payments with user-friendly features. It includes functionalities such as secure login, product cart management, and maintains an electronic record of transactions, supporting 500 requests per minute. The development follows a linear sequential model with clearly defined requirements and a structured timeline for activities including requirement gathering, design, coding, testing, and implementation.

1. Group Members: Syed Ahmer Iftikhar
Chaudhary Fahad
Muhammad Junaid
Contact► Chaudhry.fahadi@gmail.com

2.  Our project titled as “Online Shopping System” is
basically a web based application used to record
sales, online sale and purchase and handle
payments.
 The project is to promote a user-friendly, safe way
for customers to buy and receive products without
being physically at a shop.
 The shop keep an electronic history of all purchases
and transactions.

3.  Provides customers with the possibility to perform
online purchases on products.
 The information is protected by login and password,
which can be assigned to each single user of system.
 Customers are identified properly and are able to
perform online transactions using credit card and
other ways.
 A customers is able to create a cart and add
products to it and delete them as well.

4.  This project is a web based application revolves
around the aim to facilitate the user to search and
get his/her favorite in a fastest way.

11.  The interface gives the response in less than 10
seconds.
 The system should support 500 requests/min.
 The system must be secure.
 The system should be maintainable so that if any
change occur, it does not effect.
 The system should be easy to use for users.

12. We use the Linear Sequential model because:
 Our project is of small scope.
 All requirements are well-defined.
 There is no risk involved in it.

18. Activity
Duration
(Weeks)
Precedents
A Requirement Gathering 2 weeks
B Design 2 weeks A
C Coding 4 weeks A,B
D Testing 1 week C
E Implementation 1 week C,D

19. Activity
Duration
(Weeks)
Earliest
Start
Date
Latest
Start
Date
Earliest
Finish
Date
Latest
Finish
Date
Slack
A 2 weeks 0 0 2 2 0
B 2 weeks 2 3 4 5 1
C 4 weeks 4 6 8 10 2
D 1 week 9 9 10 10 0
E 1 week 11 11 12 12 0