Movie Information System

Movie Store Information Management System 2019
UNITY UNIVERSITY
DEPARTMENT OF COMPUTER SCIENCE
Movie Store Information Management System
BY
UU OOSAD PROJECT TEAM
Sub to: Instructor Nigussie Teferi
Adama, Ethiopia 2019 G.C
Page | 1
ACKNOWLEDGMENT
First and almost we want to say thank you, the almighty God, who gave us the insight and
perseverance to accomplish this project. Then we want to thank our fantastic teacher Mr. Nigussie
Teferi for giving us this opportunity to familiarize practically with Object oriented system analysis
and design through this project. His guidance and suggestions were invaluable in the successful
completion of this project.
Finally, we are indebted to our classmate who’s technical and moral support throughout our stay
at a computer science department was of great help.
Page | 2
Table of Contents
Movie Store Information Management System .............................................................................................. 1
BY ................................................................................................................................................................. 1
CHAPTER ONE ...................................................................................................................................................... 5
1. Introduction: ................................................................................................................................................ 5
1.1 Background: ..................................................................................................................................... 5
1.2 Background of the Organization:..................................................................................................... 5
1.3 Statement of the Problem ............................................................................................................... 6
1.4 Objective of the Project ................................................................................................................... 6
1.5 Significance of the Project ............................................................................................................... 6
1.5.1 Beneficiary of the system ............................................................................................................ 7
1.6 Scope of the Project ........................................................................................................................ 7
1.7 Methodology ........................................................................................................................................... 8
1.7.1 Data Collection Methods ................................................................................................................. 8
1.8 System Development Approaches ...................................................................................................... 9
1.9 System Development Tools ................................................................................................................. 9
CHAPTER TWO ................................................................................................................................................... 10
2 Requirement Analysis ................................................................................................................................ 10
2.1 Overview of Proposed System............................................................................................................... 10
2.2 Functional Requirements: ..................................................................................................................... 10
Reports: ..................................................................................................................................................... 11
2.3 Non-functional Requirements: .............................................................................................................. 11
2.3.1 Performance requirement ................................................................................................................. 11
2.2.3 Hardware requirement...................................................................................................................... 11
2.2.3 Software requirement ....................................................................................................................... 12
CHAPTER THREE................................................................................................................................................. 13
3 SYSTEM DESIGN ......................................................................................................................................... 13
3.1 Use Case Diagram and Use Case Documentation ................................................................................. 13
3.1.1 Essential Use Case Diagram ............................................................................................................... 13
3.1.2 CRC Model ......................................................................................................................................... 14
3.1.3 System Use Case Diagram ................................................................................................................. 16
Page | 3
3.1.4 Use case Documentation ................................................................................................................... 17

3.2 Sequence Diagram ................................................................................................................................. 20
3.3 Activity Diagram .................................................................................................................................... 23
3.4 Class Diagram ........................................................................................................................................ 24
3.5 System User Interface Prototype .......................................................................................................... 25
Page | 4
CHAPTER ONE
1. Introduction:
1.1 Background:
Nowadays watching movie is the major entertaining thing. Peoples are spending lots of their
time watching TV-Shows, TV-Series, Documentary movies and so on. Because of that large
customer demand, movie-selling business is increasing in the cities. However, movie-selling
business is not just easy business. It requires a good capital, commitment, business ideas and
technology to provide the product as the demand requires.
In other side providing an excellent customer service to clients are the biggest challenge to
business owners. Customers does not just buy movies, also they require a quality customer
service. They want to make sure that they got a quality movie, and they need to know basic
information about the movie before watching or buying it.
In general, movie selling companies like internet shops are facing difficulties of
providing information about their selling product (Movie). Thus, A Movie Information System
is needed to handle this problem.
1.2 Background of the Organization:
FLINTWOOD INTERNET & MOVIES is a movie and internet shop, which is found in Addis
Ababa, Ethiopia, Bole Sub City Summit area. Four months’ age we developed a desktop
application to change the traditional system, however the application is failed to provide the
intended service for customers. Currently they are using a traditional system. This will cover
the key areas of the Shop. The details of the project are listed in the remaining document.
Page | 5
1.3 Statement of the Problem
Many movie sellers provide information about their selling movie in a various method. Most of the
techniques used are manually by printing a movie information like title, genre, and the poster in a
simple paper and by making a catalogue album. This can be seen widely in the companies who
don’t resell internet service for their customers. In other side, internet and movie shops provide
this information through a different technology-based technique like posting movie information on
social networks, Facebook, Telegram, Viber etc. but this requires more cost and time both in
customers and service providers in order to get/give the movie information.
Therefore, the purpose of this research is to design and implement an automated web-based movie
information system which provides movie information to customers, that requires a small budget &
simple to implement.
1.4 Objective of the Project

