App Development :: Projects :: Project Analysis
Due: Database Error
Problem
It is up to you to come up with a problem to solve with the project you develop in this class. You will follow the same steps to create this project that you did in User Interface Design, however.
User Analysis
Identify the characteristics of your user population. If you have multiple user classes, identify each one.
Task Analysis
Determine the tasks of the problem, analyze their characteristics, and answer the general questions about tasks from the Task Analysis lesson. Think about other questions you should ask that might be relevant to your particular domain. You should find and analyze at least 3 high-level tasks. For example, in a recipe site, the most central, interesting tasks might be editing a recipe, finding a recipe, and using a recipe (to actually cook). Every task should have a goal and subtasks. Some tasks may also need preconditions, exceptions, time constraints, and frequency of use.
Domain Analysis
Determine the important entities and relationships of your problem domain, and show them in a diagram (a problem object model or entity-relationship diagram). Include multiplicities where important. Include text that defines entities or relations that aren't obvious.
To gather information for the user and task analysis you must talk with at least 3 representative users who face the problem you are tackling (at least 1 from each user class, if you have multiple user classes). If possible, observe them dealing with the problem in their real work environment. When you write up your analysis, you must give us evidence that you interviewed and observed people, but don't provide a narrative of these sessions. Instead, offer your conclusions, and justify them when you can by referring to observations. For example, "grocery shoppers may be distracted by children; one mother was repeatedly harassed by her son to buy some candy." Also, don't identify the users you interviewed by name, unless you get their permission to do so.
What to Turn In
Turn in a Google Doc with the information required from above. If you provide links to outside resources such as your domain diagram, make sure Mr. Miller has access to those external resources.
Your Google Doc should include the following parts:
- Problem Statement: Briefly state the problem(s) that your project will seek to solve. Take the user's point of view. Consider what the user's goals are, and what obstacles lie in the way.
- Analysis: Write up your user analysis, task analysis, and domain analysis clearly, concisely, and completely.
