Revision History

Candidate Name Roll No Date

Attia bano,Nageena ,2022

bibi

Document Approval
The following software Requirement Specification has been accepted and approved by the
following:
Name Signature Date

15 April,2022
 Table of Contents
Sr# Chapter Page
1 Introduction 6
1.1 Objective 6
1.1.1 Purpose 7
1.1.2 Module 7
1.2 Requirement Specification 8
1.3 Scope 8
1.4 Definitions, Acronyms, and Abbreviations 8
1.4.1 Web application 8
2 System Overview 11
2.1 Technology Used 11
2.1.1 Php storm 11
2.1.2 MySQL Database 11
2.2 Design Languages 12
2.3 Assumption and Dependencies 13
3 Specific Requirements 15
3.1 Interface requirement 15
3.2 Functional Requirement 15
3.3 Use Cases 18
 3.4 Non-functional Requirement 20
3.5 Logical Database Requirements 20
3.5.1 ER Diagram 20
3.6 Design Constraints 22
4 Analysis Models 24
4.1 Sequence Diagrams 25
4.2 Data flow Diagrams(DFD) 27
4.3 Context Diagram 28
4.3.1 Level Diagrams 29
4.3.1.1 Level 1 Artist features Diagram 29
4.3.1.2 Level 2 Admin features Diagram 30
5 System Architecture 32
5.1 Class Diagram 32
5.2 Object Diagram 34
5.3 Activity Diagram for user 34
5.4 Activity Diagram for Artist 35
5.5 State Chart Diagram 36
5.5.1 State Chart Diagram for Transaction 37
6 Data Design 39
6.1 Tables of Database 39
6.2 Data Dictionary 45
7 Human Interface Design 48
7.1 Screen Images 48
8 Supporting Information 56
8.1 Overview of the Technology 56
8.2 Appendix A-Background Research on: 57
 • Introduction
Online shopping is a form of electronic commerce which allows consumers to directly buy goods
or services from a seller over the Internet using a web browser or a mobile app. Consumers find a
product of interest by visiting the website of the retailer directly or by searching among
alternative vendors using a shopping search engine, which displays the same product's
availability and pricing at different e-retailers. As of 2020, customers can shop online using a
range of different computers and devices, including desktop computers, laptops, tablet computers
and smartphones.
This document explains the specifications and requirements of the “Nirala online shopping
store” a website. It describes the functional and Non-functional requirements of the site such as
interface, design and details.
1.1 Objective
The objectives of developing the NOSS are as given below: -

• To store data of the user who are registered in the site.

• Promoting a service or product online.
• Selling a service or product.
• Providing product support or customer service.
• Providing corporate information.
• Establishing brand awareness and corporate identity
• Easy registration
• Login dependent information retrieval and updating. Correct and consistent
maintenance of data and its quick retrieval
• Improving the switches button and hyperlink so that the candidate shall find all
the queries they need at first sight.
1.1.1 Purpose
• NOSS is a website and it is very helpful for the online shopping lovers.
• A typical online store enables the customer to browse the firm's range of products and
services, view photos or images of the products, along with information about the
 product specifications, features and prices. Online stores usually enable shoppers to use
"search" features to find specific models, brands or items.
• An online store is a website where buyers purchase goods or services from. An example
of an online store is a brick-and-mortar retail business with a website. An online store is
an ecommerce website or app where buyers can see a catalog of products or services and
electronically purchase them.
1.1.2 Modules:
• Login
• User Registration
• Product information managment
• content managment
• order managment
• cart and checkout
• payment method
• Contacts Us
HARDWARE AND SOFTWARE SPECIFICATIONS SOFTWARE REQUIREMENTS:
• Operating System : Windows XP, 2000.
• Language : HTML, Php
• Technologies : Microsoft.
• Data Bases : Xampp
• IDE : Visual Studio 2008
HARDWARE REQUIREMENTS:
• Processor : Any Processor above 500 MHz
• Ram : 128Mb.
• Hard Disk : 10 GB.
• Compact Disk : 650 Mb.
• Input device : Standard Keyboard and Mouse.
• Output device : High Resolution Monitor.