1.4.1 General Objectives
The general objective of this project is to develop and implement user-friendly web application
which mange movie information that provides information for clients and control system for shops
who is selling movies.
1.4.2 Specific Objectives

To achieve our general goal, we plan to perform the following specific operations.
 Develop a system that keep track of and forecasts the customer’s favorite movie.
 Develop a system that manages movies without requiring additional work like data entry
and sorting
 Produce reports, which facilitate top management decision.
 Design and implement a user interface for customers, employees and administrators.
 Design and implement a system to manage movie ordering process.
 Design and implement a system to manage fee collection process.
1.5 Significance of the Project
The proposed system provides different advantages to all users of the system. The first one is, it
retrieves movie information from the internet without the need of any data entry. The second
major advantage is that the system enables the customer to search for the movies that he desires
and gives a detail information about the movie. Moreover, it will allow the Administrator of the
shop to decide a systematic decision on the system.
Page | 6
1.5.1 Beneficiary of the system

For Organization
 Increase Profit.
 Minimize cost of paper, printing.
 Manages the income in more precise way.
 Increase goodwill.
For Customers
 It helps to minimize the waiting time during movie ordering.

 Gives accurate and reliable information about movies.
 Helps to get movies easily and in more flexible way.
 Recommends a movie that they like.
For Employees
 It helps to manage the Orders

 Facilitates fee collection.
 Avoids stress and gains satisfaction.
1.6 Scope of the Project

1.6.1 Delimitations of the Project
The scope of this project will be limited to the following:
 Movies information and their fees.

 To manage Clients and their orders
 To develop registration system

 To facilitate movie request keeping
 To facilitate various report generation
Page | 7
1.6.1.1 Features
 The system is easy to use, have good looks and secure.

 Get easy access to client particulars, their orders, movies, extra-curricular activities, and any
reports, anytime
 Employees will have treated to the simplest interface around for them to enter movies
information.
 Movies are automatically retrieved from best API in the business (Did not require data
entry)
 Track daily Income. Easy to use interface to check reports.
 Fees management. Track the fees of the clients.
 The system will give the edge for better reporting.
1.6.2 Limitations of the Project
 The Movie information is automatically retrieved from internet

and stored on the local database. Because of that reason the
system will provide movie information only in a single language
which is English.
 The System will only provide movie information not the movie
itself.
1.7 Methodology
1.7.1 Data Collection Methods
In this project we used object oriented approach for the system analysis and design. There are some reasons
that make us to select this system development approach. These reasons are: -
 We can inherit properties of the class that are defied in the super class.
 We can reuse methods for avoiding redundancy.
 It helps to reduce the complexity of the system and make clear program structure.
Page | 8
Observation
Since it enables us to observe the real problems of the existing system by providing
tangible and clear information, the team is simply observed the current working
system in action rather than a theory. This enables us to filter out the typical
problems of the system from different angles.
1.8 System Development Approaches

We selected Object Oriented Approaches:
Object oriented approach has the following benefits. Some of those are:
It tends to model the real world in a more complete fashion.
• It helps to reduce the complexity of the system and make clear program structure.
• It has a natural structure for modular design and leads to faster development.
For the above reasons the team chooses OOA
1.9 System Development Tools
 MSSQL – to design our database.

 MS Visual Studio - for developing the front end.
 Visio – for mapping the analysis phase
 MS-Word – to document the files
 Adobe XD - for making the prototype
 C# - to develop the front end.
 HTML – to develop front end look.
 CSS – to style the web application.
 MS-Power Point – for presentation
Page | 9
CHAPTER TWO
2 Requirement Analysis
2.1 Overview of Proposed System

