Software Requirements Specification

Course Title: Software engineering

Course Code: CSE 320

Online Inventory Management System

Submitted to:
Dr.JIMMY SINGLA

Submitted by:
P.DINESH REDDY
K18XC
REG.NO:11809727
ROLL.NO:36(B)
1. Introduction
In software industry requirement engineering is one of the most important parts of software
engineering process, which one gives us the proper scenarios what the customers want,
analyzing their needs and checking the feasibility what they need, negotiating a reasonable
solution etc. In software industries, a software project begins when a business need is
identified. So the first step is we need to understand the customer needs. Figure out a rough
feasibility analysis, not only the customer’s need but also with the people who are apparently
involved with the introducing system. In this phase after interacting with our client “Sleek
Fashion Ltd.”, we get some requirements for an inventory management solution.

This paper will be more easeful after communicating with our client with their more
specific requirements. At the same time, in this paper we will focus on Inventory
management module. Again this paper is a partial submission; more detail will be
included as per communicating with the entire stakeholder’s.

1.1 Purpose

The purpose of this document is to present a detailed description of the Online

Inventory Management System. It will explain the purpose and features of the
system, the interfaces of the system, what the system will do, the constraints under
which it must operate and how the system will react to external stimuli.

In this document we will try introduce our stakeholders along with their respective
viewpoints, describe the existing problem, combining those various view points,
balancing those to reach an ultimate “theoretical” solution of the identified problems,
generating graphical reviews through unified modeling language (UML) to formulate the
problems and the proposed solution, the project scope and the project schedule. Next
we present the solution including system analysis, the deviation between final and initial
design, the function of our Inventory management system and testing plan. Finally we
evaluate our work on different aspects, present areas of improvement and conclusion.

1.2 Scope
The outcome of the project would be automated inventory management service .The software
will have all common features and functionalities along with some other special facilities.

 To provide user efficient working environment.


 User friendly interface for the target stakeholders.

 Proper monitoring facility for the authority.

 Easy maintenance and administration.

 Ensure high level of security.
 This system will help in tracking records so that past records can be verified through them
and one can make decisions based on the past records. This system will complete the
work in a very less time resulting in less time consumption and high level of efficiency.

1.3 Glossary

Key Terms Definition

RMG Ready Made Garments

Inventory Inventory means a list compiled for some formal purpose

Production Who guide and supervise production work.

Controller

QC Quality Control

IIS Internet Information System

SRS Software Requirement Specification

DFD Data Flow Diagram

PQ Production Controller



1.5 Overview

The next chapter is identifying stakeholders. In this chapter gives an over view who are
directly or indirectly depend on the developing system and what is their point of view.

The next chapter, the General Description section, of this document gives an overview
of the functionality of the product. It describes the informal requirements and is used to
establish a context for the technical requirements specification in the next chapter.




The Forth chapter, Requirements Specification section, of this document is written
primarily for the developers and describes in technical terms the details of the
functionality of the product.

The fifth chapter, Analysis model section. In this section of this document there are some
model diagrams. List of all these analysis models used in developing specific requirements .

All the sections of the document describe the same software product in its entirety,

2. Stakeholders
The stakeholders of the software project are those people or positions who are
directly or indirectly affected or effected by the project. The stakeholders and users
who are most immediately involved in an Inventory management system can be
divided in to four groups, they are:

Executives and upper management.

Production Controller.
Production supervisor.
The root level workers.
System developers.
Different Stakeholders achieve different benefits form a software system. Consequently
each of them has a different point of view. So we have to recognize the requirements from
multiple view point. For this Inventory management system point of view of stakeholders is:

  Executives and upper management beholds the people who are concerned with
company management and company’s financial states. They always deal
with the profitability and increasing production unit. So their view about the
 system is how to utilize the system to gain highest profit.
 Production controller is the people who supervise a part of a production unit.
They will interact with our system to input the data of their subordinate
workers. Their view point would be to input that information without any kind
of difficulties and maintain the private accounts of each worker

  The production supervisors are the people who act as the subordinates of the
production controllers, and they must have the real interactions with the root
operation. This is not necessary that every supervisor will have distinguished
areas to work with; there can be more than one supervisor to supervise a
 single activity, when it’s a larger one.
