Design and development of Point Of Sale [ POS ]


Title of the project


Design and development of Point Of Sale [ POS ]


Abstract of the project


This project is a very popular and widely used in many big supermarket / departmental stores and is used to cater the need of the sales system there. This is an online system and is used maintain / control most of the activities happening in big stores. This maintains and controls the stock details and does online billing and generates various online reports.




Generic Technlogy keywords


Databases, Network and Middleware


Specific Technology keywords


MS-SQL server / Oracle, Visual Basic .NET


Project type keywords


Analysis, Design, Implementation, Testing, User Interface


Functional components of the project


Following is a list of functionalities of the system. More functionalities as deemed appropriate can be added list. And, in places where the description of functionality is not adequate, appropriate assumptions can be made.


User Login


First to enter this system the users has to login to this system. Basically there are  2 types of users in this system.


1.      Admin users - Has full access to all the modules of this system.


2.      Normal users – Has restricted access. i.e., Normal users has access to some of the modules only.


  • First a login screen should be displayed to get the user details. The user has to enter the user-id and the password. The password has to be masked with character ‘*’.
  • The user details should be verified against the details in the user tables and if he / she is valid user, they should be entered into the system. Once entered, based on the user type access to the different modules to be enabled / disabled.


  • If user enters wrong password for continuously 5 times, the account should be locked. The information about the login and logout details should be stored in a separate table.


User Details


This module contains 2 parts. User maintenance and password change.


  • User maintenance is used to create a new user, modify the details of existing user or remove the existing user.  Only the admin type user will have access to this part. Normal user won’t have access to this. While storing into database the password should be encrypted and stored. The user can choose his / her own logic to encrypt the password.


  • User password is used to change their own password. Both admin and normal user will have access to this.


Stock Details


This module is used to maintain the various products available in the store. Each product available in the store should be classified under a product category. This module will be enabled only to the admin type of users.


  • A separate screen should be provided to maintain the product category. It should provide a way to add, modify and delete the category details.


  • If a new product is received it should be added to the system with the corresponding details like product information, quantity, category, etc.


  • There should be a screen to maintain the vendor details. Vendor details should be stored in a separate table.




This is the main / core part of the entire system. The online billing is done in this part. This includes various things like collecting item details and updating price, and getting payment information, etc. This screen should have item details, counter no, user id, payment details, etc. In addition, the billing should also incorporate and offers/discounts during that period of time.




  • This screen mainly contains a grid type of control to get the various products purchased. The should have columns like Item No, Description, Batch No, Rate, Quantity, Price, etc.
  • The continuous online bill number should be generated. It should not be a cyclic number or a previously used number.


  • The user should enter item no in the corresponding column of the grid. The item number should be validated and if found valid the description, rate and other details has to be displayed automatically. Then the user should be allowed to enter the quantity and price and total should updated online.


  • Once this is done, the mode of payment should be Cash. Then the amount received should be taken as input and balance should computed and displayed.


  • After this the bill has to be printed with all these details. A confirmation screen has to be displayed on the screen about the printing. If bill is not printed properly, provision should be made to reprint the bill.




This module is used to print various online reports. This module will be enabled only to the admin type of users.


  • User details report – This contains various information about the users available.


  • User login details report – This reports takes the user ID and from / to date as input and generates the report containing the login date, login time and logout time, etc.


  • Item category report – This gives the different item categories.


  • Item details report – This gives the information about the various items available in the store along with the information like category, stock level, etc.


  • Sales report – This report takes date as input and gives details of sales made on that date along with item information. This report should be available for a given date or for a date range.


  • Vendor details report – This report gives the details about all the vendors.




This module contains the following 2 things – Help and About.


  • The Help menu should display the detail information about the system. It is like a typical help system available in any windows application.


  • The About menu should give information about this software like developed by,  version and contact details.

Steps to start-off the project


The system can be  developed using Active Server Pages as the front end. MS Access can be used as back end to this system.


The following steps will be helpful to start off the project.


  1. Study and be comfortable with technologies such as


  1. Visual Basic.NET
  2. SQL server / Oracle / MS Access


            Some links to these technologies are given in the ‘Guidelines and References’ 

            section of this document


  1. Little bit of basic knowledge of POS system would be very helpful.


  1. The system should be user friendly as much as possible. Display messages wherever required.


  1. Give the help facility in detail and easy to understand.




Hardware requirements




Alternatives (If available)


PC with min 10 GB hard-disk and 512 MB RAM.




Software requirements




Alternatives (If available)


Windows 98/XP/2000



MS-SQL server / Oracle



Visual Basic .NET




Manpower requirements


2 students can complete this in 4-5 months if they work fulltime on it.


Milestones and Timelines



Milestone Name

Milestone Description





Week no. 

from the start

of the project



Requirements Specification

Complete specification of the system (with appropriate assumptions). A document detailing the same should be written and a presentation on that be made.


Attempt should be made to add some more relevant functionalities other than those that are listed in this document.


Technology familiarization

Understanding of the technology needed to implement the project.


The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.


Database creation

A database design should be done and the same should be created with the necessary tables.


It is important to finalize on the database at this stage itself so that development and testing  can proceed with the actual database itself.

It would be better to have some sample data to use during development stage.


High-level and Detailed  Design

[ In other words, HLD and LLD]

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario.


The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).


Implementation of the system

[ Coding ]

Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options described above.

This phase contains code to communicate with the database also.


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.


Unit Testing

The system should be thoroughly tested by running for all the scenarios.


Another 1 week should be there to handle any issues found during testing of the system.


Integration Testing

The system should be thoroughly tested by running all the testcases written for the system (from milestone 5).


Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.


Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.


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 tutorial) tutorial)

Tags :
Your rating: None Average: 2 (1 vote)