1.  Introduction  

1.1   Purpose

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

This System
Requirement Specification (SRS) describe the functionality of the tailoring
management system. Instead of writing measurement manually, the customer will
be able to write itself according to this SRS. It explain functional features
of tailoring for easiness of tailor user. It just not only fulfill the User requirements,
as well as Customer requirements. This SRS will provide a friendly interface
for Advance Tailoring. This SRS developed
a Web application is intended to provide complete solutions for vendors as well
as customers through a single get way using the internet. It will enable vendors to setup online shop, customer
to browse through the website and purchase the products related to the
tailoring garments online without having to visit the shop physically.

Scope

The Tailoring website is intended to work as an online. Admin user will
be facilitated by providing the following facilities:

Admin Area:

Ø  Add Products.

Ø  Remove Products.

Ø  Update Product details.

Ø  Mange user signup/without sign-up
user.

Ø  Manage customer data related
to Tailoring.

Ø  Update the measurement on
user request.

Ø  Will be able to send an
order on the customer requirement.

                                                                                    

       Following functionalities will be
provided to customers:

Ø  Option will be given to customer :

ü  Signup

ü  Without Signup

Ø Sign-up user:

ü  Able to sign-up.

ü  Able to send order.

ü  He can send his data, eg,
address etc.

ü  Search and view details of
products.

ü  Get discount on Featured
products.

ü  Can see the data that
submitted, on login.

ü  Send request on updates the
measurement which submitted.

 

Ø  Without signup:

ü  Search and view details of
products.

ü  He just enable to send an
order.

ü  Just select
small/medium/large/extra-large.

ü  He can send his data egg. Address
etc.

1.2   Definitions,
Acronyms, and Abbreviations


AT:
Advance Tailoring.


SRS: System
requirement Specification.


GUI:
Graphical User Interface.


DB: Database 


SQL:
Structure Query Language is a system software tool, through which database
connect and manage the records.

1.4 References

In this subsection:

Ø  SRS
Template

Ø  www.youtube.com

Ø  www.google.com

Ø  www.slideshsre.com

1.5 Overview

In this subsection:

(1)   Describe
what the rest of the SRS contains

(2)   Explain
how the SRS is organized

Don’t rehash the table of contents here.  Point people to the parts of the document
they are most concerned with. 
Customers/potential users care about section 2, developers care about
section 3.

2.  The Overall Description

 2.1 Product
Perspective:

The main purpose of this SRS is to provide facility
for that kind of customer which do not want to visit shops and it might be not
interesting in visiting for the shop/market. Although in the age of modern era,
anybody don’t have time to visit shops. According to this SRS the customer will
be able to save his precious time. He will get information of all tailoring
products like Kurta Shalwar, Waistcoat etc. AT tailoring system will provide a
better stuff of clothes and option given to the customer whether he want to sign-up
for the proper measurement of the product, OR he just want to get average size
of product like Medium/large/extra

2.1.1 Operations:

Ø 
Login: In
this operation the Admin/Sign-up User will be Login first. The purpose of Login
Admin is to manage the records. While the Sign-up user login for sending information
about measurements and address etc.

Ø 
Logout:
When login in the website, after managing the records from Admin and after
sending data from Sign-up user. This operation will logout for both type of
Users in the web site

Ø 
Place
Order: In this operation a customers can send an order, the customer can be
signup or without signup. The signup user will have to login first for the
proper measurement of product.

Ø 
Ordered
Receive: In this operation the Admin will received an order from the
customers, that orders will be received in the DB first and then Admin can view
the orders.

Ø 
Signup: According
to this SRS the end users will be able to Sign up in the system..

2.1.2 Site
Adaptation Requirements

This is a kind of online of website and it required
an Internet Connection. With the help of Internet Connection the Admin and
Sign-up users can Login. Without having an Internet connection the users will
not be able to interact with this website.

2.2
Product Functions:

As
mentioned earlier in this SRS that this application provide a better interface
for the user. It maintain the two type of users, like Admin User and sign-up /
without-sign-up User.

      Admin Area:

Ø  Add Products.

Ø  Remove Products.

Ø  Update Product details.

