Project Report On

Online Web Series Website

Submitted By:

Ms. Nikita Janardan Kamble (193427)

Year 2019-2020

Under the Guidance of

Prof. Milind Paradkar

College:

Vikas College of Arts, Science & Commerce

Vikhroli (E).
Mumbai-400078

1|Page
 CERTIFICATE OF APPROVAL

Project Title: Online Web Series Website

Submitted by:

Nikita Janardan Kamble (193427)

In partial fulfilment of Third Year of the degree of B.Sc. in

“Information Technology” is approved.

Guide: Examiner(s):

1.Internal________

Head of department
(Information Technology) 2.External________

2|Page
 Acknowledgement
I, the student from Vikas College of Arts, Science and
Commerce, Mumbai of Final Year of Bachelor of Science
in the department of ‘Information Technology’ have great
pleasure in presenting my efforts of developing the project
named as “Online Web Series Website ”.
The success of my project on whole does not depend
on an individual student but on the creative team work me
and my faculty members. This would have difficult by an
individual. So I wish & acknowledge the precious guidance
from those who willingly supported to me to make this
project.
I am grateful to Prof. Dr. R. K. Patra (Principal) and
Prof. Seema Rahul (HOD) for giving me inspiration, timely
guidance and valuable suggestions during the course of
project. I am especially thankful to Prof.Milind Paradkar for
guiding me throughout project work.
Lastly, I express my sincere thanks to all teaching and
non-teaching staff of IT Department to help me entire
course.

Thanking you,
Nikita Janardan Kamble
3|Page
 TABLE OF CONTENTES
CHAPTER 1: INTRODUCTION
1.1 Background 6
1.2 Objectives 7
1.3 Purpose, Scope, and Applicability 8
1.4 Organisation of Report 10

CHAPTER 2: SURVEY OF TECHNOLOGIES

2.1 Front End 11
2.2 Back End 13

CHAPTER 3: REQUIREMENTS AND ANALYSIS

3.1 Problem Definition 14
3.2 Requirements Specification 17
3.3 Planning and Scheduling 18
3.4 Software and Hardware Requirements 22
3.5 Preliminary Product Description 23
3.6 Conceptual Models 26

CHAPTER 4: SYSTEM DESIGN

4.1 Basic Modules 27
4.2 Data Design 28
4.2.1 Schema Design 29
4.2.2 Data Integrity and Constraints 32
4.3 Data Structure 45
4.3.1 Algorithm Design 48
4.4 User Interface Design 49
4.5 Security Issues 50

CONCLUSION 51

4|Page
 CHAPTER 1 : INTRODUCTION

Introduction

Web Series is a website of videos where users can login and

view videos.
This is the website which can be accessed by all age people
from young to aged people for entertainment and socializing.
Admin is only allowed to add videos as well as any
modification if required.
User are not allowed to add videos, they can simply register
and login to view these videos.
Users can put their review for respective video and they can
have communication in group for videos.
Here we are going to show episodes of the seasons where
users can create a Web Series community and permit other
users to join the website of web series.
Also, they can give their comments as they can get social to
each other.

5|Page
1.1) Background
The most important thing is to study a system thoroughly. Here we are
studying both the existing and the proposed system so that the advantages and
disadvantages both understand. The first task was to identifying how the
system is to be computerized. Some analysis and projection was done
regarding changes to be made to the existing system. The new developed
system “Web Series” is simple without any complexities.

6|Page
1.2) Objectives

Web Series is the perfect way for enthusiastic to:

1. To provide entertainment in this hectic and busy life.

2. EXPLORE your interests with new friends who share your passions.

3. UNITE with Web Series fans from around the world! Enter a world just for its
enthusiasts.

4. DISCOVER others who share your favourites and collaborate on events,

projects, and posts.

5. ENGAGE with other seasons of web series episodes

6. SHARE your Web Series experiences from conventions and other events.

 Proposed System -

 Asp.net Support code behind technology

 It supports different controls like html controls, server controls
 It Supports language interoperability.

This project contains two modules:

a) Admin :

Admin is only allowed to add videos as well as any modification if required.

b) User :

User are not allowed to add videos. They can simply register and login to view
these videos. Users can put their review for respective video and they can have
communication in group for videos. Users can also socialize with each other.

7|Page
1.3) Purpose , Scope and Overview of Project

