Download Inventory Management System Case Study and more Essays (university) System Analysis and Design in PDF only on Docsity!
Table of Contents
- Abstract............................................................................................................................................. 1 ............................................................................................................................................................... 2
- Introduction...................................................................................................................................... 2
- System Analysis................................................................................................................................. 4
- System Design................................................................................................................................... 7
- Implementation.............................................................................................................................. 15
- Testing............................................................................................................................................ 16
- Conclusion....................................................................................................................................... 17
- Reference......................................................................................................................................... 18
1. Abstract
Inventory Management System is a desktop-based application for managing the inventory system of any organization. The Inventory Management System (IMS) refers to the system and processes to manage the stock of organization with the involvement of Technology system. This system can be used to store the details of the inventory, stock maintenance, update the inventory based on the sales details, generate sales and inventory report daily or weekly based. This project is categorized individual aspects for the sales and inventory management system. In this system we are solving different problem affecting to direct sales management and purchase management. Inventory Management System is important to ensure quality control in businesses that handle transactions resolving around consumer goods. Without proper inventory control, a large retail store may run out of stock on an important item. A good inventory management system will alert the wholesaler when it is time to record. Inventory Management System is also on important means of automatically tracking large shipment. An automated Inventory Management System helps to minimize the errors while recording the stock.
2. Introduction
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:
Only one person is responsible in assigning the details or records
It is security driven.
Warehouses can be added as per the requirement.
3. System Analysis
3.1 Background Research
We started research by identifying the need of IMS in the organization. Initially we bounded our research to find the general reasons that emerged the needs of Inventory Management System. We used different techniques to collect the data that can clearly give us the overall image of the application. The techniques we used were interview with the developers, visiting online websites that are presented as the templates and visiting some organization to see their IMS application. Basically, the following factors forced us to develop IMS application: Cost and affordability Lack of stock management. Effective flow of stock transfer and management. Difficulty in monitoring the stock management.
3.2 Requirement Analysis
We collected a number of requirements for project from our primitive research, website visits, and interview to the concerned personnel and their experiences regarding the concepts of its development. We have even visited some organization in Kathmandu valley and analyse its importance and try to develop the project by fulfilling all the weakness that were found in the application. We then decided to build same type of application with different logic flow and new language which will be suitable for the small organization.
3.3 IMS Requirement
The goal for the application is to manage the inventory management function of the organization. Once it is automated all the functions can be effectively managed and the organization can achieve the competitive advantage. Business requirement are discussed in the Scope section, with the following additional details: Helps to search the specific product and remaining stock. Details information about the product sales and purchase. Brief Information of the organization todays status in terms of news, number of present inventories as per the date entered. It helps to identify the total presented inventory in the company. To know the balance and details of sales distributed in specific date. There is proper transaction management of inventory. All transaction has specific entry date along with quantity and rate. Only admin can login in the page.
3.4 Feasibility Analysis
This software has been tested for various feasibility criterions from various point of views.
- System should maintain the details about placing order/dispatch or order i.e, order status B. Processing
- System should automatically generate the bill.
- System should inform the pending order and make changes if the order is dispatched. C. Error handling
- Should report any errors on duplicate primary keys.
- Should report any ‘Out of Range’ values on numeric fields
- Should report any data type mismatches any field on the forms.
- Should report on any ‘Invalid dates’
- Should report any violation of authorization of rights
- Should report any Invalid Login errors 3.5.2 Non-functional Requirements
- All user manuals should be provided in the necessary format
- Application should support 5 simultaneous users.
- Transaction should be completed within 1/5th^ of second
- There will be backup procedure to maintain records.
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: Figure 4.1: IMS Process flow diagram
4.2 Use Case Diagram
Login Id and Password Customer Updates Records Sends Invoice Dispatch order on time Checks Inventories <> Tracks Order Supplier
Use Case Diagram for Customer Make list of requirements Places the Order Makes payment Invoice Send GRN Customer Clerk Studies Requirements
4.4 Activity Diagram
Figure 4.3.1: IMS Activity Diagram
4.5 Sequence diagram for Supplier
Supplier Transaction Customer Invoice Log In Validate Places order Tracks order Takes customr details Fill Order details Makes Payment Dispatch Order Send order details Send Invoice Send GNR Add new entry Log Out
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.
6.2 Type of Testing
We have used one type of testing to ensure the error free features of our software application:
6.2.1 Unit Test
This type of testing is the testing of individual software components. It is typically done by the programmer and not by the testers. It requires details information and knowledge about the internal program design and code to perform this. During unit testing, we carried out various testing task such as the reflection of the unit data on database and its interface. Various types of bugs associated with the component were identified and fixed. We use various functional keys to test our software. In our software unit testing is concerned with the stock units, opening stock units and product unit’s validation as well as the validation of product units.
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.
