AVtube

A PROJECT REPORT

Submitted by

Patel Pruthviraj Vinodbhai (150670107080)

In fulfillment for the award of the degree

of

BACHELOR OF ENGINEERING
in
Computer Engineering

Sal Institute of Technology and Engineering Research, Ahmedabad

Gujarat Technological University, Ahmedabad

April-May, 2019
 Sal Institute of Technology and Engineering Research
2019

CERTIFICATE
Date:

This is certify that the project entitled “AV-Tube” has been carried out by Patel Pruthviraj
Vinodbhai (150670107080) under my guidance in partial fulfillment of the degree of Bachelor of
Engineering in Computer Branch 7th Semester of Gujarat Technological University, Ahmedabad
during the academic year 2018-19.

Assi. Prof. Pooja Mehta Dr. Vidhi Khaduja

Internal Guide Head of Department
Computer engineering Computer engineering
SALITER SALITER
 ACKNOWLEDGEMENT

I express my cavernous sense of obligation and gratitude to my guide Asst. prof. Pooja Mehta his
genuine guidance and constant encouragement throughout this project work. We are highly obliged
as our honorable guide has devoted his valuable time and shared her experience knowledge.

I extend my thanks to HOD Mr. S.G DESAI, department of Computer Engineering, SAL
COLLAGE OF ENGINEERING for providing us such an opportunity to do our project work in
our college.

I also wish to express my heartfelt appreciation to my friends and many who have rendered their
support for the successful completion of the project, both explicitly and implicitly.

i AVtube
 ABSTRACT

Nowadays, there are many people who have craze to post photo and videos on social media, and
it is very difficult for them to download and share on single platform. Vlogging in India is a
medium for today’s young generation to step up toward their talent and share their creativity
with others.

We are creating website for “AV-TUBE” in which the people can easily collaborate and
Communicate with their post and response and we provide the things according to user
requirement. In order to offer best user experience for AV-TUBE platform, We are making it
more easy to use and helpful with guidance. With unique features and concepts we can made this
idea for everyone. Each component you see in this project tells a different story.

ii AVtube
 LIST OF FIGURES
Sr.No Figure Name Page No.

1. Use case diagram 10

2. Activity diagram 12

3. Sequence diagram 14

4. ER diagram 16

5. DFD 18

iii AVtube
 LIST OF TABLE
Sr.No Table Name Page No.

1. Login_master 6

2. User_Master 6

3. Category_ Master 6

4. Channel_Master 6

5. Subscribe_Master 7

6. Playlist_ Master 7

7. Content_ Master 7

8. Review_ Master 7

9. FAQ_ Master 8

10. Feedback_Master 8

iv AVtube
 TABLE OF CONTENTS
Acknowledgement i
Abstract ii
List of Tables iii
List of Figures iv
List of Contents v

Chapter 1 Software Requirements and Specification

1.1 Introduction 1
1.2 General Description 1
1.3 Functional Requirements 1
1.4 Interface Requirements 2
1.5 Performance Requirements 2
1.6 Design Constraints 2
1.7 Non Functional Requirements 3
1.8 Operational Scenarios 3
1.9 Preliminary Schedule 3

Chapter 2 Database Dictionary 4

Chapter 3 Diagrams
3.1 UML Diagrams 9
3.2 Use Case Diagram 10
3.3 Activity Diagram 12
3.4 Sequence Diagram 14
3.5 Entity Relationship Diagram 16
Chapter 4 Data Flow Diagram 18
Chapter 5 System Screenshot 20
Chapter 6 Testing 28
Chapter 7 Future Enhancements 32
Chapter 8 Conclusion 33
Chapter 9 References 34
Appendix 35

v AVtube
 CHAPTER 1: INTRODUCTION TO PROJECT

1.1 INTRODUCTION
• Digitalization is main power of business so this project presents AV-TUBE of photos and
videos.
• Abstract system is used for the beneficial of company and end user.
• In this system there will be complete details regarding the client requirements.
• Suppose you search for a dancing talent, then all content related to dancing with their details
will be shown. So that you can easily get the search result as per your requirements.
• Every registered user can create multiple channels and playlist in our website only.
• As we know it is online market. We have to use this abstract system, so that, end user and
admin can access the content details and make them available globally.