1.2. Requirement Specification:

Here, the focus is on specifying what has been found giving analysis such
as representation, specification languages and tools, and checking the
specifications are addressed during this activity.
The requirement phase terminates with the production of the validate SRS
document. Producing the SRS document is the basic of this phase.
1.3 Scope
An AWMS is a website that displays artworks. Usually, the AWMS is run as a business,
with the purpose of displaying the artwork being to promote it to potential buyers. Other
variations include: AWMS market for collectors also known as an online secondary
market.
1.4 Definitions, acronyms and Abbreviations
1.4.1 Web Applications
A type of software that runs on some server. It is usually a piece of software that runs
online.
• Apache

Software to host The Web Locally. It Is Open Source Software.

• MySQLi

Database Management System for Managing Database. It Is Also Open Source Software.

• Xampp

Xampp is combination of apache php and MYSQLi database

• Server

Server is a powerful system that hosts some web Application.

• Open source

A software that is freely available in the market to download its codes for research or
modifications.

Web browser

Software to surf the web

• Database
A database is the collection of related data that is stored in an efficient and compact
manner. Data is stored in the form of tables in the database. Table is a collection of
rows and columns.
RAM
Random Access Memory, a type of memory. It is a temporary memory.
References
IEEE STD 830-1998, IEEE recommended practice for software requirement
specification.
 • System Overview
2.1 Technologies Used

The system is coded with PHP programming language by using PHP Storm development
environment. We will use MySQL for database.

2.1.1 PHP Storm

PhpStorm provides an editor for PHP, HTML and JavaScript with on-the-fly code analysis, error
prevention and automated refactoring for PHP and JavaScript code.

All PHP tools

The editor actually 'gets' your code and deeply understands its structure, supporting all
PHP language features for modern and legacy projects. It provides the best code completion,
refactoring, on-the-fly error prevention, and more.
Front-end technologies included
Make the most of the cutting edge front-end technologies, such as HTML5, CSS and
JavaScript, with re factorings, debugging and unit testing available. See changes instantly in the
browser thanks to Live Edit.

Built-in developer tools

Perform many routine tasks right from the IDE, thanks to Version Control Systems
integration, support for remote deployment, databases/SQL, command-line tools, Vagrant,
Composer, REST Client, and many other tools.

PhpStorm = Web Storm + PHP + DB/SQL

All the features of Web Storm are included into PhpStorm, and full-fledged support for
PHP and Databases/SQL support are added on top.

2.1.2 MySQL Database

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses.
MySQL Extension is developed, marketed, and supported by MySQL.
• MySQL works on many operating systems and with many languages including PHP,
PERL, C, C++, JAVA, etc.
• MySQL works very quickly and works well even with large data sets.
• MySQL is very friendly to PHP, the most appreciated language for web development.
• MySQL supports large databases, up to 50 million rows or more in a table.
2.2 Design Languages

Unified Modeling Language (UML), is used for graphical representations of viewpoints in

Online Student Attendance System Project.

Event Perspective

As mentioned above, this website is totally independent and not a part of some existing
system. This website needs a server i.e. web server or a local server, apache in our case.
The client send request to the server, the application host on some server will
communicate to the application and to the database management system if needed to
facilitate the request. The database server wills responses user according to demands of
the user.

2.3 Assumptions and Dependencies

