The acquisition of an Enterprise–wide software system requires careful planning and execution of a multitude of activities unrelated to the actual software systems being deployed.

1. 1
A RESOUCE PAPER OF
ENTERPRISE–WIDE SYSTEM
DEPLOYMENT OF EDM SYSTEMS
Glen B. Alleman
3101 Iris Avenue, Suite, Boulder, Colorado 80301–1900
Copyright © 1999, Niwot Ridge Consulting, Inc.
ABSTRACT. The acquisition of an Enterprise–wide software system requires careful
planning and execution of a multitude of activities unrelated to the actual
software systems being deployed. This White Paper describes the various
components of these activities and the check list approach to discovering and
addressing the road blocks to success. Without consideration for all these activities
many of the benefits of the Enterprise–wide system will not be available
immediately. Taking a quotation from the familiar transmission repair
advertisement, you pay me now or you pay me later. The effort necessary to
successfully deploy and operate and major software–based business is the same no
matter how it is planned and deployed. The number of tasks and the
consequences of not addressing these tasks grows over time. It is therefore
advantageous to addressing all the tasks in the beginning to determine which ones
must be performed to assure the continuing success of the system.

2. 2
1 INTRODUCTION ........................................................................................... 3
1.1 MOTIVATION FOR THE WHITE PAPER ..................................................... 3
1.2 WHERE TO START..................................................................................... 3
1.3 OUTLINE OF THE ACTIVITIES ................................................................... 4
2 SYSTEM ACQUISITION PROCESSES ......................................................... 5
2.1 STAKEHOLDER REQUIREMENTS ................................................................. 5
2.2 SYSTEM REQUIREMENTS............................................................................. 5
2.3 SOFTWARE CONTRACTS AND THE ACQUISITION PROCESS....................... 6
2.4 PROCURING COTS APPLICATIONS .......................................................... 6
3 INFRASTRUCTURE........................................................................................ 7
3.1 NETWORKS................................................................................................. 7
3.2 SERVERS...................................................................................................... 7
3.3 DESKTOPS................................................................................................... 7
3.4 DATABASES ................................................................................................ 7
3.5 LEGACY SYSTEMS....................................................................................... 7
4 PERSONNEL.................................................................................................... 8
4.1 TRAINING .................................................................................................. 8
4.2 RETENTION................................................................................................ 8
4.3 SUPPORT .................................................................................................... 8
4.4 RECRUITING............................................................................................... 8
5 SYSTEM SUPPORT......................................................................................... 9
5.1 SOFTWARE CONFIGURATION CONTROL ................................................... 9
5.2 INSTALLATION AND STARTUP................................................................... 9
5.3 PROBLEM REPORTING AND TRACKING..................................................... 9
5.4 SOFTWARE QUALITY METRICS................................................................... 9
5.5 APPLICATION OF THE CAPABILITY MATURITY MODEL .......................... 9
6 PERFORMANCE ANALYSIS, PREDICTION, & MANAGEMENT.......10
6.1 PERFORMANCE TESTING...........................................................................10
6.2 PERFORMANCE MODELS ...........................................................................10
6.3 PERFORMANCE METRICS...........................................................................10
6.4 PERFORMANCE MEASUREMENTS AND MONITORING ...............................10
7 SYSTEM ARCHITECTURE...........................................................................11
7.1 FEDERATION OF HETEROGENEOUS SYSTEMS...........................................11
7.2 4+1 ARCHITECTURAL VIEW....................................................................11
8 OTHER IMPACTS..........................................................................................12
8.1 MANAGEMENT OF THE VENDORS...........................................................12
8.2 SOFTWARE DEVELOPMENT ENVIRONMENTS ...........................................12
8.3 IT STRATEGY IMPACTS ............................................................................12

3. 3
1 INTRODUCTION
This White Paper is a how to description for deploying Enterprise Wide software
systems. It is focused on identifying the multitude of activities that must take
place to assure a successful outcome.
1.1 MOTIVATION FOR THE WHITE PAPER
There are numerous papers and books describing how to acquire, deploy and
manage large infrastructure based computer systems. This White Paper makes not
attempt to replace or augment this material. The missing component in all this
information is a framework in which to add meaning for the Electronic
Document Management applications and their relationships to other enterprise–
wide applications
1.2 WHERE TO START
1.2.1 Why have an EDM System?
1.2.2 Attributes of EDM
An EDM System has a set of unique attributes not found an any other
enterprise–wide software application.
ü Management of the content – the information contained inside entities is as
important as the the information about entities. The author, publish,
distribute, and update cycle deals with the content of documents and related
information as well as about the documents themselves.
ü Long lived management activities – Archival duration ranging from decades to
permanent storage.

4. 4
ü Compound relationships – between the entities and the users of the entities.
Both parent and child relationships exist in the EDM domain. In addition,
aggregation relationships exist. These relationships place unique demands on
entity indexing and the management of change.
ü Regulatory requirements –
ü Workflow –
ü Infrastructure Foundation –
• ERP
• PDM
1.3 OUTLINE OF THE ACTIVITIES

5. 5
2 SYSTEM ACQUISITION PROCESSES
2.1 STAKEHOLDER REQUIREMENTS
The requirements for the system are defined through the meta–model show in
Figure 1.
Requirement Issue
ResolutionAssumption
Response
Assertion
Conflict
Structural
Interaction
Evaluate Position
1..n
1..n
0..n
0..n1..n
1..n
2
1..1
IsA
Figure 1 – Requirements Metamodel
2.2 SYSTEM REQUIREMENTS
ü Requirements management
ü Requirements traceability
ü Test generation

6. 6
2.3 SOFTWARE CONTRACTS AND THE ACQUISITION PROCESS
2.4 PROCURING COTS APPLICATIONS
2.5 PROJECT MANAGEMENT
ü Task management
ü Risk management
ü Budget
ü Software metrics
• COCOMO
• Reliability prediction

7. 7
3 INFRASTRUCTURE
The infrastructure needed to deploy an enterprise–wide EDM System is driven by
bandwidth. The bandwidth demands are orders of magnitude greater than that
needed by traditional mainframe based terminal applications.
3.1 NETWORKS
3.2 SERVERS
3.3 DESKTOPS
3.4 DATABASES
3.5 LEGACY SYSTEMS

8. 8
4 PERSONNEL
4.1 TRAINING
4.2 RETENTION
4.3 SUPPORT
4.4 RECRUITING

9. 9
5 SYSTEM SUPPORT
5.1 SOFTWARE CONFIGURATION CONTROL
5.2 INSTALLATION AND STARTUP
5.3 PROBLEM REPORTING AND TRACKING
5.4 SOFTWARE QUALITY METRICS
5.5 APPLICATION OF THE CAPABILITY MATURITY MODEL

10. 10
6 PERFORMANCE ANALYSIS, PREDICTION, & MANAGEMENT
6.1 PERFORMANCE TESTING
6.2 PERFORMANCE MODELS
6.3 PERFORMANCE METRICS
6.4 PERFORMANCE MEASUREMENTS AND MONITORING

11. 11
7 SYSTEM ARCHITECTURE
7.1 FEDERATION OF HETEROGENEOUS SYSTEMS
7.2 4+1 ARCHITECTURAL VIEW

12. 12
8 OTHER IMPACTS
8.1 MANAGEMENT OF THE VENDORS
8.2 SOFTWARE DEVELOPMENT ENVIRONMENTS
8.3 IT STRATEGY IMPACTS