Professional Documents
Culture Documents
Functionality:
• Show List
The lists of the categories available in the repository The
products in the selected category are also displayed.
• Update Inventory
Whenever products are purchased, the amount of
products sold will be deducted from the inventory levels.
When the inventory level of a product goes down the
minimum requirement, product name will be deleted from
the available list of products. It has to be updated again
by the administrator whenever the product is added to
the inventory.
Purchase Request Module
• Functionality:
• Viewing the list of categories of products.
• To make a request for buying a product of
desired quantity.
Billing Module
• Make Bill
A bill is generated for the purchased
product.
• Transaction Log
Records the list of transactions performed
Payment module
• Credit card Payment
If the payment is through the credit card,
then the card details will be send to the
bank and the amount will be collected
later.
• Talk time payment
If the payment is through service provider
then the amount of purchase will be
deducted from the user’s talk time.
SOFTWARE REQUIREMENTS
• SERVER
• Operating system ---- Windows XP
• Server Side Prog ---- java Servlets
• Web server ---- Apache tomcat 5.5
• Database ---- Oracle 8.0
• Client
• Operating system ---- Palm OS
• Blue Tooth Mobile ---- J2ME Wireless Toolkit
HARDWARE REQUIREMENTS
• Server
• PIII or higher processors
• 256 MB RAM
• 20 GB Hard Disk
• Client
• Bluetooth enabled mobile phone is sufficient
SI S
LY
N A
A
FUNCTIONAL REQUIREMENTS
MAINTAIN INVENTORY UPDATE INVENTORY
VIEW REPOSITORY
SELECTING CATEGORY
SELECTING PRODUCTS
BILLING
VENDING
MACHINE
USER
PRODUCT INFO
<<include>>
<<include>>
MAINT AIN REPOSIT ORY
PRODUCT INFOMATION
VENDING
UPDATE INVENTORY MACHINE
<<include>>
PURCHASE
<<extend>>
ALERT S
BILLING SYST EM
<<include>>
<<include>>
<<include>>
Select Product
<<include>>
<<include>>
buy product
SUB USE-CASE FOR VIEW REPOSITORY
getCategory
<<include>>
<<include>>
getProducts
ACTIVITY DIAGRAMS
• Activity diagrams are special case of the
state machine
• Activity diagrams provide a view of flows
of what is going inside the use cases or
among several classes
Ve nding M ac hine
Activity diagram Us er Serv ic e Pr ov ider TTP
Connect
Get
Categories
Select
category
Get
Products
Select
Product
[ Yes ]
Buy ?
[ Yes ]
Display Bill
Details [ No ]
W rong
Information ?
[ Credit Card ]
Payment
mode ?
Enter Pin Enter Card
[ Bank ]
number details
[ Yes ]
Valid Valid
account? details?
[ Yes ]
[ No ]
Receipt [ No ]
Collect
the Item
SEQUENCE DIAGRAMS
1: start interface()
2: select products()
5: check details()
7: validate details()
PURCHASE
: USER : purchase UI : PURCHASE
: view inventory : VENDING
MACHINE
1: start interface()
2: select category()
3: select product()
4: select payment m ode()
5: forward details()
6: forward details()
7: check validations()
8: validate()
1: start interface()
4: forward details()
6: forward results()
1: start interface()
4: forward details()
6: authenticate details()
7: forward results()
check account()
1..n
make transaction()
<<control class>>
vending machine
CNAME
BALANCE
SERVICE
PROVIDER PIN CATEGRO PNAME
Y
To CNAME
SIMN
O
PRODUC
Vie
T MNAM
ws E
CTYPE
COST
INTER EXPIRY
BUYS DATE
ACTS CARD
TYPE
CARDNO
TID CVVNO
CName
TMODE
BILLING
SYSTEM
MNAME CREDITCARD
BAMOUNT IN
AC TE
TS R
PNAM
TDATE E
List of data base tables identified
• Category
• Products
• Measurement
• Transaction
• Service provider
• Visa
• Transaction processing(ttp)
• vodaphone
Category table
Product table
Test Description: With the cell phone number and pin as the input, validate the user.
Pre Conditions: User should have a Valid Account with Service Provider
Result: Success
Product Available
Result: Success
User Validation
Test Description: With the credit card and cvv no. as the input, validate the user.
Result: Success
CONCLUSION
The following benefits can be observed with this system:
• Convenience and flexibility in the mobile payment
scheme.
• A reliable scheme with completely no manual interaction.
• Also the reports generated by the system can be helpful
in tracking the customer needs and maintaining the
correct inventory levels.
Moreover by implementing this system we gained a clear
understanding of project life cycle and the Bluetooth
technology.
LIMITATIONS
• This project of course has a broad range
but was implemented only for the vending
machine scenario.
• Also this project, as it is implemented
using Bluetooth technology, was
constrained to the distance of operation.
FUTURE ENHANCEMENTS
• This project can further be extended to a wide
range of products and categories.
• An example of the future enhancement is an
ATM machine where a user can make a
transaction through any bank card at a single
place.
• Implementation of project in Real Time
Environment
• Also it is possible to bring a variety of customers
under one roof with the help of this system.
a n Q
T h