Evaluation & Learning Outcomes

This will be the final Blog post as part of The Magna Carta Translation Application. Today we have finished and handed over the project to the client alongside this we are concluding the assignment in terms of submission of all appropriate material.

We started this project back in March where we was introduced to the design brief and project requirements. Since then we have developed as a group/agencies learning skills that will be vital to progressing into the same client based projects outside the university. Starting with no prior knowledge of applications, how they were developed or the work that needs to go into producing a successful application, delivering the application shows how far we have come.

Completing the application has allowed us to gain swift coding, design, client communication, team working and documentation skill in connection with a client lead project. Throughout the project we have tried to remain transparent by communicating information, issues and requirements to the client as to keep the project as progressive and slic as possible.

Our Application

The Final Application we feel has been a huge success. We have achieved many things we didn’t expect to from our outset, initially we were sceptical about producing and information based application however this made us focus much more on delivering a professional application for the client.

With clear communication and presentation the the client we proposed and application that they felt fitted a very functional and specific requirement. Initially there was ambitious ideas thrown around by the client that we framed proposing and application that fitted both parties expectations and needs. One main achievement was overcoming a client proposed idea of The Magna Carta image as a form of navigation between clauses with the document. We initially felt this was slightly ambitious as our knowledge of Swift and application programing was very basic but with some support from tutors we managed to formulate an understanding of Swift which then allowed us to create this application.

Some other successes with programming was gaining and understanding of iPad specific application building and Split View Controllers, that allows 2 different types of view controllers to run within a single view. This is something even the tutors were mystified by initially but we managed to negotiate it well creating a useful feature of the application.

Working With Live Brief

Creativity and Professionalism is part of any client based interaction work no matter the product in production or timescape of project. Creativity is need  throughout all aspects of the project weather is designs, innovative ideas or pitches/discussion with clients. Creativity not only is the ability to produce ideas Remaining professionally throughout the project even when tricky and potentially problematic situation arose. Client negotiation is one situation where we had to remain professional, taking on board their ideas and feedback working with them to develop a product that they wanted and we could build successfully. Secondly when issues surrounding content and from the cathedral and 3rd party sources it was essential to remain professional and taking control of potentially problematic situations.

The Team

As part of a team we have work effectively and efficiently through good communication and organization of the work and timings. Using a social media site we were able to communicate effectively to each other gaining quick responses from all members of the team. Because of it ubiquity meant all members were quickly notified of discussions and organisations of meeting meaning workflow wants hindered or disturbed but miscommunication or un attendance as a point of contact was readily available.

Facebook Group
Facebook Group

Trello was used in organizing the workflow and delegation of tasks similar to that of a scrum board. all members had access to a live scrum board where they could interact with tasks that needed to be completed within the project. This highlighted if there was any issues or backlog with work as it was regularly checked and assessed by all members of the team.


Google Drive was used to shear and distribute files between members of the group, Being able to upload revisions of files ment there was less confusion and the the project documents were kept in the same place.

Google Drive
Google Drive

A Git repository was used in the development of the application also to track the development of the application, allowing merging between programmers files and back logging where needed. The git repo additionally gives any developer who needs to pick up the application after handover the ability to see how it was made and where specific changes took place. This is a great form of documentation for the client as it gives them a breakdown of how the application was made and the process that went through its development.

Keeping to Guidelines 

During the project there was a series to guidelines of which we had to follow and be aware off.  Firstly the design guidelines given to us by Salisbury Cathedral and RedBallon that we had to keep to pedantically making sure we always referred to there style guidelines. These outset design guidelines were colour, font and style based and it was necessary to keep to their exhibition they have recently built tieing the application and exhibition together.

Secondly keeping to apple guidelines with programing and styles of elements within the application. Specifically we looked at the design guidelines paying particular attention to sizing, icons and gestures that meant the application fitted smoothly within an apple device using its ubiquitous apple.


Through this live brief we have produced professional application fitting clients requirement learning lots of vital skills along the way. Handing the application over to the client now it will be great to see it working within the desired location helping and informing tourist visiting the Salisbury Cathedral for filling its purpose.

The Final Push

We are heading into our final week of the Magna Carta Application development for Salisbury Cathedral. This week, we have a lot of finishing up business to compete with the application and blog from all members of the group.

