Inventory Management System Report
Inventory Management System Report
Inventory Management System Report
NAVRACHANA UNIVERSITY
Bachelors of Computer Applications (BCA)
Academic Year 2011-2012
Major Project Sem-6
(T.Y.BCA)
Team-Member
Jaykishan Sharma
CERTIFICATE
By using this project any customer or user can manage his stock
so the project can be very help full for all the customer or user.
I have added many forms and function which makes project user
friendly and easy to understand.
Project Summary
Inventory Control is a very user friendly project. In this project
user can easily understand and fill up the Inventory. In this project
there are various types of forms are there like sell form, buy form in
which user can insert his Inventory, Needs & facilities then upload his
inventory.
In this project all the forms which user wants to fill up are totally
easy to understand. So in any way user is not disturbed or not confuse
at all, anyone can easily fill up Inventory.
Purpose
Goals & Objectives
The Purpose of the project is very clear that user can manage
his inventory easily. User can see stock of all inventory
Increased Reliability
Memory Leak, Deadlock and Crash Protection: .NET
automatically detects and recovers from errors like
deadlocks and memory leaks to ensure your application is
always available to your users.
Time Consuming.
It is very tedious.
All information is not placed separately.
Lot of paper work.
Slow data processing
Not user-friendly environment.
It is difficult to found records due file management system.
4) Code Generation
In Code Generation phase, the design must be decoded into a
machine-readable form. If the design of software product is done in
a detailed manner, code generation can be achieved without much
complication.
6) Maintenance
Software will definitely go through change once when it is
delivered to the customer. There are large numbers of reasons for
the change. Change could happen due to some unpredicted input
values into the system. In addition to this the changes in the system
directly have an effect on the software operations. The software
should be implemented to accommodate changes that could be
happen during the post development period.
Project Plan
Risk Identification
Technical Risks
Product Size
Hardware Requirement
Hardware Minimum Requirement
Software Requirement
Software Requirement
Operating System Window XP or more
Reliability Requirements
The system should be reliable enough in the following areas:
Without log into Login Form user cannot access the application.
Requirement Analysis
In Requirement analysis, we met to the company head and
project guide. We discussed about their requirements and the
problems they are facing with existing system.
The data collected during the fact finding study and included
in data flow and decision analysis documentation are examined to
determine how well the system is performing and whether it will.
Meet the organizations demand.
Reliability
Efficiency
The application should make optimal use of system
resources. Also the runtime performance of the system should be
considered.
Maintenance
Software maintenance applies to following phases in the existing
program
Change in software due to errors.
Change in software because the software must be adapted
to accommodate changes in its external environment.
Change in software when the customer requires functional
or performance enhancements.
Feasibility Study:
Technical Feasibility:
Front-End Selection:
Platform independent.
Easy to deploy & maintain.
Event driven programming
Front-End must support some popular Back-End like
MS Access, SQL Server and Oracle.
According to the organization requirements and
culture.
Economical Feasibility:
The cost to conduct a full system investigation.
The cost of hardware and software for class of
application being considered.
The benefit in the form of the reduced cost.
Requirement Validation
It means that the developed software is as per
requirement or not? Simply stating whatever we are
doing is right or wrong as per requirements?
Here we check each and every requirement and
compare with our product and that it satisfies the user
need.
UML Diagrams
Unified Modeling Language (UML) is a standardized general-
purpose modeling language in the field of object-oriented software
engineering.
UML includes a set of graphic notation techniques to create Visual
Models of object-oriented software-intensive systems.
Behavior Diagrams
Use Case Diagram: Describes the functionally provided by a
system in terms of actors, their goals represented as use cases,
and any dependencies among those use cases.
Activity Diagrams: Describes the business and operational
step-by-step workflows of components in a system. An activity
diagram shows the overall flow of control.
Sequence Diagram: Describes the sequence of processes.
Navrachana University, Vadodara. Page 24
Use Case Diagram
LOGIN
Add Product
Generate Bill
Update Database
Logout
product_type_name Varchar 20
product_master
Field Name Data Type Range
product_name Varchar 20
product_purchase_date Date/time
product_stock int 5
contect_person Varchar 50
contect_no Int 15
e-mail Varchar 50
product_sell_date Date/time
invoice_no Int 5
supplier_id varchar 5
stock_master
Field Name Data Type Range
product_type_id Int 5
product_stock Int 5
contect_person Varchar 50
contect_no Int 20
E-mail Varchar 50
product_purchase_date Date/time
bill_no Int 5
supplier_id Int 5
supplier_master
Field Name Data Type Range
supplier_id Int 5
(p_key)
supplier_name Varchar 50
contect_person Varchar 50
contect_no Int 20
invoice_no Int 5
product_type_id Int 5
transection_id Int 5
transection_type varchar 10
no_of_products_transection Int 5
product_stock Int 5
Implementation Environment
By applying the implementations and above analysis we
have created Web Applications in Asp.net and SQL database. That
is very to operate.
The interrelated database of SQL server 2008 is connected
to Asp.net.
Security Feature
Inventory Control is developed in C#.NET and the backend is
SQL Server 2008 database which provides maximum
security. Security is a key feature of SQL Server 2008, which
provides confidentiality, integrity, and availability of mission-
critical data.
User authentication feature in Inventory Control provides
authentication so that any unauthorized user cannot use this
application.
Books
Programming in C# a primer
By: E Balagurusamy
Publication: Tata McGraw Hill
Software Engineering
By: Sommerville
Publication: Low Price Edition
Web References
www.code.project.com
www.google.com
www.asp.net.com
www.wikipedia.org