Reference no: EM132858553

CMT656 Delivering User Experience - Cardiff School of Computer Science and Informatics

Learning Outcome 1: Understand users' needs and capture users' requirements and specification
Learning Outcome 2: Critically evaluate new prototypes and existing interactive systems through the user experience/user interfaces these provide.
Learning Outcome 3: Plan, design and prototype user experiences and user interfaces for a number of emerging technologies and interactive systems
Learning Outcome 4: Select appropriate evaluation methods, within an agile design process, to improve user experience and user interface designs, using qualitative and quantitative methods

Assignment

A website is due for a redesign. The client (your module leader) has asked you to take a look and find what changes may be needed to increase the usability, accessibility, and the interaction of the site. You will need you to justify why you suggest any changes, demonstrate the changes in a prototype and test the efficacy in benefits of the changes in comparison to the previous website. You are to produce a full UX report as deliverable for the client, which includes prototyping.

Individual marking and grade, teamwork is encouraged.

It is important to remember that you will be assessed individually for this coursework. However, you will be assigned to a team. This will help you to be able to perform activities that you may wish to do so, such as card sorting. Each team will also be paired with another to answer questionnaires and interviews. During lesson time you will be encourages to take advantage of opportunities:
1) to discuss and exchange ideas with your teammates e.g. a collaborative SDDP (Structured Dialogic Design Process) exercise.
2) for the team and individuals (on an opt in basis via a sign-up sheet) to have review time with the module leader.

Stakeholder Identification and Requirements

Stakeholders

Firstly, identify all the stakeholders with a description. Justify briefly why you chose these stakeholders.

Persona of one stakeholder
Choose one of your main stakeholders and bring them out in a persona.

Functional requirements
Once these stakeholders are identified you need to identify functional requirements. Be thorough. Requirements are vital to be identified early on as these will then act as the threshold of whether you have successfully been able to create a solution that solves the initial problem for the client. Therefore, once you identify the requirements, understand and mark which are the ones that will be needed for a minimum viable product (MVP) to occur. Label these with a unique identifier to be used later.

Non-functional requirements
Thoroughly identify the non-functional requirements and justify why these are needed. Label each with a unique identifier. Mark which ones will be needed for a minimum viable product (MVP) to be reached.

Data requirements
Thoroughly identify the data requirements for the project. Justify why these data requirements are needed and go into detail about what is needed and from where you will collate this information. Label these with a unique identifier to be used later. Mark which are the ones that will be needed for a minimum viable product (MVP) to occur.

Prototyping
Low Fidelity Prototype
You will need to produce a low fidelity design. You can use anything suitable that you would like to produce these, from paper and pen (scanned) to digital tools.

Remember that it is very important that your prototype fulfils the requirements and so you need to show why each component is there (use requirements to map them to the features) and, if there are more than the requirements-based components, to justify correctly why you added the components. Show the interaction capabilities such as screen transitions on this low fidelity prototype. Do not worry about the graphics but represent the interface correctly to the correct (low fidelity) degree.

Medium Fidelity Prototype
You will then create a clickable, interactive prototype. This prototype will require full interaction in terms of all the individual requirements and how they are implemented. All features should be functional. This is not to say if the database is supposed to have 300 clients you will need to create working profiles for each one of them, but a profile for one of them needs to be clearly shown to work with all the features. You need to show why each component is there (use requirements to map them to the features) and, if there are more than the requirements-based components, to justify correctly why you added the components. Describe the User Experience (UX) principles in detail on the decision you made to integrate good usability in the interface.

Attachment:- Delivering User Experience.rar