Documentation of Final Project

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 67

FINAL PROJECT DOCUMENTATION

Final Project Report

Online Shoes Sales & Purchase

Project Supervisor
Sir Zahid Aslam

Submitted By

Qazi Haseeb Ur Rehman , Muhammad Sulaiman

ROLL NO# 834, 828

Department of Computer Science,


Rahim Yar Khan Campus
The Islamia University of Bahawalpur
CERTIFICATE
This is to certify that <<Qazi Haseeb Ur Rehman ,Muhammad Sulaiman >>
<<834,828>> has worked on and completed his Software Project at Department of
Computer Sciences, The Islamia University of Bahawalpur (Rahim Yar Khan Campus) in
partial fulfillment of the requirement for the degree of MCS in Computer Sciences under
my guidance and supervision.

In our opinion, it is satisfactory and up to the mark and therefore fulfills the
requirements of MCS in Computer Sciences.

Supervisor / Internal Examiner


Sir Zahid Aslam
Lecturer,
Department of Computer Sciences
Rahim Yar Khan Campus
The Islamia University of Bahawalpur

___________________
(Signature)

External Examiner/Subject Specialist

___________________
(Signature)

Accepted By:
_____________
(For office use)

EXORDIUM

In the name of Allah, the Compassionate, the Merciful.

Praise be to Allah, Lord of Creation,


The Compassionate, the Merciful,
King of Judgment-day!

You alone we worship, and to You alone we pray for


help,
Guide us to the straight path

The path of those who You have favored,

Not of those who have incurred Your wrath,


Nor of those who have gone astray
DEDICATION

I want to dedicate this project to my beloved parents and my teachers. It’s


only due to their prayers that we are at this stage and performing our duties
in successful way. I also want to say thanks to my respected Sir Zahid
Aslam because of their efforts that I am at last stage of my destination. I
will never forget of my dearest Friends, seniors who encourage me at every
step of this project.
ACKNOWLEDGEMENT

I am grateful to almighty ALLAH, the most Gracious, Merciful and Beneficent WHO
helps me in every field of life. By HIS grace I have been able to complete this project
successfully.
I am thankful to my supervisor Sir Zahid Aslam whose guidance is always with
me whenever I found myself in difficulty. Who always encouraged me, and his guidance
helped me to complete this project.
I feel proud to be son of my parents, whose consideration boosts me moral to get
higher education. In fact their prayers enable me to reach this stage and complete this
project. I heartily express my thanks to my loving brothers and sisters for their love and
care. I am much thankful to my friends for their co-operation and help.
My appreciations also go to all the people who participated by sharing their
precious views and suggestions about the steganography in digital images. Thanks a lot
for all the time and effort they have given me, without their co-operation, I would not be
able to do such stupendous work..

Qazi Haseeb Ur Rehman,


Muhammad Sulaiman
PREFACE

This Documentation is about the online bookshop management system. This is online
book shopping location.by which client can put points of interest of books and
can seek it, can be individual from website, purchase online books, and see other
connected books of same writer or same class .client can see online book detail
from wherever through web and buy it with installment from Credit card.

During this document preparation I am guided by my kind, respected, and experienced


teacher Mr. Zahid Aslam who helped me a lot to refine my project and its
concern document. He with his knowledge and experience told me the art of
designing the system.

During this process I studied the present system and got information about this system
by studying the existing documents, reports they prepared. On the basis of this
information I tried my level best to fulfill the needs by designing the system.
Finally, system development was done under guidance of my respected
teachers.
PROJECT BRIEF

PROJECT NAME: Online Shoes Sales & Purchase

ORGANIZATION: ISLAMIA UNIVERSITY OF BAHAWALPUR

UNDERTAKEN BY: Waqar Ul Hassan

SUPERVISED BY: MR. ZAHID ASLAM

DATE OF START: 25/01/2021

DATE OF COMPLETION:

COMPUTER USED: INTEL CORE(TM) i5 CPU-2.40 GHZ

SOURCES LAGUAGES: HTML

OPERATING SYSTEM : WINDOWS 8.1pro

TOOL USED:
 Dream weaver
 Xampp server
 Php designer 8.0
Plagiarism Report

SRS 8%

Plagiarism Report

SDD 13%

