1.  Introduction   1.

1   PurposeThis SystemRequirement Specification (SRS) describe the functionality of the tailoringmanagement system. Instead of writing measurement manually, the customer willbe able to write itself according to this SRS. It explain functional featuresof 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 interfacefor Advance Tailoring. This SRS developeda Web application is intended to provide complete solutions for vendors as wellas customers through a single get way using the internet. It will enable vendors to setup online shop, customerto browse through the website and purchase the products related to thetailoring garments online without having to visit the shop physically.

Best services for writing your paper according to Trustpilot

Premium Partner
From $18.00 per page
4,8 / 5
Writers Experience
Recommended Service
From $13.90 per page
4,6 / 5
Writers Experience
From $20.00 per page
4,5 / 5
Writers Experience
* All Partners were chosen among 50+ writing services by our Customer Satisfaction Team

ScopeThe Tailoring website is intended to work as an online. Admin user willbe facilitated by providing the following facilities:Admin Area:Ø  Add Products.Ø  Remove Products.Ø  Update Product details.Ø  Mange user signup/without sign-upuser.Ø  Manage customer data relatedto Tailoring.Ø  Update the measurement onuser request.Ø  Will be able to send anorder on the customer requirement.

                                                                                            Following functionalities will beprovided 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 ofproducts.

ü  Get discount on Featuredproducts.ü  Can see the data thatsubmitted, on login.ü  Send request on updates themeasurement which submitted. Ø  Without signup:ü  Search and view details ofproducts.ü  He just enable to send anorder.ü  Just selectsmall/medium/large/extra-large.

ü  He can send his data egg. Addressetc.1.2   Definitions,Acronyms, and Abbreviationsv AT:Advance Tailoring. v SRS: Systemrequirement Specification.

v GUI:Graphical User Interface. v DB: Database  v SQL:Structure Query Language is a system software tool, through which databaseconnect and manage the records. 1.

4 ReferencesIn this subsection:Ø  SRSTemplateØ  www.youtube.comØ  www.

google.comØ  www.slideshsre.com1.5 OverviewIn this subsection:(1)   Describewhat the rest of the SRS contains(2)   Explainhow the SRS is organizedDon’t rehash the table of contents here.  Point people to the parts of the documentthey are most concerned with.

 Customers/potential users care about section 2, developers care aboutsection 3.2.  The Overall Description 2.1 ProductPerspective:The main purpose of this SRS is to provide facilityfor that kind of customer which do not want to visit shops and it might be notinteresting 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 willbe able to save his precious time. He will get information of all tailoringproducts like Kurta Shalwar, Waistcoat etc. AT tailoring system will provide abetter stuff of clothes and option given to the customer whether he want to sign-upfor the proper measurement of the product, OR he just want to get average sizeof product like Medium/large/extra2.1.

1 Operations:Ø Login: Inthis operation the Admin/Sign-up User will be Login first. The purpose of LoginAdmin is to manage the records. While the Sign-up user login for sending informationabout measurements and address etc.Ø Logout:When login in the website, after managing the records from Admin and aftersending data from Sign-up user. This operation will logout for both type ofUsers in the web siteØ PlaceOrder: In this operation a customers can send an order, the customer can besignup or without signup. The signup user will have to login first for theproper measurement of product.Ø OrderedReceive: In this operation the Admin will received an order from thecustomers, that orders will be received in the DB first and then Admin can viewthe orders.Ø Signup: Accordingto this SRS the end users will be able to Sign up in the system.

. 2.1.

2 SiteAdaptation RequirementsThis is a kind of online of website and it requiredan Internet Connection. With the help of Internet Connection the Admin andSign-up users can Login. Without having an Internet connection the users willnot be able to interact with this website.2.

2Product Functions:Asmentioned earlier in this SRS that this application provide a better interfacefor 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-upuser.Ø  Manage customer data relatedto Tailoring.

Ø  Update the measurement onuser request.Ø  Will be able to send anorder on the customer requirement.       Following functionalities will beprovided 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 ofproducts.Ø  Get discount on Featuredproducts.Ø  Can see the data thatsubmitted, on login.

Ø  Send request on updates themeasurement which submitted.2.3 User CharacteristicsThe Users that is being interact with the system musthave knowledge about the Computer. According to this SRS Admin User should beable to know about the system that how a system being work. The Admin caninteract with the system when he get Login in the website. Only Admin user canhave access to it for Managing records in the system.

  2.4 GeneralConstraintsØ Graphical User Interface must be interactive.Ø Admin can manage the Data stored in DB, andmanage the backup of data.Ø The Admin User have only Access of Databaseafter getting login in database.Ø Sign-up customer can send request for the updatingof information related to tailoring.Ø  The main purpose of this website is toprovide a better platform for the interaction of Admin as well as customers.

