0% found this document useful (0 votes)
7 views14 pages

Design Document

Uploaded by

Devendra Bishnoi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views14 pages

Design Document

Uploaded by

Devendra Bishnoi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Software

Design
Document

BY
Devendra Bishnoi
R30183
Komal Gupta
R31476
Hrithik Agarwal
R3130
TABLE OF CONTENTS

1. Introduction
1.1 Purpose
1.2 Scope of project
1.3 Glossary
1.4 References
1.5 Overview
2. Architecture
2.1 System Design
3. Data Design
3.1 Data Flow Diagrams
3.1.1 Level-0 DFD
3.1.2 Level- I DFD
3.1.3 Level-2 DFD
3.2 Data Dictionary
4. Softwa re Interface Design
4.1 User Interface Design-
4.2 Description
5. Mod ules
5.1 Module wise Description
1. Introduction
1.1 Purpose
The purpose of the Software Requirements Specification (SRS) document is to provide a
detailed overview of our software product, its parameters, and goals. This document aims to
gather and analyze and give an in-depth insight into the
Hybrid Movie Recommender system by defining the problem statement in detail. It
concentrates on the capabilities required by stakeholders and their needs while defining high-level
product features. The straightforward user interface, hardware, and software requirements of the
Hybrid Movie Recommender system are provided in this document.

1.2 Scope of project


This software helps users of the customer platform explore content quickly with our
recommendation system 's help. The software we are developing is a Hybrid Recommendation
System for Movies, which uses the combination of collaborative and content-based filtering in
the context of web-based recommender systems. In particular, we will link the well-known
TMDB data set. The content filtering part of the system is based on trained neural networks
representing individual user preferences. Using various experiments, we will demonstrate the
influence of supplementary user and item features on our proposed hybrid recommender's
prediction accuracy. To decrease system runtime and reveal latent user and item relations, we will
factorize our hybrid model via singular value decomposition (SVD).
Due to the enormous amount of information available online, the need for highly developed
personalization and filtering systems is growing permanently.
Recommendation systems constitute a specific type of information filtering that attempts to present
items according to the interests expressed by a user.
1.3 Glossary
Term Definition

Stakeholder Any person with interest in the project


which is not a developer.

Collaborative filtering It tries to find the correlation between


users and recommend content from other
categories that they might like.

Content-based filtering Recommendation based on information


available about the item but not about the
user.

Singular Value It is the factorization of a real or


Decomposition(SVD) complex matrix that generalizes the eigen
decomposition of a square normal matrix
to any matrix via an extension of the
polar decomposition.

1.4 References
[1] Abdollahpouri, Himan & Burke, Robin. (2019). Multi-stakeholder Recommendation and its
Connection to Multi-sided Fairness.

[2] Kunaver, Matevz & Pozrl, Tomaz & Pogacnik, Matevz & Tasic, Jurij. (2006). The evaluation of a
hybrid recommender system for recommendation of movies.

[3]Rohan Nayak, Aniket Mirajkar, Jeetesh Rokade, Prof. Girish Wadhwa(2018). Hybrid Recommendation
System For Movies
1.5 Overview
The remaining sections of this document provide a general description, including characteristics
of this project's users, the product's hardware, and the product's functional and data
requirements. A general description of the project is discussed in section 2 of this document.
Section 3 gives the functional requirements, data requirements and constraints, and assumptions
made while designing the E-Store. It also gives the user viewpoints of the product. Section 3
also gives the specific requirements of the product. Section 3 also discusses the external
interface requirements and gives a detailed description of functional requirements. Section 4 is
for supporting information.
6
1. Architecture

1.1 System Design -

USER USER USER USER


USER

System Interface

Recommende
HOME ABOUT LOGIN USER
d Movies
Page

Figure-I : The context diagram shows the main actors interacting with the system.
ADMIN
USER

Figure-2: The context diagram for UUIS.

2. Data Design

2.1 Data Flow Diagrams

2.1.1 Level-0 DFD:

Add/Update/Delete Movie details

Data items
ADMIN
USER
Movie
Recommendations

FIGURE-3
2.1.2 Level-1

MOVIE INFO

USER NAME

USERNAME MOVIE DATA

FIGURE-4
2.1.2 Level-2

USERS

USERS

CONFORMATION MAIL
USER DETAILS

MOVIES

USER DETAILS
MOVIE DETAILS

SELECTED MOVIE DETAILS

LIKE DISLIKE

FIGURE-5
2.2 Data Dictionary

FIELD TYPE NULL

User username varchar(l 00) NO


email varchar(l 00) NO
password varchar(l 00) NO
profile_image Image YES

user id int NO
-

FIELD TYPE NULL

Movies genres varchar(l 00) NO


id int NO
title varchar(l 00) NO
average_rating float NO
Cast varchar(l 00) YES

FIELD TYPE NULL

Ratings user id int NO


-

movie id int NO
-

movie liked/disliked int NO


-
3.Software Interface Design

3.1 User Interface Design-


UI is designed according to the UI design principles.

1. . The structured principle: UI is organized in such a way that related things


are combined together and unrelated things are separated.

2. The simplicity principle: It is easy to follow the provided interface.In the case of a
mistake.,the system displays an error message.

3. The visibility principle: All system functions are available through the UI. It does not
overwhelm users with too many alternatives.

4. The feedback principle: Through the system of messages, the design keeps users
informed of actions, errors, or exceptions.

5. The reuse principle: In design, the same names were used to perform the same
operations with different objects in order to reduce ambiguity.
3.2 Description
"Welcome" page is the first page the user sees when he visits the website and doesn 't log in.
Upon logging on to this page, the user can navigate to one of the pages among various available
options, the links to which have been given on the navigation bat of this page.

"Home" page is the link to the first page the user sees. It becomes the welcome page if the user
isn't logged in,movie-recommendation page if the user is logged in.

"Movies-Search" page allows the user to enter the name/genre/cast of the movie and shows the
result of the searched and related movies to the searched one.

"About" page contains information about the Movie Recommendation System(MRS).

"Register" page allows the user to get himself registered in the database of the MRS. It
asks the user his desired username , email, and password for the same.

"Login" page has a form asking the user his username and password , entering which and
clicking the submit button leads the user to the Movies-search page.

"Profile" page link appears when the user has logged in by providing the correct
username and password. This page shows the profile info of the user and allows him to change
his profile picture if he desires.
4.Modules

4.1 Module wise Description

starting() Returns the starting page with a form to fill


out the details and find the Movies.
Also shows recommendations based on the
previous movie searches, ratings by the user,
and TMDB ratings.
In the case of the new user, it is completely
based on TMDB ratings.

search(movie name/genre/cast) Takes movie name/genre/cast as parameters


and then finds out the list of movies that
match the parameters and also recommends
related movies.
Returns an HTML page showing all the
related movies.

Rating(Movie ID, User ID) Takes Movie ID and asks for rating for that
movie whether he likes it or not and stores it
under that user's ID.

about() Returns an HTML page containing the


information about the site.

reg() Takes information of the user in a form.


Checks if the information is valid.Confirms
the email address by sending a confirmation
mail.
Redirects the user to the login page.

profile() Returns the profile of the current user and a


form through which the current user can
change his profile image.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy