Report Requirements:
-
A description of the overall site that your group is planning with enough background context for your reader to understand what you are trying to do.
-
A summary of any background research into other similar sites, or useful technologies, libraries, or APIs that you have individually investigated with a description of how this has contributed to your group’s project idea and design. This can be related to the group’s site as a whole as well as for the specific feature you are responsible for in the group.
-
A list of the features/functionality in the group’s overall site and some discussion of why each is included. A clear description and discussion of the feature/functionality you will be responsible for in the group is required.
-
Site organisation and/or navigation tree diagrams with associated discussion and explanation of how your group plans to organise the pages that make up the site and how a user might typically navigate through those pages. Your diagrams can be combined if that is a useful way to present the organisation and navigation for your site. These diagrams may be hand-drawn and scanned/photographed, or created using any image/diagram software as you think fit. The diagrams and explanation you provide must include the specific feature/functionality you are responsible for, but they can also address site as a whole.
-
A sketch/wireframe/low/mid/high-fidelity prototype of an initial user interface for your group’s site and some commentary on the motivation for your design, i.e. how does your design address the feature/functionality for which you are responsible? You only need to include the design of the features/functionality that you are responsible for, but if you choose to include design for the whole site make sure you attribute the design to the correct individuals in your team. If your designs are hand-drawn then they can be scanned/photographed for inclusion in your report.
-
A project plan that demonstrates how you will organise your effort and time to achieve your goals. This plan can be presented in any appropriate form, e.g. a list of dates and tasks, a gantt chart, and/or a narrative description. It should include your personal plan to complete what you are responsible and an overall group plan. The group plan can be less detailed, but should give an indication that as a group you have discussed appropriate target completion dates for all parts of the project.
-
(Optional) As appropriate: any additional sections that you deem fit to describe your group’s project, with specific attention paid to the features/functionality you are responsible for. For example, if you have decided to implement a particular feature as an extension to the core requirements then this would be the place to report on it. Similarly if you intend to save data within the browser, then some description of the kinds of data that you intend to store, how you will store it, and how it will be structured, should be reported on.
Due Date: 3PM on Friday the 28th of April 2025.
Our plan is to create a text-based adventure web game where you awake in a forest and have to navigate your way to safety while avoiding the dangers of the forest. Each page will have a short paragraph to describe the scene, then we will use hyperlinks to other pages as options, this will be how you make actions as your character and progress your story. There will be a home page which will act as your start page where you can start your adventure, see credits, etc.
Possible websites to research:
- Options/ Game Elements
- Home/Start page
- Navbar/Navigation Links
- Javascript
- Headers and Footers
- Text Adventure Pages/HTML
- CSS
First Adventure Page
Death Screen