The supervisors are responsible to check the given input and the outcomes they
managed to produce. As these information are required for the operation of our
system, production supervisors are identified as one vital stakeholder. 

  One of the indirect stakeholders of our proposed system is the root level workers of
RMG sector, who use to do the primary level jobs of cutting, printing, and
combing all the parts together, or any other jobs for example. As because of
our limitation of resources, all the workers won’t use our system frequently.
But, for occasional possibilities, some of them will use his system, and their
illiteracy must be considered by the system developers.

2.3 Collaboration

As information from multiple viewpoints is collected, emerging requirements may be

inconsistent or may conflict with one another. So considering the scope of feasibility,
we have collaborated the following list of requirements from multiple viewpoints.
The extracted ideas gathered from the inventory department are:

 Online status of item quantity in terms of on-hand, on-hand available,

reserved, ordered, to order, rejected, defective and rework able quantities.
  Complete excise functionality and generation of excise registers.
  Quality Control based on QC parameters.
  Physical verification of stock.
  Purchasing and subcontracting.
  Accounting – inventory synchronization.
  Update delay notification.
 Keep Track of partial Production.
  All Financial transactions related to production.
.
The next steps of this analysis are analyzing credibility and go/ no- go decision making.
For these, this team needs more data to be analyzed and communicating with the client.
We hope that we will be able to submit the full Functioning paper within a short time.

3. General Description
3.1 Product Perspective
In this modern world of commercialization, garments business has been established
as one of the flourishing in Bangladesh. It has been one of the most flourishing
export sectors for our country, as we have told in background. Now, our project is
concerned with this sector. This is a huge field to cover, as hundreds of manageable
aspects can be found to maintain the highest productivity of textile manufacturing.
We choose the inventory management as our preferred field to work.

To instantiate, this can be specified as a b2b system, from producers to abroad or home
dealers through some intermediate business nodes. The important deals that our RMG
sector are mostly from abroad interests, as stated above. And our goal would be facilitate
this whole process, from collecting raw materials to the finished product shipment.

Unlike the old days, RMG sector of Bangladesh has been implementing a variety of
management software, in order to enhance the productivity, and to satisfy the customers’
needs. As these deals are very sensitive to handle, and there are a lot of variables that must
be maintained, the need of online interaction between the buyer and the seller, or even
seller to seller, is a must, and can play a dramatic influence on these deals.
As the whole process has multiple steps to the way to finished goods, a single delay
in a single step can cause delay in the shipment schedule, suppose our delay in
cutting can demolish the required time structure, which can also cause financial
damage and bad business reputation.

The existing systems have been using not for so long, and the maturity level of software
industry in our country is still very low. So, the systems which are being used in recent
days in the garments industry do have a lot of bugs, functional dependencies and design
constraints. Besides, there is still a lacking of a complete solution for managing
garments which is yet to be made. And we have to say, after studying, we find that
majority of the garment industry doesn’t use any automated management system, where
a large amount of problems in manual management can be solved in automated system.

The thing is missing all through and which we have been planning to introduce in these
kind of usual management system, is online interface to control the system. Internet has
been a pivotal determiner in every aspects life. We are proposing to introduce internet
controlling module of this system, so that the authority of our client can monitor and
manipulate the system, as well as the database through the internet.
At the same time, there are technologies being used to manage payroll,
appointments, inventory, and in many other purposes. But as our major concerns will
be inventory oriented, we will focus the most on that.

3.2 Current System Analysis

Figure 1: Current System.

The given diagram is a scenario of current system. In the present system, when the
administrator sealed the production order then the people related to the production,
specially PQ ,administrator’s make the total production planning, and according to the
plan the make a check sheet. According to the production planning total production work
is divided in to partial productions. These partial productions are the part of total
production. Combining this entire partial production element total production take place.

But the fact is that in each stage of this partial production face production loses
because of manual updating system. They cannot follow the check sheet properly.
So they cannot deliver their shipment with in due date.

So our client wants a system which can provide automated updating system,
accurate calculation of produced goods, provide proper stock information, send
notification if the shipment won’t take place on due date, keep track of partial
production, and all Financial transactions related to production.
3.3 Product Functions
Inventory Management System must be designed to meet the dictates of the
marketplace and support the company's strategic plan. Along with the inventory system
Garment industries need some more special attributes. The Software’s for Garment are
specially made for managing the various steps in order processing of garments
manufacturing process. This software is modular in design and is web enabled for
remote access as well as intranet usage without the need to install in every machine.