Zahid Aslam
Dept. of Computer Science
The Islamia University of Bahawalpur
Rahim Yar Khan Campus
Table of Contents

1: INTRODUCTION.........................................................................1
1.1 PURPOSE OF PROJECT....................................................................1
1.2 SCOPE & LIMITS...............................................................................1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS. 1
1.4 REFERENCES 1
1.5 DESCRITION & OVERVIEW 2

2 Complete Description 2
2.1 Product perspective 2
2.1.1 Operations 2
2.1.2 Site Adaptation Requirements 3
2.2 Product function & Features 3
2.3 User characteristics & Importance 3
2.4 General constraints & Avidones 4
2.5. Assumptions and Dependencies 4

3 Specific And Limitided Requirements 4

3.1 External Interface Requrirements 5


3.1.1 System Interface and Layout 5
3.1.2 Interface And Screen 5
3.1.3 Hardware Interface & Specitions 5
3.1.4 Software Interface & Layout 6
3.1.5 Communication Interface & Layout 6
3.2 Functional Requirements 6
3.2.1 <Functional Requirements or Features #1> 6
3.2.2 <Functional Requirements or Features #2> 7
3.3 Uase Cases 7
3.3.1 Use Case # 1 7
3.3.1 Use Case #2 7
3.4 Classes/Object 7
3.4.1<Class/ objects #1> 7
3.4.2 <Class/ objects #2> 7
3.5 Non-Functional Requirements 7
3.5.1 Performance 8
3.5.2 Reliability 8
3.5.3 Availability 8
3.5.4 Security 8
3.5.5 Maintainability 8
3.5.6 Portability 8
3.6 Inverse Requirements 8
3.7 Logical Database Requirements 8
3.8 Design Constraints 8
3.8.1 Standards Compliance 8
4. Analysis Models 9
4.1 Sequance Diagrams 9
4.2 Data Flow Diagrams 9
4.3 State Transtions Diagrams 9
5. Supporting Information 9
Appendix-A - Background 9
Appendix-B -Dictionary 9

Y1. INTRODUCTION..................................................................................................................................4
1.1 PURPOSE...................................................................................................................................................................4
1.2 SCOPE.......................................................................................................................................................................4
1.3 OVERVIEW................................................................................................................................................................4
1.4 REFERENCE MATERIAL............................................................................................................................................5
1.5 DEFINITIONS AND ACRONYMS.................................................................................................................................5
2. SYSTEM OVERVIEW............................................................................................................................5
2.1Techonology used………….………………………………..……………………………………………………5
2.2Application overview………………………………………………….……………………………………………5
2.3Design language…………………...……………………………………………………………………………..…5
2.4System environment…………………………………………………………………………………...……………6
2.5Assumptions………………………………………………………………………………………………………...6
2.6 General Constraint…………………………………………………………………………………………………6
3.SYSTEMARCHITECTURE……………………………………………………………………………………6
3.1 ARCHITECTURAL DESIGN.........................................................................................................................................7
3.1.1 Web Architecture……………………………………………...……………………………………………… 7
3.1.2 Block diagram…………………………………………….…………………………………………………. ... 7
3.2 DECOMPOSITION
7 DESCRIPTION………………………………………………………………………………………............................8
3.2.1 Class diagram…………………………………………………………………………………….…………….. 9
3.2.1.1 User and its type……………………………………………………………………………………………… 9
3.2.1.2 Order class diagram and type…………………………………………………………………………………10
3.2.1.3 Customer class diagram………………………………………………………………………………………11
3.2.1.4 Complete class diagram …………………………………………………………………………………….,12
3.2.2 State diagram………………………………………………….…………………………………………….…14
3.2.3 Use case……………………………………………………………………………………………………...…15
3.2.3.1 Use Case # 1: Customer login……………………………………………………………………………......16
3.2.3.2 Use Case # 2: Registration of new customer…………………………………………………………………16
3.2.3.3 Use Case # 3 Change password………………………………………………………………………………17
3.2.3.4 Use Case #4 Search product………………………………………………………………………………….18
3.2.3.5 Use Case #5 Search by Brand………………………………………………………………………………..19
3.2.3.8 Use Case #7 Product add……………………………………………………………………………………..20
3.2.3.9 Use Case #Delete item………………………………………………………………………………………..21
3.2.3.10 Use Case # Customer view the detail of Laptop…………………………….……………………………,,,.22
3.2.3.11 Use case# customer order……………………………………………………………………………….......23
3.2.3.11 Use case # Buy a product…………………………………………………………………………………...24
3.2.3 .SEQUENCEDIAGRAM……………………………………………………………………………………..25
3.2.3. 2 SEQUENCE DIAGRAM FOR ADMIN ADD NEW ITEM 25
3.2.3. 3Sequence diagram for Admin add new item……………………………………………………………...... 26
3.2.3. 3sequence diagram customer product……………………………………………………………………… ..27
3.2.4.Activity diagram…………………………………………………………………………………………..……28
4. DATA DESIGN…………………………………………………………………………………………………28
4.1 DATA DESCRIPTION……………..………………………………………………………………………………..28
4.3 Complete ER diagram………………………………….………………………………………………………. 30
4.2 Data Dictionary…………………………………………………………………………………………………..31
5.COMPONENTDESIGN………………………………………………………………………………………….32
6.HUMANINTERFACEDESIGN…………………………………………………………………………………33
7.0 SWIM_LANE_DIAGRAM……………………………………………………………………………………… 37

