Design of Proposed Inventory System using Binary Trees

COVER PAGE

Contents
1 Introduction............................................................................................................. 3
2 Variables, keys and ranges...................................................................................... 3
3 Operations............................................................................................................... 4
4 Algorithms............................................................................................................... 4
5 Larger system changes........................................................................................... 6
6 Conclusion............................................................................................................... 7
References................................................................................................................. 7

1 Introduction
This report presents a discussion on the design of the proposed inventory system.
The design is discussed in terms of the static and dynamic structure of the system
from the variables , keys and ranges and that will make up the inventory system, to
the operations and algorithms that will be used in the system with a justification as
to why those algorithms are the best fit for the system as opposed to similar
algorithms that can be used in implementing the system. The design is also
analyzed in terms of elasticity in the amount of data its supposed to handle if the
system is expanded to handle more data as a result of a merger between two
companies requiring the formed company to use the existing inventory system.
2 Variables, keys and ranges
The variables that will make up the system can be discussed using a simple class
diagram with objects and attributes that define the objects. The attributes defining
an object become the variables during implementation of the system on the basis of
the class diagram.
Figure
1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .
. . . . . . .. Class diagram
The class diagram shown in figure above models the objects modelled as classes
that will be used to implement the system. By following object-oriented
programming concepts to implement the system, we can design the system with
the following classes;
 Product- The product class will be used to model object with the following
attributes: name, price, type and quantity that is currently available for the
product. A key OOP construct will be implemented in the design of the class
as all the variables will be declared as private and then getter and setter
methods will be used to access and mutate the variables respectively.
 HouseHould- This class is a child class and inherits all the attributes and
operations of the product class. The relationship between the house hold
class and the product class is that the product class is the parent class while
the household class is the child class as shown in the class diagram. The