Information Technology Reference
In-Depth Information
Figure 4. A business solution for real estate agents
Much of the tailoring is done in design mode
and the changes made in this mode can very eas-
ily be made global for all users of VB, which is a
feature of VB's common base architecture. In the
beginning of the implementation process of VB,
the management and the application coordinator
discussed how wide the access should be. They
agreed to start with an open approach, by which
all super users had access to the design mode and
could thus save their changes globally in VB.
After a period of testing, the access rights became
restricted, and only the local developer and some
chosen super users were allowed this access right.
Having the access rights available to all super users
became a problem because not every super user
had the need to make their solutions global (shared
by all). In fact, when this feature was overused,
it tended to be disruptive to everyday work as
regular users were overloaded with functionality
they did not need. As it is now implemented, it
works well. However, this still depends on good
communication between those super users who
do not have full access rights and those who do,
such as the application coordinator.
the division of labor between the
different user groups and
developers
We see that the various roles of regular user, super
user, local developer, and professional developer
differ in responsibilities regarding EUD activities.
A typical difference is associated with multiple
access rights required when making changes
global as we just described. Another difference
is related to making the local changes. Regular
users cannot make persistent changes to the ap-
plication, but have the option to select only those
parts of the application they want to use, and the
super users help them in doing this because they
have a better overview of the VB functionality.
One super user put it this way when asked about
Search WWH ::
Custom Search