I. Introduction I.

1 Purpose: To design an online appliaction that helps the user in handling the shopping cart transactions to avail the goods in an efficient manner. I.2 Document Conventions: The transactions that are generally followed by the users and the owners which are handled manually are taken as required assumptions for designing the application. I.3 Intended Audience and Reading Suggestions: Intended for customers and shop owners to maintain and improve their business by accepting the orders through online. The users must under go document reading before using the application. I.4 Product Scope: Language that is used to develop the application is JAVA. [WRITE ABOUT JAVA FEATURES] I.5 Project Scope: The application is web oriented with below features: a. Registration of staff by the administrator with various designations. b. Self registration by the customer. c. Category management by the Purchase Manager. d. Product maintenance by the Purchase manager. e. Order placing by the customer by selecting the required products from the categories. f. Approval of orders by the sales manager. g. Report generation by the accountant. I.6 References: [WRITE SOME REFERENCES BOOK NAME, AUTHOR, DESCRIPTION] II. Overall Description: II.1 Product Perspective: In the current scenario, customers visit the shops to view or search for the required products for his purchase. This is a time consuming process and risk for the user as he may not get the best of the required or searched product in the visited shops. The orders are to be placed manually and the payments are done through manual process or through card system i.e. manual presence is must. In the proposed model, it is an online shopping mart where the customers can search for the required category products and their details without logging in. But for placing an order for the required products, the user need to be registered before logging in and placing the order with online payments. The payment is made as a tempary transaction on the user account. The order can be cancelled before the dispatch of the order. When the order is cancelled by the user, the transaction on the account is also cancelled. On dispatching the order by the sales manager of the shop, the transaction is made permanent to the shop account. This process reduces the searching time for the products, no personal visit is required reducing the user working time, etc.

II.2 Product Functions: The application is web oriented with below features: a. Registration of staff by the administrator with various designations. b. Self registration by the customer. c. Category management by the Purchase Manager. d. Product maintenance by the Purchase manager. e. Order placing by the customer by selecting the required products from the categories. f. Approval of orders by the sales manager. g. Report generation by the accountant. II.3User classes and characteristics: As the application is a web site and use web pages for working, HTML and DHTML are used for static web page designing, Java script for client side validations. JSP, Servlets and Beans are used to server side script, JDBC for handling the data base transactions. The web server (Tomcat) is used as a third party service to provide security to the application and publish it into the network. II.4Operating Environment: [WRITE THE SOFTWARE AND HARDWARE REQUIREMENTS AS GIVEN IN THE ABSTRACT] II.5Design and Implementation Constraints: As the application is a web site, the source code is deployed in the server machine under the control of the third party software called Web Server (Tomcat) that provides security to the application and publishes it into the network. The Server needs to maintain the required supporting softwares like JAVA, Web Server in working condition, Database connectivity and network connection. The client on the other hands need not maintain any additional software as the web pages of the web site can be accessed or viewed using the browser tool. II.6User Documentation: The application can be specified or provided with an inbuilt help manual describing the working nature of the application like its work flow and module descriptions. III. External Interface Requirements: III.1 User Interfaces: As the application is a web site, the web pages use raw text data as input and outputs are also generated in the same format. Hence the basic input devices of the system like keyboard and mouse can be used. Key board can be used to insert the required input data and the mouse can be used to trigger the required events that help in handling or performing the transactions and to navigate through the web pages. Monitor can be used as the output tool to view the screens that are generated. III.2 Hardware Interfaces: They are same as specified in User Interfaces. The clients need to maintain the required virtual memory and good speed process for better performance.

III.3 Software Interface: As the application is a web site, the source code is deployed in the server machine under the control of the third party software called Web Server (Tomcat) that

provides security to the application and publishes it into the network. The Server needs to maintain the required supporting softwares like JAVA, Web Server in working condition, Database connectivity and network connection. The client on the other hands need not maintain any additional software as the web pages of the web site can be accessed or viewed using the browser tool. Hence, client is free from system maintenance. III.4 Communication Interfaces: As the application is placed or deployed in Server Machine and used from the client machines remotely in the network, they need to be connected with physical communication devices like cables, routers, switches, hubs, etc. IV. System Features: The application that is proposed is split into below Modules: a. Login & Security: This module accepts the username and password from the logging in user which on validation allows the user to use the privileges associated to him. The login page also provides a privilege for the customer to make self registration after which he can login to avail the resources. The home page also provides a search engine by using which the non registered customer or user can search for the required products information by viewing them in categories. b. Administrator: He is the owner of the web site and contains privileges to maintain the staff with various designations. Each staff is associated with unique id, username and password by using they can be identified and login. Admin can view the required reports of sale of the products over the given period. c. Purchase Manager: This module is for the purchase manager to maintain the information of the categories of the products with their inventory information by filling the item stock. He can view the information of sales over the given period. d. Sales Manager: This module is for the sales manager who on logging can view the available stock, view the orders placed by the customers and dispatching them. e. Accountant: This is for the accountant to maintain the information of the accounts paid and received by the shops i.e. temporary and paid bills by the customers. He maintains the information of the best purchaser from the registered customers by accumulating them with the credit points. Appropriate gifts can be placed for his choice to avail his credit points against them. f. Customer: This module is for the customer who on logging in can view the information of the required products and place the order to the shop by selecting the required items. He can view the status of the placed order and cancel it if required, before the order is dispatched. He can view his credit points accumulated and view the gifts that can be offered to him. V. Other Non Functional Requirements: V.1Performance Requirements:

As the application is a web site, the performances of such applications depend on the below factors: a. The number of users working on the server or network at that instance of time i.e. if the number of users are more, then the performance or speed decreases and vice-versa. b. It also depends on the type of network used by the client. A good band width network is preferred for better performance. V.2Safety Requirements: Each user is specified with a username and password that is validated before logging in into the web site restricting the unauthorized users. Additional security like encrypted format of username and passwords can be applied. V.3security Requirements: As the application is deployed in the server machine and executed or accessed from the client systems remotely in the network, the users can only view the executed output of the web page (dynamic) and cannot change any part of the source code of that web page. Hence the code is safe from client modifications. VI. Feasibility Study: VI.1 Economic Feasibility: As the application is a web site, it is deployed under the server machine only ones and hence the investment is also the same. The owner need not invest every time making it economically feasible. VI.2 Technical Feasibility: The application is provided with the inbuilt user manual that helps the user in following the structure of the application and work through the transactions. Hence the user need not be trained on the application work making it technically feasible. Operational Feasibility: The application can be ensured to access or handle the specified transactions in the web site required by the user successfully making it operationally feasible.

VI.3

Product Info View Products

Product Info Set Offers

Sales Manager Login Customer Info

Best Customer

Dispatch Orders

Supplier Info

Fig 3.5 Level 3 DFD