PowerDesigner Interface Models
20 May 1996 updated
Many of us have used stand-alone interface modeling tools in the form
of screen mock-ups (e.g., Dan Bricklin's Demo II). Some of us remember
using WordStar or a COBOL source editor to simulate text screens. Of course,
complete interface design involves much more than the static look of each
panel: menus, option keys ans shortcuts, event responses, parameters, messages,
etc.
Today most designers and developers would agree that rapid GUI tools
such as PowerBuilder, Visual Basic, and Delphi have combined the interface
prototype with the actual coding process.
Questions
- Is there any need for a separate interface modeling facility outside
the GIU programming surface?
- What about an abstract overview/road map of the interface navigation?
- Do GUI programming tools give sufficient visibility to events
and responses from the user perseptive?
- ???
- Very interested in object definition and reuse in prototyping - his
question was unclear. He can explain his vision.
Issues
- Once the process/data piece is more developed, we want the ability
to prototype.
Where to go from here:
© © 1996
Applied Information Science International