There are some number of factors that are consider to be fulfill to make the project work
according to the requirements described in document.
• The mentioned system will use the latest tool available in the market, so it is
assumed the user will use the latest web browser for working that is load the UI
properly.
• There is huge involvement of php code so it is assumed that the user will not
disable the php in the browser to run the website smoothly.
• It is assumed that the front-end user is specifically from Pakistan.
• System date corresponds to Actual date and Time
• Users of the system are technically skilled persons and they understand that how
to handle this system. Login into the admin panel after authentication.
3 SPECIFIC REQUIREMENTS
3.1 Interface Requirements
User interface
There are two types of user interface.
• Client User Interface
• Administrator User Interface
Client interface
The minimal requirements are that the user would be able to communicate to the system
using GUI. GUI stand for graphical User Interface.GUI is bases on HTML5, CSS3, php
and different frameworks and libraries. a JS library and Bootstrap, a CSS framework.
Different GUI based component are used for the following actions.
Administrator Interface
The minimal requirements required for the administrator interface that the admin will
access the control panel through a GUI using some web browser. The GUI again bases on
HTML5, CSS3 and php and different libraries and frameworks. No command line utility
will be given to the user to access the system. Hyperlinks and buttons will be provided to
the admin to perform different tasks.
Hardware Interfaces
AWMS is a Web site that is why all hardware interface of this, will be those of server On
top of which it will be running. Hence the website will incorporate the server for all the
hardware instances such as CPU, memory and communication.
Software interface
As our mentioned system runs on a server, so a server having the capabilities to run the scripts
written in PHP language is required. Moreover the server should have the database like Mysqli in
order to make the application able to make transactions with records in database.
3.2 Functional Requirements
This section narrates the features and process performed by the web site. Firstly, the following
features of the system and their interaction with administrator are described check paintings,
Delete artist Update profiles, Update User, and Delete User. Then the following features related
to User are described: Search Paintings, Registration, and feedback, they are followed by a
detailed specification of the functionality of the AWMS. Data definition will also be discus in
this document .Data flow diagram will be provided in these documents.
• Add Artist profile
Introduction
This functional feature deals with the administrator. The admin can add new painting in the
database by using the interface of the AWMS.
Inputs
The admin will enter the Artist name, Artist address, time, date and other details about profile
using different UI elements.
Processing
The server with communicate the MySQL to insert the new item in the database.
Outputs
A success message will be shown to the user and database will be updated.
Error Handling
An error message will be shown upon some error while updating the item in the database.
• Delete artist profile
Introduction
This functional feature also deals with the administrator. The admin can delete Artist in the
database by using the interface of the AWMS.
Inputs
The admin will delete the item in the database with the help of ID of the artist. He would select
the id of the artist from a dropdown menu.
Processing
The server with communicate the Mysqli to delete the item in the database.
Outputs
A success message will be shown to the user and database will be updated.
Error Handling
An error message will be shown upon some error while deleting the item in the database.
• Update Existing User
Introduction
This functional feature also deals with the administrator. The admin can update an existing user
in the database by using the interface of the AWMS.
Inputs
The admin would edit the user name, user address and other details about the user using different
UI.
Processing
The server with communicate the Mysqli to update the item in the database.
Outputs
A success message will be shown to the user and database will be updated.
Error Handling
An error message will be shown upon some error while updating the admin in the database.
• New User Registration
Introduction
This functional feature deals with the user who is using the application’s front-end .He would
have to register him before any detail.
Inputs
The user will enter his complete name, address, his phone number, email address to register him.
Processing
The server with communicate the Mysqli to and the user will be added to the database.
Outputs
Database will be updated with a new user and a success message will.
Error Handling
An error message will be shown upon some error while searching a specific item the database.
• User Login:
Introduction:
The user may login to artist detail by using the credentials assigned to him upon registration.
Inputs
The user will enter his email address and password to login.
Processing
The application will communicate to the database to check if the user has registered already.
Outputs
User will be logged in if the entered credentials meets the one in the database and a success
message will be shown otherwise he will be asked to enter correct data.
Error Handling
An error message will be shown upon some error while logging into the database.
3.3 Use case Diagram
Use case describe the high level functions and scope of a system. These diagram also identify the
interactions between the system and actors. The use and actors in use case diagram describe what
the system does and how the actors use it but not how the system operates internally.
3.4 Non-functional Requirement
Performance
• Average load time of the start page of website should be less than 5 seconds.
• Average response time of the system should be less than 10 seconds.
• Our system should easily accessible on the system having minimum internet speed of
1MB/s.
Reliability
There will be a maximum of 1 bug/KLOC.
Supportability
All code will be written as specified by the Hungarian Naming Convention.
Availability
Seminar Generator will be available to client 7 days a week and 24 hours a day. In case of any
system crash a backup will be available to make the system live.
Security
Users’ information will be secure and he will be able to access only their own personal
information.
3.5 Logical Database Requirements
A logical database must be able to access the identify all files within the storage system to
operate correctly , whereas a physical database manage a much smaller fields of information
sometimes , a physical database stores only a single file with one value or word in it.
3.5.1 ER Diagram
An entity relationship diagrams is essential for modeling the data store in a database. It is the
basic design upon which a database is build. ER diagrams specify what data we will store, the
entities and their attributes.
Note:
Here,
Uname=Username, Pwd=Password, Fname= First name
3.6 Design Constraints
Design constraints are limitations on a design. These include imposed limitations that you don’t
control and limitations that self-imposed as a way to improve a design.
3.6.1 Parent component
There is no parent of “AWMS”. It works its own.
3.6.2 Application Language
Language used for this application is mainly “PHP” for server side logics and HTML.CSS for
front-end side.
4. Analysis Models
List all analysis models used in developing specific requirements previously given in this SRS.
Each model should include an introduction and a narrative description. Furthermore, each model
should be traceable the SRS’s requirement.
• The model that is basically being followed is the WATER FALL MODEL, which states
that the phases are organized in a linear order. First of all the feasibility study is done.
Once that part is over the requirement analysis and project planning begins. If system
exists one and modification and addition of new module is needed, analysis of present
system can be used as basic model.
• The design starts after the requirement analysis is complete and the coding begins after
 the design is complete. Once the programming is completed, the testing is done.
