Index - Software Development Failures [Electronic resources] : Anatomy of Abandoned Projects نسخه متنی

Index

C

Canadian Automated Air Traffic Control System (CAATS), 5

Capers, Jones, 31

CASE, 128

Challenged projects, a classification of failed projects, 9, 15, 17

Changing requirements

contributes to cost overruns and schedule delays, 138, 140, 143, 150-152

contributing to socioorganizational factor, 84, 93, 103-105

critical factor in project failure, 53, 58-60, 64, 65, 67

of large complex projects, 39, 40, 42, 44

minimizing effect in development project, 224, 225, 234

technical factor component, 111, 133, 134

Chikofsky, E. J., postdevelopment reviews, 195

Client-server architecture 26, 97, 129

Code of silence, breaking the practice, 154, 184, 253

CODIS, case study of failed project, 83, 84, 88, 89

analysis of contributing factors from user perspectives, 154, 156, 165, 171, 178-181, 183, 241, 250, 253

contributing socioorganizational factors, 92-94, 99-101, 103, 104

contributing technical factors, 111, 112, 120, 125, 132

economic issues of, 142, 148, 151

propositions of failure factors, 157, 159, 160, 162-164, 166, 167, 169, 171

Cohen, M. J., garbage can model, 183

Cole, A., on software runaways, 4, 8, 13, 17, 19-21, 42

socioorganizational factors contributing to, 51-54

technical and managerial factors contributing to, 121, 125, 132

Collaboration, in software development, 185, 189

Collett, S., on Hershey Foods' ERP project, 4, 24

Collier, B., postdevelopment reviews, 195, 196, 198

Collins, T., failed project cases, 88

Communication, in project team, 113, 117

among all project stakeholders, 174, 177, 181, 183, 185

problems in software development, 189, 234, 237

49, 50, 63. See also Total abandonment

Completion schedule, impact on software development, 222-224, 226, 228, 229, 230, 233, 235, 236

Complexity, of cofactors contributing to failures, 11, 12, 14

of software problem domain, 27, 30-34, 39, 40, 42

Computer-Aided Software Engineering (CASE), 128

Computer science, students of, 14

Computerworld, 131

Confirm case, 26, 177

contributing socioorganizational factors, 89, 93, 96, 100, 103, 104

economic factors contributing, 141, 142, 144, 149, 151

learning from, 227, 241, 249, 253

profile of, 84-86

technical factors contributing, 111-113, 116, 117, 121, 122, 125-128

Conflict model, 181, 182

Constantine, L. L., 36

Consultants, role in project development, 222, 225, 230-232, 236, 242. See also Project consultants

Continental Airlines, end user of DIA's BHS project, 91, 95, 103, 147

Coordination 185, 189

Corti, G., on risk and uncertainty, 37

Cost overruns, factor in software failures, 13, 18, 19

critical factor in software failure, 54, 60, 63, 65-68, 85, 96, 100, 104

learning from software project failures, 213, 221, 240, 246, 252, 253

major economic factor in software failures, 137, 138, 140-145, 148-152

risk of, 29, 31, 38, 44

Critical factors, life-cycle model classification, 56, 58, 64, 103, 111, 133, 134, 150

Curtis, B., large software projects study by, 93, 112, 113, 117, 126, 243-247

Cyberfile, 87