1.2 GENERAL DESCRIPTION

Server capacity is how many user can access or can be online at once. Moreis the number of users more
will be the network traffic and hence the server comes in a down state. Personal firewall and updating
is a tough task, it should be such that it should not block the network traffic , making the system
slower.Firewall of the server should not collide with the firewall of the use system.

1.3 FUNCTIONAL REQUIREMENTS

• The main objective of this software system is that it saves lots of time to find and show their
talents.
• It is very helpful mainly for end user and visitor.
• Other useful objectives for this system are as follows:
• Easily find and manage search results.
• Reduces the time for searching.
• Easy to download content for registered users.

1 AVtube
1.4 INTERFACE REQUIREMENTS
1.4.1 GUI
The user interface will consist of one main screen, allowing all the functionally to come from this one
screen. This allows the user to use the software with ease by not flicking through a number of different
screens. In addition to this the user can always see the videos they are looking for.

We decided on this type of interface because we felt that it would be very simple for the user to
navigate. From our reports we fond that the simpler the interface was, the more people liked it with
all these features compiled into one screen it will give the software more flexibility and aloows for
easy and simple usage. This will appeal to both naïve computer users and experienced computer
users with a higher selling market.

1.4.2 Hardware Interface

Since the application must run over the internet, all the hardware shall require to connect internet
will be hardware interface for the system. As for e.g. Modem, WAN – LAN, Ethernet Cross Cable.

1.4.3 Software Interface

The server computer is required when user access it through internet. End user must have an browser
to access the web application. Recommended browser is google chrome.

1.5 PERFORMANCE REQUIREMENTS

The load time of web application should not be more than 5 seconds.

The load time of GUI should not be more that 7 seconds.

The query should be processed within 10 seconds and response must be given.

1.6 DESIGN CONSTRAINTS

The system will be designed as a web application. The background processes of system can be
developed in PHP. The GUI can be developed in PHP. And for database, MySQL will be use.

2 AVtube
1.7 NON-FUNCTIONAL REQUIREMENTS
1.7.1 Security
This system will only takes an image from user and after processing it destroy itself and it does not
have any access to personal directories.

1.7.2 Reliability
This system is reliable in both usability and security.

1.7.3 Availability
The system should be available during server remains online. Whereas, we anticipate having
constant live connection for whole time.

1.7.4 Maintainability
The system will maintain in timely basis. If some error occurs, the system will handle itself and
gives the solution.

1.7.5 Reusability

The same system can be used as many times as user wants.

1.8 OPERATIONAL SCENARIOS

First end user opens web application by inserting URL in Web Browser, After loading user can search
for particular channel. User choose the channel. User want to create his channel and also uploading and
downloading the images, videos and audios.

The interaction between end user and system is reliable and does not require any manual. It has
simple UI so that user does not have to think much how the system will work.

1.9 PRELIMINARY SCHEDULE

The system must be implemented within 6 months.

3 AVtube
 CHAPTER 2 : DATABASE DICTIONARY

2.1 Introduction:
A Data Dictionary is Catalog Responsibility of the Element in a System. As the Name Suggests
these elements are structured around Data in a way to meet the Use and the Organization
requirements. A Data Dictionary is a List of Elements that composes all the Data Flow Process
through the System. If Analysts Wants to Know by What Other Means is a Table or a Data Item
Referenced in the System or where it is being used the Answers are properly developed in the Data
Dictionary. The Dictionary Id Developed during Data Flow Analysis Assists the Analysts involved
in Requirements. However it's Content is used during System Design as well.
A data dictionary, or metadata repository, as defined in the IBM Dictionary of Computing, is
"centralized repository of information about data such as meaning, relationships to other data,
origin, usage, and format." The term can have one of several closely related meanings pertaining to
databases and database management systems (DBMS).