Describe the contents and organization of the rest of this document. Since there is
already a Table of Contents, this overview will be less formal but more informative.
Describe the two basic remaining sections, the Overall Description and the
Requirements Specification.

1. Purpose of project -

....is entertainment, I got it. However, it isn’t always as simple. There are complexities
and nuances to the experience of watching Web Series that, even if it arrives at an
entertaining end, accomplishes (or can accomplish, at least) a few other things. Stories
in general are entry points to different aspects of culture, both familiar and foreign.
While some of us may say Web, Series aren’t very reliable sources in a factual or
research sense, but like I said they are entry points to further inquiry. Also, there are
different shows for different entertainment purposes. I find this kind of categorization
perhaps more useful than genre-based taxonomies. I’m going to go into these here, as
I look at how I use Web Series for different purposes. Purposes are numbered (for my
own reference), but appear in no particular order.

2. Scope of the project -

The scope of project “Web Series” is to enable the User to view from various seasons
and watch their desired one. The users are also allowed to leave a comment and also
allowed to like or dislikes their post. Users can join any forum from various forums and
they can leave desired forum.

3. Project overview -

It is a web based online project. The main aim of the project is any user they can access
the system through website at any time. As a new user also, he can collect all
information like types of Genre’s Web Series’ belong it.

8|Page
Benefits of project -

 It gives easy surfing experience to the users.

 Time saving.

 No wrong users can view the profile of other users because of

validation checks given by the system.

 Large data storage computer storage capacity is very high.

 Early and correct decision making.

 Immediate response to user’s queries.

 Due to computerization queries can answer quickly.

 User friendly.

9|Page
1.4) Organization of Report:
First chapter give overview of project and smoothly introduces you to the subject.
Second chapter is about survey of various technologies so far been used to make
shopping website.
Third chapter is about Requirements of the project and analysis of requirements.
Fourth chapter is about System Design.

10 | P a g e
 CHAPTER 2 : SURVEY OF TECHNOLOGIES
2.1) Front End
For doing survey of available technologies, I have divided those technologies into
Front End and Back End for easy understanding.

About ASP.NET as front End

.Net-What is it?
• Software platform
• Language neutral
In other words:
.NET is not a language (Runtime and a library for writing and executing written
programs in any compliant language)

What is .NET?
• .NET is a new framework for developing web-based and windows-based
applications within the Microsoft environment.
• The framework offers a fundamental shift in Microsoft strategy:
It moves application development from client-centric to server-centric.

.NET Framework services

• Common Language Runtime
• Windows Forms
• ASP.NET
-Web Forms
-Web Services
• ADO.NET, evolution of ADO
• Visual Studio .NET

11 | P a g e
Common Language Runtime (CLR)
• CLR works like a virtual machine in executing all languages.
• All .NET languages must obey the rules and standards imposed by CLR.
Examples:
- Object declaration, creation and use
- Data types, language libraries
- Error and exception handling
- Interactive Development Environment (IDE)

12 | P a g e
2.2) Back End

SQL 2008 as Back-End

SQL server is scalable database system whose primary purpose is to serve as a
backend database for client program, such as your Web browser, an accounting
program like online Gift Shop–anything that makes use of the data. In the most
common usage scenario, a client program connects to SQL server and requests some
information, whereupon SQL server processes the requests and returns results. The
client must then interpret and display these results- eg. Displaying list of Users in
alphabetical order. SQL server can structured information. Eg. You can instantly
search through millions of records and view the results of the search in many different
formats.
You can combine different data into one set; you can transform some formats
into others; you can set security rules to be enforced by SQL server; and so on.

Features of SQL Server 2008

Information representation
Unique definition of rows
Systematic treatment of Null values
Guaranteed access
High level Update, Insert, and Delete
Retrieving information from the database.
Accepting query language statements.
Enforcing security specifications.
Enforcing data integrity specifications
Enforcing transaction consistency
Managing data sharing
Optimizing queries

13 | P a g e
 CHAPTER 3 : REQUIREMENTS AND ANALYSIS

3.1) Problem Definition

Problem in existing system :
The existing system is manual system. Needs to be converted into automated
system.
Risk of mismanagement of data.
Less Security.
No proper coordination between Applications and Users.
Fewer Users.
Accuracy not guaranteed.
Not in reach of distant users.
Less reliable.
Difficulty in keeping new records.

