Student Originated Software 1997-1998 Fall Quarter
		A Software Engineering Course at The Evergreen State College

Student Originated Software User Interface Case Study Assignment Fall Quarter, 1997 Version 0.2 Last Revised: October 29, 1997 Due: November 4, 1997 The career development program without a user interface would, of course, be userless and, therefore, useless. We must now begin to think about how the various users will interact with the domain model we've developed, the set of objects that constitute the world of career development. Abbreviated objectives: This document will basically consist of two things: What the user interface will look like; namely its screens, menus, and what-have-you and How the user interface will behave; the narratives or stories that describe what happens when certain interface features are employed. I'd like to see actual screen shots demonstrating that you've mastered (or are in the process of mastering) how to build user interface objects in Smalltalk. If your team is not up to this task, please include graphics that have been either drawn by hand or have been done using a graphics program. This document should be able to serve as a communication tool to show the customer what you think the system will look like. This tool is more useful to the customer than many of the others because the "look and feel," as well as the functionality addressed by the interface, will be the main determinant of customer satisfaction. It would be nice to include, as an appendix, preliminary drawings or concepts that your group used while developing the user interface.