Title of the project
Design and implementation of Online store
Abstract of the project
Project captures activities performed by different roles in a real life online store. The project gives real life understanding of an online store and activities performed by various roles in the supply chain.
Keywords
Generic Technology keywords
Operating System - Windows
Databases “ MS Access
Programming “ Java
Network and Middleware
Software Engineering
Specific Technology keywords
JSP, servlet
Project type keywords
Application development, retail, online store
Functional components of the project
Store “
¢ Sells different goods.
¢ Shows all goods on screen along with images and price.
Customer -
¢ Select goods from store
¢ Pays by credit card
Store Manager -
¢ Ensures availability of goods in store.
¢ Monitors sales of store.
Delivery -
¢ Receives order once it has been confirmed by user.
1 - A customer can request to create login with following information
Name
Delivery Address
Email id ( it is going to be login)
Passwd
Credit card #
Store manager will approve the login request. On approval, an approval email would be sent to the customerâ„¢s email id. Email id of the customer is a valid user.
2 “ Once customer logins, he should be able to select items in his shopping cart.
(TBD “ How quantity is going to be allocated if same item has been selected by multiple user)
3 “ He should be able to add/remove/modify quantity of goods in shopping cart.
“ If placing order for selected goods, credit card # should be validated against an standard algorithm.
(TBD “ A standard algorithm should be made and all credit card number should be validated against it. Before that credit card number should be distributed by security team to customer)
6 “ Once order is placed, a mail should go to delivery.
7 “ If any time quantity of an item goes lower than a specified number, a mail should be sent to manager.
8 “ Customer should be able to modify order before order is shipped by delivery.
10 “ Manager should be able to see following reports
- Sales form date 1 to date 2 (Date validation should be done)
- Items with highest sales in qty form date 1 to date 2
- Items with qty lesser that their specified numbers.
Steps to start-off the project
Learning the following :
1. HTML
2. JSP
3. Servlets,
4. SQL
Requirements
Hardware requirements
Number Description Alternatives (If available)
1 PC with 2 GB hard-disk and 256 MB RAM
Software requirements
Number Description Alternatives (If available)
1 Windows 98 or higher
2 Tomcat server Any freely available server that can run servlets
3 Any editor to write code Notepad, textpad
4 Any RDBMS Oracle or MS Access
Manpower requirements
2 to 3 students can complete this in 4 “ 6 months if they work fulltime on it.
Milestones and Timelines
Number Milestone Name Milestone Description
Timeline
Week no.
from the start
of the project Remarks
1 Requirements Specification Complete specification of the system (with appropriate assumptions) including the framing of policy etc “
1 “ Credit card authorization
2 “ Allocation of qty if selected by multiple users at the same time
3 “ List of items and qty lower than which a mail should be sent to manager 2-3 Attempt should be made to add some more relevant functionality other than those that are listed in this document.
2 Technology familiarization Understanding of the technology needed to implement the project. 4-5 The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.
3 Database creation List of tables and attributes of each of them.
1 “ 10 customers with valid credit card numbers as provided by security
2 “ 50 items and prices
3 “ Login ids for manager, delivery, security
5-7 It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.
4 High-level and Detailed Design HLD
Assumptions
Flow charts
List of screens
DLD
Pseudo code or algorithm for each the activity 7-9 The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).
5 Implementation of the front-end of the system Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options 10-12 During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.
6 Integrating the front-end with the database 1 - Screens connected to data base and updating data base as required.
12-13
7 Integration Testing The system should be thoroughly tested by running all the testcases written for the system (from milestone 5). 14-15 Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.
8 Final Review Issues found during the previous milestone are fixed and the system is ready for the final review. 16-18 During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)
Guidelines and References
JSP, SQL, HTML, javascript -
http://w3schools.com
Servlet -