Solution of these problems :

The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.
1. User friendliness is provided in the application with various controls.
2. There is no risk of data mismanagement at any level while the project development
is under process.
3. It provides high level of security with different level of authentication.
4. Users from any part of the world can make use of the system.
5. New system will be much better in performance as compared to existing one.

14 | P a g e
Existing System :
This process is done manually. The existing system is time consuming and it is very
costly, because it involves a lot of paperwork. To manually handle such a system was
very difficult task. But now-a-days because of computerization this job is becoming
easier.
The following are the reasons why the existing should be computerized
 To increase efficiency with reduced cost.
 To save time of management for recording details of each and every
transaction.
 To check that particular product requested is available.

Limitation of Existing System :

 Time Consumption
As the records are to be manually it consumes a lot of time.

 Storage requirement
As files and registers are used the storage requirement is increased.

 Less Reliable
Use of paper for storing valuable data is not at all reliable.

 Accuracy
As the system is in manual, there are not many chances of human error.
These cause error in calculating mechanism or maintaining product
and supplier data in register.

 Difficulty in keeping new records

It is difficult for keeping all the new entries of the products, their
updates, reviews, feedback etc.

15 | P a g e
Proposed system :
The proposed system will include following features:
 Creating a database for the easily available users and Forum information with
single view.

 This system like database for storing information.

 This system is time variant and non-volatile.

 All information regarding users and their joined and un-joined forum are
available in a glance to the admin.

Advantage of the proposed system :

Time saving since all the detail information is storing in this system, it enables
significance reduction in the number of man-hours taken up for the storage and the
retrieval of the information as it removes the large registers from the scene.
 Accuracy and Reliability.

 Time- variant.

 Non-volatile.

 User friendly, accurate.

 Security of data and Integration of all function in one system.

 Remove redundancy and inconsistency of data.

 Through proper validation data inconsistency is reduced.

16 | P a g e
3.2) Requirement Specification

Functional Requirements :

 Website provide user to maintain his/her profile & account.

 Website allows users to login and view videos.
 Users can put their review for respective video.
 Users can have communication in group for videos.
 Users can create a Web Series community and permit other users to join the
website of web series.
 Users can give their comments as they can get social to each other.

Non-Functional Requirements:-

Reliability - This website can handle users with perfect accuracy. Therefore

this system is reliable to use.

Scalability - In future this site can be scalable by offering to more features.

Maintainability - This website can maintain many users’ work process. It is not

become hanging by the many users.

Security - The data upload on this website is secure from unauthorized

access. This web-site is secure from viruses.

17 | P a g e
3.3) Planning and Scheduling

System Development Life Cycles (SDLC) describes the data design and applications
design. SDLC is an interactive rather than a sequential process. Thus SDLC might help
to refine Feasibility study to the user requirements.

Fig. System Development Life Cycles (SDLC)

Planning:

SDLC planning yields a general overview of the company and its objectives.An initial
assessment of the information of the flow and intents requirement must be made
during this discovery portions of SDLC.

Analysis:
Problems defined during the planning phase are examined in great details during
analysis phase.Analysis phase of the SDLS is an effect, a though AUDIT of the users
requirements.

18 | P a g e
Detailed system Design:
In this phase, the designer complete the design of the systems processes. This include
all the necessary technical specification for the screens and reports.

Implementations:
In this phase hardware, DBMS software and the applications programs are installed
and the database designs is being implementations .

Maintenance:
As soon as the system is operable, end users being to request in it. Those changes
generates systems maintenance activities, which can be grouped into three type:

 Adoptive maintenance due to changes in business environment

 Correctives maintenance in response to systems.
 Perfective maintenance to enhance the system.

System Design :
Software design sits at the technical kernel of the software engineering process
and is applied regardless of the development paradigm and area of application. Design
is the first step in the development phase for any engineered product or system. The
designer’s goal is to produce a model or representation of an entity that will later be
built. Beginning, once system requirement have been specified and analysed, system
design is the first of the three technical activities -design, code and test that is required
to build and verify software.

Methodology Adopted :
The methodology adopted while developing the system is the Spiral model.

