Wednesday, April 18, 2012


Software and Hardware£1,500
Evaluation Costs£600
Staff Costs£25,535
Estates Costs£6,294
Indirect Costs£27,611
Grand Total£60,560


Failure to appoint RASevere (5)Very Low (1)5Ensure appointment is well publicised internally and externally; identify appointable candidates in person (City has many graduates with relevant experience)
Failure to recruit participantsBad (4)Low (2)8Use established interaction laboratory user panel if required; give participants £15 compensation.
Data LossBad (4)Low (2)8Use Subversion server for continuous version control and backup on RAID server; Regular backup schedule to external storage.
Changing Software/Hardware IssueModerate (3)High (4)12Ensure compliance with official APIs, avoid use of APIs under known threat of change or redundancy.
Server unavailabilityBad (4)Low (2)8
Ensure second tier server backup availability with Informatics Technical Support Team.


Work Package 1 (WP1): Initialisation (4 weeks)

This work package will develop the foundations for the mobile app infrastructure, moving the existing Learnmore content and index into mobile form. WP1.1 will focus on understanding the context of use, so that we can understand which content to prioritise, while WP1.2 will focus on the technical design, identifying any technical limitations for the overall design and creating an overall architecture for the underlying software.

Work Package 2: Prototyping (5 weeks)

We create one or more prototypes (WP2.1) and get initial feedback from initial trials with users (WP2.2), before undertaking some basic development work on an app (WP2.3).

Work Package 3: Development Phase 1 (5 weeks)

Building on the initial software prototype (WP2.3), the main code for the App is developed (WP3.1), while a long-term content policy is developed (WP3.2). First-cut usability trials of an actual app are undertaken to ensure that the design matches the user expectations identified in WP2.2.

Work Package 4: Development Phase 2 (7 weeks)

Final coding and testing leading to the final app (WP4.1), will be followed by field and lab testing (WP4.2). In parallel, we will refine the content strategy (WP4.3).

Work Package 5: Documentation and Dissemination (ongoing)

Throughout, we will document the App's development, the user personas and other materials that could be reused for designing other mobile apps, and the parallel organisation of a content strategy. These will be disseminated internally and externally. 

Project Team

The team on the Learnmore Project are:

George Buchanan: Project Leader, managing the day-to-day running of the project and providing guidance on app development and interaction design.

Sam Muscroft: Developer, development of the iOS app and interaction design.

Emily Allbon: Content Management, tailoring of Learnmore content and selection of appropriate content for the mobile app.

Sanmeet Kaur Dua: Domain Expert, selection of content, expertise on the needs of Law students.

The Learnmore Project

Aims and Objectives

The Learnmore project is taking an existing resource for Law students - the Learnmore part of City University's Lawbore website - and reorganising and representing the content for a mobile audience. Our aim is to create a compelling mobile learning resource for Law students, that can serve as an archetype for other mobile content projects at City University London and elsewhere.

We will be testing our success by a series of formal and informal usability studies run at City University's Interaction Laboratory. Successful navigation of the content, and high user satisfaction ratings will indicate that our mobile app is an effective means of providing students with mobile content.

Project Outputs

The specific output will be:
  1. A generic iOS (iPhone/iPad) program for housing Learnmore and similar content on mobile devices.
  2. A working Learnmore iOS app with the Learnmore content
  3. A content strategy for similar projects at City University and elsewhere