Application Development Methods

Instructions

| HOME |

Project management

Project process checklist

Teams

Form a project team (3 or 4 people) consisting of following roles by analysing the skills and strenghts of the team members. One person can fill two or three roles, if appropriate, but the team has to ensure that workload is equally divided.

a project manager who has the overall responsibility of the project, its progress and timeliness of the results. Ideally, the project manager is the most experienced person in the team, as well as has strong administrative skills. The project manager brings projects plans to the steering group and prepares progress reports.
a user representative who can be a complete novice in systems development. The user is responsible for conveying the wishes and requirements of the company to the project team, and participates in the development, especially in the user interface definition.
a visual designer
a user interface specialist
a systems analyst has responsibily for the structure of the system and the systems development process
a project secretary has main responsibility for the product documentation.
programmers for front-end and back-end development.

Project Documentation

Find the table of contents for a project description and a project plan and fill them in following instructions from the Methods page.

Final Report

The Final Report is a summary and assessment of your project work. It includes the following:

1. Description and assessment of the work process, its management and team participation.

2. Evaluation of the final product vis-à-vis originally set requirements. This evaluation has two viewpoints: that of the project team, and that of the client: would the result help the client in succeeding in its activities? If all original plans could not be realised, an outline for further developments can be included.

3. Evaluation of the project work, what was learned, and what should have been learned but was not. Problems encountered, and suggestions for developing the course. Be honest, this is a learning process.

4. Conclusions and recommendations for the future.

When writing the report and product documentation, be specific. Include a list of sources of the material (scripts, images, etc.) used and accurate process descriptions.

User centered design

Lecture: Introduction to the User-centered Design Process

User Experience and Usability

Psychology of Usability

User-Centered Design Process Map: http://www.usability.gov/how-to-and-tools/resources/ucd-map.html by U.S. Department of Health & Human Services

Describing personas: http://www.usability.gov/how-to-and-tools/methods/personas.html

Learning materials

Recommended background reading

Irmeli Sinkkonen, Hannu Kuoppala, Jarmo Parkkinen, Raino Vastamäki: Psychology of Usability. Edita Publishing Oy, 2005

Sampsa Hyysalo: Health technology development and use. 2010.

Usability:

Usability and User Experience Community of the Society for Technical Communication http://www.stcsig.org/usability/
EU sponsored usability site
Usability first site
User Interface Engineering company site

Task

Complete a small usability testing assignment.

XML

Introduction to XML

Standards:

Due Dates

Deliverables which are late or missing will be penalized. Due dates may be changed for compelling reasons. The students are responsible for making change arrangements with the instructor before the work is due.

Academic Integrity

Dishonesty is not part of academic and professional work. Dishonesty includes e.g.:

claiming the work of another as your own
stealing someone else's work.

To avoid any misinterpretations, make sure that all work that you hand in includes a list of authors: the team members.

Created by: Jaana Holvikivi
Updated: 24.1.2016