7.1.0 Requirement_Matri x ……………………………………………...…………………38


`
`

1. Introduction
Software Requirement Specification (SRS) is documentation can describe the
system in detail. Software Requirement Specification (SRS) are provided by the
information about the working of system that can provide functionalities on
requirements. Author also defined the functionalities of the system in detail.

1.1 Purpose of Product


Software Requirement Specification (SRS) Documentation is defined the internal
and external requirement for any system. The requirement analysts are collecting
the requirement of the system through interview, meetings, observation. Some
time the analyst also involves the Question Documentation for end user and
collects their ideas about the new system.
The requirement is collect from their client in written documents. These
requirements also collect from different resources. The requirement is stable with
the passage of time. They will also change with the passage of time.
The aim of Software Requirement Specification (SRS) to receive the information
about Laptop Point or Online Laptop Shop. These documents are providing the
information about the functional and non-functional specification about Laptop
Point. The Document is describing the nature of the system, environment and
interface to developer.

1.2 Scope_&_Limits
The Software is design in a way on one document. The aims of Laptop Point to
purchase their information to their customers about the computer generation and
models.
It provided the new price of a laptop. It the facilities to see the requirements more
clearly.
The Laptop point is the way to provide the information.
`

1.3 Defining the Headings and Stand For


The Short name that can be appear in S.R.S it will be define properly. The Short
form of Heading that can used in S.R.S must be defined.

1.4 reference
In this sub part :
(1) Complete description of all documents that can be used in S.R.S.
(2) Recognize every page or topic, Document detail analyses the
sources from which the references can be obtained and service can
be used.
This information can be provided by reference to an appendix or to another
document on the off chance that your application utilizes particular
conventions or RFC's, at that point reference them here so architects know
where to discover them.
The Detail that can be received in references for in appendix and every
Documentation on of the chance that the particular application utilized the
conversions, and R.F.C’s in point the point can exist here the design will be
solve the every point of view.

1.5 Description & Overview


The project entitled “Laptop Point” enables customer to buy Computer in order
online. They also buy the Computer or Laptops from the shop. The aim of to
develop a project to online that our customer can contact from anywhere in the
world.
The “Laptop Point” also provides the updating of price on computer or Laptops.
The user or client check the price of the product and order the product online. They
purchase the Computer or Laptop anywhere from the world.
The customer visits the items of “Laptop Point” in internet. They can just chose the
product and replace the order of product. The product Deliver to the client in
received postal address of the client. The laptop point is way that can user interact
the shop keeper. The shop keeper provided the necessary detail to their customer.

2. Complete _Description and Details

2.1 Product Point of view


This product is website application_interface. It is standalone system and cover
maximum users. It requires web browser and internet connection to provide
services and function. It may runs on variety of system but its RAM should not
be less than 512MB and it requires disk space of 30MB.
`

2.2 Product Functions & Features


Online shoes Sales &Purchase is webbing based application software or product. User
can purchase the Shoes of different brands..

2.3 User Characteristics & Importance


