Defining functional requirements based
on client type
If you have been asked to Web enable an existing Lotus Notes application,
begin by defining the functional requirements for browser access of the
One of the reasons for the term "rich clients" is because they
have a rich set of functionality. This is particularly true of Lotus Notes.
In contrast, Web browsers have been historically referred to as "thin
clients" and have lacked the feature set of client-server applications.
Web technologies have advanced. There are
now a number of frameworks that enable the development of rich Web applications.
However, it is still not possible to exactly duplicate all the functionality
of a Lotus Notes client application in a Web browser. Consequently, when
Web enabling a Notes database, it is important to determine what functionality
is required on the Web and how it can be implemented.
Most Web-enabled Lotus Notes applications do not have the same set of features
that are available to both Notes clients and Web browsers. For example,
the Lotus Notes interface of a help desk application may allow members
of the help desk to create and update trouble tickets. By contrast, the
browser interface to the same application may only enable authenticated
users to view the status of tickets created for their individual issues.
Before you begin Web enabling an existing
Lotus Notes application, you must answer the following questions:
- Will the users who currently access the application
in Notes be the same users who access the application on the Web?
- Will the users who access the application
with a browser require the same functionality that is available with a
- How will users access the application on
the Web? That is, will it be part of the corporate intranet or Web site
or will it be a stand-alone application?
answers to these questions will help you define the functional requirements
for the browser interface and assist you in creating use cases for design