Online Cosmetic SRS

Software Requirements
Specification
for
Online Cosmetic Selling
Version 1.0 approved
Prepared by Siyaf Malik
Mega IT Marketing
12 April 2019
Software Requirements Specification for Online cosmetic selling Page ii
Table of Contents
Table of Contents...........................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................2
1.3 Intended Audience and Reading Suggestions.............................................................................2
1.4 Product Scope.............................................................................................................................2
1.5 References..................................................................................................................................3
2. Overall Description..................................................................................................................3
2.1 Product Perspective....................................................................................................................3
2.2 Product Functions.......................................................................................................................4
2.3 User Classes and Characteristics................................................................................................4
2.4 Operating Environment..............................................................................................................4
2.5 Design and Implementation Constraints.....................................................................................5
2.6 User Documentation...................................................................................................................5
2.7 Assumptions and Dependencies.................................................................................................5
3. External Interface Requirements...........................................................................................6
3.1 User Interfaces............................................................................................................................6
3.2 Hardware Interfaces...................................................................................................................6
3.3 Software Interfaces.....................................................................................................................6
3.4 Communications Interfaces........................................................................................................7
4. System Features.......................................................................................................................7
4.1 Registration Module...................................................................................................................8
4.2 Product Browse Module.............................................................................................................9
4.3 Shopping Cart Module...............................................................................................................9
4.4 Shipping and Billing Module.....................................................................................................9
4.5 Admin user management Module...............................................................................................9
4.6 Admin order management Module.............................................................................................9
5. Other Nonfunctional Requirements.......................................................................................9
5.1 Performance Requirements.........................................................................................................9
5.2 Safety Requirements...................................................................................................................9
5.3 Security Requirements..............................................................................................................10
5.4 Software Quality Attributes......................................................................................................10
5.5 Business Rules..........................................................................................................................10
6. Other Requirements..............................................................................................................10
Appendix A: Glossary..................................................................................................................11
Appendix B: Analysis Models.....................................................................................................11
Appendix C: To Be Determined List.............................................................................................11
Software Requirements Specification for online cosmetic selling Page 1
1. Introduction
Today everything is transformed into web as the technology is developing. From phone bills to
monthly transactions everything can be sent easily across the world. Online service systems
provide an easy approach for customers and other related people to track their services online
from home. This project is an attempt to build a software system which can interact with customer
and fulfill the needs of a good working website which includes requirement analysis done after
meeting with the customer requirements, Project planning carried out after carefully observing the
different modules easy and complex and looking at budget, System design and detail design
followed by coding, testing and integration and testing.
1.1 Purpose
The purpose of this document is to present a detailed Online Cosmetics Selling System. It will
explain the different functional as well as nonfunctional requirements of the system, the interfaces
of the system, what the system will do or how the system will interact with the external users, the
constraints under which it will operate. This Software Requirement Specification document will
provide a clear understanding of what is expected by the client in the proposed Online Event
Creation System. This will give a clear idea on how the software should be developed by the
development team for the end users. This SRS will provide a solid base or foundation for the
project.
1.2 Document Conventions
In “Online Cosmetics Selling” we have used IEEE format the Main Title Font Size is 18, Font type
is Arial, Face: Bold and sub Titles Font size is 11.
1.3 Intended Audience and Reading Suggestions
This is my own business and supervisor is my audience.
1.4 Product Scope
The purpose of this document is to present a detailed Online Cosmetics Selling. It will explain the
different functional as well as non-functional requirements of the system, the interfaces of the
system, what the system will do or how the system will interact with the external users, the
constraints under which it will operate. This Software Requirement Specification document will
provide a clear understanding of what is expected by the client in the proposed Online Cosmetics
Selling. This will give a clear idea on how the software should be developed by the development
team for the end users. This SRS will provide a solid base or foundation for the project. From this
SRS, the designers can design low level design documents and the testers can create test plans
and various test case documents.
The main goal of the project is to design a scalable and extensible system for managing the
Online Cosmetics Selling. The system will be designed with the user-centric approach that will
ensure that the user requirements mentioned in the documents must be full filled and must
conforms to the required standards. The proposed software is multi-platform software such that it
will work in all the operating systems and most of the browsers.
1.5 References
Below are my main source of information through which I have searched standards of coding and
software specifications:-
https://www.google.com/
https://www.wikipedia.org/
https://www.slideshare.net/
2. Overall Description
For solving the requirements of system, the developer is responsible for developing the system
which meets the System requirement specification.
This includes installation of the system at the client’s location and demonstrating the system and
acceptance testing should be successful. Develop a required user manual which will make the
user understand its function and describe it. If any training is required, it should be given to the
required personnel. After one year of installation, it’s maintenance should be done.
2.1 Product Perspective
My product is a replacement of certain existing systems that are developed earlier on high scale
and I am developing self-contained file having more functionalities of fast reporting using
enhanced database techniques and further necessities of my client.
2.2 Product Functions
 Data will be gathered and updated through web interface inputs to our database.
 Customer can register and search for products and find the suitable offers and purchase
