Concept: Representing Graphical User-Interfaces
var backPath = './../../../';
var imgPath = './../../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_qwxC8N7YEdmjRZts2c4ZjQ", "{0F994CCE-2B28-414A-9D31-DA23C13B95D4}", "1.9267995424810726E-305"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_QV4x0AISEdqTna4sZVFRow", "_kjFBYN7HEdm8G6yT7-Wdqw", "{351D0945-8FD3-458D-B514-E25E3B445264}", "1.9267995424810726E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qwxC8N7YEdmjRZts2c4ZjQ", "{0F994CCE-2B28-414A-9D31-DA23C13B95D4}", "1.9267995424810726E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_kjFBYN7HEdm8G6yT7-Wdqw", "{351D0945-8FD3-458D-B514-E25E3B445264}", "1.9267995424810726E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_mTMIkN7REdmjRZts2c4ZjQ", "{351D0945-8FD3-458D-B514-E25E3B445264}", "1.9267995424810726E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_vzRNgDIcEdqDs_9ORT1Rig", "1.9267995424810726E-305"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
Concept: Representing Graphical User-Interfaces
This guideline outlines a method for designing a GUI.
Relationships
Related Elements
Design the User Interface
Navigation Map
User-Interface Designer
Main Description
In systems in which there is a great deal of user interaction, it is often desirable to represent the entire user
interface as a single analysis class during Use-Case Analysis. These classes are, in reality, composed of many different kinds of other classes: buttons, windows,
menus, sub-panes, controls, etc. Using a single class to represent this complex collaboration is sometimes too great an
over-simplification. While a single class could be used, refining it as we go along, it is often easier to represent
this with a more encompassing concept, the subsystem.
In this case, a single class (or subsystem) was used to represent complex collaborations such as GUI interfaces due to
our limited design vocabulary. This class was regarded, in a sense, as the entry point to complex
collaborations, but it really was not a class in the real sense (it did not have a single well-defined set of
responsibilities, except in a very loose sense) and it often disappeared in the design process. In the end, one
discovers the real classes and collaborations, and distributes the behavior of each place-holder class to
them. Some of the work performed in Prototype the User Interface by the Role: User-Interface Designer when producing the Artifact: User-Interface Prototype may be able to be carried forward
and reused, depending on the nature of that prototype.
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
contentPage.onload();
Wyszukiwarka
Podobne podstrony:
design user interface?ABE09Frup user interface?signer1ECFC9prototype user interfaceL52E1A7prototype user interface?95CB55rup user interface prototype?0D4BBCrup user interface prototyper37E5AAUser Interface Service 2200SRM1131 (05 2005) US ENdesign user interface?2FDA9Drup user interface?signer979A5D2(eBook PDF GUI) Design Patterns as Tools for User Interface Designrup user interface prototype?21B1E2rup user interface prototypeX0984ADuser interface generalB3C0B9representing interfaces to external systems?6D84D3więcej podobnych podstron