Development of an online Sales and Inventory Management System -SIMS
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
computer science technology
Active In SP

Posts: 740
Joined: Jan 2010
18-01-2010, 07:01 PM

.doc   Development of an online Sales and Inventory Management System -SIMS.doc (Size: 49.5 KB / Downloads: 335)
Development of an online Sales and Inventory Management System (SIMS)
Title of the project and implimentation

Development of an online Sales and Inventory Management System (SIMS)

Abstract of the project and implimentation

This project and implimentation is aimed at developing an online Sales and Inventory Management System (SIMS) for a departmental store. This system can be used to store the details of the inventory, update the inventory based on the sale details, produce receipts for sales, generate sales and inventory reports periodically etc. This is one integrated system that contains both the user component (used by salespersons, sales managers inventory managers etc) and the admin component (used by the administrators for performing admin level functions such as adding new items to the inventory, changing the price of an item etc).

This system runs on multiple terminals, offers a GUI interface to its users and connects to a common database(s).


Generic Technlogy keywords

Databases, Network and middleware, Programming

Specific Technology keywords

MS-SQL server, MS-Access, Visual Basic 6, Java

Project type keywords

Analysis, Design, Implementation, Testing, User Interface

Functional components of the project and implimentation

Following is a list of functionalities of the system. More functionalities that you find appropriate can be added to this list. And, in places where the description of a functionality is not adequate, you can make appropriate assumptions and proceed.

There are registered people in the system (sales people working in the shop, inventory managers, admin et al). Each one of them may have some exclusive privileges (admin, for example, could create new users to the system whereas sales people cannot).

1. A sales person should be able to

¢ login to the system through the initial screen of the system

¢ change the password after logging into the system

¢ see the status of the inventory, ie, whether a particular item is available or not etc

¢ search for a particular item by typing the initial letters (˜app™ for example may bring up the item ˜apple™ in the top) or by category-wise (apple, for example, may be looked up by going through the category ˜fruits™)

¢ enter the items purchased by a customer and produce a bill for the same (the bill will have a unique sale id, date, time, item/quantity/price details etc)

¢ cancel the produced bill, in case of error in entering the details, and produce a new one

¢ take back an already sold item that is not satisfactory to the customer (the shop allows that) and produce a receipt for the same

¢ inform the inventory manager about the items that are not available, so that they can be stocked

¢ inform the sales manager about any exceptions (such as an item is being purchased, but it is not available in the system)

¢ get help about the system on how to use the different features of the system

2. The inventory manager should be able to

¢ login to the system/change his password after logging in etc

¢ check the status of the inventory

¢ see the reports from sales people about items that are not available and need to be kept in the inventory

¢ validate the inventory against the sales done in the previous day (whether the items that are sold and the change in the inventory for the corresponding items match etc)

¢ generate inventory reports of the items category-wise, price-wise etc

¢ generate inventory-trends (like how is coffee powder stock changing over the month)

3. The sales manager should be able to

¢ login to the system/change his password after logging in etc

¢ check how many bills have been generated in the day so far

¢ check how much money is transacted in the day so far

¢ check how many bills have been cancelled so far in the day(due to wrong entry by the sales persons)

¢ check how many items have been returned so far in the day

¢ check for any exception reports from the sales persons and correct it by contacting the inventory manager

¢ generate sales-trend graphs for each of the item (like how is apple selling in the last one month)

4. The administrator should be able to

¢ login to the system and change his password after logging in

¢ add new users to the system

¢ add new items/categories to the inventory (˜grape™ may be added to the category ˜fruits™ or a new category such as ˜vegetables™ may be added)

¢ change the price of an item

Steps to start-off the project and implimentation

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

1. Study and be comfortable with technologies such as Java/Visual Basic, SQL server/MS-Access etc. Some links to these technologies are given in the ËœGuidelines and Referencesâ„¢ section of this document

2. Make a database of items/categories

3. Make a list of sales persons/managers/administrator who would be using the system

4. Create the front-page of the system giving a brief description about the system and a login box

5. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system

6. Create other sub-systems like error notification, screens for various functions (like purchase, cancellation, return of items, admin pages etc)


Hardware requirements

Number Description Alternatives (If available)
1 PC with 2 GB hard-disk and 256 MB RAM Not-Applicable

Software requirements

Number Description Alternatives (If available)
1 Windows 95/98/XP with MS-office Not Applicable
2 MS-SQL server 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


