Software
Requirement Specification
For "NetShop.Com" System
Akash Jain,
Mukesh Mishra,
Rahul,
Nitin,
Lovely,
1 INTRODUCTION 1.1 1.1.1 Purpose of SRS document
The purpose of this SRS is to supply our customer (in this case the general market) with an outline of a software product
1.1.2 Intended Audience
Individuals that are responsible for reviewing proposals for this system. This may include Managers, Network and DB Administrators of the company that may be interested in our software
1.2 Scope
1.2.1 Software Product to be produced
This product currently code-named "NetShop.Com"
1.2.2 Purpose of "NetShop"
Provide an environment for users of this system (See Section 2.3) to conduct a virtual "NetShop.Com"/"Swap meet" This procedure can be summarized as follows:
1.2.2.1
The user will be able to register as a member and be a part of our virtual community.
1.2.2.21111111111111111.1
This system could be accessible from anywhere over the Internet. 1.2.2.3 The user should be able to provide positive identification and a valid e-mail address 1.2.2.4 The user should be able to provide a unique user name and password for a positive identification during subsequent visits to the site. 1.2.2.5 There will be a user agreement and a privacy policy that the user will have to agree to upon registering.
1.2.2.6 The user will be able to see a picture on his computer or URL for a picture that corresponds to the item to be purchased.
The user will be able to have a wish list of items that he/she wants to buy in the future 1.2.2.11 The system and database can be modified by administrator as per requirements.
1.3 Definitions,
Acronyms and Abbreviations
SRS: Software Requirement Specification. URL: Universal Resource Locator. Text mapping to IP SQL: Sequential Query Language (A Querying and reporting language used by all modern RDBMS) HTML: Hypertext Markup Language. A Formatting Language Used to encode web pages DB: The Microsoft Acess used by our software.1.4 REFERENCES ERD (Attachment A) DFD (Attachment B) Data dictionary (Attachment C) URL to a prototype GUI of the system
1.5 OVERVIEW 1.5.1 Contents of the SRS This SRS will provide a description of "NetShop.Com" system. It will provide an outline of the requirements. It will also provide an overview of the characteristics and constraints of the "NetShop.Com" system. 1.5.2 SRS Organization This SRS is organized in accordance with ANSI/IEEE Std. 830-1984
2. GENERAL DESCRIPTION 2.1
Product Perspective
The "NetShop.Com" system would be one of the first systems of its type and functionality..It also provides and creates a virtual store front for end users to buy items on Net. The principle external interfaces that will be used include a Register Screen, Login Screen, Shopping Cart Screen, Account Status Screen "NetShop" is a very flexible system that could be integrated into any Shoppiong web site. 2.2 Product Function The main functions of "Netshop" will be divided into two categories: user (buyer) and administrative. The user will be able to buy items, add/delete items from shopping cart, check their account status Administrator will be able to change template, check history of sales, access users information and account status of each user, have a total control of database, and have a total control of system configuration.2.3 User Characteristics
The users are required to have basic knowledge and experience using a web browser. However, the GUI should provide enough guidance to an average user. Administrator of this system should have knowledge of the specifics of hardware, operating system and software environment of the host system. This includes but is not limited to the knowledge of web server and database administration. Preferably the administrator will have basic knowledge of ANSI SQL, however this is not required. 2.4 General Constraints 2.4.1 This software system should be engineered to be as platform independent as possible, thus excluding the proprietary technologies. Preferably the development technology would be open-source, making it easy to understand particular features and shortcomings. 2.4.2 This software system should be easily installable by a System Administrator who possesses only knowledge about the system that he/she is working on. 2.4.3 This software system should run in conjunction with Java Web Server or JSDK2.0.2.4.4
This softwre system should run with ANSI complaint SQL Database.
2.4.5
This software can be run on plenty of operationg system support Java 2 or have JVM
2.5 Assumptions and Dependences 2.5.1 Software developers assume that an ANSI compliant SQL database is available, or can be installed on the system under which it should function (See 2.4.4). 2.5.2 Software developers assume that a modern web-server(Java Web Server) is available on the host system (See 2.4.3). 2.5.4 Software developers assume that hardware/software combination of the host system will be able to support the load associated with an e-commerce application. 2.5.5 Software developers assume that there will be a System Administrator that will maintain this system and its database.
3. SPECIFIC REQUIREMENTS 3.1 Functional Requirements
3.1.1.3 Processing
The login function takes in a username and a password. It runs a check against the database to verify this information. If the check is successful then it will write a Session on the users computer for subsequent access to the system during the current session. 3.1.1.4 Outputs User access to the system using Session functions. 3.1.2 REGISTER functional requirements 3.1.2.1 Introduction The register function takes a user's information and creates a user account for that person on the system. 3.1.2.2 Inputs User InformationThe people that want to be user of our system must pass the following Information in registration process.
Firstname, Lastname, FullAddress, Phone, Landmark, Email address, Username(a unique id which helps them to access this system) ,Password ,Hint Question ,Hint Answer.
3.1.2.3 Processing This function takes a users information, validate it and creates an account on the system for that user.
3.1.2.4 Output
An message for registration confirmation is display to the user. User's Database3.1.3 SHOPPING CART functional requirements 3.1.3.1 Introduction The shopping cart function allows a member to purchase items from the "NetShop" system. It also provides easy item tracking for the user 3.1.3.2 Inputs user id
Product id
Price
3.1.3.3 Processing The shopping cart takes the user.u_key and the item.i_key(s) of the items that the user wants to purchase and creates a transaction record. 3.1.3.4 Outputs Transaction Record
3.1.3.5 Deletion User will be able to remove the selected item from his shopping cart.
3.1.4 DISPLAY functional requirements 3.1.4.1 Introduction This function is called from other functions to display listings of items in a formatted output. 3.1.8.2 InputsOrder id
User key id
3.1.8.3 Processing This function takes the order id and user id fetches item records and prints out the listing in a formatted way
3.1 External Interface Requirements 3.2.1 User Interfaces Any modern web browser including, but not limited to Microsoft Internet Explorer Version 4.0 and above and Netscape Navigator Version 4.0 and above, using display resolution of 800x600 pixels or greater. NOTE: At this time the prototype ONLY works properly with Internet Explorer 4.0 and above.
3.2.2 Hardware Interfaces "NetShop" system will not have a direct hardware access, all hardware interfacing will be done through the documented operating system routines. 3.2.3 Software Interfaces "NetShop" system will interface with the Java web server and using JSDK APIs provided by the implementation language. (See 2.4.3 2.4.5) 3.2.4 Communication Interfaces All of the communication between client and server computers will be handled by the Java Web Server 2.0 software. 3.3 Performance Requirements 3.3.1 Hardware Requirements The host computer hardware and operating system should be able to handle minimum number of simultaneous users utilizing our system, which at this time is limited to 50, without significant performance degradation. 3.4 Design Constraints 3.4.1 Standards Compliance The "NetShop" system should only contain source code that complies with JAVA 2 compiler. 3.4.1.2 The system should comply with ANSI SQL standard (See 2.4.4)
3.4.2 Hardware Limitations
If the usage of the "NetShop" system should go beyond the acceptable performance level. There should exist an option to move the system to a more powerful computer, however this system is not designed to be used in a distributed computing environment. 3.4.3 Software Limitations The "NetShop" system only supports ANSI SQL compliant databases. Thus limiting the RDBMS software choices for a host company.
3.4.4 Portability Constraints The "NetShop" system should be designed in such a way, that porting this system to a foreign operating system/software environment should incur only minimal effort.
3.5 Attributes
3.5.2 Maintainability 3.5.2.1 Detailed documentation of the code and SRS will enable easy maintenance of the "NetShop". 3.5.2.2 Most of the system functions will be controlled using the administrative interface. 3.6 Other Requirements 3.6.1 Database See section 2.4.4 3.6.2 Operating System See section 2.4.5
3.6.3 Interfaces with other 3rd party software The "NetShop" system should not need any external 3rd party software to operate 3.6.4 Licensing At the time of this writing it is our intension as developers of this software to provide it under the extended GPL licensing, for non-commercial use. (See attachment D). However, for commercial use of this application a commercial license will be required.
Attachment C (Data Dictionary)