Development of ISPCC Childline Website


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Development of ISPCC Childline Website

  1. 1. Development of new Childline website 2012
  2. 2. Steps to creating a website
  3. 3. DocumentationSpecification This document describes in great detail the different roles of users that will use the website: -children -volunteers- to engage children in conversation, to record information/ details of engagements -supervisors- to set up volunteer accounts, to monitor best practice on chats both live and historical, to collect data for stats etc -administrator- to edit and maintain
  4. 4. Different roles involve different Different roles involve different responsibilities, tasks,responsibilities, tasks, and access tohad and access to different parts of the site. All thisdifferent parts of muchsite. All possible to to be to be explained in as the detail as this hadexplaineddevelopers provide a detailed breakdownto enable the in as much detail as possible of costs and timelines.enable the developers provide a detailedbreakdown of costs and timelines.
  5. 5. Costs Evaluated with developers and price and payment schedule negotiatedPrototype This document creates a wireframe of the site from the specification document provided and allows those not familiar with specification documents a clearer picture of how the site will be created, what page goes here, what page goes there.
  6. 6. Functional Specification This document goes hand-in-hand with the prototype. It is a re-worked version of the original specification document and in addition allows you to see how the site will work functionally; you can go back and forth between the prototype- to see how the site will be laid out- and the functional requirements document- to see how the portion of the site you are looking at in the prototype should work. Once this document has been completed and it meets the original specification, it will be used by the development team as a template for creating the site.
  7. 7. Design Moodboard - this is a 1-2 page document showing colour palette suggested by the design team based on the type of site and interaction required. It also details the level of use of each colour, where the colours will be used, the fonts, the shape of buttons, highlighting, etc. Mock-ups of different page types - The different page types detailed in the functional specification are mocked-up using the design ideas from the moodboard. At this point we sought feedback from children in Dublin and Monaghan about the design choices.
  8. 8. Development Converting the functional specification into php code, and creating the images and stylesheets necessary to give the site the correct look together with the functionalityHosting requirements Deciding where to host the site, ensuring the server is capable of handling thousands of simultaneous conversations
  9. 9. Testing• Checking each line of functional specification against the implementation.• Test the roles for all user types in various scenarios.• Ensuring that the hosting server is capable of handling thousands of simultaneous conversations, so that we are future-proofed.• Purchase a Verisign SSL certificate to provide strong encryption for the site, apply and test to ensure it doesn’t break the chat functionality.• Plan the deployment and go live strategy- to ensure a smooth transition between the old site and new site; to extract data from old site and import into new site between shifts to ensure no data loss; to guarantee that only the new site is visible when we go live (relates to the 48-hour that it can take for all DNS servers worldwide to reflect the changes to the repointing of the website IP address)• Upload & format all content
  10. 10. Go Live• Creation of manual for volunteers and supervisors• Training given by development team to supervisors• Training given by supervisors to volunteers• Website goes live