|
Gatsby Design Assistant Versus Traditional Prototyping
Traditionally, designers have prototyped their database application interfaces with RAD tools such as Visual Basic, which provide a static a picture of what an application will look like. Gatsby Design Assistant allows you to take a completely different approach.
| Capabilities |
Gatsby Design Assistant |
Traditional Prototypes |
| Live and Fully Interactive |
Yes
Gatsby Design Assistant functional prototypes are live, full featured applications that allow testing of real world use cases.
|
No
You get only a static mockup of what the interface might look like.
|
| Dynamic |
Yes
Functional prototypes are dynamically built on the fly from the underlying physical database schema so there is nothing to build.
|
No
You have to construct the prototype manually.
|
| Adaptable |
Yes
The functional prototype is built directly from the underlying physical database schema so it stays in sync with your design.
|
No
Requires manual updates to reflect design changes.
|
| Role Aware
|
Yes
The functional prototype is built dynamically to reflect the security context of the logged in user.
|
No
You’d need to manually build a separate prototype for each role.
|
| Deployable |
Yes
With Design Assistant you have the option of deploying as a Web-based application with Gatsby Database Explorer.
|
No
With traditional methods the end prototype is either thrown away or implemented through considerable effort.
|
| Empowers Database Professionals |
Yes
Design Assistant takes advantage of business rules designed into the database.
|
No
These tools are focused towards programmers.
|
| Code free |
Yes
Design Assistant interfaces are created dynamically. Accessing the prototypes does not force the database professional to do any programming at all.
|
No
Even the simplest of these products require programming to prototype
anything more complicated than a screen shot.
|
|
Privacy
