You must create a website which, through the use of forms, enables the user to create a website suitable for documenting holidays.
The site created will have a homepage with links to pages, each of which documents a holiday. Using recognized design techniques you must think about the features which the users would expect of such a site and design them into the system. Remember, they wish to document their holidays, and not just create a collection of their pictures.
There will be two levels of access to the site: author and visitor. That is to say that there must be a facility on the homepage whereby the author can identify him- or herself and thereby add new holiday pages. Pages will be created interactively, but as a one-off process. That is to say that once a holiday page has been created it cannot be edited or deleted. Whenever a new holiday page is created the homepage will be updated to include a link to that page.
Anyone else visiting the homepage can access any of the holiday pages – but only after providing a passphrase. That is to say that each holiday page will have one passphrase associated with it, such that anyone knowing the passphrase can access it.
The intention is to provide a certain level of confidentiality. Pages should be accessible to chosen friends and family, but not to just anyone browsing the web. That is to say, that the website owner can distribute passphrases for each page to the people who they want to allow access. They may also provide hints so that the ‘right’ people can get access, but not strangers.
For instance, if the hint was ‘What was the name of the hotel?’ then anyone who was on that holiday should know the answer.
Author access is rather more sensitive: it should be impossible (or at least hard) for the casual visitor to get author-level access – and start messing with the site. The author password will be fixed and hardwired into the system. There will be no facility for the author to change the password.
Nevertheless, the site should be quite secure, so that the password remains confidential.
The system will generate HTML pages. There will also be a need to store image files associated with each holiday page. It will be sensible to create a clean structure for these files. It is also important that duplicate filenames should not cause any problems – in a manner that is appropriate for the specified non-expert author. Recall, that the names of image files in cameras are normally generated automatically.
Digital photographs straight out of the camera tend to be very large: fine if you want to print them on a poster, but they entail large file size. This makes them slow to move around. If authors are allowed to upload large images this will take a long time when creating the page – and again every time the page is viewed.
You should implement – and document – a suitable solution to this problem.
You must include a file called design.php in which you must show your design rationale, that you have used techniques and tools of user-centred design that you have learned to develop your design. You should show how you have moved from the requirements to the implementation, by way of wireframes, for instance.
You should also show how you have attempted to implement the specification. If there is anywhere that you have not been able to meet the full specification you must document why.
Your site should implement all the functionality described herein.
Your CMS site should be highly usable. You must show that you have carried out a Simple Usability Scale (SUS) evaluation of your site with at least five testers. You should present the results of this evaluation (in your design.php page).
You must establish the accessibility of your application and explain the techniques by which you have achieved an accessible system in terms of the following set of accessibility criteria. Note that these apply both to the pages that make up the CMS and the pages which it generates.