IMS Case Study
IMS Case Study
1. Abstract.......................................................................................................................................... 2
2. Introduction ................................................................................................................................... 3
3. System Analysis ............................................................................................................................. 5
4. System Design ................................................................................................................................ 8
5. Implementation ........................................................................................................................... 15
6. Testing .......................................................................................................................................... 16
7. Conclusion ................................................................................................................................... 17
8. Reference ..................................................................................................................................... 18
1|Page
1. Abstract
2|Page
2. Introduction
2.1 Introduction to Inventory Management System
The project Inventory Management System is a complete desktop-based application. The
main aim of the project is to develop Inventory Management System Model software in
which all the information regarding the stock of the organization will be presented. It is an
intranet-based desktop application which has admin component to manage the inventory and
maintenance of the inventory system. This desktop application is based on the management
of stock of an organization. The application contains general organization profile, sales
details, Purchase details and the remaining stock that are presented in the organization. There
is a provision of updating the inventory also. This application also provides the remaining
balance of the stock as well as the details of the balance of transaction. Each new stock is
created and entitled with the named and the entry date of that stock and it can also be update
any time when required as per the transaction or the sales is returned in case. Here the login
page is created in order to protect the management of the stock of organization in order to
prevent it from the threads and misuse of the inventory.
3|Page
2.4 Scope of the Application
Inventory Management System (IMS) is targeted to the small or medium organization which
doesn’t have many warehouses i.e. only to those organization that has single power of
authority. Some of the scope are:
4|Page
3. System Analysis
5|Page
3.4 Feasibility Analysis
This software has been tested for various feasibility criterions from various point of
views.
3.4.1 Economic Feasibility
The system is estimated to be economically affordable. The system is medium scale
desktop application and has affordable price. The benefits include increased efficiency,
effectiveness, and the better performance. Comparing the cost and benefits the system is
found to be economically feasible.
A. Input/output
6|Page
4. System shall provide search facility on customer name, Order Placed, date of order,
date of order dispatch, date of transaction, transaction amount, credit card no etc.
5. System should provide facility for change in address/name.
6. System should maintain the details about placing order/dispatch or order i.e, order
status
B. Processing
2. System should inform the pending order and make changes if the order is dispatched.
C. Error handling
3. Should report any data type mismatches any field on the forms.
7|Page
4. System Design
4.1Process Flow Diagram
Process Flow Diagram or Flowchart is a diagram which uses geometric symbols and
arrows to define the relationships. It is a diagrammatic representation of the algorithm.
The Process flow Diagram of our application is shown below:
8|Page
4.2 Use Case Diagram
9|Page
Use case Diagram for Supplier
Checks Inventories
<<include>>
Tracks Order
Sends Invoice
Supplier
Updates Records
10 | P a g e
Use Case Diagram for Customer
Studies
Requirements
Makes payment
Customer Clerk
Invoice
Send GRN
11 | P a g e
4.3 Class Diagram for a customer order
Customer Order
Cust_Id Order_no
Name Ordercredate
Addr1 Order_status
Addr2 Shipment_dat
Cust_city e
Pincode Challan
Addcust()
Updatecust() calcBilltotal()
Getcustdet() Payment calctotalweig
Amount ht()
Payment
date
Makepayme
nt()
Getinvoice()
Ordetdetail Material
Orderno
Materialqty Materialcode
Materialvalue Plantcode
Stckqty
Caclsubtotal
calcweight Getpriceforqty()
Credit Cheque
Number Chqno
Type Bankname
Expirydate Bankid
validating validating
GRN
Recivedqty
Damaged
Rejected
Rejectgood()
Description()
12 | P a g e
4.4 Activity Diagram
13 | P a g e
4.5 Sequence diagram for Supplier
Log In
Validate
Tracks order
Places order
Makes Payment
Dispatch Order
Send GNR
14 | P a g e
5. Implementation
Inventory Management System will be designed using Visual Studio as mentioned earlier
following the three-tier application architecture. It provided us with the code editor as a white
blank space and the solution explorer where every code file is kept. Code Editor is where the
logical were developed into code and kept safe in the solution explorer. In solution explorer
we kept every code file by creating the folder and adding those files in a folder that are
similar in nature. The main folder is the Inventory Management System.
15 | P a g e
6. Testing
6.1 Purpose of Testing
The purpose of software testing is to access or evaluate the capabilities or attributes of
a software program’s ability to adequately meet the applicable standards and
application need. Testing does not ensure quality and the purpose of testing is not to find
bugs. Testing can be verification and validation or reliability estimation. The primary
objective if testing includes:
To identifying defects in the application.
The most important role of testing is simply to provide information.
to check the proper working of the application while inserting updating and deleting
the entry of the products.
16 | P a g e
7. Conclusion
7.1 Project Limitation
Since this is our first project it has some limitation. Due to less knowledge in particular fields
and limited time we were not able to fulfil all our expectations that we expected we could do
while the project got started. We hope this limitation are considerable. Some of the project
limitations are:
This application is not suitable for those organization where there is large quantity of
product and different level of warehouses
This software application is able to generate only simple reports.
Single admin panel is only made.
It is not suitable for large organization.
7.2 Conclusion
To conclude, Inventory Management System is a simple desktop based application basically
suitable for small organization. It has every basic item which are used for the small
organization. Our team is successful in making the application where we can update, insert
and delete the item as per the requirement. This application also provides a simple report on
daily basis to know the daily sales and purchase details. This application matches for small
organization where there small limited if warehouse. Through it has some limitations, our
team strongly believes that the implementation of this system will surely benefit the
organization.
17 | P a g e
8.Reference
https://en.wikipedia.org/wiki/Inventory_management_software
https://blog.capterra.com/what-is-an-inventory-management-system/
https://creately.com
https://www.scribd.com
https://www.academia.edu/Documents/in/Inventory_Management_System
18 | P a g e