19 | P a g e
The process begins at the centre position. From there it moves clockwise in traversals.
Each traversal of the spiral usually results in a deliverable. It is not clearly defined
what this deliverable is. This changes from traversal to traversal. For example, the first
traversals may result in a requirement specification. The second will result in a
prototype, and the next one will result in another prototype or sample of a product,
until the last traversal leads to a product which is suitable to be sold. Consequently,
the related activities and their documentation will also mature towards the outer
traversals. E.g. a formal design and testing session would be placed into the last
traversal.

There are different instances of this model many with 3 to 6 task regions. These regions
are:

 The planning task - to define resources, responsibilities, milestones and

schedules.
 The goal determination task - to define the requirements and constraints
for the product and define possible alternatives.
 The risk analysis task - to assess both technical and management risks.
 The engineering task - to design and implement one or more prototypes or
samples of the application

20 | P a g e
The most outstanding distinction between the spiral model and other software
models is the explicit risk evaluation task. Although risk management is part of
the other processes as well, it does not have an own representation in the
process model. For other models the risk assessment is a sub-task e.g. of the
overall planning and management. Further there are no fixed phases for
requirements specification, design or testing in the spiral model. Prototyping
may be used to find and define requirements. This may then be followed by
"normal" phases as they can be found in other process models to handle design
and testing.
The advantages of the spiral model are that it reflects the development approach
in many industries much better than the other process models do. It uses a
stepwise approach which e.g. goes hand in hand with the habit of maintaining a
number of hardware sample phases in cases where the product to be produced is
not only software for a given environment, but also contains the development of
hardware. This way the developers and the Patient can understand and react
much better to risks in the evolutionary process. By having an iterative process
which reduces formalisms and omit table activities in the earlier phases the use
of resources is optimized. Further, any risks should be detected much earlier
than in other process models and measures can be taken to handle them.

21 | P a g e
3.4) Software and Hardware Requirements

There are two types of requirements:

1) Hardware Requirements
2) Software Requirements

1) Hardware Requirements –

 Processor: Intel core i3 or above

 Processor speed: 2.00 GHz CPU
 RAM: 2 GB or above
 Hard disk utilization: 160 GB or above

2) Software Requirements –

 Front End: HTML5, CSS3, ASP.NET

 Client-side Scripting: JavaScript and J Query
 Server-side Scripting: AJAX and C#
 Back End: SQL Server 2008

22 | P a g e
3.5) Preliminary Product Description
Preliminary Investigation -
The first step in our project development involved the preliminary investigation i.e.:
the information gathering for software requirement to be done before starting the
project, which begin as:
1. Our project deals with Patient Relationship Management, this software will
help organizations to maintain records of their clients and Patient Tests.
2. Important aspect of Patient Relationship Management is that Employees need
to login to gain access to the Pathology Lab’s DB regarding Clients and Patient
Tests, only authorized employees will be able to see and modify records.

Request Clarification :
To understand each and every step in our project our detailed Preliminary
investigation included all the criteria required for proper implementation of the
project.
The request requirement of the end user is to get a Patient relationship
Management system which will help him to minimize processing time and gain
more profit with happy Patients.

Feasibility Study :
Our project uses .NET as the front end and SQL Server 2008 as the back end
for our development of the phase. The main requirement of the development of
the project is that our project will be used for Patient Relationship Management.
The feasibility study must be able to answer the following:
 Is there new or better way to do this?
 What is the cost and saving of the alternatives?
 What is recommended?

23 | P a g e
Preliminary Requirement Analysis -
Market Survey -
A detailed market survey was conducted for evaluating the market potential
of Web Series Website. Following are the key finding of the market survey.
 Web Series websites would prove to be the key Base for any organization but
not limited to Web Series Production House. It can also be used for Media
institute to keep record of Web Series that’s crazy has increased from year one
to last year including views of individual episodes.
 Simple easy to use
 Low Maintenance Cost
 Easy deployment of application

Project Planning Objectives –

The project planning was done to ensure that the project is delivered on schedule,
budget and meeting the quality requirements. The project planning also helps ensure
the resource loading is even and all the tasks are covered.

Feasibility -
A feasibility study was done before the start of the project with the goals to
analyse the users need, skill set of the team and technology availability for the Web
Series website. As listed in the market survey above, there is a strong need for such
software and the technology is available to make easy to use, easy deployable software.
The team has the required skill set to develop the application.