Inventory Management System has some features which are badly needed for a
complete Inventory system of Garment industries. So the features are,

  Web based interface

  User based Login - password based authentication for data protection.
 Dynamic Modular structure – Each and every section related to a
production has separate menus.
  Manage master details of buyer, supplier and vendor.
  Job Work tracking.
  Raw material tracking.
  Shipment tracking.
  Product category and product stock information with value.
  Reports include purchase, issues, stocks & categories.
  Customized package
  Notification System in case of any process delay.
 Check sheet automation.

These features are primary requirement of our client for this inventory management
system. This feature list will change in terms of client demand

3.4 Potential User of the of the System

There are two groups of users in our system. They are the production controller and
the system maintenance administrators. They have different authorities in our
system which is shown as follows;
Production Controller: They are the Controller of the production in each and every
section related to total production. They can insert the detail product information
which is completed. Besides, they are able to view order sheet and sample sheet to
keep their production accurate. But their authentication domain is limited between
their field, which can be exemplified as the production controller who is in charge of
cutting, will not have the access to the information about payroll or customers.
Administrator: They are authorized staffs to control the system. They are assigned
with different level of authority to control different parts of the system like inventory
and administrators. In addition, administrators are responsible to maintain database.
3.5 User Characteristics
The users of the software are classified into two categories – Registered user and
unregistered user.

Both users will be able to visit the homepage of the website but only the registered
user is allowed to give input in the system. To work through the system one user
should go through some fixed steps-

  First of all the user should be registered.

 The separate production module will be presented to the user as
a catalog for viewing.
 The user can browse through the categories to choose the
 module they desire.
 The user can input partially complete production quantity of the
total production.
 Finally the product will be delivered within a fixed and trusted time
 period to the next production module.
 And the process will continue until the shipment is completed

3.6 Assumptions and Dependencies

After completing our study about inventory and inventory management system, we thought
that, our Inventory management software will be ideal one in terms of garments industries of
our country. According to our view that inventory system will Contain module like:
  Information of different products category
  Available stock
  Price of different items
  transaction details
  One can also extract any reports relating to purchase and Sale.
  The inventory management application will have all the categories,
 Subcategories, items, Stock details and reports.

The administrator of this inventory system will have right to create product, add items
delete items etc. The application will provide all information of the products. The
category will be tagged with subcategory. Again the subcategories are tagged with
different items in the respective category and rate of the item. Each item will have a
specific bar code. The rates will be tagged to the bar code.

Using these functions the user can:

  Add items to inventory
  Edit items in inventory
 Add an action for an item

The application will also help to generate reports to get latest update on

 Master Entry
  Purchase order entry
  Receive entry
  Delivery entry
 Report

This inventory system also has some dependencies like

If data’s are inserted it cannot be deleted except
administrator User can insert a data but can’t delete
If data’s are not inserted, user cannot view report.

4. Requirement Analysis
Requirement Analysis presents the requirement specification, software and
hardware requirements for both system developers and system users, process
model and data model. In this section we specify the External Interface
Requirements, functional and nonfunctional requirements of the system.

4.1 External Interface Requirements

4.1.1 User Interfaces

User interface is one of the most important elements in any software. Most of the
software’s are used by non- technical persons. So they always seek of user friendly
environment in their system. And the user interface makes the system more familiar to its
user. For our system we do not design an user interface yet. But the process is going on.
4.1.2 Hardware Interfaces
In the current version of the software, it will have no special hardware interface
with other external systems. It will run in a general-purpose computer system
with general-purpose hardware and software.
4.1.3 Software Interfaces
The Current version of this system will be built on the following software:

Server:
  Internet Information system
  MsSQL server 2008.
 MVC 3.
Client:
  JavaScript.
  OpenSSL.
 JavaScript (synchronous/asynchronous) Enable Browser.
4.1.4 Communications Interfaces
All sorts of communications between server and client programs will be using ADO.NET
(ActiveX Data Objects for .NET) is a set of computer software components that programmers
Online Inventory Management System

can use to access data and data services. It is a part of the base class library that is
included with the Microsoft .NET Framework. It is commonly used by programmers to
access and modify data stored in relational database systems, though it can also access
data in non-relational sources and the messaging will be done by XML format.