The user of laptop point is customer and common peoples are used this
product. The laptop point are provide the facility to people they can serves our
service from online and get the deals with our shop keepers. The user is
important in business point of view. The user is seeing the easiest way to find
anything for us. So the Laptop point provides the facility according to user or
customers’ needs. The laptop point is facilitating their customer in every point
of view. The user or customer is also seeing the all modules of our page of web
and every models of Computer according to their need.

2.4 General Constraints & Avidness


The project and software of Laptop Point software is work on different
version of windows. The user is customer is creating account and
register in laptop point by a way that cans any one cannot see their
deals and data. The laptop point secure the user or customers data
by using the password Fields.

2.5Assumptions, Dependencies, Relations & Links


Every of the part that infected the requirement exists in the S.R.S. In These
parts will no the design steps of challenges of the software but a, after
developing the application, the changing of requirements of the project may
be effects on the functionalities of the system. The limited software is available
on the market like windows and the product are specially designed for android
base. The project are available are on play store and every user are download
them. The changing are must be implemented in SRS if we are change the
Operating System.
In this part we solve the every condition of the system that may be affected in
every point of view in our project. So the system or project cannot run on
different environment without android.
`

3. Limited_and_Specific_Requirements
The most important part of the SRS requirement is most important. The client
requirements are collect in two phases, but the third section also exist, the
third part are used to provide the detail the about the project design,
maintained and testing etc.
Every requirement in these parts is bellow:
 Correctness & accuracy
 Traceableness or backtracking (both forward and backward to prior)
 Unambiguous or complex and difficult requirements
 Verifiable and Testability check the functionality of system
 Prioritized and importance (because to importance and/or stability,
correctness)
 Completeness and full nests
 Consistency and state forwarding
 Uniquely identifiable and like primary key not null and not duplication.
To solves the problems are organize in best way according to requirements. In
this way the specific and general requirements are understandable in simple
way. Further the S.R.S are never just a software, product design papers, in one
will discard the duplication of the overloading and the software design are
exist in software requirements are collect in SRS in every point of view.

3.1 Outside Boundary Requirements

3.1.1 System Interfaces Layout


The interface in the system according to the environment of the today
programming point of view. Now we are developed the system according to
user need so the system are worked with their functionalities and
understandable for end user. We tried to run project user work on the project
without user training. But some time it included. The interface are normal way
and understandable.

3.1.2 Interfaces & Screen


Specify:
(1) The logical and conceptual prop ties of every edge among the
software invention and its_ users and clients.
(2) It all the depends of utilizing the edge with the user that can must
use the system, and their client.
(3) The framework with clients will combine with working of software.
The graphical user interface and summon line and different type of
edges.? The every type of interface like common and uncommon are
necessary.? The event when you analyses the product according to
A.D.A (Amercan _with Disabilities _Act) on your edges.?
`

3.1.3 Hardware Edges & Specifications


Define the aim of the prop ties of every edges between the software items and tools of
hardware and their framework. This will provide support for design uniqueness. This
term also added the routs as will as gadgets are to be sustain, they are the be
conventions and upload. The system programme will takes Mac with 64 MB Random
Access Memory. The part of optimizing the realistic tools your application will be
controls and communication channel will be developed. For example the different web
based and android based application are appear. The developer should chose the tools
for the development of the application and should design the interface for the
application. The interface design are also according to the user or client requirements.
The tools selection are must be selected in development of or software because they
provide the proper description in any part of software development

3.1.4 Software Edges & Layout


