Project Proposal; Reviewing Existing Solutions (G2)
The purpose of this proposal is to summarize the problem domain, the existing interface or infrastructure, related interfaces of interest, and your plans on where to focus as a group. This is a critical step in the process, since it allows the instructor to ensure that the project is appropriate and to suggest changes if parts of the project are not appropriate.
Included in the proposal should be the following things:
- A description of the project problem domain. This description should answer the questions:
- What types of users will use this interface?
- What types of things will users try to accomplish with this interface?
- What context of use is relevant to the project?
- Will users be coordinating this interface with other tools?
- The names of at least two users who meet the following criteria:
- They must be people who actually do the tasks that this interface is trying to address.
- They must not be members of the project team.
- They must agree to spend time with you for user/task analysis and then later for user testing.
- A description of the existing solutions to the problem, with some discussion of each to explain why it is inadequate or why you can do better. Note: The fact that an existing solution is expensive, or works on a different platform, is not sufficient, since that would not require any innovation in the user interface, merely re-implementation or porting.
- A brief (1 or 2 paragraph) description of where your group wants to focus, and your particular strengths (as a team) in that area. It is not always necessary to do a complete design or application -- for some projects it will be most valuable to focus on a particularly difficult part of an existing system or process. If you have design ideas, a sketch can help here. When you're looking for an advantage, familiarity with the domain, with existing applications, etc., can all help you. Feel free to include a list of "out of scope" items, if you want to be clear in managing our (and your) expectations.
The grade on the project proposal will be based on the evidence that you understand the project, the existing solutions, and the project environment. Length is not a good indicator of quality; excessive detail often reveals insufficient understanding and thought. Poor proposals, and proposals for projects that are rejected as inappropriate, can be revised and re-submitted before our next studio.