Ø  Mange user signup/without sign-up
user.

Ø  Manage customer data related
to Tailoring.

Ø  Update the measurement on
user request.

Ø  Will be able to send an
order on the customer requirement.

       Following functionalities will be
provided to customers:

           Sign-up user:

Ø  Able to sign-up.

Ø  Able to send order.

Ø  He can send his data, eg,
address etc.

Ø  Search and view details of
products.

Ø  Get discount on Featured
products.

Ø  Can see the data that
submitted, on login.

Ø  Send request on updates the
measurement which submitted.

2.3 User Characteristics

The Users that is being interact with the system must
have knowledge about the Computer. According to this SRS Admin User should be
able to know about the system that how a system being work. The Admin can
interact with the system when he get Login in the website. Only Admin user can
have access to it for Managing records in the system. 

2.4 General
Constraints

Ø 
Graphical User Interface must be interactive.

Ø 
Admin can manage the Data stored in DB, and
manage the backup of data.

Ø 
The Admin User have only Access of Database
after getting login in database.

Ø 
Sign-up customer can send request for the updating
of information related to tailoring.

Ø 
 The main purpose of this website is to
provide a better platform for the interaction of Admin as well as customers.

Ø 
This website is connected to Database, when
users interact with the website the data that is submitted by the users must be
store in Database. 

2.5
Assumptions and Dependencies

Ø 
This SRS defines a web base application. It works
on simple laptop/desktop which have latest operating system installed on it.

Ø 
A better GUI will be given to the users in
English language.

Ø 
This website will perform its working on Web
Browsers.

Ø 
In case of having problem in DB, Backup is
restored manually.

Ø 
Further functionalities can added later as to
fulfill the user requirements.

 

3.  Specific Requirements   

In this SRS, specific requirements are the most important
section. In this section all kind of requirements related to software design
and its implementation have to describe in detail for the Guidance of Software
project.

3.1 External Interface Requirements

3.1.1 System Interfaces

The
Graphical User interface (GUI) will be the interface through system which the
user can interact with the system and use the system according to his
requirements. The GUI will be design in such a way that user can easily
interact with the system.

3.1.2 Interfaces

In this SRS there will be of two user type:

v  Sign-up user

v  The admin user

Each of which will have its own corresponding
interface through which they can interact with the system and perform their
tasks easily.

3.1.3 Hardware Interfaces

             Following are the hardware requirements.

Ø  Core
2 duo /Laptop 1.7 GHz class or better processor.

Ø  1GB or more RAM (2GB recommended).

Ø  At least 500 MB Hard
disk space.

3.1.4 Software Interfaces

v
Software: Visual
Studio 2015

v
Programming Language:  C#

C sharp is
a multi-paradigm programming language encompassing strong
typing, imperative, declarative, functional, generic, object-oriented (class-based),
and component-oriented programming disciplines. It was developed
by Microsoft within its .NET initiative
and later approved as a standard by Ecma (ECMA-334)
and ISO (ISO/IEC 23270:2006). C# is one of the programming languages
designed for the Common Language Infrastructure.

v  Server: Microsoft SQL server 2012

Microsoft SQL Server: is a relational database management system developed
by Microsoft. As a database server, it is a software
product with the primary function of storing and retrieving data as
requested by other software applications—which may run either on the same
computer or on another computer across a network (including the Internet).

 Following are the Software interfaces that
required.

Ø 
OS
(window 8.1 or higher).

Ø 
MySQL
(2012) database.

