Appendix C (Continued)

Documentation consistency Specifying outcomes

Documentation detail Staff communication between project phases

Documentation method Staff knowledge and skill

Documentation process description Staff preferences

Documentation quality Staff skills

Documentation utility Staff turnover

Early involvement Staffing

Early testing Staffing turnover

Enterprise-level requirements process details Standardization

ER (data) model Standardized platform approach

ER diagrams Standardized use

Faith and trust Standards

Focus on overview Success measures

Formal information requirements Task accounting

Functional area Task complexity

Guideline design/process Team size

Hardware capacity Technology diversity

Hardware/software capacity Testing/quality assurance

Hierarchy chart Time, money

Hiring Tool investment

Ideal documentation approach Tool platform selection

Implementation issues with ER versus OO Tool use

Implementation of modeling Tools

Individual expertise and contribution Tools description

Individual performance Training

Information requirements documents Training methods

IT staff skill levels UML

Java provides some CASE tool functionality UML use

Java, OO approach UML/CASE tools

Leadership Uncertain situations

Learning / Improvement Universal development approach

Level at which business process documentation

occurs

Use

Linkage of requirements to technical models Use case

Management mandate Use of OO

Manual approach Use of packages

Master scheduling Use of UML

Matrix organization Use/non-use of UML

Measurement User characteristics

Meeting all requirements User contract

Mentors User expectations

Metrics User involvement

Modeling User liaison

Modeling formality User satisfaction

Modeling thoroughness User signoff

Modular training User survey

Multinational staffing User type

Narrowed features/simplification Value of CASE tools, difficult to measure

Need for developer – user communication Vendor experience

Non-OO design Vendor selection

Object /class diagrams Vendor staff turnover

Object diagrams Visual representation

Object-ERD Visualization of screens and outputs

On-line CASE tools Word document

OO Work expectations

OO Approach ----------------------

Ability to model system Project cost

Ability to provide documentation Project difficulty

Ability to provide modeling Project management organization

Adoption of UML practices Project management quality

Amount of risk Project management success

Application success Project organization

Change management Project outcomes

Client satisfaction Project process success (ease/flow)

Client satisfaction Project quality

Communication requirements Project success

Communication with users Prototyping

Component oriented production environment Quality assurance

Cost Quality of documentation

Design quality Quality of information requirements document/

Detailed user requirements Quality of packaged processes

Developer satisfaction Quality of tool use

Developer skills Quality of use of OO

Developer team communication Quick view

Developer-user communication Requirements documents

Development guidelines Reuse

Development model Role of analysts

Development outcome Role specialization

Deviation from standards Satisfaction measure -- questionnaire

Documentation Scalability

Documentation outcomes Scope definition

Documentation quality Scope problems

Documentation success Sense of closure

Documentation utility Skill development

Documenting business issues/decisions Skills

Ease of data retrieval for user Staff mentoring

Ease of learning OO Staff skills

Economic value Staff skills and knowledge

Effective tool use Staff training

Effort on documentation Staffing alternatives

Enhance knowledge base for project work Standardization

ER use Standardized platform approach

Extra overhead Standardized use

Formality of documentation State chart diagram

Formality of modeling State transition diagrams

Generating user feedback Subset of CASE tools

Information requirements success Success measure – fulfill all contracted

requirements

In-house use of CASE tool Sufficient modeling

Insurance against personnel loss System consistency

Integrating data and process views System use

Integration of development environments Technology diversity

Internal versus external staffing Technology diversity

IT role Tendency to use OO/UML

Learning curve Testing effectiveness

Maintenance Thorough modeling

Model use Tool use

Modeling formality Training

Narrowed features/Simplification Turnover

Need for analysis and documentation UML use

Appendix D: Concept List for

Dependent Variables (Effect)

Need for requirements documentation UML use (sequence diagrams and use case

diagrams)

Need for specific tool Use case

Obligation satisfied Use levels of ER

On-line CASE tools Use of DFD and ER

OO Use of modeling

OO project management Use of OO approach

OO skill development Use of sequence diagrams

OO skills Use of use case

OO success Used for development

OO tool use Used for testing

OO use Usefulness of models

Package customization User participation

Package stability User requirements writing

Pattern of modeling content User satisfaction

Performance User understanding

Pressure for IT personnel to perform Version control

Problem understanding Visualization of documentation

Appendix D (Continued)