SOFTWARE ARCHITECTURE AND DESIGN

(SWE2004)
PROJECT REVIEW- INVENTORY MANAGEMENT SYSTEM

FACULTY: PROF. SENTHIL KUMARAN U

SUBMITTED BY:
17MIS0114-UDAYAKRISHNAN S

SLOT: A11+TA11
SCENARIO:

A small consignment shop needs a system to manage the inventory of their

store. They have an extremely limited budget, and do not want to purchase an
expensive software suite in such a risky economic environment.
In a single software package, they will need the ability to handle in-store
transactions, mange inventory, create reports, and create an online presence.
Inventory Management with analytics is an online software application
which fulfils the requirement of a typical Stock
It provides the interface to users in a graphical way to manage the daily
transactions as well as historical data. Also provides the management reports like
monthly inwards, monthly deliveries and monthly returns.
This application maintains the centralized database so that any changes
done at a location reflects immediately.

ABSTRACT:

This project is aimed at developing a desktop-based application named Inventory

Management for managing the inventory system of any organization. The
Inventory Management (IM) 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. In this system we are solving different problem affecting
to direct sales management and purchase management. Inventory management is
important to ensure quality control in businesses that handle transactions
revolving around consumer goods. Without the proper inventory control, a large
retail store may run out of stock on an important item. A good inventory
management is also on important means of automatically tracking large shipment.
An automated inventory management helps to minimize the errors while
recording the stock.

ACTORS AND ACTIVITIES:

Inventory Management is one of the basic problems for a company. It may cause
a lot of paperwork, if there is no automated system available. Implementing such
a system is possible but there are a lot of preliminary works such as determination
of the requirements, system structure decision – software requirements, barcode
system selection and determination of the software tools, Inventory System is to
provide a Central Asset Repository of information used to define assets and relate
the asset to its owner, location, and relative importance.
 The Inventory System should be integrated within the everyday functions
performed by personnel associated with entering and maintaining asset
information. The system will reduce the effort devoted to asset management,
while supplying many personnel with the information they need to perform their
functional responsibilities.

USECASES:
Context level diagram:

DESCRIPTION:

Context level diagram is an initial DFD to provide a top-level description

of the problem.
In other words, Creation of model context diagram contains the data flows
described that are external to the system, the following diagram explains about
the context level DFD of inventory management system.

JUSTIFICATION:

This is the zero level DFD of Inventory Management System, where we have
elaborated the high-level process of Inventory. It’s a basic overview of the whole
inventory system or process being analyzed or modeled. It should be easily
understood by a wide audience, including Inventory, purchasing and payment in
zero level DFD of Inventory Management System, we have described the high-
level flow of the Inventory system.
HIGH LEVEL ENTITIES AND PROCESS FLOW OF INVENTORY
MANAGEMENT SYSTEM:
• Managing all the Inventory.
• Managing all the Customer.
• Managing all the Purchasing.
• Managing all the Receiving Stock.
• Managing all the Payment.
• Managing all the Supplier.
• Managing all the Login.

DFD DIAGRAM:

DFD(Data flow Diagram):

A major distinction between the DFD and the Structure Chart is that the
DFD is non-sequential and describes the structure of the problem, while the
structure chart describes a solution in terms of a hierarchy of program units.
The objective of the Structured Systems Analysis steps is to produce a functional
specification that describes what the system is to do.
LEVEL ONE DATA FLOW DIAGRAM:
JUSTIFICATION:
First level DFD of Inventory Management system shows how the system
is divided into sub-system, each of which deals with one or more of the data flows
to or from an external agent, and which together provide all of the functionality
of the Inventory Management System as a whole. It also identifies internal data
stores of Login, supplier, payment, receiving stock, purchasing that must be
present in order for the inventory system to do its job, and shows the flow of data
between the various parts of inventory system. DFD level 1 provides a more
detailed breakout of pieces of the 1st level DFD. You will highlight the main
functionalities of Inventory.

