ClapperBoard via WordPress - Buse Akin

. Project Scope

• I goal to provide general ideas about the plan of the website. Some important software applications are used in my project and all of them will be discussed. Some subtopics will support and show the details of the project:

. Introduction

. Goals and Objectives

• On the internet database, there are a lot of movie-rating websites however none of these are useful to make lists, share ideas and interact other people lists. As a person who loves to watch movies, I always need a platform or application which will keep my movies that I watched. On ClapperBoard people can log in to website, create their own watchedlist and watchlist(with the date they determined), rate the movies, share their lists, see other user’s lists, search the movies or directors, and they can see categorized movies with genres. There will be also a notification system to new released movies which is selected by users. ClapperBoard is going to be a platform which every movie addicts want to join.

. Statement of Scope

• In ClapperBoard, I get inspired from the Leonardo Da Vinci’s famous quote; “Simplicity is the ultimate sophistication.”. Website will be minimal and effective for the users. All they need to do is register first then enjoy the site. There will be two default list which are watchedlist and watchlist, they can easily add or delete movies to the lists, they can add date to remember when they watched the movie or when they will watch the movie. There will be share buttons to share the lists they like, spoiler buttons to make sure comments can readable.

. Major Constraints

• At the creating stage, timing will be very important for this project. My main goal is to finish the project coding beginnig of the April and then move to testing stage. Design is crucial, this website cannot be complicated with lot of colors, buttons etc. It should be simple because there will be a lot of movies, movie pictures, informations etc.
• Database design is another important point of this project. I need to design it as good as possible and provide to variety for the movie lovers.

. Technical Details

. Technologies I use

• Platforms:
  • MySQL Workbench
  • WordPress
  • Erwin for Data Modeling

• Languages:
  • PHP
  • MySQL
  • HTML
  • CSS

. Database Design and Description

. Introduction

• The first thing to do in order to create database, is to complete data modeling. In Data Modeling, the job is to take the requirements and begin to design a rough plan or layout for the requirements. There are several phases of design to create a model before implementation. Before project, blueprints helps to find and plan out the overall design of the project. Creating rough sketches and designs can provide new information as well. During the project having a data model is useful for project tracking and scheduling the project. Data Modeling contains three steps. These are Conceptual, Logical and Physical Phases.

. Conceptual Phase

Conceptual phase is the first step in the data modeling. In conceptual phase, overall goal is to design a basic simplified overview of the project. At this point, the restrictions are not taking into account. Conceptual phase provides a good understanding of the concept as a whole. There is only information about entities and the relationship in between entities. The picture below shows the entity relationship diagram for the conceptual phase.

• The entities in this design are;
  • Movies; this entity will store basic movie information. It has a many-to-many relationship with ‘Director’ entity.
  • Conjunction MD; this entity will ensure the many-to-many relationship between ‘Movies’ and ‘Director’.
  • Director; will store basic information about directors.
  • List Detail; this entity will hold specific movie information in the ‘List Detail’ entity.
  • Movie List; this entity will hold the information about movie lists, which are created by users.
  • Users; will store basic information about users.
  • Liked List; thie entity will hold the specific list information that one users liked.

. Logical Phase

Logical phase is the second step in data modeling. In logical phase, user requirements are taken into account, thus provides a clear view of the restrictions. It is overall logical understanding of the concept. In logical phase, attributes, primary keys, foreign key should be represented as well as entity names and entity relationships. The picture below shows the entity relationship diagram of logical phase.

. Physical Phase

The third and final phase of data modeling is the physical phase. In physical phase, technical restrictions applied to the design from logical phase. This final phase provides overall physical structure of the database, that is the final blue prints. At this stage in the project, the physical phase is still on process. The final table names should be decided, as well as column names and column types. Thus requires more time to do the proper analysis. Implementation and population of database with sample data can only start after finalizing the data modeling.

. Flow Diagrams

. WebSite Navigation

BURAYI DÜZENLE

. WelcomePage

• You should log in to see lists, add movies, or make comments to movies.

. HomePage

• You can see the the users’ which you follow acts on your homepage.
• You can see the movies that inserted to website.

. MyLists

• In the Mylists Page, there will be 2 default lists ; watched list, watchlist. You can allso add new lists.

. Explore

• There will be explore section to see genres, shared lists, new released movies, etc.

. SearchBar

• for directors/movies

. EditPage

• User section with edit, friends, notification, logout segments.

. Project Schedule

For the ClapperBoard website project, there are some stages;
1. Project Analysis (4-5 weeks)
1.1 Project Design (3-4 weeks)
2. Database Design (3-4 weeks)
2.1 Finalize Database Design (last 1 week of DB Design)
3. Coding
3.1 Implementation ( starts same time with Finalize Database Design) 3.2 Front End Development (2 weeks)
3.3 Sample Database Population ( starts same time with Front End Development 2 weeks)
4. Testing (takes 2-3 weeks)
5. Finalize Project
5.1 Finalize Project with the Test Results (takes 2 weeks)
5.2 Addind missing data/content (takes 1 week)

. Weeks

BURAYI DÜZENLEMEN LAZIM

I.Week

• Name of the project is determined.
• Logo was created.

. Risk Management

.Project Risks

According to the schedule, this project should be done in the first week of May. Although, some problems might occur during analysis and development. In case of any problem, there might be a change in schedule in order to fix everything.

• Some problems might happen due to the server.
• There might be some legal issues as well, specially with IMDB. Also, there might be copyright issues with movies, movie production companies, directors, actors, etc.
• Security is another risk that project has. Especially with user loggings, their passwords must be encrypted with the correct algorithm, in order to prevent their privacy. Need to prevent possible hackings.
• Browser problems might happen due to the layout of wordpress. The layouts and design might change according to the browsers.
• Some extensions in wordpress, might not be compatible with the other extensions.

. Developer

. Contact Information

Name: Buse AKIN
Responsibility: Front End Develeoper & Database Designer
Phone Number: 607 338 0140
E-mail Address: bakin2@binghamton.edu