the product with Cash on Delivery.
 Admin portal will control the system by checking the product inventory, stock maintenance
and confirming the delivery time to customer.
2.3 User Classes and Characteristics
Users are classified into three categories: -
 R1 users are those who can insert, update and delete any record until product is not
posted.
 R2 users will verify the physical status of products in stock and change the status of
record to posted.
 R3 users will see all stock and inventory reports.

2.4 Operating Environment
Microsoft Windows 7/8/10 operating system having browsers like chrome, firefox, Microsoft Edge
will be used to access the online system.
Minimum hardware requirement is 1 GB of RAM,100 GB of HDD and Pantium IV and above
processor.
2.5 Design and Implementation Constraints
Whenever necessary, this will help the customer and product user to view the records of the
product immediately. Whenever needed, this software also has the ability to add, update and
delete the record to smoother the process of the product activities (creating, updating, deleting
and viewing). English is used in GUI.
Login and password used for the identification of users (Cosmetic Product, Product Viewer and
Admin). This system will work on web server.
2.6 User Documentation
User document will be submitted with complete software at the end of project submission.
2.7 Assumptions and Dependencies
 Internet is must for our system. Without internet it cannot be access able because it is
web based application.

 Each User must view the site.
 There is only one Administrator.
 Server must always run under windows system as it is Microsoft product.
 Proper browsers should be installed.
 Text readers should be installed to view the help files.

3. External Interface Requirements
HTML5, CSS3 and JS and bootstrap components will be used as frontend language.
3.1 User Interfaces
 Professional look and feel.
 Use of FORMS with all registration forms.
 Browser testing and support for IE, MOZZILA, CHROME.
 Use of graphical tool for user friendliness.
 Responsive interfaces.
3.2 Hardware Interfaces
 Internet
 Server for deployment.
3.3 Software Interfaces
 Front end client on internet. Firefox, chrome, internet explorer, safari and all other web
browser.
 Database server. WAMMP

 Deployment end.
o PHP
o JavaScript
o HTML5
o CSS3
o Bootstrap
o AJAX
o jQuery
3.4 Communications Interfaces
HTTP protocol is used for this. This is web based so web browsers are used like chrome.
4. System Features
Four types of user would be in one websites.
1.One User will search the cosmetic product.
2.The customer see the product and its rates. if the customer is satisfied, then the customer order
for specific product.
3.We provide free home delivery and cash payment on that time.
4.Admin view the specific product which is chosen by user and save the user record to deliver the
product.
4.1 Registration Module
4.1.1 Description and Priority
To access the application every user need to register with their unique Login ID to
place an order.
4.1.2 Stimulus/Response Sequences
When user will enter Login ID and password and database will verify the
credentials, Login Approved popup will be displayed otherwise Incorrect Login ID or
password error will occur.
4.1.3 Functional Requirements
 Admin has the authority to add or block the users. He will log into the system
and can scroll through registered users.
 The customer will log into our system after registering him or herself. He or she
can then place the order and related information about the product can be given
then such as charges, brand etc.
 The viewers will search our system about the required product. if he desired to
buy the products he or she will then register and make payments before getting
it.
REQ-1: Login ID
REQ-2: Password
4.2 Product Browse Module
4.3 Shopping Cart Module
4.4 Shipping and Billing Module
4.5 Admin user management Module
4.6 Admin order management Module
5. Other Nonfunctional Requirements
5.1 Performance Requirements
While data is recording in database, data analyses must be fast to fetch big data sets in minimum
time. Views and indexing will be used in databased and more techniques will be used to
normalize the data. jQuery Datatable plugin is used to show reports on front end.
5.2 Safety Requirements
Only authorized users will be allowed to access the system.
5.3 Security Requirements
Unique Login ID will ensure the security of system.
5.4 Software Quality Attributes
 Portable.
 Reliable.
 Responsive.
 User friendly.
