garment shop supplement ay
TRANSCRIPT
8/4/2019 Garment Shop Supplement Ay
http://slidepdf.com/reader/full/garment-shop-supplement-ay 1/7
SHAIKH
<Online Garment Shop>Supplementary Specifications
Version <1.0>
8/4/2019 Garment Shop Supplement Ay
http://slidepdf.com/reader/full/garment-shop-supplement-ay 2/7
Version: <1.1>
Date: <29/04/2011>
<document identifier>
Confidential SHAIKH, 2012 Page 2
Revision History Date Version Description Author
<29/04/2011> <1.2> <use case description document> <Waleed Imtiaz BCS-
FA09-137>
<Inam-ul-haq Mirza
BCS-FA09-144>
<Bilal Tabassum BCS-
FA09-023>
8/4/2019 Garment Shop Supplement Ay
http://slidepdf.com/reader/full/garment-shop-supplement-ay 3/7
Version: <1.1>
Date: <29/04/2011>
<document identifier>
Confidential SHAIKH, 2012 Page 3
Table of Contents
1. Introduction Error! Bookmark not defined.
1.1 Purpose Error! Bookmark not defined.
1.2 Scope Error! Bookmark not defined.
1.3 Definitions, Acronyms, and Abbreviations Error! Bookmark not defined.
1.4 References Error! Bookmark not defined.
1.5 Overview Error! Bookmark not defined.
2. Assumptions and Dependencies Error! Bookmark not defined.
3. Usability Error! Bookmark not defined.
3.1 <Usability Requirement One> Error! Bookmark not defined.
4. Reliability Error! Bookmark not defined.
4.1 <Reliability Requirement One> Error! Bookmark not defined.
5. Performance Error! Bookmark not defined.
5.1 <Performance Requirement One> Error! Bookmark not defined.
6. Supportability Error! Bookmark not defined.
6.1 <Supportability Requirement One> Error! Bookmark not defined.
7. Design Constraints Error! Bookmark not defined.
7.1 <Design Constraint One> Error! Bookmark not defined.
8. Security Error! Bookmark not defined.
9. Online User Documentation and Help System Requirements Error! Bookmark not defined.
10. Interfaces Error! Bookmark not defined.
10.1 User Interfaces Error! Bookmark not defined.
10.2 Hardware Interfaces Error! Bookmark not defined. 10.3 Software Interfaces Error! Bookmark not defined.
10.4 Communications Interfaces Error! Bookmark not defined.
11. Applicable Standards Error! Bookmark not defined.
8/4/2019 Garment Shop Supplement Ay
http://slidepdf.com/reader/full/garment-shop-supplement-ay 4/7
Version: <1.1>
Date: <29/04/2011>
<document identifier>
Confidential SHAIKH, 2012 Page 4
Supplementary SpecificationsIntroduction:
The Online garments shop(Ogs) web application is intended to provide complete solutions forcustomers through a single get way using the internet as the sole medium. It will enable
customers or visitors to visit online shops, customer to browse through the shop and purchase
them online without having to visit the shop physically. The administration module will enable
a system administrator to approve and for maintain various lists of stock category
Purpose:
The purpose of this document is to define requirements that are not captured in use case models
Supplementary specification describes the non-functional requirements of the system
1.1 Scope:The scope of supplementary specification is describe as a document that specifies the non-
functional specification of a software according to our project that is (ONLINE GARMENTS-
SHOP the project contains many non-functional attributes like usability ,
scalarability,correctness,performability,security,
marketability,reuseability.
1.2 Definitions, Acronyms, and Abbreviations:
JAVA EE: Java Enterprise Edition 5 is a programming platform— part of the Java Platform-for
developing and running distributed multi-tier architecture Java applications, based largely onmodular software components running on an application server.
HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between a web
browser & a Web Server.
HTTPS: Secure Hypertext Transfer Protocol is a HTTP.
TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used
to connect hosts on the Internet.
PHP : Hypertext Preprocessor
CSS : Cascading Style Sheet
HTML: Hypertext Markup Language
JAVA Script : JAVA Script
1.4: References:
Software Engineering Standards Committee. Recommended practice for software
requirements specifications. Standard 830, IEEE, 1998.
8/4/2019 Garment Shop Supplement Ay
http://slidepdf.com/reader/full/garment-shop-supplement-ay 5/7
Version: <1.1>
Date: <29/04/2011>
<document identifier>
Confidential SHAIKH, 2012 Page 5
1.5: Overview:
In this document we describes the project scope its non functional dependencies its whole
design depending
Upon the requirements of a software that includes the performance useability, security ,design constraints
2: Assumptions and Dependencies:
To access the online garment shop you just need the internet connection and internet browser toaccess it
The users know the English language, as the user interface will be provided in English
• Usability• Users will be made familiar with the Learning management system environment of the
Game, some control relevant training is required.
•
The system is user friendly and self-explanatory.
• Reliability• The system has to be very reliable to prevent the loss of system data and to keep the Mood and interest of
the user intact.
• AvailabilityThe system is available 100% for the user and is used 24 hrs a day and 365 days a year. The
system shall be operational 24 hours a day and 7 days a week.
• Mean Time between Failures (MTBF)
After 1 hour.
• Mean Time to Repair (MTTR)
Even if the system fails, the system will be recovered back within 5 to 6 minutes or less.
• Accuracy
The accuracy of the system is limited by the accuracy of the speed at which the user uses the system.
•
Maximum Bugs or Defect Rate
1%.
• Access Reliability
The system shall provide 100% access reliability.
8/4/2019 Garment Shop Supplement Ay
http://slidepdf.com/reader/full/garment-shop-supplement-ay 6/7
Version: <1.1>
Date: <29/04/2011>
<document identifier>
Confidential SHAIKH, 2012 Page 6
• Performance
• Response Time
Firstly as user login to the system no sooner system will show subjects to which the userwants to attempt or read as a tutorial.
• Reading time
The system will monitor the user in how much time he or she is reading the task.
5.3 Capacity
The system is capable of handling 1 user at a time.•
• Resource Utilization
Intelligent management system will not have any memory leaks and will use reasonable memory
(10MB) and CPU processing (~4%).
• Supportability
• Maintenance
The maintenance of the system shall be done as per the Bugs detected.
•
• Standards
The coding standards and naming conventions will be as per the American standards.
• Design Constraints
• Software Language Used
The languages that shall be used for coding the Intelligent Management system are PHP and MYSQL.
For working on the coding phase of the Intelligent Learning management system, MYSQL Should beinstalled on the OS.
• Security
• Only the registered students and System admin will be able to use this system.
• The network will be firewall enabled to avoid any security threats.