Smart Inventory Management System 2
Thus the cycle is repeated for every day. Currently all the above activities are done
manually. The process is a tedious one. To arrive at the Inwards, outwards or returns
for items, data has to be gathered from various sources. Because of this errors are
occurring in the process, which is leading to delayed deliveries to the customers.
Some times because of the errors wrong products are sent out which have no
requirement & thus a lot of money is being wasted in maintaining the stock.
Automating such a process will not only eliminate the errors in the process, but also
bring down the delivery times & make the company more competitive. So it was
decided that an automated system should be developed to make the whole process
simpler & easier.
The following is the system developed for the above stated needs. An initial
feasibility study was performed & a conclusion was arrived at that automating such a
system will not only achieve all the things mentioned above, but will also provide
additional Reports which will enable the Management to look at the statistical side of
the inwards, inwards & returns related to each godown. This would also create an
effective Stock management system, which would reduce the confusion in
maintaining the stocks at different godowns, thus effectively reducing the expenditure
costs of the company. Another advantage was that the whole Accounts system could
be linked to this system in future, which would finally reduce the Overheads of the
company.
1.3 Project Plan
It was decided to use good Software engineering principals in the development of the
system since the company had quite a big Stock management & was aiming to add
new godowns & employees & expand their operations in the near future. So the
following Project Plan was drawn up:
1. The Analysts will interact with the current manual system users to get the
Requirements. As a part of this the Requirements Specification Document will be
created.
2. The requirements Specifications document will contain the Analysis & Design of
the system & UML will be used as the modeling language to express the Analysis &
Design of the System. According to Grady Booch et al, in The Unified Modeling
Language User Guide [UML-1998], “The Unified Modeling Language (UML) is a
graphical language for visualizing, specifying, constructing, and documenting the
artifacts of a software-intensive system. The UML gives you a standard way to write a
system's blueprints, covering conceptual things, such as business processes and
system functions, as well as concrete things, such as classes written in a specific
programming language, database schemas, and reusable software components”.
3. The Analysis, Design, Implementation & testing of the System itself will be
broadly based on the Rational Unified Software Development process. According to
Ivar Jacobson et al, in The Unified Software Development Process (The Addison-
Wesley Object Technology Series) [USDP-2000], the Unified Software Development
Process contains Inception, Elaboration, Construction & Transition as the main
Phases, which contain further cycles & iterations. This process will be followed to