SOFTWARE REQUIREMENT

FOR
VENDING MACHINE
SPECIFICATION
COMPONENT SYSTEM

VERSION 1 APPROVED
PREPARED BY NURSYAFIRA, AZRUL IKHWAN AND
IFFAH AFIQAH
23 NOVEMBER 2016

1. INTRODUCTION
1.1 PURPOSE

The purpose of this document is to specify and identify the requirement from the user or
stakeholder for the control system for the Vending Machine Control system for the Vimto Soft
Drink Company. This document will describe the required system facilities (functional
requirement) and system performance characteristics (non-functional requirement).

This document will focus on how to establish the requirements for the system and
simulator, to determine the scope of the systems needed to meet the user requirements, to
identify the system capacity and the requirements for future expansion and to provide the basis
for the development of the system.

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 1

1.2 SCOPE

1.2.1 : Software System

The function of this system will be control of the operation of the vending machine. In particular
it will:

a. Control interaction with the customer.

b. Display information to carry out the instructions of the maintainer.

1.2.2 : Software Documentation

Complete and easily understood documentation of the system will be provided to aid in future
maintenance of the system. In particular for the following deliverables will be produced:

a. The Use-Case Diagram description.

b. The Sequence Diagram description.
c. The Class Diagram description.

1.3 DESCRIPTIONS

TERMS DESCRIPTION
Customer The public who will use the VMCS machine.
Maintainer Someone who has been entrusted with a simple set of
instruction to use/maintain the system.
Controller Overall simulation of the VMCS background activity.

1.4 REFERENCES

IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications.

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 2

 2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVES

The Vimto Soft Drink Company operates and maintains a large number of automatic soft
drinks dispenser at various its throughout Singapore and it has decided to invest in a
computerized control system, which will be installed in a new range of soft drinks vending
machines. This machine will sell several different brands of drinks, which can retail at different
prices.

This VMCS shall duplicate the functionality of the existing system and add new
functionality made feasible to the new technology. It also will allow the vending machine
maintainer to check ad remove cash, and to check the number of drinks cans held.

2.2 PRODUCT FUNCTIONS

Product functions to be implemented:

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 3

 a. Acceptance/rejection and cumulative totaling of money input by customer.
b. Dispensation of the selected drinks to the customer.
c. Indication if selected brands are unavailable.
d. Dispensation of change to customer.
e. Display of requested information to the vending machine maintainer.
f. Injection of new drink price to the vending machine by the maintainer.
g. Transfer of cash held within machine to the maintainer.
h. Simulation of the customer/maintainer interface and the interface with the vending
machine machinery.

2.3 SYSTEM INTERFACES

The system shall interface with:

a. The mechanical drinks can dispense mechanism within the vending machine.
b. The coin checking, storage and dispensing mechanism within the vending machine.
c. The door locking/unlocking mechanism within the vending machine.

2.3 USER CHARACTERISTIC

USER CHARACTERISTIC
Customer The person who would be members of the general public.
Maintainer The person who will have a set of simple instructions to use
with the system.
Controller The overall simulation of the VMCS

2.4 CONSTRAINTS

The system is not subject to any general constraint.

2.5 ASSUMPTION AND DEPENDENCIES

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 4

 3. SPECIFIC REQUIREMENT

3.1 EXTERNAL INTERFACES REQUIREMENT

3.1.1 User Interfaces
a. The VMCS will communicate with the customer panel. This will be simulated
by the Simulator Software package.
b. The VMCS will communicate with the maintainer via the maintainer control
panel. This will be simulated by the Simulator Software.
c. The VMCS simulation will be controlled by the simulator control panel.
d. Data for the VMCS simulation will be input via the vending machine
simulation panel.
3.1.2 Hardware Interfaces
a. The VMCS shall interface to the coin storage mechanisms by a simple
interface where commands and data will be exchanged in simple 16-bit words.
b. The VMCS shall interface to the drinks can storage and dispenser mechanisms
by a simple interface where commands and data will be exchange in simple
16-bit words.
c. The VMCS shall interface to the customer control panel by a simple interface
where commands and messages will be exchanged in simple 16-bit words.
3.1.3 Software Interfaces

Neither the VMCS software nor the simulator software shall interface with other software
packages.

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 5

3.2 FUNCTIONAL REQUIREMENT
3.2.1 Customer

BRIEF DESCRIPTION

This use case provides the capability to buy a drink.

CHARACTERISTIC OF ACTIVATION

This use case is activated by the customer.

PRE-CONDITION

The VMCS simulation for customer panel has been activated.

BASIC FLOWS

1. The use case begins when the customer choose the brand of the drink can.
2. The customer need to enter the coin that is required to buy a drink (SRS_REQ_101)
3. The system shall validate the inserted coin (SRS_REQ_102)
a. [A1:Coin Valid]

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 6

 b. [A2:Coin Invalid]