Week no.
from the start
of the project and implimentation Remarks

1 Requirements Specification Complete specification of the system (with appropriate assumptions) including the database design (for storing the items details). A document detailing the same should be written and a presentation on that be made. 1-2 Attempt should be made to add some more relevant functionalities other than those that are listed in this document.

And, attempt should be made to present an overall view of the system which makes sense for the users of the system.
2 Technology familiarization Understanding of the technology needed to implement the project and implimentation. 3-4 The presentation should be from the point of view of being able to apply it to the project and implimentation, rather than from a theoretical perspective.
3 High-level and Detailed Design Listing down all possible scenarios (like searching for an item, producing a bill, cancelling a bill, notifying about items that are out of stock, adding a new user, adding a new item etc) and then coming up with flow-charts or pseudocode to handle the scenario. 5-7 The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).
4 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 sales persons/ sales manager/ inventory manager and the administrator for the various functions etc. 7-9 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.

The test scenarios can be grouped under the respective user who would be associated with it (producing a bill, for example, can be grouped under Ëœsales personsâ„¢ testcases)
5 Integrating the front-end with the database The front-end developed in the earlier milestone will now be able to update the sales/inventory database. Other features like report generation etc should be functional at this stage. In short, the system should be ready for integration testing. 10-12
6 Integration Testing The system should be thoroughly tested by running all the testcases written for the system (from milestone 5). 13-14 Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.
7 Final Review Issues found during the previous milestone are fixed and the system is ready for the final review. 15-16 During the final review of the project and implimentation, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)
Use Search at wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
seminar surveyer
Active In SP

Posts: 3,541
Joined: Sep 2010
24-12-2010, 12:02 PM

.doc   SMS REPORT o7 FINAL.doc (Size: 1.38 MB / Downloads: 153)


Sales management is attainment of an organization's sales goals in an effective & efficient manner through planning, staffing, training, leading & controlling organizational resources. Revenue, sales, and sources of funds fuel organizations and the management of that process is the most important function.
Sales Management System allows you to easily manage and automate sales teams, generate more revenue with more accurate business intelligence.Sales management gives the sales organization the resources needed to capitalize on every lead/prospect/customer and ensure peak yield for the company.
Sales Management System is an easy to use, fully integrated and a customizable platform that provides comprehensive sales automation for the company. Coupled with Customer Management System, Document Management System and Marketing Management System, the company can provide full comprehensive Customer Resources Management System.

The four phase-model of Management process is one of many useful frameworks for planning the sales process. It includes:
1. Conception – What will be offered?
2. Planning – How?
3. Execution – When and at what pace and scale?
4. Control – How will feedback and contingencies be acted upon?
5. Feedback – How we have to integrate and reply back activity to activity?
This model is cyclical, so it is a constant/continuous process.

Sales Management, however, is concerned with the process of encouraging customers to exchange their funds for your services or goods. By contrast, marketing might concern itself with expanding opportunities for installing more processes in more places and expanding or creating new sales channels. For example, a firm might have "walk-in customers." Sales management would concern itself with the customer experience, the sales dialog ("whats in it for me," suggestive selling, up-selling, positioning statements, consultative sales), and ultimately closing the sale. This organization's marketing department, on the other hand, would be concerned with developing sales channels other than "walk-in" customers or increasing the volume. For example, out-bound telephonic out-reach might be a viable additional sales channel. Sales management, in turn would be tasked with developing this channel's compensation plan, customer experience, sales dialog, and closing. Developing a sales management process for the 'walk-in customer sales process' might be very different from the 'out-bound telephonic sales management process.

ASP.NET offers a novel programming model and infrastructure that facilitates a powerful new class of applications. ASP.NET is a compiled. NET-based environment, so one can author applications in any .NET compatible language, including Visual Basic, C# and Jscript.NET. Developers can effortlessly access the advantage of these technologies, which consist of a managed Common Language Runtime environment, type safety, inheritance, and so on. With the aid of Microsoft Visual Studio.NET Web development becomes easier.

Web Forms permits us to build powerful forms-based Web pages. When building these pages, we can use Web Forms controls to create common UI elements and program them for common tasks. These controls permit us to rapidly build up a Web Form.

Web services enable the exchange of data in client-server or server-server scenarios, using standards like HTTP, SOAP (Simple Object Access Protocol) and XML messaging to move data across firewalls. XML provides meaning to data, and SOAP is the protocol that allows web services to communicate easily with one another. Web services are not tied to a particular component technology or object-calling convention. As a result, programs written in any language, using any component model, and running on any operating system can access Web services.