The proposed system is a web based Movie Information System for Movie Shops. It can work both on
localhost or using a domain name as a public web application. This web application will automate the movie
ordering process, gives information easily for customers and generates various reports. This chapter includes
requirement analysis, system modelling, database design and user interface.
2.2 Functional Requirements:

 Registration – The user requires to register in order to request an order
 Registration Failure – If the user already exists on the database.
 Sign in – The user can login to the system with his/her username and
password
 Sign Out – The user can log out from the system
 Sign in Failure – If the user does not exist on the database or the
username or password is incorrect.
 User role check - after logging in, the user role will be checked from the
database and the user interface will be displayed according to their role.
 Display - user with defined roles can display the content of the database.
 Anonymous Users: can view movie information
o can search movies
o can sign up or register to be a member
 Customers: can view movie information
o can search movies
o can make orders
o can cancel orders
o can view orders invoice
o can view and change their information
 Employees: can view movie information
o Can add new movies
o Can edit movies
o Can delete movies
o Can set movie as best of all time
o Can view orders
o Can set orders status
Page | 10
o Can view weekly reports

 Administrators:
o Can create administrator account
o Can create employee account
o Can view reports
o Can set movie as free movies
Reports:
₰ Movie
₰ Income.
₰ Client or Visit
₰ Credit or Loan
2.3 Non-functional Requirements:
2.3.1 Performance requirement
 There is no restriction on the number of users added into

the database.
 There is no restriction on the number of users at a time.
 The administrator or employee is allowed to add only one
thousand movies (1000) movies per day.
 There is no platform restriction to use the system.
2.2.3 Hardware requirement
The System requires the following hardware in order to function properly
Hardware Qty Minimum Specification

Core 2 due CPU with 3 GB
Computer 1 memory, and 50 GB Hard Disk
space minimum
Access Point / Router 1 400 Mbps single band
minimum
Page | 11
2.2.3 Software requirement
The System requires the following software in order to function properly
Software Qty Minimum Specification

Operating System 1 Windows 7 Service Pack 2
minimum
Web Server IIS Server 9 minimum
SQL Server 1 SQL Express 2008 R2 minimum

SQL Server Management Studio 1 SQL Express 2008 R2 minimum
Browser - Internet Explorer 9+ minimum
Internet Connection 1 2G minimum
Page | 12
CHAPTER THREE
3 SYSTEM DESIGN
Model is a representation in a certain medium of something in the same or another medium.
An abstract representation that illustrates the components or relationship of a specified application or

component.
3.1 Use Case Diagram and Use Case Documentation
Actors of proposed system
No. Actors
1. Administrator
2. Employee
3. Customer
4. Anonymous User
Use case of proposed system
Use case ID Name

UC-01 Login
UC-02 Register
UC-03 View Movie
UC-04 Add to Cart
UC-05 Remove From Cart
3.1.1 Essential Use Case Diagram

Essential use case means to understand what users needed to see on the system from functional point of
view. This use case diagram is not technology based and simple to draw with pen or pencil. It’s also source
for proposed system modeling.
Page | 13
Existing system essential use case diagram
3.1.2 CRC Model

A CRC model is really a collection of standard index cards that represent classes. The cards are divided into
three sections. Along the top of the card you write the name of the class. In the body of the card you list the
class responsibilities on the left and collaborators on the right.
List of classes are:
 Customer
 Employee
 Administrator
 Anonymous User
Page | 14
Customer CRC model
Customer
View Movie Information ()
Request Order () Employee
Cancel Order () Employee
Change Username & Password()
Login()
Logout()
View Fee() Customer
Employee CRC model
Employee
View Orders() Customer
Checkout Order Request() Customer
View Fee() Customer
Add New Movie()
Edit Movie()
Generate Report()
Login()
Logout()
Administrator CRC model
Administrator
View Orders() Customer
Checkout Order Request() Customer
View Fee() Customer
Add New Movie()
Edit Movie()
Generate Report()
Create Employee Account()
Login()
Logout()
Anonymous Users CRC model
Anonymous Users
Register()
Login()
Page | 15
3.1.3 System Use Case Diagram

