Appendix C: Concept List for
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67
68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84
85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101
102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118
119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135
136 137 138 139 140 141 142 143 144 145 146
Independent Variables (Cause)
Ability to translate to other language/culture OO definition
Abstract thinking OO design
Active document management OO programming language
Activity diagrams OO tool use
Adding requirements into package code OO use
Addition of consultants Org strategy
Additions to package Organizational computing outcome measures
Adoption of standards Outcome measure
Analysis Outcome measure (defects)
Analysis process, descriptive Outcome measure (usage)
Application of OO throughout project Outcome measures
Application type Package customization
Architect correctly Paper prototyping
Architecture level Pattern of modeling content
Asset management Paying for changes to specs
Attention to user Performance
Bugs Personalization of training
CASE tool use Phased development with multiple leaders
CASE tool use (Rational Rose and Visio) Physical arrangement
Change management Procedural programming skills
Change management process Process mapping
Change processes Process time
Class diagrams Project domain
Class models Project management
Class or Object Diagrams Project manager people skills
Clauses where requirements not fulfilled Project manager technical skills
Communication Project objective, measure of success
Communication Project outcome measures
Conflicting assignments Project size
Consistent modeling Project size
Consulting firm Project staffing
Cost Project staffing
Cost center Project success measure
Cost per transaction Prototypes
Culture Prototyping
Customer knowledge base Quality assurance
Data modeling Quality of architecture
Data services layer Quality of contact with users
Database tool Rapid evolution, many changes
Decentralization Rational Rose use
Defined requirements Rational Rose/UML
Demands on staff versus actual capabilities Reduction of technical “holds”
Description of analysis process Relationship of DFD to ER modeling
Description of anticipated development
environment
Requirement specification
Descriptive, communication tool Requirements
Design processes Requirements determination staffing
Developer acceptance Requirements Gathering
Developer coordination Reusability
Developer preference Reuse
Developer skills Roles of implementation and domain models
Development environment Scalability
Development staff skills Scope creep
Development tasks Self-training