4.2 Functional Requirements

Functional requirements define the functions that are requested by our stakeholders
Different functions are needed by different users of the system. Different administrators have
authority to maintain the system. The system specifies the authority of the administrator. The
administrator has got control over the database of the system. S/He can make changes to
update the total inventory system, and the update will be carried out dynamically.

4.2.1 General functional requirements:

 Garment production is combination of different partial production. To keep track

 of those partial production there will some modules in the system those are,
  Sketch Submission: In the garment manufacturing the first step is
designing the sketch for the dresses that have to be prepared. That
sketch contains all sort of information related to the product. So in the
time of production work this sketch is followed very strictly. Our client
wants functionality in the system that the administrator can submit a
sketch in the system according to their buyer that can available to all the
other users of the system. And this sketch will help the administrator to
 prepare a well-balanced check sheet for the production.
Production Pattern: The pattern design is taken for creating the
production patterns according to the sketch design. The production
pattern is one which will be used for huge production of garments. The
pattern maker makes the patterns on standard pattern making paper.
But our client wants a module that will keep all the production
pattern according to their buyer name.
  Spreading: With the help of spreading machines, fabric is stacked on
one another in reaches or lays that may go over 100 ft. Long and
hundreds of plies (fabric pieces) thick. But our system will
calculate the amount of fabric pieces to balance it with the check
 sheet to get profitable production.
 Cutting: Cutting the clothes to the desired sizes is a massively
 important job in RMG business.
  Sorting: Sorting the inventory to increase the productivity is challenge,
which must be overcome to ensure the best management of the
company. The sorter sorts the patterns according to size and
 design and makes bundles of them.
  Sewing: There are sewing stations for sewing different parts of the cut
pieces. In this workplace, there are many operators who perform
a single operation. One operator may make only straight seams,
while another may make sleeve insets.
  Finishing.
 Packing.
These modules contain the database of every worker and supervisor accounts
created, as well as the amount of resources, raw materials and other facilities
received from the authority, and their outcomes must be posted in a regular basis by
the person responsible to handle a specific module, the controller, which is noted in
the functional requirements for controllers below.
  An effective database to store important data of every deal.
  Every module will have separated record for all the transactions occur.
  Limited external accessibility, between a company or between a selected group.
 Limited internal accessibility, one module can be maintained and
manipulated by one person or one group of responsible employees.

4.2.2 Functional Requirements for Production Controller

 Login.

 Browse desired modules.

 Browse desired supervisor portfolio.

 Notify the system about the module requirements.

 Input product quantity after compiled.

 Distribute requirements between the production supervisors.

 Supervise inter-work station combination.

 View production details with delivery date.

 Browse through different production areas.

 Balancing the check sheet.

4.2.3 Functional Requirements for Production Supervisor

 Login.

 Get update from the controller.

 Setting the goal of the group and updating it on the system.

 Input the worker-to-worker data.

 Supervise own worker group performance.

 Notify the dependent working group supervisors through the system.

 Balancing the group input and output.

 Submitting the group balance sheet to the responsible controller.
4.2.4 Functional Requirements for Administrator

 Login.

 Accessibility to the whole system.

 Monitoring the total system as well as the database.

 Giving the total goal of a deal as the input.

 Clarifying the resources.

 Distributing the job segments to the controllers.

 Getting update information about the production.

 Getting update information about production delay.

 Getting update information about operation.

 Invoice information collection.

 Change settings

4.2.5 Quality Function Deployment

Quality function deployment is a method to transform user demands into design

quality, to deploy the functions forming quality, and to deploy methods for achieving
the design quality into subsystems and component parts, and ultimately to specific
elements of the manufacturing process.

QFD is designed to help planners focus on characteristics of a new or existing

product or service from the viewpoints of market segments, company, or technology-
development needs. The technique yields graphs and matrices.

QFD helps transform customer needs into engineering characteristics for a product
or service, prioritizing each product or service characteristic while simultaneously
setting development targets for product or service.

Quality Function Deployment (QFD) can be categorized by-

  Normal Requirements,
  Expected Requirements, and
 Exciting Requirements.

Here is the list of functional quality of our product,

4.2.5.1 Normal Requirements

Normal requirements are those requirements which stakeholders want to be available in