TOP-DOWN METHODOLOGY:
DEFINITION:
A top-down approach (also known as stepwise design and in some cases
used as a synonym of decomposition) is essentially the breaking down of a system
to gain insight into its compositional sub-systems in a reverse engineering
fashion. Top-down approach starts with a big picture.
ADVANTAGES:
• The advantage of this approach is that decisions can be made and
implemented very quickly.
• This is particularly important when time is limited.
• The other benefit of top-down project planning is that it helps align the
project goals with the organizations strategic goals as upper management
is giving the directions.
JUSTIFICATION:
Top-down inventory planning involves setting a sales and inventory plan
at a high classification level and pushing it down to a more detailed level-from
the top, down. The lowest level of classification that a plan is set to depends on
the company.
For example, a retailer who manages multiple categories across a women’s
business may set their sales and inventory plans at a very high-level tops, bottoms,
and accessories. If this company’s highest revenue driving category is bottoms,
they may set sales and inventory plans for that area at a deeper level classification
(pants, skirts, shorts etc).
SET OF PRINCIPLES THAT ARE FOLLOWED AS A TOP-DOWN
METHODOLGY IN INVENTORY MANAGEMENT:

1. Set Par Levels: Make inventory management easier by setting “Par levels”
for each of your products.
2. First in First Out(FIFO) is an important principle of inventory
management.
3. Manage relationship.
4. Contingency Planning.
5. Regular Auditing.
6. Prioritize with ABC.
7. Accurate Forecasting.
8. Consider Dropshipping.

FUNCTIONAL REQUIREMENTS
The System aims at providing an efficient interface to the user for managing of
inventory, it shall also provide the user varied options for managing the inventory
through various functions at hand. The ingredient levels are continuously
monitored based on their usage and are checked for the threshold levels in the
inventory and accordingly the user is alerted about low levels of certain
ingredients. The design is such that the user does not have to manually update the
inventory every time, the System does if for the user.
The System calculates and predicts the amount of usage for specific set days that
are pre-set by the user(admin) , it also alerts the user of an impending action to
order ingredients before the specific day set by the user. Therefore the user never
has to worry about manually calculating the estimated usage of the ingredients as
the System does it for the user.
The simple interface of the System has functions like adding a recipe, removing or
updating the recipe. It also extends to functions such as adding a vendor for an
ingredient, removing the vendor, checking threshold levels, processing orders,
altering processed orders etc.

NON-FUNCTIONAL REQUIREMENTS:
• USABILITY
• RELIABILITY
• PERFORMANCE
• SUPPORTABILITY
• PACKAGING
• IMPLEMENTATION
• INTERFACING

COGNITIVE DIMENSIONS:
ABSTRACTION:
What are the minimum and maximum level of abstraction exposed by the
notation? Abstraction is an important process of understanding and interpreting
design problems in architectural education.
Physical level: The lowest level of abstraction describes how a system actually
stores data. The physical level describes complex low-level data structures in
detail.
Logical level: The next higher level of abstraction describes what data the
database stores, and what relationships exist among those data. The logical level
thus describes an entire database in terms of a small number of relatively simple
structures.
VISCOCITY:
Are there in the notation any inherent barriers to change? How much effort is
required to make a change to a program expressed in the notation?

Input: old password, new password, confirm password

Process: student activates the function to change the password. The new password
and confirm password fields are entered. If they match, the old password will be
updated with the new one.
Output: Error or confirmation message will be display

CLOSENESS OF MAPPING:
How closely does the notation correspond to the problem world?
As the name specifies INVENTORY MANAGEMENT SYSTEM is a software
developed for managing various activities by the manager.
For the past few years the number of inventory systems are increasing rapidly.

Identification of the drawbacks of the existing system leads to the designing of

computerized system that will be compatible to the existing system with the
system Which is more user friendly and more GUI oriented. We can improve the
efficiency of the system, thus overcome the drawbacks of the existing system.

PROGRESSIVE EVALUTION:
How easy is it to evaluate and obtain feedback on an incomplete solution?
(1) Programme materials are detailed and complete
(2) Are they applicable and practical?
(3) Programme materials provides concept and ideas which are practical to be
obtained in working environments
(4) Programme conducted in reflected on case scenario and showing how it is
applied on real world situation.
PREMATURE COMMITMENT (AND ENFORCED LOOK AHEAD):
Early design-Early decision which is unavoidable, Measure that can be
applied to HCI designs, for our purposes, measure of the quality of the design
process, rather than of the design product.

