Professional Documents
Culture Documents
Shoes Sales and Purchase Srs
Shoes Sales and Purchase Srs
Project Supervisor
M/s IQRA YAQOOB
Submitted By
WAQAR UL HASSAN
FA19M2MB083
1
CERTIFICATE
This is to certify that Waqar Ul Hassan FA19M2MB083 has worked on and completed his
Software Project at Department of computer Sciences, The Islamia University of
Bahawalpur 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.
___________________
(Signature)
___________________
(Signature)
Accepted By:
_____________
(For office use)
EXORDIUM
2
In the name of Allah, the Compassionate, the Merciful.
3
DEDICATION
4
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 M/S IQRA YAQOOB 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..
5
PROJECT BRIEF
DATE OF COMPLETION:
TOOL USED:
Dream weaver
Xampp server
Php designer 8.
Table of Contents
1: INTRODUCTION.........................................................................1
1.1 PURPOSE OF PROJECT....................................................................1
1.2 SCOPE & LIMITS...............................................................................1
6
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
7
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 Appendix-B
-Dictionary 9
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.
8
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 Shose
Sale and Purchaseor Online Shoes Shop. These documents are providing the information about
the functional and non-functional specification about Shose Sale And Purchase. 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 Shose Sale and Purchase to
purchase their information to their customers about the shoes generation and models.
It provided the new price of a shoes. It the facilities to see the requirements more clearly.
The Shose Sale and Purchases 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.
9
The customer visits the items of “Shose Sale and Purchase” 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 Shose Sale and Purchaseis way that can user interact the
shop keeper. The shop keeper provided the necessary detail to their customer.
10
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 solve 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.
11
when you analyses the product according to A.D.A (Amercan _with
Disabilities _Act) on your edges.?
3.1.4.1 Microsoft_SQL_Server_7
The database must include will used in development of Shose Sale and Purchase. The software
will database will link the data items. The DBA also used in Shose Sale and Purchase. The SQL
are provide the facility to add the information in data base. The table included in Shose Sale and
Purchase feedback or relation table through SQL. The SQL used in Shose Sale and Purchase
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.
12
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.
Use Cases
The Part provide use cases of the functional requirements of the complete product.
13
Use _Case #:01
14
Use _Case #: 02
3.4.1 Users
15
3.4.2 Customer / Client
16
3.4.4 Orders
17
3.4.7 Shopping information
18
3.5 Non-Functional Requirements / Efficient Requirements
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.
19
4.1 Sequence Diagrams of Shose Sale and Purchase
20
LEVEL 1 DFD OF OSB
21
4.3 State_Transition_Diagrams_(STD) and Their_States
22
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
K
23