Navigation path

Interface and technical design

The purpose of the interface and technical design phase is to translate the site’s objectives into a visual solution and to define the site’s “look and feel”.

 

Description

This section describes in detail the different activities to be carried out in order to implement a site’s objectives and requirements, and to make sure that a created site “fits” into the EUROPA family. Many of the activities are classical design activities that concern the creation of discrete elements that express the objectives and vision of the site in concrete terms and elements. Here can also be found the various guidelines and rules in force with regard to the visual design, including a walkthrough of the standard templates and their various key constituent components.

 
 

Activities

  • Establishing precise page layout, page design and user interface design standards
  • Creation of illustrations, photography, logos, flash animations, and any other audiovisual content (collect the captions)
  • Rich Media Packages (RMP) and any other audiovisual content (collect the captions)
  • Acquisition of copyrights if necessary for third parties elements
  • Programming and scripting with CGI, ColdFusion, Java, XSLT
  • Customization of search functionality (Verity, thesaurus, indexing, search multilingual, collections, topics, HotPages, etc.)
  • Design and validation of accessibility features (WAI, etc.)
  • Design database, application including back-office system
  • Perform any additional necessary translations
 
 

Quality Assurance/ Evaluation criteria

  • Content proofreading
  • Pre-translation linguistic advice/editing by DGT.D.2
  • Translations proofreading
 
 

Inputs

  • Presentation Style Guide
  • Relevant standards (IPG, technical standards)
  • Relevant constraints (Data Centre, DIGIT, etc.)
  • Site specification
  • Detailed site design specifications
  • Specifications of user platform (browser environment. connection speed required, etc.)
  • Specifications of Web server resources needed
  • Programming proposals based on functional needs of the future site
  • Site “storyboard” , diagrams (site maps, thumbnails, outlines, tables of contents)
  • Content plan/schedule: detailed description of site contents
    (hierarchical list of all content (texts, picture material) by page; for each element identify who is responsible for supplying the content; deadlines)
  • Prototype(s)
  • Schedule for site design and construction
 
 

Outputs

  • Graphic design specifications for all page types
  • Site thumbnails, and roughs (Graphics/Interface deign Models, graphic design and interface design sketches)
  • Non-text content (Illustrations, Photography, other A/V, etc.)
  • Text, edited and proofread
  • Finished HTML template(s)
  • Finished examples of key pages
  • Interface design and master page precise layout
  • JavaScript scripts, Java applets, etc.