Technically, it is a database about a database. There is no one set standard in terms of layout or the
level of detail to which a data dictionary should be written. A data dictionary defines the structure
of the database itself (not that of the data held in the database) and is used in control and maintenance
of large databases. Among other items of information, it records (1) what data is stored, (2) name,
description, and characteristics of each data element, (3) types of relationships between data
elements, (4) access rights and frequency of access, also called system dictionary when used in the
context of a system design. Database users and application developers can benefit from an
authoritative data dictionary document that catalogs the organization, contents, and conventions of
one or more databases. This typically includes the names and descriptions of various tables (records
or Entities) and their contents (fields) plus additional details, like the type and length of each data
element. Another important piece of information that a data dictionary can provide is the
relationship between Tables. If using Set descriptors, identifying which Sets database Tables
participate in. In an active data dictionary constraints may be placed upon the underlying data.

4 AVtube
2.2 Features of Data Dictionary:

A data dictionary describes the structure and attributes of data items to be used within software
application (usually a database). Software development teams need comprehensive data dictionary
to refer to during the development and maintenance of a new database. This is so that they are all
working using the same data formats when reading or writing data.

A data dictionary includes the names and descriptions of the tables and the fields contained in a
table. It also documents information about the data type, field length and other things such
validation. The main purpose of the data dictionary is to provide metadata or information about data.
The volume of data in most information system is substantial more than a single analyst can easily
keep track of the same. When the teams of analyst work on assistance the task of coordinating data
definition becomes more complex. Individual depends on the information provided by others with
their Assumption and the Specification made by them.

Data Dictionary is Integral component of Structured Analysis. Since data flow diagram by them do
not fully describe the subject of the Investigation. The Data Dictionary provides additional
information about system.

Functions of the Data Dictionary 1.

Defines the data element.
2. Helps in the scheduling.
3. Helps in the control
4. Permits the various users who know which data is available and how can it be obtained
5. Helps in the identification of the organizational data irregularity
6. Acts as a very essential data management tool.
7. Provides with a good standardization mechanism
8. Acts as the corporate glossary of the ever growing information resource.
9. Provides the report facility, the control facility along with the excerpt facility
5 AVtube
Table: Login_Master
Attribute Datatype Size Constraint Description
L_Id Int 5 Primary_Key Unique Id for Login_Master
Email Varchar 30 Unique Stores email id of user
Psw Varchar 20 Not Null Stores password of user
User_type Bit Allow Null Stores user type(admin or user)

Table: User_Master
Attribute Datatype Size Constraint Description
U_Id Int 5 Primary_Key Unique Id for User_Master
L_Id Int 5 Foreign Key Stores reference key to login master
First_Name Varchar 20 Not Null Stores first name of user
Last_Name Varchar 20 Not Null Stores last name of user
BOD Date Allow Null Stores date of birth of user
Mob_No Varchar 10 Not Null Stores contact number of user

Table: Category_Master
Attribute Datatype Size Constraint Description
Cat_Id Int 5 Primary_Key Unique Id for Category_Master
Cat_Name Varchar 20 Not Null Stores category name

Table: Channel_Master
Attribute Datatype Size Constraint Description
C_Id Int 5 Primary_Key Unique Id for Channel_Master
Cat_Id Int 5 Foreign Key Stores reference key to Category
C_Name Varchar 20 Not Null Stores name of channel
C_datet Date Not Null Stores creation date of channel
C_State Bit Allow Null Set state of channel as active or not

6 AVtube
Table: Subscribe_Master
Attribute Datatype Size Constraint Description
Sub_Id Int 5 Primary_Key Unique Id for Subscribe_Master
C_Id Int 5 Foreign Key Stores reference key to channel
U_Id Int 5 Foreign Key Stores reference key to User

Table: Playlist_Master
Attribute Datatype Size Constraint Description
P_Id Int 5 Primary_Key Unique Id for Playlist_Master
C_Id Int 5 Foreign Key Stores reference key to Channel
P_Name Varchar 20 Not Null Stores name of playlist
P_Description Varchar 500 Allow Null Stores description about playlist
P_date Date Not Null Stores creation date of playlist
P_State Bit Allow Null Set state of playlist as active or not