Ø This website is connected to Database, whenusers interact with the website the data that is submitted by the users must bestore in Database.  2.5Assumptions and DependenciesØ This SRS defines a web base application. It workson simple laptop/desktop which have latest operating system installed on it.Ø A better GUI will be given to the users inEnglish language.

Ø This website will perform its working on WebBrowsers.Ø In case of having problem in DB, Backup isrestored manually.Ø Further functionalities can added later as tofulfill the user requirements. 3.  Specific Requirements    In this SRS, specific requirements are the most importantsection. In this section all kind of requirements related to software designand its implementation have to describe in detail for the Guidance of Softwareproject. 3.1 External Interface Requirements3.

1.1 System InterfacesTheGraphical User interface (GUI) will be the interface through system which theuser can interact with the system and use the system according to hisrequirements. The GUI will be design in such a way that user can easilyinteract with the system.3.1.2 InterfacesIn this SRS there will be of two user type:v  Sign-up user v  The admin userEach of which will have its own correspondinginterface through which they can interact with the system and perform theirtasks easily.3.

1.3 Hardware Interfaces             Following are the hardware requirements.Ø  Core2 duo /Laptop 1.7 GHz class or better processor.Ø  1GB or more RAM (2GB recommended).Ø  At least 500 MB Harddisk space.

3.1.4 Software InterfacesvSoftware: VisualStudio 2015vProgramming Language:  C# C sharp isa multi-paradigm programming language encompassing strongtyping, imperative, declarative, functional, generic, object-oriented (class-based),and component-oriented programming disciplines. It was developedby Microsoft within its .

