3 – Data Process Model (Inventory Management System)


This section shows the flow of information through a system. Each process transform inputs into outputs.

The Choose of SDLC

A waterfall model is a sequential (non-iterative) design process, used in software development processes, in which progress is seen as flowing steadily downwards through the phases of conception, initiation, analysis, design, construction, testing, implementation and maintenance. The first phase of the waterfall model is a Requirements in which the developers of the system needed to know what are needed in the system or what is really the clients want to that system in order to meet their satisfaction. Once the client is satisfied for the use of waterfall model, the developers can draw up the specification document with some assurance that the product meets the client’s real need. So therefore, proponents used the waterfall methodology for the Inventory Management System in Transmission Specialist INC. project due to the following reasons:

a. Clarity of User Requirements

The waterfall model assures that the software meets the user requirements. The working prototype has been validated trough the interaction with the client, it is reasonable to expect that the resulting specification is based on the user requirements.

b. Familiarity with Technology

Though system prototyping is not good when the system use new technology with which the analyst and the programmers are not familiar with but since a common programming language which is C#.

c. System Complexity

Waterfall model is appropriate and useful in this study since it is not a complicated system.

d. System Reliability

With the use of waterfall model, we can see the progress of the project as it goes to its completion.

e. Schedule Visibility

Since every phase of this model means completion, so I think waterfall model is suitable for this project.

The Waterfall Model

Figure 1.1 The Waterfall Model

The Waterfall methodology also known as the Waterfall Model—is a sequential software development process, where progress flows steadily toward the conclusion (like a waterfall) through the phases of a project (that is, analysis, design, development, testing). This involves fully documenting a project in advance, including the user interface, user stories, and all the features’ variations and outcomes.

The proponent’s uses waterfall method to ensure that the software is guided from planning to implementation with no backtracking, and once the software implemented, everything will be stable and finished.

Requirement analysis

In this phase the proponents fully understand the problems from the informants. The proponents asked questions regarding the system they currently used in their inventory. The proponents also asked on how the process being made during pull-in and pull-out of items. Every questions that was answered by the informants are listed in order to analyze the need to build the product requirements.

Design phase

The proponents design and layout of the new system according to the gathered information from the informants. The proponents designed the layout of the system based from the gathered information. And in this phase the proponents started to analyze the data gathered and started the documentation in each requirement

Implementation phase

In this phase, the proponents started to implement the prototype of the system. The coding of the system was done by our project manager. The coding was takes about a month until the system is functional.

Verification and Testings

Before the system was released to the client’s, the proponents test the functionality of the system as it based on the problem from the informants. The proponents make sure that the system is fully functional in order to meet the client’s satisfaction. Testing was being done in every there’s some adjustments of the system.


The proponents knew that there would still be updates and patches every year to maintain the system more stable and more efficient. There are some issues which come up in the client environment. To fix those issues, patches are released and also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

Context Diagram

A system context diagram is a diagram that defines the boundary between the system, or part of a system, and its environment.


Figure 1.2 Context Diagram

The user can access the system and can do the following actions: View Inventory for viewing the records, Update Inventory for recording transactions every items going inside and outside the warehouse and Pull-out/delete Item. It requires security password before the user can do Update Inventory and Pull-out Item action.

Event Partition Diagram

The figures below show the event partition of the context diagram.

Figure 1.3 View Inventory process

User can view the whole inventory stocks, the list of pulled-out items and the list of damage items. View stocks button will show the whole inventory stock while view pulled-out items will show the list of the pulled-out items and view damage items will show the list of damage items. It has a search functionality for the user to be able to check for item availability.

Figure 1.4 Update Inventory process

User can add new item, update an existing item and delete an item. After the user select action, the non-food inventory table will be updated and the system will give notification if the action is success. It has a search functionality for the user to be able to check for item availability.

Bibliography and References




Other Connected Topics

2-Feasibility Analysis

1-The Envirotnment

Leave a Reply

Your email address will not be published. Required fields are marked *