26-02-2013, 09:21 AM
Development of an online Sales and Inventory Management System (SIMS)
Development of an online.doc (Size: 55.5 KB / Downloads: 18)
Objective
These guidelines are for the student to adopt to make progress in the project.
Given below are the templates for the documents related to the project. These are just guidelines only. These can be improved by the team.
Requirements Specification (RS)
Following is a template for the RS document. Some example requirements are entered in to it to show how to use the template. Make sure that you enter even the smallest/most trivial requirements also. That would help in validating the system during testing.
Inventory/Sales/User Databases Fields Specification
A database to store the details about the items in the inventory should be designed. A unique code should be given for each item in the inventory. This will be the key of the database.
A database to store the sales details should be there. The key for this database is the unique sale id generated when producing the bill. Some example fields in this database are: the list of items bought under the sale id (a maximum of up to 30 item codes can be there), the date and time of the transaction, the total amount of the transaction, whether the customer paid by cash or card, whether any item was returned later etc
A database to store the user details should be there. The key for this database is the user id. This database will have the user details like his encrypted password, his leave/shift details etc.
Some example fields and the range of valid values for those fields for the inventory database are given below. These need not be taken as such. They can be modified by the team
Test-Plan (TP)
The test-plan is basically a list of testcases that need to be run on the system. Some of the testcases can be run independently for some components (report generation from the database, for example, can be tested independently) and some of the testcases require the whole system to be ready for their execution. It is better to test each component as and when it is ready before integrating the components.