Swinburne University INF20003: Indyflix Movie Rental System Report

This report provides a comprehensive analysis of the Indyflix movie rental business, based in Melbourne, Australia, which is looking to expand both digitally and physically. The report begins with an executive summary and an introduction to the company, its background, and its competitors, particularly in the context of the Australian entertainment industry. It details the current manual processes of the business, including customer interactions, movie ordering, and overdue management. The core of the report focuses on the functional and non-functional requirements of a new system, detailing website functionalities, administrator capabilities, and data structures. It includes a data dictionary, process descriptions, and system modeling through a context diagram, level-0 diagram, ER diagram, DFD fragments and an event list. The report references various academic sources to support its analysis and proposed solutions, aiming to modernize Indyflix's operations and improve customer service.

Executive summary
The report provides an overview of Indyflix movie rentals which are based out in Melbourne,
Australia. They currently have 5 stores and are looking to expand further both digitally and
physically. Although their business is based on an outdated model, they’re a growing profitable
business. This report talks about the problems they are facing with their current IT system and
how can it be overcome by developing a new system. As such, the report talks about the
business, it’s competitors and provides an overview of the problems faced by them. The report
would then present a proposed system with the help of process table, functional and non-
functional requirement list and diagrams.
Introduction
Indyflix is a Melbourne based company. Their core business in to movie rentals. Although their
business model is quite old and that such businesses who were popular in the 1990s has largely
been defunct, Indyflix is thriving and growing. This is because they are into the niche business of
loaning independent movie, music and gaming. Viewers who are bored from mainstream movies
and music and also those who are passionate about independent movies and music are the prime
customers of Indyflix. However, their business management system as well as their website is
quite limited technologically. It not only creates issues and problems in their day-to-day
business, but is also restricting them now that they are growing exponentially. As a result, they
wish to upgrade their business management system along with their website with modern
technologies and principles allowing them to grow further and also help their customers be
served better by them.
Company/Organization Background
Australia is one of the major earning sources for International movies including Hollywood and
Bollywood. This is also primarily because of the large expat community and cosmopolitan nature
of Australia. In 2017, Movies accounted for nearly 53.2% of the video rentals in Blu-Ray and
DVDs which increased by 3% from the previous year. According to Screen producers Australia,
Independent films employee hundreds of thousands of practitioners, producers, employees,
actors and member with an annual production activity amounting to 1.7 Billion AUD. It is
evident that feature films are a major part of the entertainment industry in Australia and also that
people are interested in Independent films.
Live TV currently is the major video-based entertainment channel in Australia. However, there is

a major undercurrent that shows consumers migrating to on-demand based subscription
providers in Australia. As a result, Live TV and Hollywood are not the mere competitors of
Indyflix, it is also the on-demand streaming services. These streaming services include YouTube,
YouTube Premium, Netflix, ABC iView, Stan, Amazon Prime and Foxtel. Apart from them
Quickflix is also a major video rental and on-demand streaming service provider based in
Australia. So, it’s evident that Indyflix has a lot of strong and powerful competitors. However,
the major advantage with Indyflix is that they are operating in a niche segment. This niche
segment is about curating movies from independent producers and filmmakers. Since they have
become a reputable brand in this segment, over a period of time, they will have strong brand
recognition and reputation for the same.
Current (Manual) Process
• Customer’s details are taken manually on a piece of paper from the customer and then
again fed into the system.
• The customer has to walk into the store, get his card validated in order to borrow a
movie. At the same time, the store assistant must check for the customer’s dues or any
other issues before lending the movie (Pomffyova and Bartkova, 2016).
• The overdue movies report is generated every day and the assistant has to call each
customer to notify them for the same.
• New movies are ordered from suppliers after creating a purchase order. Movies are also
monitored manually so that appropriate stocks are kept.
• If a movie is reserved for a customer and as and when it arrives, the customer is contacted
on their phone by an assistant.
Functional Requirements of the New system
Website
• Dynamic catalog of movies – Realtime and automatic updating of movies in stock.
• Search – Ability to search for movies.
• Review and Parental guidance – Ability to add parental guidance and review for movies
only if they own it.
• Profile – Online filling of form and creation of user profile (Ahmad, Belloir and Bruel,
2015).
• Notifications – Automatic notifications of movie due and unpaid amount dues.
• Shopping cart - Ability to add a movie to a shopping cart and place and order.
Administrator
• Automatic posting of customer details by customers or online-filing of customer details by
store administrators.
• Customer only needs to provide a short ID to get themselves validated or can use in-store