5.5 Business Rules
 R1 users are those who can insert, update and delete any record until product is not
posted.
 R2 users will verify the physical status of products in stock and change the status of
record to posted.
 R3 users will see all stock and inventory reports.

6. Other Requirements
MySQL phpMyAdmin is required as database. I will focus on Model-View-Controller coding
scheme in developing of my product such as CodeIgniter
Appendix A: Glossary
At this time there is no particular language that requires explanation for the development team.
As we know English is the universal language so it will be best for the communication to
developers others related persons.
Appendix B: Analysis Models
I will use the data flow diagram method to analyze this application because the main purpose of this
website to maintain all activities of website.
Appendix C: To Be Determined List
The table of contact is given in the start of this document through which the user can track the whole
document through any a proper and easy way.

Analysis Phase:
 Project SRS.
 Requirement Analysis Phase I:
 Abstract.
 Project Scheduling (using MS Project - Latest Version)
 Pert Diagram.
 Requirement Elicitation
 Observations
 Project Dependencies
 Interviews
 Questionnaire.
 Definition of the Problem
 Candidates
 Scope.
 Requirement Analysis Phase II:
 List of Inputs to the System.
 List of Output from the System
 Hardware and Software Requirements
 Hardware Requirements.
 Software Requirements.
 Feasibility Study.
 Technical.
 Financial.
 Economic
 Social.
Abstract
Today everything is transformed into web as the technology is developing. From phone
bills to monthly transactions everything can be sent easily across the world. Online
service systems provide an easy approach for customers and other related people to track
their services online from home. This project is an attempt to build a software system
which can interact with customer and fulfill the needs of a good working website which
includes requirement analysis done after meeting with the customer requirements, Project
planning carried out after carefully observing the different modules easy and complex and
looking at budget, System design and detail design followed by coding, testing and
integration and testing. Water fall model was adopted to scheme this design. System
design and detail design followed by coding, testing and integration and testing.
Introduction
After analyzing the requirements of the task to be performed, the next step is to analyze
the problem and understand its context. The first activity in the phase is studying the
existing system and other is to understand the requirements and domain of the new
system. Both the activities are equally important, but the first activity serves as a basis of
giving the functional specifications and then successful design of the proposed system.
Understanding the properties and requirements of a new system is more difficult and
requires creative thinking and understanding of existing running system is also difficult,
improper understanding of present system can lead diversion from solution.
E-commerce is fast gaining ground as an accepted and used business paradigm. More
and more business houses are implementing web sites providing functionality for
performing commercial transactions over the web. It is reasonable to say that the process
of shopping on the web is becoming common place.
The application is very useful where the buyer can directly buy the products from home
via internet on mobile or system. The application reduces lot of work load for customer as
well as owner.
REQUIREMENT ELICITATION:
Observations
This Mega It Marketing Cosmetics Store provides the facility to shop online. Customers
are identified properly first they will see a login form to validate their identity. Otherwise
they have to fill a registration form to register their account and login to the website. Then
a screen will appear where different Cosmetics items or products could be seen. If
customer wants to search any other item he can search by clicking on search bar. After
order the item our product account member will allow you to logout due to security
purposes. Observation could be Formal or Informal. This is most effective when and
analyst wants to obtain an understanding of a system. This technique used when analyst
wants either participates in or watches a person perform activities to learn about the
system.
Project dependencies:
FRONT END:
 HTML
Hyper Text Markup Language is a syntax used to format a text
document on the web.

 CSS
CSS is a style sheet language used for describing the look and
formatting of a document written in a markup language.

 JAVA SCRIPT
Java Script is a dynamic computer programming language. It is most
commonly used as part of web browsers, whose implementations allow
client-side scripts to interact with the user, control the browser, communicate
asynchronously, and alter the document content that is displayed. Java
Script is used to create popup windows displaying different alerts in the
system like “User registered successfully, Product added to cart” etc.
 jQuery
 Bootstrap
