1. E. TECHNOLOGY REQUIREMENTS: (Product Technology)
1. Environmental:
 Describe supported hardware platforms, operating systems, database
management systems, network operating systems, for clients and servers.
2. Architecture implementation:
 Describe your styles and generations of client/server approaches, and future
direction. Discuss Two-tier vs. Three tier, and WEB approaches you have and
will be taking.
 Describe Open API's to commercial workflow products.
3. User interface:
 Generation of interface, modal/ non-modal. Current, and planned.
 Describe the range of technology interfaces currently supported. e.g. IVR
4. Application Development (AD) environment:
 What tools were used for the development of the product(s).
 What tools are available to customize and enhance the application?
 Which are standard tools (available on the market), and which are
proprietary?
5. Extensible application models
 Describe models to define the logical application, used to evaluate
functionality of data, to integrate, to make enhancements.
6. Application Management tools:
 What tools do you use for change management, software distribution, and
systems management? What tools are available with the product(s). Which
tools are standard (available on the market), and which are proprietary?
7. Preferred Technical Environment:
 We describe the desired technical architecture of a purchased application to
define a benchmark that will create evaluation criteria to measure the cost of
implementation and maintenance of al application system The intent of this
architecture is to ensure the maximum amount of robustness, interoperability,
and management of the application. In general, as we adhere to architectures
that we currently support, we lower the overall cost of implementation.

2. E. TECHNOLOGY REQUIREMENTS: (Product Technology)
 Following are three defined areas: Technical Components, Management
Components, and Application integration. For each item listed in each area,
respond and describe how your product matches/meets/fits the desired item:
8. Technical Components:
(a) Clients:
 Windows 95 and NT with 32 bit API
 Winsock network interface
 Standard development tool (Powerbuilder, Uniface, C++)
 DDE and OLE
(b) Server:
 Sybase 11.X
 Unix (HP-UX or AIX preferred)
 Trial Windows NT
 Netscape Commerce Server
 C
 PERL (for simple CGI and scripting)
(c) MiddleWare:
 Sybase database API
 Sybase Stored Procedures
 TCP/IP Socket Interfaces
 Secured Socket Layer
9. Management Components:
(a) Security:
 We must be able to adapt security architecture to changes in technology and
institution needs. We must be able to uniquely identify and authenticate each
user of the system and attribute actions in the system to individuals.
 System must allow the appropriate interfaces to their security components to
be able to adapt company specific security needs.
 Security must support Password Token Authentication.
(b) Version Control:
 Cellular One currently plans to use a distributed file server model for enabling
version control. New versions of the application are placed on strategically
located file servers and the applications are launched over a network.
 Installation components on the desktop must be kept minimal, and should be
packaged in an easy to use installer that is deliverable over the network using
WEB of FTP.
 The application should employ version checking to ensure the proper version
of the client is being used.

3. E. TECHNOLOGY REQUIREMENTS: (Product Technology)
(c) Performance and Problem Determination:
 The application needs to provide error logs, messages, monitors, and traces
so that functional and performance problems can be tracked, analyzed, and
action taken quickly.
10. Application Integration:
 Applications do not stand-alone. They interface with other in-house or purchased
applications. The application should provide mechanisms to define common
interfaces without modifying purchased code. A well-defined Applications
Integration Interface (AAI) will provide documented interfaces to address these
needs.
(a) Import and Export Utilities:
 The application should provide common routines to extract and import data from
other databases. These utilities should be written at the application level, not just
with database utilities, and should provide error checking and reconciliation
mechanisms.
(b) Real Time Interfaces:
 By stored procedures or server based code, provide a mechanism to invoke
standard routines when certain conditions occur, or provide these routines to be
invoked when conditions are met in other applications. E.g.: when action "A" is
taken on an employee, provide the ability to invoke a procedure that will update
other databases.
(c) Application Utilities:
 The application should provide a set of utilities to mange the application
information at the application level, not at the database level. Purging, archiving,
etc.