Table: Content_Master
Attribute Datatype Size Constraint Description
Con_Id Int 5 Primary_Key Unique Id for Content_Master
C_Id Int 5 Foreign Key Stores reference key to Channel
Con_Description Varchar 500 Allow Null Stores description about content
Con_date Date Not Null Stores creation date of content
Type Bit Allow Null Set type of content as image or video
Image Blob Not Null Stores image as content
Video Blob Not Null Stores video as content

Table: Review_Master
Attribute Datatype Size Constraint Description
R_Id Int 5 Primary_Key Unique Id for Review_Master
Con_Id Int 5 Foreign Key Stores reference key to Content
U_Id Int 5 Foreign Key Stores reference key to User_Master
Description Varchar 500 Allow Null Stores description about content
R_date Date Not Null Stores creation date of content
Rate Int 5 Stores rating of review given by user

7 AVtube
Table: FAQ_Master
Attribute Datatype Size Constraint Description
Faq_Id Int 5 Primary_Key Unique Id for FAQ_Master
Faq_Title Varchar 5 Not Null Stores FAQ Question
Faq_Ans Varchar 5 Not Null Stores FAQ Answer

Table: Feedback_Master
Attribute Datatype Size Constraint Description
F_Id Int 5 Primary_Key Unique Id for Feedback_Master
U_Id Int 5 Foreign Key Stores reference key to user
F_Time Date 20 Not Null Stores time of Feedback
F_Response Varchar 500 Not Null Stores Feedback Response

8 AVtube
 CHAPTER 3: DIAGRAMS

3.1 UML Diagram

Unified Modeling Language
In The Unified Modeling Language User Guide, the original developers of the UML Grady Booch.
James Rum Baugh, and Ivar Jacobson provide a tutorial to the core aspects of the language in a two
color format designed to facilitate learning. Starting with a conceptual model of the UML, the book
progressively applies the UML to a series of increasingly complex modeling problems across variety
of application domains. This example driven approach helps readers quickly understand and apply
the UML. For more advanced developers, the book includes a learning track focused on applying
the UML to advanced modeling problems.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed
as trademarks where those designations appear in this book, and Addison Wesley Longman Inc.
was aware of a trademark claim, the designations have been printed in initial caps are all in caps.
The author and publisher have taken care in the preparation of this book, but make no expressed or
implied warranty of any kind and assume no responsibility for errors or omissions.

No liability is assumed for incidental or consequential damages in connection with or arising out of
the use of the information or programs contained herein.

To model a system the most important aspect is to capture the dynamic behavior. To clarify a bit in
details, dynamic behavior means the behavior of the system when it is running operating So only
static behavior is not sufficient to model a system rather dynamic behavior is more important than
static behavior. In UML there are five diagrams available to model dynamic nature.

List of UML Diagrams Shown are as follows:

• Use Case Diagram
• Activity Diagram
• Sequence Diagram
• Entity Relationship Diagram
9 AVtube
3.2 USE CASE DIAGRAM

Use case diagrams are used to gather the requirements of a system including internal and external
influences. These requirements are mostly design requirements. So when a system is analyzed to
gather its functionalities use cases are prepared and actors are identified.

The purposes of use case diagrams can be as follows:

• Used to gather requirements of a system.
• Used to get an outside view of a system.
• Identify external and internal factors influencing the system.
• Show the interacting among the requirements are actors.

Use case diagrams are considered for high level requirement analysis of a system. So when the
requirements of a system are analyzed the functionalities are captured in use cases.

So we can say that use cases are nothing but the system functionalities written in an organized
manner. Now the second things which are relevant to the use cases are the actors.

Actors can be defined as something that interacts with the system. The actors can be human user,
some internal applications or may be some external applications. So in a brief when we are planning
to draw an use case diagram we should have the following items identified. Functionalities to be
represented as a use case as relationships among the use cases and actors.