In this model the sequence of activities performed in a software development project are:-
• Requirement
• Analysis
• System design
• Implementation
• Testing
• Maintenance

4.1 Sequence Diagram

A sequence diagram or system sequence diagram shows objects interactions arranged in time
sequence in the fields of software engineering, it depicts the objects involved in the scenario and
the sequence of the messages exchanged between the objects needed to carry out the
functionality of scenario.
4.2 Data flow Diagrams (DFD)
A DFD is a way of representing a flow of data through a process or a system. The DFD also
provides information about the outputs and inputs of each entity and the process itself. A data
flow diagram has no control flow there are no decision rules and loops.

4.3 Context Diagram

A system context diagram in engineering is a diagram that defines the boundary between the
system, or part of a system and its environment showing the entities that interact with it. This
diagram is a high level view of a system.

4.3.1 Level Diagram

4.3.1.1 Level 1 Artist Features Diagram
4.3.1.2 level 2 Admin Features Diagram
• System Architecture
• Class Diagram
Transaction
Transaction ID (k)
CustomerID (k)
PurchaseDate
Sales prize
CUSTOMER
CustomerID (k)
Name
Email
Contact No
Address
Zip code
City
State
5.2Object Diagram
5.3 Activity Diagram for user
5.4 Activity Diagram for Artist

5.5 Sate Chat Diagrams

State Chart Diagram for online registration

5.5.1 State chart diagram for online transaction
6. Data Design
6.1 Tables of Database
• Open The Browser and put inside
http://localhost/artwork/

• Art_work

Description
This website about art_work where some website pages like admin, pages, reach_us, slider,
social_media, user_reg.

• Admin

Description

This Table keeps record of admin (like, id, Full name, Username, password)

• Pages

Description
This table keep record of dashboard, home and about_us.

• Reach_us

Description

This table keep record of admin address, city, state, zip code and contact_number.
 • Slider

Description

This table keep record of art image id, image name and path.

• Social_Media

Description

This table keep record of admin id, Facebook page’s link, twitter’s link and instagram link.
 • User_reg

