Analysis of VideoRentOZ: Requirements, Domain, and System Design

This assignment presents a detailed analysis of the VideoRentOZ case study, focusing on requirements gathering, domain analysis, and system design. The document begins with requirement gathering from the owner's perspective, followed by domain analysis, including domain definitions and scopes, as well as a domain dictionary. Behavioral modeling is then explored through stakeholders, actors, use cases (register membership, rent video, buy item), and use case diagrams. Furthermore, the assignment delves into structural and dynamic modeling, including grammatical objects, class diagrams (customer, payment, rental item, local store, online portal, supplier, category, staff), and their respective attributes and operations. Finally, the assignment showcases the relationships between different elements of the system to comprehensively capture the business logic and functional requirements of VideoRentOZ.

I. Requirement Gathering
1. Owner view.
Assumption.
Customer is registered in both stores.
Customer pays deposit as security while renting an item.
II. Domain Analysis
Step 1. The table below showing domain definitions and its domain scope.
VideoRentOZ
Domain Scope
Domain Scope Outline
Customer  Customer buys

Sale item  Items are available
Local Store  Store holds items
Online portal  Store hold items for online transactions
Rental item  Items are available for buying
Catalogue item  Catalogue has items
Supplier  Supplies item to company
Product  Products are available
Staff  Staff works on order
manager  Manages staffs
Step 2.
VideoRentOZ
Domain Dictionary
Name Type Description
Customer role Buy or rent item
Sale item process Supplier sale item
Local store role Stores products
Online store role Display products on line
Renting
item
process Customer rents item
Register process Customer register both on line and local store
payment process Payment is made on bought product
Manager role Managers staff
staff role Works in company
Membership
card
Business rule During registration membership card is issued
Payment
mode
Business rule Pay via prepay card or gift card
sale object Product being sold
contract object Contract between buyer and company
III. Behavioral Modeling

1.
VideoRentOZ
Stakeholders & Actors
Name Description
Customer Person who buys and rent items
staff. Are employees of Video RentOz
Alex Owns of VideoRentoz
Manager An individual who is in charge ofstaff
suppliers An individual who sales product to VideoRentOz
2. Buying ,renting and registration
3.
VideoRentOZ
VideoRentOZ Management: Use Cases Summary
ID Name Description Actors
10
0 Register membership Customer registers on online portal or on
local store and membership card is
issued
custom
er
11
0 Rent video Customer need to rent item from
company
custom
er
Buy item. Customer need to buy item from
company
custom
er
17
0
Check item Staff checks on item if it is available on
portal or local store
staff
Pay Customer makes payment for item custom
er
Works Customer works on order staff
4.
Use Case: Register membership
ID: 102
Scope: Register membership

Priority: 10/10
Summary: Customer registers on portal or local store and a card is
issue
Primary Actor: Customer
Supporting
Actors:
staff
Stakeholders: customer, owner and staff
Generalization: Renting item on portal or local store
Include: Product must be paid first before ordering.
Extend: Payment uses both gift cards and prepaid cards
Precondition: Customer not yet register and has no membership
Trigger: Customer wants to register
Normal Flow: Customer visit online portal or local store to register.
Customer enter details.
Customer gets membership card
Customer buys or rents item
Sub-Flows ……………………………………………………………..
Alternate
Flow/
Exceptions:
Online portal is down
Customer not registered
No membership cards
Products out of store.
Post-
Condition:
Customer already registered and has membership card
Non-
Behavioral
Requirements:
……………………………………………………………..
Open Issues: new customers need to register
customer lacks enough money.
Source: ……… Case Study – Video Rent OZ
…………………………………………………..
Author: ……………………………………………………………..
Revision &
Date
……………………………………………………………..
Use Case: Rent Video
ID: 103
Scope: Rent video
Priority: 10/10

Summary: Customer rents video from company.
Primary Actor: Customer.
Supporting
Actors:
staff and suppliers
Stakeholders: customer, owner ,supplier and staff
Generalization: Catalogue item,rental item and sale item all are products
Include:
Extend: Item has different categories
Precondition: video not yet rented
Trigger: customer wants to rent video
Normal Flow: Customer order video
Customer pays deposit for video
Sub-Flows ……………………………………………………………..
Alternate
Flow/
Exceptions:
Video are not available in store
Customer has no deposit to pay
Post-
Condition:
video returned and video rented
Non-
Behavioral
Requirements:
……………………………………………………………..
Open Issues: Customer needs more video to rent
Source: …… Case Study – Video Rent OZ
………………………………………………………..
Author: ……………………………………………………………..
Revision &
Date
……………………………………………………………..
5.

6.

IV. Structural and Dynamic Modeling
1.
Grammatical
Objects
Class Comments
contract Item ………………………………………….
Credit card Payment ………………………………………….
Gift card payment ………………………………………….
2.
Class Description Responsibilities Use Case
customer customer buys item To buy buy
payment customer makes
payment
payment made pay
Rent item Customer rents item Item rented rent
category Category belongs to
rent item
Belongs to item
staff Staff works on item To check and works on
item
Checks and
works
supplier Supplier supplies item To supply supplying
Local store Local store holds item To hold item stores
Online portal Online portal holds
item
To hold item records
3.
CLASS CUSTOMER
ATTRIBUTES
Attribute Collaborators
name String it is private
email email it is private
Phone number Integer it is private
OPERATIONS
Operation Collaborators
registering It is public and void
Makespayment It is public and void

Renting It is public and void
BuyingItem It is public and void
CLASS PAYMENT
ATTRIBUTES
Attribute Collaborators
name string and private
date it is date and private
cost Long and private
OPERATIONS
Operation Collaborators
Payment it is public and void
CLASS RENTAL ITEM
ATTRIBUTES
Attribute Collaborators
name String it is private
date Date it is private
cost Long it is private
Item status String it is private
ItemId String it is private
Cost Long it is private
Category String it is private
OPERATIONS
Operation Collaborators
IsssuingItem it is public and it is void
Returning item it is public and void
Rentingitem It is public and void
CLASS Local Store
ATTRIBUTES
Attribute Collaborators
name string it is private
storeId string it is private

Location Location it is private
OPERATIONS
Operation Collaborators
registering it is public and void
CLASS ONLINE PORTAL
ATTRIBUTES
Attribute Collaborators
name string and private
portalId string and private
location String and private
category String and private
OPERATIONS
Operation Collaborators
registering it is public and void
CLASS SUPPLIER
ATTRIBUTES
Attribute Collaborators
name string and private
email email and private
contacts Interger and private
Supplier id String
OPERATIONS
Operation Collaborators
Supplying public and return items
CLASS CATEGORY
ATTRIBUTES
Attribute Collaborators
name string and private
price long and private
CategoryId Private and string
Rating It is private and string
OPERATIONS
Operation Collaborators
Renting item it is string and public
CLASS STAFF
ATTRIBUTES
Attribute Collaborators
name

email
jobID String and private
position String and private
OPERATIONS
Operation Collaborators
working onItem it is public and void
CheckingItem Public and void
4.
5.

Reference