Professional Documents
Culture Documents
Documentation of Final Project
Documentation of Final Project
Documentation of Final Project
Project Supervisor
Sir Zahid Aslam
Submitted By
In our opinion, it is satisfactory and up to the mark and therefore fulfills the
requirements of MCS in Computer Sciences.
___________________
(Signature)
___________________
(Signature)
Accepted By:
_____________
(For office use)
EXORDIUM
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..
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 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
DATE OF COMPLETION:
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
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
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.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.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.
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.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.
Use_Cases
The Part provide use cases of the functional_requirements of the complete
product.
Use _Case #: 02
…
3.4.1 Users
3.4.4 Orders
`
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.
5. Supporting_and_Required _Information
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
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)
The Client are connect the internet and takes the advanctes of the “Laptop Point” that
they will be referred .
3.0 SYSTEM_ARCHITECTURE_DESIGN
3.1.0 Architectural Design
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.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
`
Actors Systems
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.0 Sequence_diagram
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.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.
`
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
`
7.0 SWIM_LANE_DIAGRAMME
`
7.1.0 REQUIREMENTS_MATRIX
`
.
`
13 %
SIMILARITY INDEX
7% 1% 10%
INTERNET SOURCES PUBLICATIONS STUDENT PAPERS
PRIMARY SOURCES
.
`