Software project Estimation -

The first step in software project planning is cost estimation. Software cost
estimation is becoming increasingly important in today’s software industry. Because
software is usually the most expensive part of a computer system, good estimations
become essential for a developer to accurately cost a project. We have used Functional
point-based estimation to do the estimation of the project. Following are the details of
the estimates:

Decomposition Techniques -
Software today is a huge size and estimating the cost to produce it can be a big problem.
For this reason, we decompose the problem into smaller problems and then solve them

24 | P a g e
 more readily. Basic software metrics are usually measured in either lines of code (LOC)
or function points (FP) Both of these metrics have their own estimation techniques
which are different, but they have many similar characteristics. We have used Function
Point Decomposition Technique to get the software project estimation.

Software Risk -
A detail risk analysis was done. The team got together and brainstormed all
the possible risks for the project and a detail mitigation plan was done. The risk details
are as follows:

Sr. Risk Mitigation Plan

No.

1. Required Skill Set for the The team has basic skills. Training will be planned
project to enhance the expertise of the team.

2. The Availability of The application development will be made available

development software. by the college.

3. Increase in given Cost. The cost will be under control by completing the
software in time

4. Business impact of project. This Risk will be under control by making the
software user friendly and deliver it on time

25 | P a g e
3.6) Conceptual Models

The system after careful analysis has been identified to be presented with the following
modules and roles. The modules involved are:
Admin
User

The administrator is the super user of this application. Only admin have access into this
admin page. The administrator has all the information about all the users and about all
videos.
1. Manage Videos
2. Manage Playlists
3. Manage Users

26 | P a g e
 CHAPTER 4 : SYSTEM DESIGN

4.1) Basic Module

27 | P a g e
4.2) Data Design
Databases are the storehouses of data used in the software systems. The data is stored
in tables inside the database. Several tables are created for the manipulation of the data
for the system. Two essential settings for a database are:
Primary Key - the field that is unique for all the record occurrences.
Foreign Key - the field used to set relation between tables.
Normalization is a technique to avoid redundancy in the tables.

Online
Web
User Videos
Series
website

28 | P a g e
4.2.1) Schema Design
Table Serials

Table Episode

29 | P a g e
Table Movie

Table Comment

30 | P a g e
 Table Forum

Table Forum Joining

Table Comment

31 | P a g e
4.2.2) Data Integrity and Constraints:
Data integrity can be done by combining tables with constraints. Check
constraints place specific data value restrictions on the contents of a column through
the specification of a Boolean expression. The expression is explicitly defined in the
table DDL and is formulated in much the same way that SQL WHERE clauses are
formulated. Any attempt to modify the column data (i.e., during INSERT and UPDATE
processing) will cause the expression to be evaluated. If the modification confirms to
the Boolean expression, the modification is permitted to continue. If not, the statement
will fail with a constraint violation.

Class Diagram :

32 | P a g e
Use Case Diagram :

33 | P a g e
Activity Diagram :
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency.

34 | P a g e
Activity Diagram (User) :

35 | P a g e
Activity Diagram (Admin) :

36 | P a g e
E-R Diagram :

37 | P a g e
Sequence Diagram :
A sequence diagram in a Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. A
sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario. Sequence
diagrams typically are associated with use case realizations in the Logical View of the
system under development.

38 | P a g e
39 | P a g e
Data Flow Diagram :
Data flows are data structures in motion, while data stores are data structures. Data
flows are paths or ‘pipe lines’, along which data structures travel, whereas the data
stores are place where data structures are kept until needed.
Data flows are data structures in motion, while data stores are data structures at rest.
Hence it is possible that the data flow and the data store would be made up of the same
data structure.

Data flow diagrams is a very handy tool for the system analyst because it gives the
analyst the overall picture of the system, it is a diagrammatic approach.

A DFD is a pictorial representation of the path which data takes from its initial
interaction with the existing system until it completes any interaction. The diagram will
describe the logical data flows dealing the movements of any physical items. The DFD
also gives the insight into the data that is used in the system i.e., who actually uses it is
temporarily stored.

A DFD does not show a sequence of steps. A DFD only shows what the different
process in a system is and what data flows between them.

40 | P a g e
RULES FOR DFD -

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions reads left to right and
top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with rounded circles.
 A process is required for all the data transformation and transfers. Therefore,