the System. The normal requirements of this proposed application are given below-

  The Inventory System must keep track of all compiled products or
resources records, which is expected to generate and must notify if resources
associated with the production is missing or order is incomplete.

 The system must have an option to produce check sheet.

 The system will perform authorization of users for security purposes. All
the users as well as the administrator must have to perform this part.

 All types of resources and price information related to any
production must have to store in the system.

 If any kind of change will occur, there will be an update option in the
system, using that administrator can change the existing information.

 Users can browse through different production module.

  The system must have the production plan making option.
  Every module will have separated record for all the compilations occur.
 Limited external accessibility, between companies or between
selected groups.
 Limited internal accessibility, one module can be maintained and
manipulated by one person or one group of responsible employees.
 Well-structured database to store inventory records.

4.2.5.2 Expected Requirements

Expected requirements are those requirements which stakeholders not mentioned to

be available in the system but he/she expects this will provide by the developer in
the system. The expected requirements for our proposed system are given below-

  The system will contain user friendly interface that will be designed in a
manner which implements functionalities that are easily accessible
by the users.

 The system must ensure database backups, which are as recent
and complete as possible
  Check sheet, production planning, and backup files should be in
readable file format or in crystal reports format.

 Order will be issued according to buyer name. This will help
authority to deal with their respected buyer.

4.2.5.3 Exciting Requirements

Exciting requirements are those requirements which stakeholders not actually want
but these requirements have to fulfill to make the system interesting. The exciting
requirements for our proposed system are given below-
 Production planning with investment and estimated profit will be
calculated through the system.

 Normal users and administrators have to login through different
login page which will ensure that, without administrator no one
can change any information of a production as well as the system.

 System has the notifying system for any kind of delay occurs in
the given period. But the system can notify the dependent working
group supervisors if the administrators need them.

 Administrators can distribute the job segments to the controllers.

4.3 Non-Functional Requirement

Non-functional Requirements of a system specify the performance, reliability,
availability, security, maintainability, portability of a system. So below there are a
short description each of those non-functional requirements.

4.3.1 Performance
Our proposed inventory management system will be used in Garment industry.
There are lot of internal and external operation which are inter-related with each
other for fruit full production. So the communication among each end system should
be tightly scheduled and the notification should be sent in timely manner.

4.3.2 Reliability
The production process in the garment industries is a combination of different
operations, which generate lots of data. These data lose can cause high damage to
a specific module as well as to the total process. So if the reliability is not confirmed,
this lacking will affect the production performance.
4.3.3 Availability
This system will be dedicated to a particular client. So the availability will be
restricted of this system.

4.3.4 Security
This system will deal with huge amount of data. So security is a prime issue of our
system. So the system should be secured from external interfere by providing
efficient security to the entire system.

4.3.5 Maintainability
Software maintenance in software engineering is the modification of a software
product after delivery to correct faults, to improve performance or other attributes.
Maintainability of software is categorized in four classes:
 Adaptive – dealing with changes and adapting in the software environment.

 Perfective – accommodating with new or changed user requirements which
concern functional enhancements to the software.

 Corrective – dealing with errors found and fixing it.

 Preventive – concerns activities aiming on increasing software maintainability
and prevent problems in the future.

So to maintain our system we will try to concentrate on this four classes.
4.3.5 Portability
Portability is the degree to which software running on one platform can easily be converted
to run on another. Portability is hard to quantify, because it is hard to predict on what other
platforms the software will be required to run. So to make our system portable we have to
use languages, operating systems and tools that are universally available and standardized.
4.3.7 Operational Requirement

The system can be viewed by open source Mozilla Firefox.

The system is supported by the IIS(Internet information’s system).

The team used MsSQL database to develop and maintain the

database management systems.

4.3.8 Design Constraints

When the project team is started to design the system, at that time the team always
tries to meet all the requirements of their client properly. But some time client’s make
the job difficult for the team to design the system by raising some last moment
requirements. This is considered as main constraints of designing a system.

Sometime clients do not give the proper information which is needed by the team to
design software, because of company policies. At that situation software project team
start their work without proper overview through the existing system to design new one.
5. Analysis Models
Analysis model is one of the most important parts of SRS. All the models give us
clear view of the developing system. In this section, here is the list of all analysis
models used in developing specific requirements of the current developing system.

 Scenario based model:


  Use Case Diagram.
  Activity Diagram.
 Swim lane Diagram.


 Flow Model

 Data Flow Diagram.


 Class Model:

  Class Diagram.
 CRC Diagram.


 Behavioral model:

  State transition Diagram.
  Sequence Diagram.
 Collaboration Diagram.