checkout to automatically check themselves out.
• Automatic generation of required reports (Jamshed, 2014).
• Automatic updation of inventory and sending of notification to the Suppliers.
• Centralized database system combining all stores and online website.
• Automatic reminders and notifications being sent to customers
• Ability to edit customer’s profile and ability to view their past orders and wish list.
Non-functional requirements
• The design and interaction of the website should be based on Nielsen design principles
and other golden rules of user interface design.
• The fonts and texts should be legible to both administrators and customers.
• The system should provide error reports and alert users making syntactical mistakes.
Documentation
Data dictionary
Logical data Data Dictionary for the following processes
Movie_Rent = customerID + customerContactNo + customerName + { movieID }
Return_Movie = Date_of_Return + Return_Time + {movieID}
(Tewary and Kosalge, 2013)
Data element description
DATA DICTIONARY – MOVE RENT
Field Name Caption Data Type Field
Size
Format
Movie_Rent Autonumber 6 000000
customerName First_Last Text 50 Identify movie
type and brand
customerID NumericID integer 6 000000
customerContactNo MobileNo Text 10 0000 0000 00
DATA DICTIONARY – RETURN MOVIE
Field Name Caption Data Type Field Size Format
Return_Date Date 10 dd/mm/yyyy

format/Text
Return_Time Time of day Time
format/Text
5 00:00 24hr time
Process description
Process Name Description
1.0 Register customer System receives a request for registration request
from the customer. It will then check whether the
customer already existing using contact email
information of the customer. Then, a newly generated
customerID is sent to the customer and updates the
customer data store with the profile details of new
customer (Muhairat ,2010).
2.0 Process loan System receives a request for loaning a movie. It will
take the customer ID and movieID from the
respective data stores. Then it will create a new loan
and update the loan details in the respective data
store.
3.0 Generate reminder At least 48-hours before the return data, system will
send the reminder to the customer via SMS/reminder
extracted from the “customer” data store.
4.0 Calculate overdue When system processes for a loan, the overdue is
calculated by extracting data through “loan” and
“customer” data store and same is sent to customer
using SMS/email.
5.0 Return loan System receives request for returning the loan,
attendant checks for overdue and asks user to make
payment. Then data is updated in “loan” and “movie”
data stores.
6.0 Purchase movie System receives request for purchasing a movie. Data
is extracted from customer; movie data stores and a
new purchase is updated in the “sale” data store.
7.0 Make Payment Customer sends payment data via credit card or cash

and same is updated in invoice data store.
8.0 Renewal System receives the request for loan. It extracts
customer details from customer and loan data to
check for overdue and same is then updated in “loan”
data store.
9.0 Generate report System receives request to generate report and
depending on the type of request, data is extracted
from respective data stores and report is processed.
10.0 Update inventory System receives request for updating the inventory of
movies. Supplier confirms the order and movie data is
extracted from “movie” data store and same is
updated with new copies of movie (Sunner and Bajaj,
2016).
Modelling for the proposed system
Context diagram
Level-0 diagram
(
ER diagram
References
Ahmad, M., Belloir, N. and Bruel, J. (2015). Modeling and verification of Functional and Non-
Functional Requirements of ambient Self-Adaptive Systems. Journal of Systems and Software,
107, pp.50-70.
Jamshed, S. (2014). Qualitative research method-interviewing and observation. Journal of Basic
and Clinical Pharmacy, 5(4), p.87.
Muhairat (2010). UML Diagrams Generator: A New CASE Tool to Construct the Use-Case and
Class Diagrams from an Event Table. Journal of Computer Science, 6(3), pp.253-260.
Pomffyova, M. and Bartkova, L. (2016). Take Advantage of Information Systems to Increase
Competitiveness in SMEs. Procedia - Social and Behavioral Sciences, 220, pp.346-354.
Sunner, D. and Bajaj, H. (2016). Classification of Functional and Non-functional Requirements
in Agile by Cluster Neuro-Genetic Approach. International Journal of Software Engineering and
Its Applications, 10(10), pp.129-138.

Tewary, A. and Kosalge, P. (2013). Implementing service oriented architecture - a case study.
International Journal of Business Information Systems, 14(2), p.164.
Appendix
DFD fragment
•
•
Event list
# EVENT
TYPE EVENT TRIGGER SOURCE USE CASE RESP
1 External Customer request for
registration Customer online
enquiry Customer Register
customer - Provi
custom
data
- Get
existin
of cust
-
Regist
confirm
- Custo
record
update
2 External Customer requests for
movie loan Request loan Customer Process loan - Provi
movie
- Get
custom
details
- Get m
details
- Conf
movie

3 Temporal Reminder of
return date
48-hrs before
return date
System Generate
reminder
- Creat
remind
report
4 External Calculation of
overdue
Return date is
approaching
system Calculate
overdue
- Calcu
5 External Customer
requests for
returning loan
Customer
creates online
enquiry
Customer Return loan - Calcu
overdu
6 External Customer
requests for
purchase
Customer
creates online
enquiry
Customer Purchase
movie
- Gets
custom
- Rece
movie
- Upda
movie
7 External Payment to
attendant
Purchase
movie
Customer Make Payment - Calcu
payme
8 External Customer
requests for
renewal
Customer
creates online
enquiry
Customer Renewal - Calcu
overdu
- Chec
reserva
reques
9 External Management
request for
request
Management
creates online
enquiry
Management Generate
report
- Rece
from
respect
store
- Provi
report
10 External Attendant
request to
update
inventory
Attendant gets
orders from
supplier
Attendant Update
inventory
- Rece
from m
data st
- Upda
movie
store