DESIGN METHOD:
JSP diagram for input:
FOR PAYMENT DETAILS/SALES DETIALS:

COMBINED STRUCTURE DIAGRAM:

OUTPUT:
1.Food details.
2.Cancelling food and event.
3.Payments.
INPUTS:
1.Obtain date, item, quantity for the event and invention.
2.Debit card, credit card, Demand draft.
3.Reciept.
4.Reviews, reasons for the cancel of event.

CONVERTING PROGRAM TO TEXT

WITHOUT CONDITION(ITERATIVE):
LOOP
get date of the invention
get invention details
get invention type
get cancelling details
print the payment
print reviews and document it
print receipts
END LOOP

CONVERTING PROGRAM TO TEXT WITH

CONDITIONS:
LOOP
get date of the invention
get invention details
get invention type
CASE of type
wasted invention type;
END CASE
print the payment
print reviews
print receipts
END LOOP

ARCHITECTURE STYLE:
PIPES AND FILTERS ARCHITECTURE
In a pipe and filter each component has a set of inputs and a set of outputs.
A component reads stream of data on its input and produces streams of data on its
outputs. This is usually accomplished by applying a local transformation to the
input streams and computing incrementally, so that the output begins before input
is consumed. Hence components are termed filters. The connectors of this style
serve as conduits for the streams, transmitting outputs of one filter to input of
another. Hence the connectors are termed pipes.

JUSTIFICATION:
Among the important invariants of the style is the condition that filters must
be independent entities; in particular, they should not share state with other filters.
Another important invariant is that filters do not know the identity of their up
streams and down-stream filters. Their specification might restrict what appears
on the output pipes, but they may not identify the components at the ends of those
pipes. further-more, the correctness of the output of a pipe and filter network
should not depend on the order in which the filters perform their incremental
processing -although fair scheduling can be assumed.
Common specialization of this include pipelines, which resists the
topologies to linear sequences of filters; bounded pipes, which resists the amount
of data that can reside on a pipe; and typed pipes; which require that the data
passes between two filters have a well-defined type.
A degenerate case of a pipeline architecture occurs when each filter process
all of its input data as a single entity. In this case the architecture becomes a batch
sequential system. In these systems pipes no longer serve the function of
providing a stream of data and therefore are largely vestigial. Hence such systems
are best treated as instances of a separate architectural style.
The best-known example of pipe and filters architectures are programs
written in the UNIX shell. Unix supports this style by providing a notation for
connecting components and by providing run time mechanism for implementing
pipes. As another well -known example, traditionally compilers have been viewed
as pipeline systems.

ADVANTAGES:

1.They support reuse

2.They are easy to maintain and enhance

3.They permit certain kinds of specialised analysis

UI DESIGN
FUNCTIONAL DIMENSIONS
EXTERNAL REQUIREMENTS: NO EXTERNAL EVENTS: In this system,
any external applications, users, I/O devices, constraints are not included.

CUSTOMIZABILITY:
MEDIUM: Admin alone can make changes in the database.
UI ADAPTABILITY:
LOCAL BEHAVIOR CHANGE: In this system there is a change in the user
interface behaviour, unless there are some new functionalities.

COMPUTER SYSTEM ARCHITECTURE:

MULTIPROCESSING: The system is having two or more processing unit which
shares main memory and peripheral in order to simultaneously process and save
program.

BASIC INTERACTIONS:
MENU: Menu Based Interaction System

NATURAL LANGUAGE: Voice Recognition System is used to tell the amount

of fuel required by the customer.

PORTABILITY:
MEDIUM: Administrator alone can make changes in the software.

CONCLUSION:
In any business, make it big or small, we must understand that taking good care
of our inventory is very important. If we as managers do not understand the
concept of good inventory management, we must learn to be familiar with it and
its applications. One of the reasons for the failure of a business is its inventory
management. There are many ways to fight failure, and we can start from here.
There is new technology that can help us maintain and supervise our inventory.
What we can do is learn, implement and evaluate our business. And you can start
with your INVENTORY!!!