BACK END:
The back end is implemented using My SQL which is used to design the
databases.
My SQL:
My SQL is the world's second most widely used open-source relational database
management system (RDBMS). The SQL phrase stands for Structured Query Language.
Definition of the problem:
ERROR AVOIDANCE
At this stage care is to be taken to ensure that input data remains accurate form the stage
at which it is recorded upto the stage in which the data is accepted by the
system. This can be achieved only by means of careful control each time the data is
handled.
Candidates
1. Customer
2. Administrator
Customer
The customers can login to the System. They can view their product details and buy
their Items or Products. The customer can just view the information whereas they
could not make changes in the database.
Administrator:
The administrator plays an important role in the Online Cosmetics store. The
administrator controls the entire database. The report of the product is generated by
the administrator itself. The main role of the administrator is to secure the database
and can add/delete the products from the database.
Scope:
This Document plays a vital role in the development life cycle (SDLC) and it describes the
complete requirement of the system. It is meant for use by the developers and will be the
basic d u r i n g t e s t i n g p h a s e . A n y c h a n g e s m a d e t o t h e r e q u i r e m e n t s i n
t h e f u t u r e w i l l h a v e t o g o through formal change approval process.
Functionality:
Since it stands alone application, one or more user may use it at a time.
Usability:
Windows XP/7/8/10
Technology:
HTML, CSS, Javascript, jQuery, PHP Codeigniter
Reliability:
The system is available for 24 hours a day.

REQUIREMENT ANALYSIS PHASE-2

List of inputs to the system
INPUT DESIGN
Input design is the integral part of any web application. The main objective during the
input design is as given below:
To get precise information from user.
To ensure all required fields are filled by user.
To ensure that the input is acceptable and understood by the user.
INPUT STAGES:
The main input stages can be listed as below:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction
INPUT TYPES
It is necessary to determine the various types of inputs. Inputs can be categorized as
follows:
External inputs, which are prime inputs for the system.
Internal inputs, which are user communications with the system.
Operational, which are computer department’s communications to the system?

Interactive, which are inputs entered during a dialogue.
INPUT MEDIA
At this stage choice has to be made about the input media. To conclude about
the input media consideration has to be given to;
Type of input
Flexibility of format
Speed
Accuracy
Verification methods
Rejection rates
Ease of correction
Storage and handling requirements
Security
Easy to use
List of Outputs from the system
OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate
t h e r e s u l t s o f processing to users. They are also used to provides a
permanent copy of the results for later consultation. The various types of outputs in
general are:
External Outputs, whose destination is outside the organization.
Internal Outputs whose destination is within organization and they are the
User’s main interface with the computer.
Operational outputs whose use is purely with in the computer department.
Interface outputs, which involve the user in communicating directly with
OUTPUT DEFINITION
The outputs should be defined in terms of the following points:
Type of the output
Content of the output
Format of the output
Location of the output
Frequency of the output
Volume of the output
Sequence of the output It is not always desirable to print or display data as it
is held on a computer. It should be decided as which form of the output is the most
suitable. For Example
Will decimal points need to be inserted. Should leading zeros be suppressed.

Output Media
In the next stage it is to be decided that which medium is the most appropriate
for the output. The main considerations when deciding about the output media are:
The suitability for the device to the particular application.
The need for a hard copy.
The response time required.
The location of the users
The software and hardware available. Keeping in view the above description the
project is to have outputs mainly coming under the category of internal outputs.
The main outputs desired according to the requirement specification: The outputs were
needed to be generated as a hot copy and as well as queries to be viewed on
the screen. Keeping in view these outputs, the format for the output is taken from the
outputs, which are currently being obtained after manual processing. The
standard printer is to be used as output media for hard copies.
Hardware and Software Requirements:
Hardware Requirements:
CPU: Pentium IV or greater.
RAM: 1GB or greater.
Hard Disk: 100GB or greater.
Software Requirements
Wamp Server, Netbeans editor
Operating system Windows 7/8/10
Web browser: Chrome/Mozilla Firefox