(MySQL will work as backend using C#).

Ø 
Visual
studio (2015).

(Visual studio woks as front end for giving
an interactive GUI).

 3.1.4.1 MYSQL Server                                                                                     

SQL
server will provide an interface for Admin. Only Admin have accessibility to
DB. He will accessibility of managing records of customers. SQL server will be
helpful for attaining the backup of DB.

3.1.5 Communications Interfaces

The
communication between the different parts of the system is important since they
depend on each other. Software communicates with MYSQL server.

3.2 Functional Requirements

This section describes specific features of the
software project.  If desired, some
requirements may be specified in the use-case format and listed in the Use
Cases Section.

3.2.1

3.2.1.1 Introduction: Admin interact
with the system and got logged in the system for the processing.

3.2.1.2
Input: It
gives Username & password

3.2.1.3
Processing:  When admin
input Username & and password then matching process start for the
authentication of Admin from DB.

3.2.1.4
Output: Admin logged in the
system and perform his tasks.

3.2.1.5 Error: Admin
can be logged in case of given wrong Username & password.

 

3.2.2

3.2
.2.1 Introduction: Admin only have access to DB, it
will be able to add items in DB.

3.2.2.2 Input: Give command using Add/Insert Buttons in GUI.

3.2.2.3 Processing: After given command from Admin, the date Added in DB.

3.2.2.4 Output: After successful command data will be inserted in DB.

3.2.2.5 Error: Error can be occur in case of giving successful message but
data not inserted in DB.

3.2.3                                                                                                           

3.2
.3.1 Introduction: Admin only have access to DB, it
will be able remove items from DB.

3.2.32 Input: Give command using Delete/Remove Buttons in GUI.

3.2.3.3 Processing: After given command from Admin, the data Deleted/Remove from
DB.

3.2.3.4 Output: After successful command data will be deleted in DB.

3.2.3.5 Error: Error can be occur in case of select one record, and select
multiple.

3.2.4

3.2
.4.1 Introduction: Admin only have access to DB, it will
be able to Update/Edit data from DB.

3.2.4.2 Input: Give command using Edit/Update Buttons in GUI.

3.2.4.3 Processing: After given command from Admin, the data Updated from DB.

3.2.4.4 Output: After successful command data will be update in DB.

3.2.4.5 Error: Error can be occur in case of Update one record, and
Updated multiple.

3.2.5

3.2
.5.1 Introduction: Admin only have access to DB, it
will be able to View/Display items.

3.2.5.2 Input: Give command using Buttons in GUI.

3.2.5.3 Processing: After given command from Admin, the data can be view in
grid view.

3.2.5.4 Output: After successful command data will be Shown/View from DB.

3.2.5.5 Error: Error can be occur in case of not showing in specific
search record.

3.2.6

3.2.6.1 Introduction: Two
type of users will be in the system. The Sign-up User will sign-up in the in
the system, after sign-up he will be able to give measurement. While without sign-up
users just only give selection of item and give information egg. Address etc.

3.2.6.2 Input: Sign-up users insert data for getting sign-up and Measurement
related to Tailoring. While without Sign-up just only select the item and
insert information egg. Address etc.

3.2.6.3 Processing: After insertion date from Signup/ without Sign-up user will
be inserted in DB

3.2.6.4 Output: The Account of Sign-up Users will be created, and the data
of Without Sign-up user will be stored in DB and given an Id to it.

3.2.6.5 Error: Error possibly occur in case of generating an Account on
same Id/Email.

3.2.7

3.2.3.1
Introduction: Two type of users will be in the
system for Login in the system, Admin and Sign-up Users. The Admin/Sign-up User
will sign-up in the in the system, after completion of tasks. An option will be
given to them for Logout in the system.

3.2.3.2 Input: The Admin / Sign-up users just only click on the Logout
button.

3.2.3.3 Processing: After clicking on the Logout button, Session that was
created in the DB will be destroy.

3.2.3.4 Output: After Logout of both Admin and Sign-up user just only use
GUI.

3.2.3.5 Error: Error possibly occur in case of Session remain opened, that
have to be destroy in the system.

3.3 Use Cases

This section contains use cases of the AT management system.

 

 3.3.1 Use Case # 1

 

 

                                                                                                                                                                                                                       

 

 

3.5 Non-Functional Requirements

Non-functional requirements may exist for the
following attributes.  Often these
requirements must be achieved at a system-wide level rather than at a unit
level.  State the requirements in the
following sections in measurable terms (e.g., 95% of transaction shall be
processed in less than a second, system downtime may not exceed 1 minute per
day, > 30 day MTBF value, etc.).

3.5.1
Performance

Advance tailoring is an
online system in which three types of users are involved. One is Administrator,
second one is Sign-up users, and third one is Without Sign-up users. This
system allows accessibility to multiple users at a time.

3.5.2
Reliability

This
system will perform its functionality properly. User authentication will be required to
manage Admin panel and other activities of user. Visitors will also be enabling
to create their accounts to store their personal information.

 

3.5.3 Availability

                                   The main objective of the system is to provide high
availability of the Tailor. We will use latest frameworks and tools to create
the application in light way so that the system should accept the high access
load

3.5.4 Security

                               In Advance
tailoring application security will be given like entering username and
password. The Sign-up user and admin can login in the system. The Administrator
have accessibility of database and he is only responsible of managing records
of AT.

3.5.5
Maintainability

                                              The maintainability can be required with the passage of
time, like demand of user increases for a specific product. AT System will
support modification.

 

3.5.6
Portability

                               AT system is an
online system that will run on different kind of system. This system is not
required portability.

3.6 Inverse Requirements

All the products will be deliver cash on delivery. If
the user don’t wanted to take that product he will return that product in case
of not opened the parcel.

3.7
Logical Database Requirements

v  Database
will be created for this project.

v  Our
database keeps all record of our system.

v  User
can’t interfere in database.

v  Admin
user just have accessibility of DB.

v  The
DB will be containing all records of users and products.

 

3.8
Design Constraints


All fields will be filled correctly.


All necessary fields must be filled.


Customer data will store in database.


No field will be remain empty, especially for
input measurement and address etc.


If measurement is less than 0 digit then never
store it and error message show.


After completing an operation display a message
of record save or error.

4. Analysis Models

4.1 Sequence Diagram

 

 

 

4.2 Data Flow Diagrams (DFD
0)

 

 

4.3 Data Flow Diagrams (DFD 1)

 

4.4 State-Transition
Diagrams (STD)

 

 

5. Supporting Information

 

 A – Data Dictionary:

Ø  Advance
Tailoring (AD)                                                                                 page
# 1

Ø  Availability                                                                                                     page
# 14

Ø  Add
Data

Ø  Admin
Area                                                                                                     page
# 1

Ø  Asynchronous                                                                                                 page
# 2

Ø  Assumptions                                                                                                  

Ø  Analysis
Model

Ø  Abbreviations

 

c – Data Dictionary:

Ø  Classes
Objects                                                                                               page
# 1

Ø  Class
Diagram                                                                                                 page
#

Ø  Communications
Interfaces

 

D – Data Dictionary:

Ø  Data
Flow Diagram (FD)                                                                                page
# 17

Ø  Data
Flow Diagrams  (level 0)                                                                        page
# 18

Ø  Data
Flow Diagram  (level 1)                                                                         page
# 19

Ø  Definitions

Ø  Delete
Data

 

p – Data Dictionary:

Ø  Purpose                                                                                                page
# 3,6

Ø  Processing

Ø  Place
Order                                                                                                     page

Ø  Product
Function

Ø  Programing
Language                                                                                     page
#  7

 

 

S – Data Dictionary:

Ø  System
Requirement Specification (SRS)

Ø  SQL
(Structure Query language)

Ø  State Transition
Diagram (STD)                                                                     page # 19

Ø  Site
Adaptation Requirements

Ø  Sequence
Diagram (SQ)                                                                                 page
# 16

Ø  System
Interfaces

Ø  Specification

Ø  Signup
user                                                                                                     page
# 1

Ø  Software

Ø  Security

U – Data Dictionary:

Ø  Update                                                                                                             page
# 7

Ø  Use
Case#1                 ………………………………….                               page
# 9

Ø  Use
Case#2                 ………………………………….                               page # 10        

Ø  Use
Case#3                                                                                                     page
# 10

Ø  Use
Case#4                                                                                                     page
# 11

Ø  Use
Case # 5                                                                                                   page
# 12

Ø  User
Characteristics

Ø  Design
Constraints                                                                                          page
# 7

 

L – Data Dictionary:

Ø  Login                                                                                                               page
# 3,6

Ø  Logout                                                                                                            page
# 3,8

Ø  Logical
Database                                                                                            page
#  7

Ø  Use
Case#3                                                                                                     page
# 10