Page
37
downs for maintenance. Fore these purposes, they will require this
product to automatically set up an initial connection to the Internet so
that they can get step-by-step guidance / meaningful error messages
during system boot ups, clustering, hot-swapping, and periodic server
shutdowns. >>
<< User profile 3: Systems Engineers (SEs) who are familiar with
server technologies, but not familiar with Munix / MOON products.
Application: Will utilize this product's graphical user interface to
configure and test the product. They will use this product possibly as an
adjunct to Remote Procedure Caller (for Linux / Munix images) and
ConfigBuilder (for cluster design and server configuration). Device
monitoring will offer productivity improvement for this class of user,
making our products more compelling vis-ŕ-vis the competition…>>
5.2 Usage Tasks and Use Cases
<<For each of the user profiles specified in section 5.2, what are the
specific tasks that these individuals would participate in? What would
they be trying to accomplish, what would be the state of the system
before they begin their task, what input would they provide to the
system (required and optional input), and how would the system
respond? If applicable, consider tasks and use cases for people with
disabilities, either directly or in combination with assistive technology,
especially if the product is targeted to be sold to the US Federal
Government or Public Sector.>>
<<This section should be specific and detailed enough to help your
engineers to create the needed task flows and interaction
specifications (if applicable) for the user interface of the product or
feature. In addition, this will assist your testing group to develop
realistic test scenarios, as well as for the documentation group to
understand and document the product in the given scenario.>>
(Note: Use cases should reflect common tasks, and need not be completely
©2007 Franteractive Inc. All rights reserved.