Feasibility Study
The feasibility study tells us the problem and the information needs of the customers. It is
made to determine the resources required to provide an information systems solution, the
cost and benefits of such a solution, and the feasibility of such a solution. The analyst
conducting the study gathers information using a variety of methods, the most popular of
which are:
Interviewing users, employees, managers, and customers.
Developing and administering questionnaires to interested stakeholders, such as
potential users of the information system.
Observing or monitoring users of the current system to determine their needs as well
as their satisfaction and dissatisfaction with the current system.
Collecting, examining, and analyzing documents, reports, layouts, procedures,
manuals, and any other documentation relating to the operations of the current
system.
Modeling, observing, and simulating the work activities of the current system.
Technical
Technical phase all the working forms are work as per according to the client
requirement validation other interface security. This project use both hardware and
software so it is very important that both hardware and software will successfully
satisfy the requirements. The project will be developed easily by available technology.
The possibility that the organization has or can procure the necessary resources. This
is demonstrated if the needed hardware and software are available in the marketplace
or can be developed by the time of implementation.
Financial
This website provides cost effective to client so that all the selling online no place
required to sell anything just provide easy access to their customer on one click and
all then delivery at home. Checking of cost which is invested on the project. If the cost
is acceptable for us and for client, then we will go for more. It includes identification of
all the benefits.
Cost of development
In cost of development, programmers, analyst other people’s salary who are related in
development. Again costs of computer, hardware, testing, training etc. are involved.
Cost of using the system
Cost of using the system is pre-defined and in some times it’s depends on user. Cost
of using a system can be divided in two ways. Fixed cost and variable cost:
Fixed cost: Software purchase cost & license cost are fixed
Variable cost: Salaries of system operation are fixed, but it depends on client software
also.
Cost of computer use
Suppliers e.g. printer, paper, magnetic tapes, floppy disks.
Social
Client is socially strong and the customer are very nearer to their buyer and also
communication is very easy. Social feasibility is a determination of whether a
proposed project is acceptable to the people or not. This determination typically
examines the probability of the project accepted by the group directly affected by the
proposed system change. The product will be used to serve the customers in All Over
Pakistan.

Online Cosmetic SRS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Cosmetic SRS

Uploaded by

Copyright:

Available Formats

Software Requirements

Online Cosmetic Selling

Version 1.0 approved

Prepared by Siyaf Malik

followed by coding, testing and integration and testing.

is Arial, Face: Bold and sub Titles Font size is 11.

This is my own business and supervisor is my audience.

and various test case documents.

which meets the System requirement specification.

enhanced database techniques and further necessities of my client.

the product with Cash on Delivery.

and confirming the delivery time to customer.

Users are classified into three categories: -

 R3 users will see all stock and inventory reports.

will be used to access the online system.

Minimum hardware requirement is 1 GB of RAM,100 GB of HDD and Pantium IV and above

and viewing). English is used in GUI.

Admin). This system will work on web server.

web based application.

 Each User must view the site.

 There is only one Administrator.

 Server must always run under windows system as it is Microsoft product.

 Proper browsers should be installed.

 Text readers should be installed to view the help files.

 Professional look and feel.

 Use of FORMS with all registration forms.

 Browser testing and support for IE, MOZZILA, CHROME.

 Use of graphical tool for user friendliness.

 Server for deployment.

 Database server. WAMMP

Four types of user would be in one websites.

1.One User will search the cosmetic product.

for specific product.

credentials, Login Approved popup will be displayed otherwise Incorrect Login ID or

password error will occur.

and can scroll through registered users.

then such as charges, brand etc.

Only authorized users will be allowed to access the system.

Unique Login ID will ensure the security of system.

 R3 users will see all stock and inventory reports.

MySQL phpMyAdmin is required as database. I will focus on Model-View-Controller coding

scheme in developing of my product such as CodeIgniter

developers others related persons.

website to maintain all activities of website.

document through any a proper and easy way.

 Requirement Analysis Phase I:

improper understanding of present system can lead diversion from solution.

of shopping on the web is becoming common place.

document on the web.

formatting of a document written in a markup language.

Java Script is a dynamic computer programming language. It is most

commonly used as part of web browsers, whose implementations allow

asynchronously, and alter the document content that is displayed. Java

Script is used to create popup windows displaying different alerts in the

system like “User registered successfully, Product added to cart” etc.

Definition of the problem:

could not make changes in the database.

and can add/delete the products from the database.

t h e f u t u r e w i l l h a v e t o g o through formal change approval process.

HTML, CSS, Javascript, jQuery, PHP Codeigniter

The system is available for 24 hours a day.

REQUIREMENT ANALYSIS PHASE-2

input design is as given below: