Working in a small team or individually, design and code a delightful user experience. Follow a rapid application development approach. You can either use (1) a system concept from a previous MIS class or (2) use an entirely new business and system concept.
For example, the project can be connected to the MIS 4596 capstone project, or a project in MIS 3502 or MIS 3506. Discuss these options with the instructor in advance.
Use one of the following technologies in the project:
- An interactive website using the Genesis framework on WordPress
- A CSS framework such as Bootstrap.
- Origami Studio
Project proposal and team members
- Form a group of 3-4 people or chose to work on your own
- I recommend forming a team by (a) looking for team members who share complementary skills.
- By the project proposal due date on the Owlbox folder for your group (see below), submit a Word document that contains (a) project title, (b) full names of team members, and (c) a project proposal with 3 simple paragraphs as follows.
- Overview: Provide general context of the organization or domain (2-3 sentences).
- Problem Statement: What is the problem? (2-3 sentences)
- Opportunity: How will you approach the problem (2-3 sentences).
- Submit all project related documents via Owlbox. Create a new folder in OWLbox called UXDesign_LastName1_Lastname2_Lastname3_Lastname4 (i.e., the last names of each team member) OR a professionally relevant name for the group. All team members plus your instructors should have access to this folder.
- Share all project related material in this folder. As the term progresses you will also post documents and other updates inside this group. The instructor(s) will from time to time visit the group and provide feedback.
Required project activities
The project should include the following activities. The word ‘activity’ denotes that these are recurring and recursive processes, they are not stages. Please submit documentation and the result for each of the major activities of your project. This means that for example in activity 1 you will be submitting the problem statement, for activity 5, submit the five evaluation results.
- Activity 1: A problem statement
- Identify the key situation of concern, why is it necessary to fix it?
- Activity 2: The experience model
- Pick an appropriate method to study the user(s), justify the choice, document your work, and prepare a summary of what you learnt from conducting the user study.
- Model the relevant activities of users. The model could be a list of key steps, a diagram, a series of pictures; whatever works best to capture the key tasks your users will perform.
- Establish the design requirements including the interaction model and system concept. The interaction model is driven by the underlying target device. For example, the interaction model is ‘graphical mouse driven’ for a website designed for desktop computers, it is ‘voice’ for an Alexa based skill. Or it may be a combination of mouse, touch, keyboard, voice for a general purpose application. The system concept is the combination of software and hardware and how you envision it combining together to engage the target users.
- Describe the associated business model that will drive the above interaction model and system concept.
- Activity 3: Design the system
- Pick an appropriate form factor (e.g., mobile, virtual, device, desktop).
- Sketch the preliminary interface.
- Activity 4: Build the system
- Use the prototyping method for constructing the system.
- Activity 5: Evaluate the system
- Evaluate the system a minimum of five times, i.e., provide the results of five different sequential evaluation processes as you refine the design.
- Identify the strengths and weaknesses of the final user experience using the course concepts, specifically Norman’s framework.
The draft submission should include a status update on all of the above activities and the following components:
- A solid problem statement
- Plan for the user study, user model, and preliminary results
- Preliminary set of design requirements including the selection of the design tool
- Preliminary business model
- Selected form factor
- Screen prints of the current version of your solution
- Evaluation plan
Submit the above as a Word or PowerPoint document.
Status reports in class
The team will frequently provide status updates in class. The status updates are informal and free flowing with no set time length or format. The goal of each status update is to:
- Demonstrate progress
- Get help on problems
Use Word or PowerPoint for the updates. If you are working in a team then one team member will present the first time, and the next team member will present the second time, and so on.
Submit a Word or PowerPoint file that includes all of the above required project activities.