Introduction of Database management System

A database is a collection of interrelated data. The collection of data must be logically coherent with some inherent meaning. A database is designed and built for a specific purpose, keeping in mind the needs of the applications that are going to use it and end users of those applications. It is managed by a software package known a database management system (DBMS).
A DBMS is a software system that enables users to record and maintain database. It provides an environment where in data can be stored and retrieved from database easily and must efficiently. The data can be any thing that is deemed to be of significant to the organization, the system is serving.

What is .NET?

.NET is set of common services which can be used from a number of languages and have the following specialties:
i. These services are executed in the form of intermediate code that is independent of the underlying architecture.
ii. They operate in the runtime (Common Language Runtime), which manages resources and monitors applications execution.
The .NET frameworks are a multi-language environment for building, deploying, and running web services and applications. The Microsoft .NET platform provides .NET infrastructure and tools to build and operate a new generation of services.

In recent years, Database Management System (DBMS) have established themselves as primary means of data storage for information system ranging from large commercial transaction to PC desktop application. At the heart of today’s most of the information system is Relational Database System (RDBMS).
Have been the workhouse for data management operation for over a decade and continue to evolve and mature, providing sophisticated storage, retrieval and distribution function to enterprise – wide data processing and management system compared to the file system, RDBMS provides organization with capability to easily integrate and leverage the massive amount of operational data into meaningful data.
The evolution of high-powered database engine such as SQL Server 2005 has faster the development of advance enabling technology including client/server ,data warehousing and online processing ,all of which comprise the core today’s state –of –art information system. A database is an organized collection of related information. Any meaningful data is called information. A database management system is a collection of interrelated data a set of programs to access that data.
The SQL Server architecture in this section is generic architecture that applies all platforms on which SQL run. These may be different platform, but the fundamentals are same. Physically in its simplest form, an SQL database is nothing more than a set of files on the disk. The physical relation of these files is irrelevant to the function of the database. Logically the database is divided into a set of user account, each of which is identified by username and password unique to the database. Tables and objects are owned one by one of these. SQL Server maintains its own list of authorized user and their associated privileged, manages memory cache paging; control locking for concurrent resource usage; dispatch and schedules users request ; manages space usage within its table space structure.

seminar tips
Super Moderator

Posts: 8,857
Joined: Oct 2012
03-12-2012, 11:15 AM

to get information about the topic "inventory management system" full report ppt and related topic refer the link bellow


Active In SP

Posts: 1
Joined: Jan 2013
06-01-2013, 02:14 AM

Im creating a sales and inventory mangement sytem .Above details were realy valuable for me starting the project and implimentation.Now I have got stuck creating use case.It will be gladly appriciated if you could send me the Use Case ans class diagram of the system.

Important Note..!

If you are not satisfied with above reply ,..Please


So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  Development of an Online Course Portal for a campus seminar topics 5 6,168 31-10-2016, 02:29 PM
Last Post: jaseela123
  ONLINE EL-CHICO RESTAURANT MANAGEMENT SYSTEM seminar flower 1 642 08-04-2016, 11:10 AM
Last Post: mkaasees
  Report on Online grievance redressal system study tips 1 653 04-04-2016, 03:53 PM
Last Post: mkaasees
  PROJECT ON HOSPITAL MANAGEMENT SYSTEM seminar flower 1 951 01-04-2016, 11:54 AM
Last Post: mkaasees
  ABSTRACT ON REPORT HOSPITAL MANAGEMENT SYSTEM study tips 1 588 01-04-2016, 11:53 AM
Last Post: mkaasees
  Online Rental House Web Portal smart paper boy 5 4,024 30-01-2015, 12:29 PM
Last Post: bharath9530
  HOSTEL MANAGEMENT SYSTEM pdf seminar tips 3 7,614 09-12-2014, 03:42 PM
Last Post: mkaasees
Thumbs Up Inventory Control System uttuswami 2 742 20-10-2014, 07:46 PM
Last Post: CxWfRyIPv
  Project Report On OnLine Cab Service project girl 1 976 22-08-2014, 07:29 PM
Last Post: HKGSuIeNq
  scholarship MANAGEMENT SYSTEM seminar tips 6 5,136 12-08-2014, 07:56 AM
Last Post: donsilver