Use cases are used during requirements elicitation and analysis to represent the functionality of the system.
Use cases focus on the behavior of the system from an external point of view.
A use case describes a function provided by the system that yields a visible result for an actor. An actor
describes any entity that interacts with the system. The identification of actors and use cases results in the
definition of the boundary of the system, that is in differentiating the tasks accomplished by the system and
the tasks accomplished by the system and the tasks accomplished by its environment. The actors are outside
the boundary of the system, whereas the use cases are inside the boundary of the system.
Proposed system use case diagram
Page | 16
Order Movie use case diagram
3.1.4 Use case Documentation

The use case document is a business document which provides a story of how a system and its actors will be
utilized to achieve a specific goal. An effective use case should provide a detailed step by step description of
how the system will be used by its actors to achieve the planned outcome. The purpose of the use case is to
tie the business needs of the system to the design parameters of the system to ensure that the completed
system achieves the goals established by the business requirements. The level of detail in use cases may vary
greatly depending on the size and complexity of the system being designed.
Register use case description
Name Register
Identifier UC-003
Description Create a new account in order to use the system fully
Actor Anonymous Users
Pre-Condition None
Post Condition The system creates an account if the user is not registered before
Extends None
Page | 17
Includes UC-001
UC-002
Basic Course of Action
1. Anonymous user wants to be a member.
2. Anonymous user browses the website using “UC-001”
3. The system displays the website
4. Anonymous user clicks “Signup” link “UC-002”
5. The system displays the signup form “UC-004”
6. Anonymous user fills the user information then click the button “UC-004”
7. The system checks if the user exists on the database
8. The system displays the user credential form “UC-005”
9. Anonymous user fills the last form “UC-005”
10. The system will verify if the information is filled correctly then add the user to the database
and sets the user role as “Customer”.
11. The system will display the success message “UC-006”
Alternative course of Action A: User already exist on the database
7.1 the system determines that the user already registered.
7.2 the system informs that the user already exist on the database.
Login use case description
Name Login
Identifier UC-007
Description Login to the user account to get access
Actor Employee/Admin/Customers
Pre-Condition The User need to be a registered user
Post Condition None
Extends None
Includes UC-001
UC-003
1. User wants to sign in into the system.
2. User browse the website using “UC-001”
4. User clicks “Login” link “UC-008”
5. The system displays the Login form “UC-009”
6. User fills the Login credential then click the login button “UC-009”
7. The system checks the user credential and identifies the user role
8. The system will display the main window based on the user’s role
Alternative course of Action A: Username or Password is incorrect
7.1 the system determines that the user name or password is incorrect
7.2 the system informs to the user that the username or password is incorrect
Page | 18
View movie use case description
Name View Movie

Identifier UC-010
Description View movie information like the name, genre, release date etc.
Actor Customers, Anonymous Users
Pre-Condition UC-001/None
Post Condition None
Extends None
Includes UC-001
1. Customer wants to see the movie information
2. Customer logs into the system using “UC-001”
3. The system displays the main window “UC-001”
4. Customer selects a movie then click “read more” link “UC-006”
5. The system will display the movie detail window “UC-007”
Alternative course of Action
Add to cart use case description
Name Add to cart

Identifier UC-011
Description The customer adds a movie to the cart that he wants to be sent to his
flash drive or storage device
Actor Customers
Pre-Condition 1. The User need to have an account
2. The user needs to sign into the system
Post Condition The user needs to choose the movie
Extends None
Includes UC-001
UC-007
1. User wants to add a movie into the cart.
2. User browse the website using “UC-001”
4. User logs into the system “UC-007”
5. User Selects a movie then click add to cart button “UC-012”
6. The system checks if the movie is not carted before
7. The system adds the movie to the cart
8. The system changes the movie status to carted
Alternative course of Action A:
Page | 19
Remove from cart use case description
Name Remove From Cart

Identifier UC-011
Description The customer removes a movie that is already putted on the cart in
order to tell the employee to cancel the movie if its set or being sent
into the customers storage device
Actor Customers
Pre-Condition 1. The User need to have an account
2.The user needs to sign into the system
3. The user needs to add a movie to the cart before
Post Condition The user needs to choose the movie
Extends None
Includes UC-001
UC-007
UC-011
1. User wants to remove the movie from the cart.
2.User browse the website using “UC-001”
4. User logs into the system “UC-007”
5. User Selects a movie then click remove from cart button “UC-014”
6. The system checks if the movie is carted before
7. The system removes the movie from the cart
8. The system deletes the movie from the cart database
Alternative course of Action A:
3.2 Sequence Diagram

