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

Index

S

Saarinen, T., 162

SABRE, 86, 113

Sage, A. P., 160-162

SAP software

use in FoxMeyer's Delta project, 86, 90, 94, 97, 101, 102, 114, 118, 122, 123, 129, 130, 145, 146

use in Hershey Food's ERP project, 24

Sauer, C., IS failure study case by, 13, 51

Schedule delays

contribute to software failure, 60, 63, 85, 251

factor in software failures, 13, 18, 19

risk of software projects, 29, 31, 38, 44

Schmidt, R. C., software project risk, 180, 181

Senior management, 14

role in CODIS, 153, 157, 158, 164-169, 171, 175-177, 179-181, 184

role in postabandonment review, 213

role in project failure and aftermath, 243, 245, 246, 248-250, 252

role in successful project outcomes, 223, 224, 227-230, 233, 235

Senior management involvement, 156, 159, 176

Senior management support, 212, 229, 230, 242

Siebel Systems, 24

Sillince, J. A. A., 234

SIM. See Stakeholders Interaction Model

Simon, H. A., hierarchic design, 31

Slinger, Walter, DIA's BHS project chief engineer, 119, 120, 147

Social dimension, 73, 80, 83, 107, 133

Socioorganizational factors

contributing to software failures, 6, 14, 153, 218

impact on economic factors, 139, 140, 143, 150

impact on project failures cases, 73, 80, 84, 88

impact on software development stages, 103-105, 107, 133

Socioorganizational problems, 48, 64-69

Sociotechnical factors

contributing to software failures, 65-69, 111, 115, 218

impact on development stages, 133-135

impact on economic factors, 139, 140, 143

Software crises, in software development, 5, 10, 11, 13, 30, 190

Software developer, 14, 32-37, 62, 67, 85, 101

Software development practice, 190-195, 253

improving, 221, 227, 241, 253

role of postmortems, 201, 212, 213, 217

Software engineering, 10-12, 14, 202, 211, 240

Software failures. See also Software runaways

cause of, 88, 116

learning from, 189-191, 194, 239, 242

scope of the problem, 3-7, 8, 10, 12, 15, 29, 40, 42, 49, 50, 63

Software problems, 33-35

Software project abandonment. See Abandonment

Software runaways, 8, 49, 50, 63, 88, 121, 189, 239, 240

Sommerville, I., 10, 48-50

Songini, M., report on Hershey Foods' ERP project, 24

50

Stakeholder group

diversity and level of commitment, 36, 37, 58, 39

expectations, 50, 57, 60, 140, 151

interactions within, 107, 115, 153, 155, 158

involvement in software development, 15, 29, 34, 83, 85

in postabandonment review, 191, 192, 194, 198, 199, 200, 201

role in successful project outcomes, 222-224, 226, 232-234

Stakeholders Interaction Model (SIM), 171, 173, 174, 175, 177, 183, 223, 233, 236, 245

Standish Group, study of software failures, 4, 5, 9, 13, 15-21, 42, 51-54, 82, 132

Stedman, C., 4, 24

Strassman, Paul, 124

Streeter, L. A., on coordination in project teams, 36, 100, 121, 126, 175, 244, 245

Structured interviews, for postabandonment reviews, 197, 198, 218

Substantial abandonment, 17-21

Successful project outcomes, improving chances of, 221-223, 225, 227-229, 232, 234-236, 242

Survey questionnaire, for postabandonment reviews, 197, 198, 218

SYS, 202-209

Systems development methodology

absence in CODIS, 153-156, 161, 162, 166, 170, 171, 185

software development process, 47, 48, 49, 55, 56, 63

Systems functionalities

role in software failures, 240, 242, 246. See also Project features

role in successful project outcomes, 222-226, 228, 233-235

Systems life-cycle. See Life-cycle model

Systems managers. See SYS

Szilagyi, J. G., Bank of America's Masternet system, 4