NET initiativeand later approved as a standard by Ecma (ECMA-334)and ISO (ISO/IEC 23270:2006). C# is one of the programming languagesdesigned for the Common Language Infrastructure.v  Server: Microsoft SQL server 2012Microsoft SQL Server: is a relational database management system developedby Microsoft. As a database server, it is a softwareproduct with the primary function of storing and retrieving data asrequested by other software applications—which may run either on the samecomputer or on another computer across a network (including the Internet).

 Following are the Software interfaces thatrequired.Ø OS(window 8.1 or higher).Ø MySQL(2012) database.(MySQL will work as backend using C#).Ø Visualstudio (2015).

(Visual studio woks as front end for givingan interactive GUI).  3.1.4.

1 MYSQL Server                                                                                      SQLserver will provide an interface for Admin. Only Admin have accessibility toDB. He will accessibility of managing records of customers. SQL server will behelpful for attaining the backup of DB.3.1.5 Communications InterfacesThecommunication between the different parts of the system is important since theydepend on each other. Software communicates with MYSQL server.

3.2 Functional RequirementsThis section describes specific features of thesoftware project.  If desired, somerequirements may be specified in the use-case format and listed in the UseCases Section.

3.2.1 Introduction: Admin interactwith the system and got logged in the system for the processing.3.

2.1.2Input: Itgives Username & password3.2.1.3Processing:  When admininput Username & and password then matching process start for theauthentication of Admin from DB.3.

2.1.4Output: Admin logged in thesystem and perform his tasks. Error: Admincan be logged in case of given wrong Username & password.

 3.2.2 Introduction: Admin only have access to DB, itwill be able to add items in DB.3.2.

2.2 Input: Give command using Add/Insert Buttons in GUI. Processing: After given command from Admin, the date Added in DB.


4 Output: After successful command data will be inserted in DB. Error: Error can be occur in case of giving successful message butdata not inserted in DB.3.2.

3                                                                                                            3.2.3.

1 Introduction: Admin only have access to DB, itwill be able remove items from DB.3.2.

32 Input: Give command using Delete/Remove Buttons in GUI. Processing: After given command from Admin, the data Deleted/Remove fromDB.3.2.3.

4 Output: After successful command data will be deleted in DB. Error: Error can be occur in case of select one record, and selectmultiple.

3.2.4 Introduction: Admin only have access to DB, it willbe able to Update/Edit data from DB. Input: Give command using Edit/Update Buttons in GUI.3.

2.4.3 Processing: After given command from Admin, the data Updated from DB. 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, andUpdated multiple.3.2.

5 Introduction: Admin only have access to DB, itwill be able to View/Display items.3.2.

5.2 Input: Give command using Buttons in GUI. Processing: After given command from Admin, the data can be view ingrid 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 specificsearch record.3.2.6 Introduction: Twotype of users will be in the system. The Sign-up User will sign-up in the inthe system, after sign-up he will be able to give measurement.

While without sign-upusers 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 Measurementrelated to Tailoring. While without Sign-up just only select the item andinsert information egg. Address etc.3.

2.6.3 Processing: After insertion date from Signup/ without Sign-up user willbe inserted in DB3.2.6.

4 Output: The Account of Sign-up Users will be created, and the dataof Without Sign-up user will be stored in DB and given an Id to it. Error: Error possibly occur in case of generating an Account onsame Id/Email.3.

2.7 Two type of users will be in thesystem for Login in the system, Admin and Sign-up Users. The Admin/Sign-up Userwill sign-up in the in the system, after completion of tasks.

An option will begiven to them for Logout in the system. Input: The Admin / Sign-up users just only click on the Logoutbutton.3.

2.3.3 Processing: After clicking on the Logout button, Session that wascreated in the DB will be destroy. Output: After Logout of both Admin and Sign-up user just only useGUI. Error: Error possibly occur in case of Session remain opened, thathave to be destroy in the system.3.3 Use CasesThis section contains use cases of the AT management system.  3.

3.1 Use Case # 1                                                                                                                                                                                                                           3.5 Non-Functional RequirementsNon-functional requirements may exist for thefollowing attributes.

  Often theserequirements must be achieved at a system-wide level rather than at a unitlevel.  State the requirements in thefollowing sections in measurable terms (e.g., 95% of transaction shall beprocessed in less than a second, system downtime may not exceed 1 minute perday, > 30 day MTBF value, etc.). 3.5.1PerformanceAdvance tailoring is anonline 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. Thissystem allows accessibility to multiple users at a time. 3.5.2ReliabilityThissystem will perform its functionality properly. User authentication will be required tomanage Admin panel and other activities of user. Visitors will also be enablingto create their accounts to store their personal information.

 3.5.3 Availability                                   The main objective of the system is to provide highavailability of the Tailor. We will use latest frameworks and tools to createthe application in light way so that the system should accept the high accessload3.5.4 Security                               In Advancetailoring application security will be given like entering username andpassword. The Sign-up user and admin can login in the system. The Administratorhave accessibility of database and he is only responsible of managing recordsof AT.

3.5.5Maintainability                                              The maintainability can be required with the passage oftime, like demand of user increases for a specific product. AT System willsupport modification. 3.5.6Portability                               AT system is anonline system that will run on different kind of system.

This system is notrequired portability.3.6 Inverse RequirementsAll the products will be deliver cash on delivery.

Ifthe user don’t wanted to take that product he will return that product in caseof not opened the parcel.3.7Logical Database Requirementsv  Databasewill be created for this project.

v  Ourdatabase keeps all record of our system.v  Usercan’t interfere in database.v  Adminuser just have accessibility of DB.

v  TheDB will be containing all records of users and products. 3.8Design Constraintsv All fields will be filled correctly.v All necessary fields must be filled.v Customer data will store in database.v No field will be remain empty, especially forinput measurement and address etc.

v If measurement is less than 0 digit then neverstore it and error message show.v After completing an operation display a messageof record save or error.4. Analysis Models4.

1 Sequence Diagram   4.2 Data Flow Diagrams (DFD0)  4.3 Data Flow Diagrams (DFD 1) 4.4 State-TransitionDiagrams (STD)  5.

Supporting Information  A – Data Dictionary:Ø  AdvanceTailoring (AD)                                                                                 page# 1Ø  Availability                                                                                                     page# 14Ø  AddDataØ  AdminArea                                                                                                     page# 1Ø  Asynchronous                                                                                                 page# 2Ø  Assumptions                                                                                                   Ø  AnalysisModelØ  Abbreviations c – Data Dictionary:Ø  ClassesObjects                                                                                               page# 1Ø  ClassDiagram                                                                                                 page# Ø  CommunicationsInterfaces D – Data Dictionary:Ø  DataFlow Diagram (FD)                                                                                page# 17Ø  DataFlow Diagrams  (level 0)                                                                        page# 18Ø  DataFlow Diagram  (level 1)                                                                         page# 19Ø  DefinitionsØ  DeleteData p – Data Dictionary: Ø  Purpose                                                                                                page# 3,6Ø  ProcessingØ  PlaceOrder                                                                                                     pageØ  ProductFunctionØ  ProgramingLanguage                                                                                     page#  7  S – Data Dictionary:Ø  SystemRequirement Specification (SRS)Ø  SQL(Structure Query language)Ø  State TransitionDiagram (STD)                                                                     page # 19Ø  SiteAdaptation RequirementsØ  SequenceDiagram (SQ)                                                                                 page# 16Ø  SystemInterfacesØ  SpecificationØ  Signupuser                                                                                                     page# 1Ø  SoftwareØ  SecurityU – Data Dictionary: Ø  Update                                                                                                             page# 7Ø  UseCase#1                 ………………………………….                               page# 9Ø  UseCase#2                 ………………………………….                               page # 10         Ø  UseCase#3                                                                                                     page# 10Ø  UseCase#4                                                                                                     page# 11Ø  UseCase # 5                                                                                                   page# 12Ø  UserCharacteristicsØ  DesignConstraints                                                                                          page# 7 L – Data Dictionary:Ø  Login                                                                                                               page# 3,6Ø  Logout                                                                                                            page# 3,8Ø  LogicalDatabase                                                                                            page#  7Ø  UseCase#3                                                                                                     page# 10