never connect a data store to a data source or the destinations or another data
store with just a data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything the process
is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple Record retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.
 There can’t be unnamed data flow.
 A data flow can’t connect two external entities.

41 | P a g e
Sr. No Name Description
Symbol
1. External An external entity is source
Entity or destination a data flow
which is outside the area of
study. For egg, Patient,
Student etc.

2. Process A process shows a

transformation or
manipulation of data flows
within the system.

3. Dataflow A data flow shows the flow

of information from its
source to its destination. A
data flow is represented by
a line, with arrowheads
showing the direction of
flow.

42 | P a g e
4. Data File or A data stores a holding
Data store place for information
within the system. Data
stores may be long-term
OR files such as sales ledgers,
or may be short-term
accumulations: for
example, batches of
documents that are waiting
to be processed.

LEVELS OF DFD:

The complexity of the business system means that it is a responsible to represent

the operations of any system of single data flow diagram. At the top level, an Overview
of the different systems in an organization is shown by the way of context analysis
diagram. When exploded into DFD

They are represented by:

 LEVEL 0: SYSTEM INPUT/OUTPUT

 LEVEL 1: SUBSYSTEM LEVEL DATAFLOW FUNCTIONAL
 LEVEL 2: FILE LEVEL DETAIL DATA FLOW.

The input and output data shown should be consistent from one level to the next.

LEVEL 0: SYSTEM INPUT/OUTPUT LEVEL

A level-0 DFD describes the system-wide boundaries, dealing inputs to and outputs
from the system and major processes. This diagram is similar to the combined user-
level context diagram.

43 | P a g e
LEVEL 1: SUBSYSTEM LEVEL DATA FLOW

A level-1 DFD describes the next level of details within the system, detailing the data
flows between subsystems, which makeup the whole.

LEVEL 2: FILE LEVEL DETAIL DATA FLOW

All the projects are feasible given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of the project at the earliest possible
time. Feasibility and the risk analysis are pertained in many ways. If project risk is great.

FIRST LEVEL DATAFLOW DIAGRAM

44 | P a g e
4.3) Data Structures
User_master Table :
Description: This is User table for storing user details.

45 | P a g e
 Fields Datatypes Constraints

UserID Int Primary Key

UserName varchar(50) Foreign key

UserPassword varchar(50)

UserContact varchar(50)

UserAddress varchar(50)

UserRole varchar(50)

Video_Details Table :
Description: This is Video Table for storing video details.

46 | P a g e
 Fields Datatypes Constraints

V_Id Int Primary key

Video_Name varchar(Max) Foreign key

Sample_Video_File nvarchar(200)

Release_Date Int

Genre varchar(50)

Writer varchar(50)

Language varchar(50)

Full_Video_File nvarchar(200)

Video_Image nvarchar(50)

Feedback_Details Table:
Description: This is Feedback table for storing customer feedback.

47 | P a g e
 Fields Datatypes Constraints

User Name varchar(50) Foreign key

Email varchar(50)

Comment varchar(Max)

Date Date

4.3.1) Algorithm Design

1. Users will register to site by giving his/her detail.
2. It will save details in Database and it will redirect it to Login Page.

48 | P a g e
3. User will login to the site.
4. It will check with the database. If the details matched with database, it will
direct to main page.

4.4) User Interface Design:

1. Login/ Register facility will be provided at the right side of the webpage.
2. Person can select/search item using search field which will be available at the
top.

49 | P a g e
3. Recommended Artists are display below the search bar for easy access.
4. Recommended Albums are display right side of the site.
5. Songs list are display in centre of the site.

Search Login Signup

Recommended Series

Recommended
Videos
Video List

4.5) Security Issues :

 Now a day’s data is new currency so it should be secure.

50 | P a g e
  User personal details should not get leak.
 Site need to be protected from cyber-attacks.
 Guarding data so that users only see what they should see.

Conclusion :
This Website would allow our customers convenient and easy access to the site.

51 | P a g e
I have designed this project to provide the user with easy navigation, retrieval of
data and necessary feedback as much as possible.
A good video showing site design must be accompanied with user-friendly logic.
Online Web Series Website provides knowledge about the latest technology used
in developing web enabled website and client server technology that will be great
demand in future.

52 | P a g e