Description
This table keep record of user first name, last name, gender, contact number, email, password
and address.
6.2 Data Dictionary
• Art_work
• Admin
• Pages
• Reach_us
• Slider
• Social media
• User_reg
• Admin

• Id

• Full_nm

• Username

• Password

• Pages

• Dashboard

• Home
• About_us

• Reach_us

• Id

• Name

• Address

• City

• State

• Zip code

• Contect_number

• Slider

• Id

• Img_nm

• Path

• Social_media

• Id

• Facebook

• Twitter
• Instagram

• User_reg

• First name

• Lastname

• Gender

• Contact

• Email

• Password

• Address
7. Human Interface Design
7.2 Screen Images
• Open The Browser and put inside
http://localhost/artwork/
• Sign_up

• Log In

• Home Page

• Slider
• Recent Products

• About us

• Arts

• Reach us

• Cart us

• Footer
8. Supporting Information
8.1 Overview of the Technology
Front end: HTML, CSS
• Html is used to create and save web document (For example, Notepad/ Notepad++).
• CSS (Cascading Style Sheets) create attractive layout.
Back end: PHP, MySQL
• PHP: Hypertext preprocessor (PHP) is a Technology that allows software developers to
create dynamically generated web pages in HTML, or other document types as per client
request. PHP is open source software.
• MySQL: MySQL is a Database, widely used for accessing querying, updating and
managing data in Databases.
Software Requirement
• XAMPP Server

8.2 Appendix A
Glossary
• Actor
It represents a role, external entity that interacts with our system.
• Use case
Graphical Represent of interaction among system and actor.
• Scenario
The time of actual input and expected output.
• Use case diagram
Represent use the services and functionality by the system by the actor. UML Use Case
Diagrams. Use case diagrams are usually referred to as behavior diagrams used to
describe a set of actions (use cases) that some system or systems (subject) should or can
 perform in collaboration with one or more external users of the system (actors).

• Use case Realization

How the use case realizes in the design table model.
• Activity diagram
Graphical represent of the process flow of use case etc. Activity diagram is another
important diagram in UML to describe the dynamic aspects of the system. Activity
diagram is basically a flowchart to represent the flow from one activity to another
activity. The activity can be described as an operation of the system. The control flow is
drawn from one operation to another.

• Sequence diagram
Represents the interaction of an object to perform a job. A sequence diagram shows
object interactions arranged in time sequence. It depicts the objects and classes involved
in the scenario and the sequence of messages exchanged between the objects needed to
carry out the functionality of the scenario. ... Sequence diagrams are sometimes called
event diagrams or event scenarios

• Collaboration diagram
Alternative representation of sequence diagram.
• Data model
Represent the persistence object model.
• Class diagram
A class diagram is an illustration of the relationships and source code dependencies
among classes in the Unified Modeling Language (UML). In this context, a class defines
the methods and variables in an object, which is a specific entity in a program or the unit
of code representing that entity
• State Transition Diagram
Specifically a state diagram describes the behavior of a single object in response to a
series of events in a system. Sometimes it's also known as a state machine diagram. This
UML diagram models the dynamic flow of control from state to state of a particular
object within a system.
Database
• Data flow diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modeling its process aspects. A DFD is often used as a preliminary
step to create an overview of the system without going into great detail, which can later
 be elaborated.
• Entities
An entity is any object in the system that we want to model and store information about.
Entities are usually recognizable concepts, either concrete or abstract, such as person,
places, things, or events which have relevance to the database. Some specific examples of
entities are user admin and Artist.
• Attributes
In general, an attribute is a characteristic. In a database management system (DBMS), an
attribute refers to a database component, such as a table. It also may refer to a database
field. Attributes describe the instances in the row of a database.
• Relationship
A relationship, in the context of databases, is a situation that exists between two relational
database tables when one table has a foreign key that references the primary key of the
other table. Relationships allow relational databases to split and store data in different
tables, while linking disparate data items.