10 AVtube
Fig (3.2) Use case Diagram

11 AVtube
3.3 ACTIVITY DIAGRAM

Activity diagram is basically a flow chart to represent the flow form one activity to another activity.
It captures the dynamic behavior of the system. Other four diagrams are used to show the message
how from one object to another but activity diagram to show more activity to another activity is a
particular operation of the system. Activity diagrams are not only used for visualizing dynamic
nature of system but they are also used to construct the executable system by using forward and
reverse engineering techniques.

The only missing thing in activity diagram is the message part. It does not show any message flow
from one activity to another. Activity diagram is some time considered as the flow chart. Although
the diagrams looks like a flow chart but it is not, it shows different flow like parallel, branched,
concurrent, single etc. This diagram has more impact on business understanding the implementation
details
Following are the main usages of activity diagra
• Modeling work flow by using activities
• Modeling business requirements
• High level understanding of the system's functionalities Investigate business
requirements at a later stage.

12 AVtube
Fig (3.3) Activity Diagram For User

13 AVtube
3.4 SEQUENCE DIAGRAM

A Sequence diagram is an interaction that shows how object operate with one and in what order. A
sequence diagram has interactions arranged in time sequence. It depicts the objects and classes
involved in the scene.

A sequence diagram shows, as parallel vertical lines lifelines, different processes which are live
simultaneously, and, as horizontal arrows, the messages exchanged between them in the order in
which they occur. This allows the specification of simple runtime scenarios in a graphical manner.
Messages written with horizontal arrows with, the message name written above, they display
interaction. Solid arrow heads represent synchronous calls, open arrowheads represent
asynchronous, and dashed lines represent reply messages. If a caller sends a synchronous message,
it must wait until the message is done, such as invoking subroutine.

If caller sends an asynchronous message, it can continue processing and doesn't have to wait for a
response. Asynchronous calls are present in multithreaded applications and in messageoriented
middleware. Activation boxes, or method-call boxes, are opaque rectangles drawn on top of lifelines
to represent that processes are being performed in response to the message (Execution Specifications
in UML).

