<Project Name>
User-Interface Prototype
Version <1.0>
[Note: The following template is provided for use with the
Unified Process for EDUcation. Text enclosed in square brackets and displayed
in blue italics (style=InfoBlue) is included to provide guidance to the author
and should be deleted before publishing the document. A paragraph entered
following this style will automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which
display a gray background when selected), select File>Properties and replace
the Title, Subject and Company fields with the appropriate information for this
document. After closing the dialog, automatic fields may be updated throughout
the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or
simply click on the field and press F9. This must be done separately for
Headers and Footers. Alt-F9 will toggle between displaying the field names and
the field contents. See Word help for more information on working with fields.]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms, and Abbreviations
3. Secondary Windows: Property windows
4. Secondary Windows: Other types
User-Interface
Prototype
[The introduction of the User-Interface Prototype provides
an overview of the entire document. It includes the purpose, scope,
definitions, acronyms, abbreviations, references, and overview of this User-Interface
Prototype.
The User-Interface Prototype captures the system
requirements that are not readily captured in the use cases of the use-case
model. Such requirements include:
·
Legal and regulatory requirements, including
application standards.
·
Quality attributes of the system to be built,
including usability, reliability, performance, and supportability requirements.
·
Other requirements such as operating systems and
environments, compatibility requirements, and design constraints.]
[Specify the purpose of this User-Interface Prototype.]
[A brief description of the scope of this User-Interface
Prototype; what Project(s) it is associated with and anything else that is
affected or influenced by this document.]
[This subsection provides the definitions of all terms,
acronyms, and abbreviations required to properly interpret the User-Interface
Prototype. This information may be provided by reference to the project’s
Glossary.]
[This subsection provides a complete list of all documents
referenced elsewhere in the User-Interface Prototype. Identify each
document by title, report number if applicable, date, and publishing
organization. Specify the sources from which the references can be obtained.
This information may be provided by reference to an appendix or to another
document.]
[This subsection describes what the rest of the User-Interface
Prototype contains and explains how the document is organized.]
[The primary windows handle the major interaction with the
user, and often contain an arbitrary number of objects. Primary windows are often considered to be
more important to the application since they need to provide extensive
usability. Therefore, development efforts tend to be more focused on the
primary windows]
[Briefly explain the context and the purpose of
this primary window; its interaction with the user]
[List the window objects, the related operation
that is performed when the object is selected and how the user can
interact with that object. The user must
be able to identify uniquely each object]
[Composite objects in a user interface are objects that are
visually composed of other objects. For example, a paragraph
is a composite of characters, or a complex drawing
object is a composite of more primitive drawing objects. List the main composites and the objects they
contain]
[Visual dimensions are:
position, size, shape and color. This
section is used to provide supplementary information about the window object.]
[Describe where the window usually positions itself and its
position attributes: movable,
scrollable, modal, floating, document, plain box, and parent (name the
children), child (name the parent) or orphan, etc.]
[Specify the default size of the window and its size
attributes: hideable, minimizable,
restorable, resizable, trayable, closeable, etc.]
[Specify the default shape of the window and if there are any
special shapes it can take]
[If using special color schemes reflecting importance in the
user-interface, list the colors, their use and their context]
[Include a screenshot sample if available. The sample can be scanned drawings (from a
paper sketch), bitmaps or other image formats (from a drawing tool) and
executables (interactive prototype). In
this last case, refer to the proper file package]
[Secondary windows are used to support the interactions with
primary windows by providing details (properties) about their objects and
operations on those objects. Secondary windows are often displayed by
navigating through primary windows, and not vice versa.]
[Refer to the Primary window section for information
on the subsections]
[In addition to property windows, there are other types of
secondary windows, such as dialog boxes, message boxes, palettes, and pop-up
windows.]
[Refer to the Primary window section for information
on the subsections]
[Specify the type the secondary window (other than property
window; these are documented in the previous section. Other secondary window types can be: dialog boxes, message boxes, palettes, and
pop-up windows, etc.]
[If the user-interface is based on any graphics standards,
specify the standards and constraints used]
[If using any other standards (i.e. personalization elements)
specify the standards and constraints used]
[Explain how the primary windows and secondary windows are
linked together along with applicable diagrams if there are any. If necessary, provide a navigation map.]