(1) Check the utilization the items that will be required in programming
interface with the frame work of application that will be will be
developed.
(2) Name , title
(3) Mnemonic and view
(4) Specification number /requirements
(5) Version number / model
(6) Source of running
Every interface, provide:
(1) Detail of the problems that will be appear in the developing the application
of the required item.
(2) Definition of the interface as far as message substance and arrangement.
(3) Defiantly add the comment or feedback page in the application page.
(4)
3.1.4.1 Microsoft_SQL_Server_7
The database must include will used in development of laptop point. The software will
database will link the data items. The DBA also used in Laptop Point. The SQL are
provide the facility to add the information in data base. The table included in Laptop
point feedback or relation table through SQL. The SQL used in Laptop point because
the SQL are open source. The SQL are easy to link table and connect database with
Website. The SQL server are necessary part of the website application development.
`

3.1.5 Communications Interfaces & Layout

Determine the different interfaces to correspondences, for example, nearby system


conventions, and so on. These are conventions you should straightforwardly
connect with. On the off chance that you happen to utilize web benefits
straightforwardly to your application at that point don't show it here. On the
off chance that you are utilizing a custom convention to impart between
frameworks, at that point archive that convention here so originators realize
what to plan. In the event that is a normal convention, you can provide
information a current archive or R.F.C.

3.2 Functional_Requirements

This part are portrays nominate highlights of the undertaking. In the event that
coveted, a few necessities might be indicated the utilization casesorganize and
recorded in the Use.Cases Part.

3.2.1 <Useful Prerequisite or Characteristic #1>


Introduction and Abstraction
Inputs and Instruction
Handing out and Working
Display and Results
Error Handling and Error Controlling

<Functional Requirement or Feature of Product #2>


Use_Cases
The Part provide use cases of the functional_requirements of the complete
product.

Use _Case #:01

Use _Case #: 02

3.4 Classes_Objects_ Functions


This section contains major classes of the major classes of the system and
function or method that can use in system.
`

3.4.1 Users

3.4.2 Customer / Client

3.4.3 Administrator or Admin


`

3.4.4 Orders
`

3.4.5 Order Details Clients


`
`

3.4.7 Shopping information

3.5 Non-Functional Requirements / Efficient Requirements

Non-functional requirements are used to describe the system contains.


Functional requirements are the functions of the system and services of the
system and nonfunctional requirements describe actual constrains that will be
on proposed system.

3.5.1 Performance & Working


Online Shopping on Laptop Pint is having good activity then the different
online shopping’s sites.
Laptop Point has good performance and give accurate to its user and it’s also
clients.

3.5.2 Reliability & Sharing


OSB site is more reliable for its share the information to their users. User can
purchase anything from the Laptop Point and then heed decided the product and
order them.

3.5.3 Availability Service


Laptop Point site is avail 24 hours and provided the service to its user and gave the new
ideas of to their customer and Clients. Clients satisfied the performance of the laptop
point.
`

3.5.4 Security& Denney UN authorized access


The Laptop Point Provided the service to their customers to secure data from
UN authorized access. The unauthorized Danger for User Data.

3.5.5 Maintainability and Updating


The Laptop Point Provide the faculty to their customer that can update their
product with the passage of the time.

3.5.6 Portability & Different Platform


The Laptop provides the facility and service the Laptop Point can be run on any
version of windows.

4. Analysis Models
The information that can be used in development of the software are
necessary element will be added in software. S.R.S also include the whole
description in short way and then provide description. This model that will
used also move back and traceable if the user requirements change in any
situation.

4.1 Sequence Diagrams of Laptop Point

4.2 Data Flow Diagrams (DFD) of Laptop Point


Context Level Data Flow Diagrammed:
LEVEL 0 Data Flow Diagrammed:
`

LEVEL 1 DFD OF OSB


`

4.3 State_Transition_Diagrams_(STD) and Their_States

5. Supporting_and_Required _Information

Appendix _A_environment Research _on the:


part _1
part_ 2
part_ 3
………
Part _n
`

Methodology used:
We use Universal model for this project.
1. Techniques used:
 HTML5
 PHP
 MySQL
 CSS 3
 JavaScript
2. Tools used:
 Dream weaver
 Xampp server

SRS Laptop Point


ORIGINALITY REPORT

8 %
SIMILARITY INDEX
6% 2% 9%
INTERNET SOURCES PUBLICATIONS STUDENT PAPERS
PRIMARY SOURCES

1
Submitted to Higher Education Commission 8%
Pakistan
`

SSD
`

1. INTRODUCTION
a. .0 Purpose_Aim
The aim of the Programmer view document of (SDD) is all of the way in any point
of view related to the Presented architecture. SDD are provide the better help to
develop and organize the code of the software that will be produced.SDD are also
the body part of the required software that will developed. The SDD are better
solution provided by the programmer to test their software in organize way and the
deliver to their customer.
SDD are also provide information about the architecture of the system.

