Politics Mapper

Introduction

The ability to manage the project was essential in the development of Politics Mapper; we had to keep in contact with our clients, requesting feedback, whilst also organising ourselves and delegating team members in an effective, efficient manner. This section of our report details the delegation of work and the management roles of each team member.

Management

For this project, Anuz was our team leader and so it was his responsibility to maintain contact with our clients, organise bi-weekly meetings and to ensure the project was meeting deadlines. Esben was responsible for overseeing the back-end of the system being developed: the server, ElasticSearch instance and node app, while Reece was put in charge of developing the user interface and merging it with the web application. All team members contributed to reports, presentations and videos in relation to Politics Mapper.

Work Packages

Anuz

  • Graphical representation
    • Researched on timeline templates
    • Produced a timeline to display search results (not implemented)
  • Team organisation
    • Kept contact with client
    • Organised bi-weekly meetings with clients
    • Organised regular team meetings
  • Project report
    • Requirements background
    • Usability
    • User manual
    • Video of final product
    • Presentation

Reece

  • User interface
    • User interface mockups
    • CSS 3 for user interface
    • HTML 5 Bootstrap user interface prototype
    • Jade user interface for web application
  • Web application
    • Views: merging with the UI prototype
    • Routes: to allow querying from search bar
  • Project report
    • Coding of website
    • Population of website
    • Introductions to each topic
    • Development plan and timeline
    • Home page
    • Iterative design process
    • Project management
    • SDK and collaboration opportunities
    • Community forum
    • Requirements
    • Presentation

Esben

  • Search back-end
    • Defined system architecture
    • Wrote code for pre-processing and conversion of Hansard data
    • Wrote code for indexing of data
    • Integrated ElasticSearch into our product
    • Optimisation of search results
  • Server infrastructure and application architecture
    • Set up servers (installation and manage dependencies)
    • Defined server infrastructure
    • Defined architecture of application
    • Manage cluster on Azure
  • Front-end
    • Wrote major part of node application (with integration of Reece’s work on UI)
    • Interface front-end with backend
  • Project report
    • Architecture
    • Technical achievements
    • Design patterns
    • Testing and evaluation
    • System manual