4. The system shall monitor the amount of accepted money (SRS_REQ_103)
5. The system shall display the amount of money that has been inserted
(SRS_REQ_104)
6. The system shall determine the total amount of the money has been
inserted(SRS_REQ_105)[A3:Money Not Enough]
7. The system shall determine any change should be sent at the end of transaction
(SRS_REQ_106)[R1:Change Calculation]
a. [A4:Enough Change]
b. [A5:Not Enough Change]
8. The system shall dispense the appropriate drinks can. (SRS_REQ_107) [A6:Brand
Unavailable]
9. Use case ends.

ALTERNATIVE FLOWS

A1: Coin Valid

a. Accept the coins (SRS_REQ_108)

b. The use case continues.

A2: Coin Invalid

a. Reject the coins (SRS_REQ_109)

b. Indicate the rejection to the customer (SRS_REQ_110)
c. The use case continues.

A3: Money Not Enough

a. The system shall flash the message (SRS_REQ_111)[M1:Money Not Enough]

b. The system shall wait for the customer to insert the correct amount of the money
(SRS_REQ_112)
c. The use case continues.

A4: Enough Change

a. The appropriate change shall be the output(SRS_REQ_113)

b. The use case continues.

A5: Not Enough Change

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 7

a. The appropriate message shall be seen by the customer (SRS_REQ_114) [M2:Not
Enough Change]
b. The use case continues.

A6: Brand Unavailable

a. The system shall not respond (SRS_REQ_115)

b. The system shall wait for the customer to choose a valid drinks brand
(SRS_REQ_116)
c. The use case continues.

EXCEPTION FLOWS

Not Applicable

POST CONDITION

The drinks will be dispensed to customer

RULE(S)

R1: Change Calculation (SRS_REQ_117)

Change Money = Inserted Money The Price of The Drinks

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 8

3.2.2 MAINTAINER

BRIEF DESCRIPTION

This use case provides the capability to maintain the system.

CHARACTERISTIC OF ACTIVATION

This use case is activated by the maintainer.

PRE-CONDITION

The simulation has been activated

BASIC FLOW

1. The use cases begin when the maintainer panel has been activated.
2. The maintainer shall entered the password for authority (SRS_REQ_201)
3. The system shall validate the password (SRS_REQ_202) [A1:Invalid Password]
4. The system will unlock the door of the vending machine (SRS_REQ_203)
5. The VMCS shall not begin any transactions whilst the maintainer is operate it
(SRS_REQ_204)
6. The VMCS shall display the information of the VMCS to the maintainer
(SRS_REQ_205)
7. The system shall on request transfer all cash held within the vending machine to the
maintainer (SRS_REQ_206)
8. The maintainer be able to change :
a. The number of cans held by the machine (SRS_REQ_207)
b. The cash/change held by the machine (SRS_REQ_208)

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 9

9. The VMCS shall monitor the status of the cans held by the vending machine
(SRS_REQ_209)
10. The use cases ends.

ALTERNATE FLOWS

A1: Invalid Change

a. The system shall flash PASSWORD INVALID (SRS_REQ_210)

b. The maintainer need to enter the password again (SRS_REQ_211)
c. The use case continues.

EXCEPTION FLOWS

Not applicable

POST-CONDITION

The maintainer collects the money from the machines.

RULE

Not Applicable

SYSTEM MESSAGE

Not Applicable

3.2.3 CONTROLLER //k.i.v

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 10

 BRIEF DESCRIPTION

This use case provide the capability to start simulation and manage

3.3 PERFORMANCE REQUIREMENTS

There is no requirement on the performance on the system.

3.4 DESIGN CONSTRAINT

3.4.1 Methods

Object-oriented development (OOD) technique with UML notation shall be used to this
project.

3.5 SOFTWARE SYSTEM ATTRIBUTES

3.6 OTHER REQUIREMENTS

3.6.1 Reliability

The VMCS system shall have a mean time between failures of 1000 hours.
SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 11
3.6.2 Maintainability

The VMCS mean down time shall be 5 hours.

3.6.3 Availability

The VMCS shall operate from when the main power is switched on for the vending
machine, and it will close down if the main power is cut off. If the VMCS is in the
process of a transaction with the customer then it will not continue this transaction when
power is restored, nor will keep the record.

3.6.4 Security

Access to operate the functions available to the maintainer will be restricted by use of the
correct password.

3.6.5 Expandability

The number of drink brands may increase to 10 over a period of time.

3.6.6 Integrity

Once installed in the vending machine hardware, the VMCS software shall not be capable
of being changed.

SYSTEM REQUIREMENT SPECIFICATON | VERSION 1.0 12