b. .0 Scope_Limites
The task entitled "Web based shopping administration arrangement of general
laptops" empowers client to purchase portable or embellishments from anyplace
through on the web. This application advances a part of the things for shopping. To
buy things, customer needs to make a record. The people who do not have a record,
they can simply see the open thing. The product outline advancement of
undertaking is single record. The fundamental motivation behind web based
shopping administration arrangement of all inclusive laptops is to give data about
various organization of portable. It likewise gives data of new brand and market
cost of brand. It likewise give office to client to choose value extend .It additionally
give office to buy versatile.
The working of the Laptop Point are based on the delivery of the laptop in any
where in required places according to their criteria and it will be the facility to
purchase the product in online way. The custumer or

1.3.0 Overview_Presentation
The project entitled “Laptop Point” enables customer to buy Computer in order
online. They also buy the Computer or Laptops from the shop. The aim of to
develop a project to online that our customer can contact from anywhere in the
world.
The “Laptop Point” also provides the updating of price on computer or Laptops.
The user or client check the price of the product and order the product online. They
purchase the Computer or Laptop anywhere from the world.
The customer visits the items of “Laptop Point” in internet. They can just chose the
product and replace the order of product. The product Deliver to the client in
received postal address of the client. The laptop point is way that can user interact
the shop keeper. The shop keeper provided the necessary detail to their customer.

1.4.0 Reference_Material_Help
Referenceces Material http://Www.w3school.com
http://Www.tutrioal.com
`

1.5.0 Definitions_and_Acronyms
Software_Design_Documentation_ (SDD)
Data_Flow_Diagram_(DFD)
Personal_Home_Page_(PHP)
Hyper_Text_Markup_Language_(HTML)
Case-Cascading-Style-Sheet_(CSS)
Context_Flow_Diagram_(CFD)
Integrated_Development_Environments_(IDE)
Structured_Query_Language_(SQL)
Graphical_user_interface_(GUI)
Internet_protocol_(IP)

2.0 SYSTEM_OVERVIEW and Technologies

2.1.0 Technologies used


PHP and HTML are used in the construction on the Project and we are used My SQL
Database in the Project.
PHP are also used in server side and also used. The client side are usage the
HTML,CSS,SCRIPT, Java and etc.
2.2.0 Application_overview
The primary purpose of the project is to provide the facility to the customer that will be
used a website and takes facilities. The Software is design in a way on one document.
The aims of Laptop Point to purchase their information to their customers about the
computer generation and models. It provided the new price of a laptop. It the facilities
to see the requirements more clearly. The Laptop point is the way to provide the
information.
2.3.0 Design_languages_Ways
The U.M.L are defined for required project and Software. U.M.L are design of
“Laptop Point”
are the Client side are used.
2.4.0 System_environment_Interface
Application are used in all kind of windows and desktop environment.
2.5.0 Assumptions_Advantages

The Client are connect the internet and takes the advanctes of the “Laptop Point” that
they will be referred .

2.6.0 General_Constraint & Limits


System are used to local server to store data like My SQL is used for store date and
other required operation. Server side coding are exist in PHP. Front Side are used for
Bootstrap.
`

3.0 SYSTEM_ARCHITECTURE_DESIGN
3.1.0 Architectural Design

Determine the different interfaces to correspondences, for example, nearby system


conventions, and so on. These are conventions you should straightforwardly
connect with. On the off chance that you happen to utilize web benefits
straightforwardly to your application at that point don't show it here. On the
off chance that you are utilizing a custom convention to impart between
frameworks, at that point archive that convention here so originators realize
what to plan. In the event that is a normal convention, you can provide
information a current archive or R.F.C.
3.1.1.0 Web Architecture
The Internet Protocol are connection are required for shipping the from “Laptop Point”
web site. Laptop and desktop or other devices are connect using inter TCP/IP. The date
store in data base with the help of web server and the web server are also connect to
web application for storing data. The data and other information of user store in this
way.
`

3.1.2.0 Block_diagram

3.2.0 Decomposition_Detail
The customer visits the items of “Laptop Point” in internet. They can just chose the
product and replace the order of product. The product Deliver to the client in
received postal address of the client. The laptop point is way that can user interact
the shop keeper. The shop keeper provided the necessary detail to their customer.
`
`

3.2.1.0 Class_diagram
3.2.1.1.0 User_and_its_type
`

3.2.1.2.0 Order_class diagram_and_type


`

3.2.1.3.0 Customer_class_diagram
`

3.2.1.4.0 Complete_class_diagram
`

3.2.2.0 State_diagram

Actor…
Customer….
Admin…
3.2.3.0 Use_case
Use_case 1.0: login
`