Trello has been used throughout this project to specifically to control the groups workflow however, coming into the final stages it’s now more specific tasks that need to delegated to members of the team. An openly available document on a team Google Drive folder or the Group connected social media group has become essential for quickly communicating tasks to members when away from group meeting.

Currently list heading into final week:


  • Fix the fatal error getting the filters to work
  • Get the final colours sorted out
  • Put the app icon in
  • Make and put in the splash screen
  • Add category for hidden details.
    • Get Kayley to make icon
  • Put the right details and get new shapes for the hidden details.
    • Put the Hidden Details icon in
  • Maybe show which category is selected somewhere
  • proofread the clauses – names, categories etc.


  • How the programming meets the learning objectives
  • Make videos of the app working to blog about
  • The animations (Spring, fade, etc)
  • App icon and splash screen
  • Debates about swift (why we used it)
  • Hidden details category
  • make a video of a user interacting with the app


  • Gather all the project files
  • Make the file tree in a single directory
  • Make readme files for the directory
  • set up wordpress on Dakar
  • copy wordpress content to new blog
  • create index.html page as a directory for our project


  • Draw up final designs – blog about them
  • Make a nicely annotated final design with as many details as possible
  • Blog about meeting the learning objectives with the design process
  • Make the icon for the hidden details
  • Edit the money icon (possibly others)

We are aiming to get all these tasked finished with a few days to spare giving everyone time to assess each other’s work before the hand it to the client. This will mean we can ensure the app and blog work is to the high standards expected throughout the project.

Individual Weighting Factor

This project will be assessment on 2 factors. The application and written elements on the blog will be a group covered mark where each member will receive the same mark. A second mark designed to differentiate members within group will be added to the group mark. In previous projects this has been done through a CASPAR system where members got to mark each other member in private. This cause a lot of problems as some people did not submit there evaluations of other members of the group.

Individual weighting factor could be considered a far more specific and tailored way for each group to designate/assigned weighting factors to each element or individuals contribution to the project. “A modified pool allocated to a fixed pool of marks or points. This allow the students to allocate marks freely and then calculate an individual weighting factor based on the ratio between the individual score and the average score for all members of the group.”  (Conway et al, 1993). This is applied to a predefined group assessment criteria which can be outset by the assessor or in our case the group itself.

We have set out a set of 4 criteria’s for the individual weighting factors in which each factor was possible to fully meet by all members. We felt that basing them on aspects of the applications development and the project itself allowed all members, no matter designer, developer or manager could have had involvement in each

Individual weighting factors

1. Attendance and contribution to discussion (group meeting)
2. Meeting responsibilities and keeping to workflow (trello)
3. Blog performance (the BLOG)
4. Production Process (app Production design and development)

Attendance and contribution to discussion (group meeting) – this allowed us to focus on general project contributions like attending outset meeting, expressing opinions and thoughts at the meeting and being able to articulate one’s self to the group discussions. We felt this was necessary as in group projects members sometimes can hide away and this could push these individual forward to express themselves more if they know their grade will depend on it.

Meeting responsibilities and keeping to workflow (trello) – Trello is a project management system we are using to deal with projects work flow and which is discussed in a previous post “Scrum & Sprint Boards” how the group are using this.  For this assessment factor we felt that it should be considered how members engaged with this and the effect it had upon the group.

Blog performance – Considering the writing factor of the blog is key to the project as it’s the main product for assessment to final mark of the project. We need to not only look at the amount of writing but the quality of it as well and if it helped towards the development of the application and project.

Production Process – the production process will look at the application development in terms of designing, swift development and content production.

As a group we feel that the individual weighting factor is an effective way to assess members within the group fairly distributing them evenly depending on the participation and contribution towards the project. When the project we can give a conclusive summary of how effective it was.

Mick Healey “Developing Student Capability Using Peer and Self Assessment: A Preliminary Evaluation of The Distribution of a Pool of Marks Technique for Assessing The Contribution of Individuals to a Group Project”, Using Assessment to Develop Capability conference, 1993. 1 http://www-new1.heacademy.ac.uk/assets/documents/resources/heca/heca_as06.pdf