Sequence diagram shows the sequence of messages exchanged by the set of objects. The objects are
arranged from left to right across the diagram an actor that initiates the interaction is often shown on
the left. The vertical dimension represents time. The top of the diagram is the starting point, and time
progress downwards towards the bottom of the diagram. A vertical dashed line, called a lifeline, is
attached to each object or actor. The lifeline becomes a box, called an activation box.
Page | 20
Registration sequence diagram
Page | 21
Add to Cart Sequence Diagram
Add to cart sequence diagram
Page | 22
View Detail Movie Sequence Diagram
View Detail sequence diagram
3.3 Activity Diagram

Activity diagram is used to understand the flow of work that an object or component performs. It can also be
used to visualize the interaction between different use cases.
Login Activity Diagram
Page | 23
Order Movie Activity Diagram
3.4 Class Diagram

Class diagrams are the most common diagrams used in UML. Class diagram consists of classes, interfaces,
associations and collaboration. Class diagrams basically represent the object-oriented view of a system.
Hence, it is generally used for development purpose. Class diagram is a static diagram. It represents a static
Page | 24
view of an application .
3.5 System User Interface Prototype

Which represents an interface for most use cases without providing much or any functionality. User
interface prototypes are used to evaluate issues such as alternative user interface concepts or window
layouts. User interface design creates an effective communication medium between a human and a
computer. Following a set of interface design principles, design identifies interface objects and actions and
actions and then creates a screen layout that forms the basis for a user interface prototype.
Login user interface prototype
Page | 25
Register user interface prototype
Page | 26
Main Page user interface prototype
Customers Main Page user interface prototype
Series Movie user interface prototype
Page | 27
Customers Cart user interface prototype
Page | 28
Employee Movies user interface prototype
Employee View Order user interface prototype
Page | 29

Movie Information System

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Movie Information System

Caricato da

Copyright:

Formati disponibili

Movie Store Information Management System 2019

DEPARTMENT OF COMPUTER SCIENCE

Movie Store Information Management System

UU OOSAD PROJECT TEAM

Sub to: Instructor Nigussie Teferi

Adama, Ethiopia 2019 G.C

3.1.4 Use case Documentation ................................................................................................................... 17

1.2 Background of the Organization:

1.3 Statement of the Problem

1.4 Objective of the Project

1.4.2 Specific Objectives

1.5 Significance of the Project

1.5.1 Beneficiary of the system

 It helps to minimize the waiting time during movie ordering.

 It helps to manage the Orders

1.6 Scope of the Project

The scope of this project will be limited to the following:

 Movies information and their fees.

 To develop registration system

 The system is easy to use, have good looks and secure.

1.6.2 Limitations of the Project

 The Movie information is automatically retrieved from internet

1.8 System Development Approaches

For the above reasons the team chooses OOA

1.9 System Development Tools

 MSSQL – to design our database.

 MS-Power Point – for presentation

2.1 Overview of Proposed System

2.2 Functional Requirements:

o Can view weekly reports

2.3 Non-functional Requirements:

2.3.1 Performance requirement

 There is no restriction on the number of users added into

2.2.3 Hardware requirement

The System requires the following hardware in order to function properly

Hardware Qty Minimum Specification

2.2.3 Software requirement

The System requires the following software in order to function properly

Software Qty Minimum Specification

SQL Server 1 SQL Express 2008 R2 minimum

An abstract representation that illustrates the components or relationship of a specified application or

3.1 Use Case Diagram and Use Case Documentation

Actors of proposed system

Use case of proposed system

Use case ID Name

3.1.1 Essential Use Case Diagram

Existing system essential use case diagram

3.1.2 CRC Model

List of classes are:

Customer CRC model

Employee CRC model

Administrator CRC model

Anonymous Users CRC model

3.1.3 System Use Case Diagram

Proposed system use case diagram

Order Movie use case diagram

3.1.4 Use case Documentation

Register use case description

Login use case description

View movie use case description

Name View Movie

Add to cart use case description

Name Add to cart