DOWNLOAD FREE ONLINE SHOPPING CART PROJECT IN JAVA WITH SRS DOCUMENT
WHAT IS SRS ? SIMPLE DEFINITION OF SOFTWARE REQUIREMENT SPECIFICATION
Table of Content
1. Introduction
1.1. Purpose of this document
1.2. Scope of Development Project
1.3. References
1.4. Overview of the Document
2. Overall Description
2.1. Product Perspectives
2.2. Overview of functional requirements
2.3. Overview of data requirements
2.4. General Constraints, dependencies and guidelines
2.5. User view of product use
3. External Interface requirements
3.1. User Interface
3.2. Hardware Interface
3.3. Software Interface
3.4. Communication protocol and interface
4. Requirements
4.1. Business Requirements
4.2. Detailed Functional Requirements
4.3. Logical Data Flow Requirements
5. Other nonfunctional requirements
5.1. Performance requirements
5.2. Quality attributes
5.3. Safety requirements
5.4. Security requirements
5.5. User Documentation
6. Other requirements
6.1. Appendix – A : Glossary
6.2. Appendix – B : Analysis Models
6.3. Appendix – C : Issues List
1. INTRODUCTION
1.1. Purpose
This document is our understanding of potential clients’ system requirements and dependencies at this initial phase of project prior to any actual design or development work. This will help in the full automation of a SHOPPING CENTRE. The document will help us to understand what our project is meant for. We also look forward for a reassurance that, the clients and our development team understand the other requirements from that perspective at this given point of time.
This document states in precise and explicit language those functions and capabilities a software system must provide, as well as states any required constraints by which the system must abide. It also functions as a blueprint for completing our project as efficiently as possible. This should be considered as a benchmark document because all subsequent project management documents, such as design specifications, statements of work, software architecture specifications, static system analysis, testing and validation plans, and documentation plans, are related to it.
1.2. Scope
The task on hand is to develop A SHOPPING CENTRE System . The aim of this project is to automate the key process involved in the SHOPPING CENTRE. The aim of this web-based project is to develop a tool intended to automate the various process involved in the SHOPPING CENTRE and also help members to get information about new arrivals, availability of the reserved products
1.3 Reference
A. Books:
| Name | Author | Publication |
| System Analysis and Design | Ellias Awadm | Galgotia |
| Java Scripts | Jaison William,Charlton Ling, R. Allen Wyke | Sams |
| | James Goodwill,Richard HighTower | Wrox |
| Beginning MySql | Robert Sheldon & Geoff Moss | Wrox |
| Java 2:The Complete Reference | Herbert Schildt | Tata Mc Graw-Hill |
| Beginning JSP | Vivek Chopra & Jon Eaves | Wrox |
| Software Engineering | Roger S Pressman | McGraw Hill |
1.4 Document overview
The document provides a full description of the project for the owners of the site. It lists all the functions performed by the system. It deals with the details of each of the system functions and actions in full for the software developer’s assistance. These are cross-referenced by topic to increase understanding of the various functions involved.
The project is divided in to the following sections
1.4.1. Overall description:
This section discusses the functional requirements, data requirements, its constraints and dependencies.
1.4.2. External Interface requirements:
This section mentions the various interfaces associated with the project such as hardware interface, software interface, communication protocol and interfaces.
1.4.3. System features:
This section discusses the functional requirements in detail.
1.4.4. Other non-Functional requirements:
This section discusses non functional characters of the project such as performance, quality, safety, security in this section.
1.4.5. Requirement Traceability Matrix:
Requirement Traceability Matrix means Mapping between test cases and customer requirements.
1.4.6. Other Requirements
The requirements which are not mentioned in the above sections are mentioned here.
2. Overall Description
This gives you inside information about the overall features used in this project.
2. 1 Product Perspective
- This product has been designed to facilitate operations and activities much easier for the user.
- This product consists of three modules namely Admin module, and User module.
- This product can be accessed by a JavaScript enabled web browser with a specified internet bandwidth.
- This product is designed to run on the existing hardware consisting of a client computer capable of running the JavaScript.
- This product requires the client computer to have a graphic capability of displaying up to 256 colors or more.
- This product has certain features that require the client to register.
- The administrator processes the login part of the user.
2.2 Overview of Functional Requirements
Home Page
| purpose | Enables user for login and search products through advanced features |
| inputs | 1. User Registration 2. Searching 3. Login 4. online product News 5. About us 6. Contact us 7. Feedback 8. Sitemap 9. Terms and Conditions |
| processing | When a link is clicked, the browser navigates to the next page |
| outputs | The next page referenced by the link that was clicked |
2.3 Overview of Data Requirements
- Input Data: The software will be totally mouse driven. All input data are from left mouse clicks on context buttons such as directional buttons or menu options.
- Output Data: Facts and graphics will be displayed to the monitor via the Flash MX plug-in.
2. 4 General Constraints, Dependencies and Guidelines
A. Constraints
System Constraints
- The client system should have the bandwidth specified by the admin for the product to run. Here the bandwidth used is 56kbps.
- The specification regarding the software’s required is another important constraint. This involves the JavaScript enabled web browser, flash players, Operating Systems as well. etc.
- This product requires the client computer to have a graphics capability of displaying up to 256 colors or more.
- This product requires the client computer to have all the hardware features as specified such as processor speed, configuration etc.
- This product requires the Java Virtual Machine to run and also the corresponding drivers of it.
Performance Constraints
- The system should have all the resources as specified in the system requirements.
- The system should be able to counter issues like database load, latency etc.
- The system is monitored frequently in order to recover from performance constraints.
B. Dependencies
Operational Scenarios
The different operational scenarios present are,
Admin Side
- The operating systems used are Windows NT, Windows 2000, and Linux etc.
- The main tool used for communication are Internet, JavaScript enabled Web-Browser.
- The different software tools used here are MySql, Eclipse, Apache server, Struts, Core Java, etc.
Client Side
- The operating system used in the client side is Windows NT, windows 2000, Linux etc.
- The main tools used for communication are Internet and Web Browser.
- The main Software tools required in the client side are Java Script enabled Web-Browser, Flash Player, Java virtual machine etc.
- The corresponding driver for all software’s to work.
Business Requirements
This involves the requirement which facilitates the business related to an
organization. This may include the following,
- Advertising is a very important concept in business requirements.
- The scope of the business enables the company to expand the overall product features.
- The popularity of the product determines how large the product should be.
- This involves all the business requirements to be analyzed.
Features
· Usability
This product is designed in such a way that it meets all the requirements of the
user. Also these requirements are established in such a way that it is accessed
easily by the user. This system provides different functionalities to enable the
user to get a clear picture of what they want to explore.
· Reliability
The system is designed in such a way to make it more reliable for the user so that the money spends worth it. The system ensures to be of the highest quality standard and will last the distance as specified.
· Adaptability
The system is designed in such a way that it is adaptable to the different working environments such as hardware and software features. Since this design is based on Java it can be run on any operating systems.
- Scalability
The product has been designed to be scalable. The product ensures the ability to scale to support larger or smaller volumes of data and more or less users.