Supporting Information: Application Requirements:

The web application you are writing the design specification for should provide the following functionality to the user:

You MUST produce: ONE technical design document (stated above) that describes how this specification can be implemented as a dynamic web application.

Application Pages:

The application should provide at least the following application views (a view can be considered as either a page, or an aspect of a page):

The home page view should provide a summary view of at least THREE of the games available on the site AND links to content related your chosen console platform.

An individual game view for each of the recommended games which presents information on the game (e.g. genre, release date, etc), the recommendation also displays ALL the user contributed reviews associated with the game.

A Ranking view which presents a table of all games, with key information, including your review score and average user score.

A Game Console Overview, which presents important information about your chosen console platform. If you chose PS5, then you should have details of the difference between the standard and digital versions. If you chose Xbox, then you should have a comparison of differences between Series S and X.

Each of the views/pages should be hyperlinked together with some form of master page/common layout containing content that is present across all pages of the application, such as a global navigation scheme the layout of this navigation is up to you.

Functional Requirements:

Your web application should provide the following functionality to the user:

Provide a description, recommendation and supporting information on at least TEN GAMES for your chosen console. They can be any game that was been released on the platform before the hand-in deadline.

Each game should have the FOLLOWING CONTENT with it:

o An editorial recommendation (your own review) - this does not need to be more than a couple of paragraphs.

o A recommendation score (out of 10) the score you award is up to you scores DO NOT need to be unique across the games.

o A key facts section which provides details about the game (e.g. who created it, when is it released, what platforms/regions, what genre of the media, age rating etc.).

o Links to THREE OFFICIAL game reviews from an external review source (e.g. a magazine review/newspaper review/game review site such as IGN/Gamespot etc).

o The site should also support USER REVIEWS; these are reviews posted by users of the site. If there are no user reviews for a given game, this should be made clear to the user. The site should not support anonymous reviews. This data should be gather from logged in user (see profile system) stored in a JSON file.

o The user reviews should provide a rating for the game out of five.

Each game should also have a consumer information section which:

o Displays Three Online Retailers that sell the game, including a price, retailer information and direct link to the game on sale. You do not need to use the same retailer for all games.

The application should have a user profile system:

o As a minimum, the user should have to specify their username and password to log in.

o Users do not have to log in to view the content of the site, only to post reviews on games.

o When logged in, the users name should be displayed. This should be present the whole time they are logged in, regardless of what part of the site they are on.

o ADDITIONAL MARKS will be awarded for:

Storing information on the user (e-mail address, etc)

Profile Specific information (e.g. allowing them to pick a favourite game from the list of games or showing reviews they have made).

The application should have a ranking system, which displays all games as a table:

o You will also be awarded marks based on how informative and concise the table is (e.g. your choice of columns) as a minimum, it should include your Recommendation Score.

o Higher marks for being able to sort this table of information based on these categories and their rating.

o It is up to you how you determine the overall rating of a game based on the reviews.

The application should have a console overview, presenting useful information about your chosen console.

o This could be technical information about the console, the history of the console, current news related to the console.

o You can use content from other sites and multi-media sources to help present this information.

o If you chose PS5, then you should have details of the difference between the standard and digital versions. If you chose Xbox, then you should have a comparison of differences between Series S and X.

You should carefully study the Application Requirements before attempting the following sections of the report.

Section 2: Server-side Design.

o 2.1: Data Requirements Class Diagram: In this section, use a conceptual Class Diagram to present the server-side representation of your application data. representation required to populate the following web pages, you are expected to adopt an OBJECT-CENTRIC view of this data:

o The console games you are representing o The key facts associated with each game.

o The recommendation of the game (both content and score) o The external reviews associated with the game

o The retail information associated with the game. o A users own review and score of a particular game.

o The ranking system applied to the scores from the different reviews/recommendations associated with each game.

o The users profile.

Your diagram should specify any relationships (e.g. composition / aggregation / inheritance) that exist between these items.

o 2.2: Examples of the Class Data

Using the classes, you have derived in section 2.1, you should illustrate the data held by a typical instance of EACH class, you should provide at least TWO examples in each case. A common way of doing this to use a table, where the fields of the classes make up the columns, and the instances represent the rows.

o 2.3: Site Map: In this section, you should describe how the functionality of the application is split across a set of PHP pages and the purpose of each page. You should also illustrate the link structure of your site (how the pages are connected to each other, with examples of the data that is transmitted in the HTTP GET/POST Requests from one page to another (if any)). The Conceptual Web Site template in Visio, with some annotation on connectors, is suitable for this purpose.

o 2.4: Server-Side Logic Activity Diagram:

Use an Activity diagram to show the workflow for how the server generates the following page:

o Presenting the game editorial recommendation and recommendation score view of the highest scoring game.

NOTE: READ THE APPLICATION REQUIREMENTS CAREFULLY AND MAKE ALL THE DIAGRAMS ON HARDCOPY(PAGES) AND POST HERE, I WILL DRAW IT ON VISIO/ETC THEN