graphical overview and prototype
4. graphical overview of the system and a prototype of the interface
In this assignment, you will make your design decisions concrete. They will be documented in three forms:
- a "map" of the system architecture,
a prototype of all or a portion of the system,
- the prototype will instantiate all or portions of your design
- the prototype will be demonstrated in class (and the demonstration will be 30% of the grade for this component)
- and system documentation of your system
The fourth component concludes with a system documentation of your prototype. You do not need to follow the sample outline strictly, but it does give you some idea of the material that should be covered.
Sample Outline, System Documentation
- Conceptual Model
- System scope
- System goals
- The Users of the System
- Definition of the target audience
Summary data on characteristics of the target audience:
- physical characteristics
- knowledge and experience
- computer/IT experience or knowledge
- level of experience with the task
- psychological characteristics
- Two or more personas
- The Task Being Supported by the System
Some combination of a
- hierarchical task analysis
- structure chart
- or GOMS model focusing on user goals
and a set of use cases and scenarios
- a complete set or used in conjunction with other documentation tools
Description of additional salient job/task characteristics
- Task description Some combination of a
- Interface Design Decisions
Major design decisions and the rationale for each
- 5-6 of the most important decisions)
Basis for rationale may include
- informal user studies,
- research results reported in the literature,
- or guidelines provided in the literature
- Major design decisions and the rationale for each
- Interface Design Description
- User environment design or state transition diagram
- Additional notes documenting the interface description
- one copy as a “running” version, if available;
- second copy as .pdf
If you are considering a web site, you might want to consider looking at this circa 1999 model of what a system description might look like. Yours does not have to include everything you see here, but you might want to think about whether or not your system description fully describes the system you have designed.
If you are considering a standalone system, this different, and more recent, system description might provide you with an example of what a fully developed standalone system task might look like.
Mobile apps are becoming more important. If you are considering an app, this recent example of a system description might provide you with a better example of what a fully developed mobile app task might look like.
To provide something that may be useful for your peers to evaluate in task 05 the system description should be the total package.
Include in it your user analysis,
your task analysis,
your design decisions,
your graphical overview,
and your prototype.
If you were not fully satisfied with how you did on any of the earlier components, this is your opportunity to make the necessary changes to make any or all of the earlier components better.
This is the version that will be graded. The entire package should be turned in, by sending the instructor an email note which will include a URL link to the place in your web storage space where you have saved the document. It should be a single document (in pdf, Word, or similar format). You may point the evaluators to a "working" prototype if you wish, but all screen views should also be available in the documentation package.
This task is due after your prototype demonstrations,
by 2359 hours on Monday, 11 April 2016