Unit 9 & 21 – Task 3 – U9-P2, U21-P2

Introduction

This document serves as the formal introduction into the information regarding what is required as per what is stated within Unit 9 & 21’s Task 3, with this document covering all of the task for P2 for both course units. With the introduction of this document there is difference with what is included over previous similar documentation, being that the emphasis of the information gathered is focused on the project as a whole rather than labelling past information with the past website form the client (as the basis). It is to cover the different areas of information obtained from a sent out form, which allows for us to not only meet the criteria for the course, but also record information to be used further into development.

With the collection aspect of this document it serves to hold all of the necessary details and information into one familiar and recognisable location. Not only for the purpose of analysing in a sequential process, but to create specification requirements for the client and website project as to meet what is needed. Part of the information gathered is based off of analysis of the existing website in order to determine what areas either show potential for expansion, or might require being created from the ground up. Said analysis is able to contribute towards different areas of this document, such as with viewing the current constraints of the existing website in order to prioritise areas that would most benefit the client with the proposed project.

Purpose

The purpose of the website project is to modernise and build off of the potential features present within the existing build of the website. When it comes to what modernising means for this website, it means with the inclusion of new standard features of website design that were either not present when the website was initially built (as well as those just starting to become standards). A significant example of this is with the use of responsive design over using the original static design to not only allow for adaptable viewing experiences, but allow for mobile viewing without constant zooming by the user. Aside from the features to be included within the new structure for the website, also means the redesigning of information since different areas containing text can be qualified as outdated or illegitimate.

Context

The context behind the state of the current website appears to be based from prioritisation into other areas during and after the websites original release, this is present with the absence of features and types of accessibility which are present in other outlets at their disposal. An example of this is with their linking their external social media which have had the same standard footer links to ‘share’ to them (Twitter, Facebook). However, whilst the social media have advanced with the platform it is present on, the website has had no significant updates in order to maintain that connect-ability.

With what the website project is going to be intended to be used for after it is completed, excluding the adaptation of design the functions are meant to stay the same. Them being the provision of information regarding the different functions of the charity (contact, location, history, ETC.). This would remain consistent with the history of the current website and all of the past build of the website, where the information has remained the same, only varying in quantity.

Assumptions

  • With the use of the gallery banner, there is nowhere that states if there is any existing assets in order to make the gallery, we assume that said imagery either exists or will made by them.
  • That the client is comfortable with allowing our website development team to select the colour scheme to replace the previous one.
  • Having the preferred design as “Modern” would mean something different for each team member, meaning that there would be the risk of varying interpretation.
  • That we would be able to implement all of the desired new features and functionalities whilst ensuring that each page within the website would be able to load quickly (including linking social media).
  • That all of the members developing the new website would be contactable at realistic times due to restrictions with the distance each member.
  • The client would allow for possible changes if the initial requirements are found to be unreachable, or unrealistic to the client end goal.
  • That the information from their website is to be copied over without any modifications, meaning that the client is okay with no work being done to the textual content of the website.

Constraints

  • Client Contact-ability – with how we obtain information from the client, we have to send any documentation through the manager of our college work experience. However, that means that there is a significant amount of reliance on that manage solely, which is further emphasised when considering that they are not present a majority of the time. Instead we have to utilise online communications (with varying results currently).
  • Time – since this website project is part of pre-planned work experience there is no restrictions financial, instead all of the restrictions with the development of the project into the new website are based around the available time to each member of the development team in terms of managing education and work.
  • Load Time – One of the central points of the client’s specifications are with improving the loading of the website’s pages. This could potentially become a constraint later in design and development due to the desired inclusion of other features, an example of this is with the use of Google Maps when displaying the differing locations present within the Community Centres & Environment Groups pages.

Functional Requirements

Navigation Bar, Site Map, Sub-Menu, Search Bar, Social Media Links, Contact Form, Header Title (Original), Embedded Hyperlinks, Download Attachments, Logo, Gallery

  • Contact Form – More Categories.
  • Gallery Banner – Use of a Gallery instead of a static image.
  • Search Bar – Less prominent.
  • Social Media Links – Use of Social Media Logos.
  • Download Attachments – Relocation of attachments.
  • Logo – Social Media Logo instead of text.
  • Sub-Menu – All of the download attachments are to relocated.

Assumptions of Functional Requirements

  • Site Map – They want a Site Map so they have one.
  • Embedded Hyperlinks – They want them to remain.

Non-Functional Requirements

Gallery Banner, Logo, Portability (Tablet, Smartphone), Responsive Design, Performance.

  • Performance – To load quickly.
  • Responsive Design – They acknowledge the problems with the current website.
  • Responsive Design – To allow for simple smartphone usage.

Assumptions of Functional Requirements

  • Responsive – The Design of the website would allow for Responsive.
  • Portability – All designs would allow for tablet use also.

Required Responsive Design

  • Having a dedicated smartphone view as opposed to only using a static form of the desktop view.
  • Shrinking the amount of icons present in the navigation bar as it rolls over into a secondary row, which not only compromises on the level of professionalism Big Local is displaying elsewhere. It also covers a piece of the banner throughout every page on the website.
  • The re-introduction of a dropdown menu with a newer system without complicating navigation (older navigation was found with research).
  • The movement of the login feature as with a smartphone viewing would most likely separate the content from the banner, possibly be moved to a separate location outside of the pages (such as next to the search function).