Software engineering project
12.2. Consider one of the following interactive applications (or an application assigned by your instructor):
-A desktop publishing system
-A computer-aided design system
-An automated course registration system for a university
-A library management system
-An Internet-based polling booth for public elections
-A home banking system
Develop a user model, design model, mental model, and implementation model, for any one of these systems. Regardless of the technique used to create the user task model, a model describing the users’ actions using the operators (keys pressed, mouse operations, menu selections, icon manipulations, commands typed) available in the proposed computer system should be built for each usage scenario. Also do a quick write-up on the system you’ve chosen and your initial thoughts on its design.
12.3. Perform a detailed task analysis for the system you chose in Problem 12.2.
12.4. Create a customer journey map for the system you chose in Problem 12.2.
12.5. Continuing Problem 12.2, define interface objects and actions for the application you have chosen. Identify each object type.
12.6. Develop a set of screen layouts and organize them into a storyboard for the system you chose in Problem 12.2.
12.7. Use a prototyping tool like PowerPoint or Keynote to create a prototype for the storyboard you created in Problem 12.6. Page links, form elements, etc. can make the prototype interactive. Feel free to experiment but this aspect is not required.
12.8. Describe your approach to user help facilities for the task analysis design model and task analysis you performed as part of Problems 12.3, 12.4, and 12.5.
12.9. Provide a few examples that illustrate why response time variability can be an issue.
12.10. Develop an approach that would automatically integrate error messages and a user help facility. That is, the system would automatically recognize the error type and provide a help window with suggestions for correcting it.
12.11. Develop an interface evaluation questionnaire that contains 15 generic questions that would apply to most interfaces. Add 5 more questions specific to your application.