Use_case 2.0: register.new.member


Use_case 3.0: change.password
Use_case 4.0: search.product
Use_case 5.0: search brand
Use_case 8.0:add.product
Use_case 9.0:delete.product
Use_case 10.0:custome. view.detail
Use_case 11.0:order
Use _case 12.0:buy.product
`

3.2.3.2.0 Use_Case # 2: Registration_of_new_customer

Actors Systems

Preconditions Also Entered in Site.

Post_condition Users successfuly log in System.

Descriptions User are use their accounts.

Actor actions System Response are show

Users are click the login from. System are display log in from.

User enter name and password System process have login successful or
not.
`

3.2.3.3.0 Use_Case # 3 Change_password


`

3.2.3.4.0 Use_Case #4 Search_product


`

3.2.3.5.0 Use Case #5 Search_by_Brand


`
`

3.2.3.8.0 Use_Case #7_add


`

3.2.3.9.0 Use_Case #Delete_item


`

3.2.3.10.0 Use_Case # Customer_view_the_detail_of_Laptop


`

3.2.3.11.0 Use_case# customer_order


`

3.2.3.11.0 Use_case # Buy_a_product


`

3.2.3.0 Sequence_diagram

3.2.3. 1.0 Sequence_diagram_for_Admin_add_new_item


`

3.2.3.0 3Sequence_diagram_for_Admin_Delete_item
`

3.2.3.0 3sequence_diagram_customer_product
`

3.2.4.0 Activity_diagram_

4.0 DATA_DESIGN & VIEW


4.1.0 Data_Description
My SQL are served in project to store data in database and retrieved data from the data
base. PHP are the way to served in Software to store Back end of project. The PHP are
also used to retrieve data from data base.

4.2.0 Data_Objects
ADMIN:-
Id: Specific Id or identification in Database.
Name: Describe Admin Name.
Age: Describe Admin age.
Address: Describe Admin address.
E-mail: Electronic Mail of admin that will be connect to Site.
Phone Number: Cell Number are used to talking about the system pros.
User:-
Id: Specific ID in database. .
Name: Describe the name of user.
Age: Describe the age of User.
Address: Describe the address of the user.
E-mail: E-mail of admin that will be used to connect with system.
Phone Number: Phone are used to talk with the user problems user.
Laptops: Like a Phone Number But alternatives.
Name: The Description and the name the laptops.
Price: It is show the price of laptops.
Id: Specific Identification of the laptops.
Company name: It is describes the name of the laptops company.
`

Model: It is Describes the models and year of the laptops.

Order:-
Order id:-Unique Identification ID of each customer.
Date and time:- The Date and time of the customer replaced the order.
Customer name:- Identify name of customer.
Bill:-
Bill id:- it described the required amount of product in bill.
Bill name: It identify bill name of customer with product.
Customer name: It show the name of customer.

4.3.0 Complete_ER_Diagram
`

4.2.0 Data_Dictionary
`

5.0 COMPONENT_DESIGN

6.0 HUMAN_LAYOUT_DESIGN
6.1.0 Overview of User Interface
6.1.1.0 Log_in
The User are connect through their user name and password. After entering the user
name and password the user interact the home page of the site. The home pages are
defined in different categories. For example
`

Laptops
Laptop Parts
It also provides the price of the laptop and other products. It also provide the detail
about the product and model of the product. The Laptop Point also provide the user
guide to their customers.

Log_in_from
`
`

6.1.2.0 Home_page
When the user login in the home page of Laptop Point the home page Display Like this.
The home page also divided in different section and it will display like this.
Information about Laptop. The information about Laptop Prices. The information about
the description of the Laptop. It also provided the information about the coming models
of the laptops.
`

6.1.3.0 Order_from
`

6.1.5 Admin Add product from


`

7.0 SWIM_LANE_DIAGRAMME
`

7.1.0 REQUIREMENTS_MATRIX
`

.
`

SDD Laptop Point


ORIGINALITY REPORT

13 %
SIMILARITY INDEX
7% 1% 10%
INTERNET SOURCES PUBLICATIONS STUDENT PAPERS
PRIMARY SOURCES

Submitted to Higher Education Commission


1
13%
Pakistan
`

.
`

You might also like