5.1 Scenario Based Model

5.1.1 Use Case diagram

In software and systems engineering , a use case is a list of steps, typically defining
interactions between a role or actor and a system, to achieve a goal. The actor can
be a human or an external system.
Initially after analyzing the requirements of our client we notify two potential actors in our
proposed system. But this can change any time when their requirements are modified.

So in this system normal users are production controllers. They can browse through
their production related modules. They can view all the production details, all the
partial production areas related to their production, can create check sheet according
to order quantity.

Figure 2: Use Case Diagram

On the other hand admin can change system settings, update operation information,
Update production information etc.

5.1.2 Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control.
 Figure 3: Activity Diagram.

If we consider the given activity diagram, it will easier for us to find out step-by step
operational workflows of total system. When the process starts it will allow a user to
select his/her own authentication. If the user logged in as an Administrator, the user
has the authority to select operation between change settings of the working module
and update information of the production.

On the other hand if the user logged in as a production controller, after valid authentication
the production controller can give input in the system to ensure the partial production of the
total production. In any state of the production if the delay is occurred, production controller
can notify administration about the delay to handle shipment related issues.
5.2 Flow model
5.2.1 Data flow diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modeling its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be
used for the visualization of data processing .

A DFD shows what kinds of data will be input to and output from the system, where
the data will come from and go to, and where the data will be stored. It does not
show information about the timing of processes, or information about whether
processes will operate in sequence or in parallel

Figure 5: Data Flow Diagram (Level 0)

Data flow diagram (level 0):

DFD level 0 , is the representation of the system which can only shows the inputs and outputs of
the system without dealing with any function and file or database issue. In the given figure this is
the data flow diagram (Level 0) for our proposed inventory management system. Control panel
and the planning is two input entity which can give data command to the system, all the inputs
will process in the system and the outputs will view in the display panel or as notification. And the
system also can produce check sheet according to given planning.
 Figure 6: Data Flow Diagram (Level 1)

Data flow diagram (Level 1):

DFD level 1, is the representation of the system which can visualize the relation
among the functions and the file or database with the inputs and outputs. Control
panel and planning entity can give input command to the system, which can process
by some functions in this system like interact with user, configure, and update input,
display status. There is a database related with configure function which one can
modify production information. And display status, notification, check sheet can
produce output depend on all the functions which configure inputs.
5.3 Class Model
5.3.1Class Diagram
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by showing the system's
classes, their attributes, operations or methods, and the relationships among the classes.

Figure 7: Class Diagram

In the above exposed diagram ‘Module’ is the parent class which has two child
classes ‘Administrator’ and ‘Production Controller’. Order Class deals with all the
steps related to order and maintained by administrator. ‘Store ‘and ‘Shipment’ class
maintained by production controller.
5.3.2 Class Responsibility Collaboration Diagram

Figure 8: CRC Diagram

A Class Responsibility Collaborator (CRC) model is a collection of standard index

cards that have been divided into three sections,

Section 1: A class represents a collection of similar objects.

Section 2: A responsibility is something that a class knows or does.

Section 3: A collaborator is another class that a class interacts with.

5.4.2 Sequence Diagram

Figure 10: Sequence Diagram

A sequence diagram in a Unified Modeling Language (UML) is a kind of interaction

diagram that shows how processes operate with one another and in what order. It is
a construct of our proposed system’s Sequence Chart. A sequence diagram shows
object interactions arranged in time sequence. It depicts the objects and classes
involved in the scenario and the sequence of Command exchanged between the
objects needed to carry out the functionality of the scenario.
5.4.3 Collaboration Diagram

Figure 11: Collaboration Diagram

Collaboration diagrams belong to a group of UML diagrams called Interaction

Diagrams. Collaboration diagrams, like Sequence Diagrams, show how objects
interact over the course of time. However, instead of showing the sequence of
events by the layout on the diagram, collaboration diagrams show the sequence by
numbering the Commands on the diagram. This makes it easier to show how the
objects are linked together, but harder to see the sequence at a glance.