Objects calling methods on themselves use messages and add new activation boxes on top of any
others to indicate a further level of processing. If an object is destroyed (removed from memory, a
X is drawn on top of the lifeline, and the dashed line ceases to be drawn below it. It should be the
result of a message, either from the object itself, or another. A message sent from outside the
diagram can be represented by a message originating from a filled in circle (found message in UML)
or from a border of the sequence diagram (gate in UML).

14 AVtube
Fig (3.4) Sequence Diagram For Admin

15 AVtube
3.5 ER DIAGRAM:

An Entity Relationship Diagram (ERD) is a visual representation of different data using conventions
that describe how these data are related to each other. In the diagram, the elements inside rectangles
are called entities while the items inside diamonds denote the relationships between entities.

ER model as a conceptual modeling approach that views real world data as systems or entities and
relationships. Entities are data objects that maintain different relationships with each other
additionally, entities are also described further using attributes. There are three basic elements in an
ER Diagram: entity, attribute, relationship. There are more elements which are based on the main
elements. They are weak entity, multivalued attribute, derived attribute, weak relationship and
recursive relationship. Cardinality and ordinarily are two other notations used in ER diagrams to
further define relationships.

1. Entities: Entities are Distinguishable object that can be represented in the Database
2. Relationship: It is meaningful interaction between the entities. 3. Attributes: It is nothing
but properties of entities

In ER Diagram three types of Relationship exists:

1. One to One (1:1): Relationship
2. One to Many (1: M) Relationship
3. Many to Many (M:M) Relationships

Different shapes with their meaning:- 1.

Rectangle: This represents entity sets.
2. Ellipse: This represents attributes
3. Diamonds: This represents relationship sets
4. Line: Links attributes to entity sets and entity sets to Relationship sets

16 AVtube
Fig (3.5) ER Diagram

17 AVtube
 CHAPTER 4: DATA FLOW DIAGRAM

Data flow diagrams (DFD) illustrate how data is processed by a system in terms of inputs and data.
In these diagrams much data tows between elements in a system and between the system and
external elements.

Four Basic Elements of DFD are:

• Data flows represented by named pipelines
• Processes represented by circles
• External Entities represented by rectangles
• Data stores represented by open ended rectangles.

The external entities are the sources and destinations of a system's input and output. They are objects
that are not within the system, but with which the system interacts Data Storage represents entities
in the system in which the data is stored. Examples include databases and files.

Process represents an action taken on the data. This may include a calculation, conversation, or other
task performed. Process can send and receive control signals that help to explain the control over
the data flowing through the system. Data Flows represent then movement of information through
the system Control signals connect control transforms to other objects on the diagram and represent
control over data source or destination of data.

18 AVtube
Fig (4) DFD Work Diagram

19 AVtube
 CHAPTER 5: SYSTEM SCREENSHOTS

1. Home Page

20 AVtube
2. Contact us

21 AVtube
3. Our Gallery

22 AVtube
4. Login page

5. signup page

23 AVtube
6. Admin page

24 AVtube
7. Admin tasks

25 AVtube
8. User profile

26 AVtube
9. User feedback

27 AVtube
 CHAPTER 6: TESTING
Software testing is an investigation conducted to provide stakeholders with information about the quality of
the software product or service under test. Software testing can also provide an objective, independent view
of the software to allow the business to appreciate and understand the risks of software implementation. Test
techniques include the process of executing a program or application with the intent of finding software bugs
(errors or other defects), and verifying that the software product is fit for use.

Software testing involves the execution of a software component or system component to evaluate one or
more properties of interest. In general, these properties indicate the extent to which the component or system
under test

• meets the requirements that guided its design and development,

• responds correctly to all kinds of inputs,
• performs its functions within an acceptable time,
• is sufficiently usable,
• can be installed and run in its intended environments, and
• Achieves the general result its stakeholder’s desire.

Software testing can be conducted as soon as executable software (even if partially complete) exists. The
overall approach to software development often determines when and how testing is conducted. For example,
in a phased process, most testing occurs after system requirements have been defined and then implemented
in testable programs. In contrast, under an agile approach, requirements, programming, and testing are often
done concurrently.

Testing methods

Static vs. Dynamic Testing

There are many approaches available in software testing. Reviews, walkthroughs, or inspections are referred
to as static testing, whereas actually executing programmed code with a given set of test cases is referred to
as dynamic testing. Static testing is often implicit, as proofreading, plus when programming tools/text editors
check source code structure or compilers (pre-compilers) check syntax and data flow as static program
analysis. Dynamic testing takes place when the program itself is run. Dynamic testing may begin before the

28 AVtube
program is 100% complete in order to test particular sections of code and are applied to discrete functions or
modules. Typical techniques for this are either using stubs/drivers or execution from a debugger environment.

Static testing involves verification, whereas dynamic testing also involves validation. Together they help
improve software quality. Among the techniques for static analysis, mutation testing can be used to ensure
the test cases will detect errors that are introduced by mutating the source code.

The box approach

Software testing methods are traditionally divided into white- and black-box testing. These two approaches are
used to describe the point of view that the tester takes when designing test cases.

White-Box Testing
White-box testing (also known as clear box testing, glass box testing, and transparent box testing and
structural testing, by seeing the source code) tests internal structures or workings of a program, as opposed to
the functionality exposed to the end-user. In white-box testing, an internal perspective of the system, as well
as programming skills, is used to design test cases. The tester chooses inputs to exercise paths through the
code and determine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit
testing (ICT).

Black-Box Testing
Black-box testing treats the software as a "black box", examining functionality without any knowledge of internal
implementation, without seeing the source code. The testers are only aware of what the software is supposed to

do, not how it does it.[15] Black-box testing methods include: equivalence partitioning, boundary value analysis,
all-pairs testing, state transition tables, decision table testing, fuzz testing, model-based testing, use case testing,
exploratory testing, and specification-based testing
Testing levels
Unit testing
• Integration testing
o INCREMETAL
o NON-INCREMENTAL
• Component interface testing
• System testing
• Operational acceptance testing
29 AVtube
 • Test case for admin model
Test Case Id Description Input Expected Pass/Fail
result
Tc01 Login into Id and Open admin Pass
admin side password page
Tc02 Create Channel Channel will Pass
Various name create
channels
Tc03 Update and Click on Channel can be Pass
remove buttons delete or
channel update
Tc04 Select multiple Click on No multiple Fail
files to upload choose file file choosen
in photo
gallery
Tc05 Saving process Click on Save Pass
of files save successfully
button
Tc06 User contact Click on Contact list of Fail
details contact the usres

30 AVtube
 • Test case for user model
Test case id Description Input Expected Pass/Fail
result
Tc01 User While sign User could Fail
registration up successfully
without selection of registered
selecting channels
channel
Tc02 Profile Click on User name and Pass
changing profile icon password
should be
changed or
updated if user
will chage
details
Tc03 See the lists of Click on A page with Pass
channels channel channel details
icon should be
displayed
Tc04 User can give Click on User should Pass
the feedback feedback fill the
icon feedback form
and feedback
should be save
and listed
bellow
Tc05 Fast questions Click on Lists of Fail
and answers FAQ questions
(FAQ) icon should be open
and user can
be give ans of
that

31 AVtube
 CHAPTER 7: FUTURE WORK

• The prime objective of “AV-TUBE” is to find any of the relative content with highest views,
multi search options, channels or playlists for the particular category.
• Add subtitle to video content
• Enhancement and improvement to video performance
• Improve quality of video by determine speed of internet.
• More End user features i.e., likes, comments.
• Create clickable links inside post to navigate between next and previous content.
• Auto play, delete , trim and combine content
• Apply special effects such as slow motion, transitions and color change.
• Social media sharing to share content on other social websites.

32 AVtube
 CHAPTER 8 : CONCLUSION

The project is a social-media based solution for an IT based company. The project has mainly two
modules admin and user. The system will be online and will be developed in PHP. The project is
scheduled to be completed in approximately four months. The project will require good knowledge
of PHP and PhpMyAdmin. The system to be developed is intended to be user friendly and secure.
All the possible errors and wrong input to be entered by the user is also considered and the focus is
handling such wrong inputs by validating the input before any process.

The project is a web based application and will run online. Therefore it will require internet
connection live while working. The system will not require much resource to run. On the server side
it will require Apache to be installed. For database PhpMyAdmin is used so that it can easily handle
and manage a large amount of data. The security features of SQL also make it the best suitable
Relational Database Management System for this project. The project is concluded as a solution of
the manual system which will be effective and useful for the organization.

33 AVtube
 CHAPTER 9: REFERENCES

• https://www.google.com
• http://www.wikipedia.org
• http://www.stackoverflow.com
• http://www.tutorialspoint.com
• http://www.youtube.com
• http:/en.wikipedia.org/wiki/Vlogging

34 AVtube
APPENDIX

35 AVtube
36 AVtube
37 AVtube
38 AVtube
39 AVtube
Business Model Canvas (BMC)

40 AVtube
 BMC Report

KEY PARTNERS
• Student Teacher
• Company
• Organization
• Community
• Administrator

KEY ACTIVITIES
• Data collection
• Upload multi type files
• Create multiple account

KEY RESOURCES
• Server
• PC with active internet
• Web browser
• Multiple users

VALUE PROPOSITIONS
• User feedback
• Upload data
• Surfing
• Minimal cost

CUSTOMER RELATIONSHIP
• Customer help desk
• Customer feedback

41 AVtube
CHANNELS
• Audio/video call
• Email for any query

CUSTOMER SEGMENTS
• vlogger blogger
• educational
• youth

COST STRUCTURE
 server management fees
REVENUE STREAMS
 Free of charge

42 AVtube
43 AVtube
44 AVtube
45 AVtube