Index_S

S

SARS, 100

schedule delays, 9 “10, 272 “73

Sch n, Donald, 121, 163 “64, 311

Semi-Automatic Ground Environment (SAGE), 130

Senge, Peter, 171, 312

September 11, 2001, 99 “100

Shapiro, Carl, 311

SHARE, 244

shared vision, 173 “74

Shneiderman, Ben, 312

short releases, 21

simplicity, of code, 210

site, business, 248

Slack (DeMarco), 306

Snyder, Nancy Tennant, 307

software architecture

agile software development and, 194 “97

human aspects of, 193

vs. design, 193 “94, 275 “76

software business, 243 “50

software characteristics, 203 “7

See also programming styles

software development

See also software engineering

case studies, 275 “77

complexity of, xxii

customer requirements and, 55 “69

eXtreme Programming (XP), 18 “22

heuristics of, 181 “98

abstraction, 186 “98

structured programming, 184

successive refinement, 184 “86

methods , 13 “27

abstraction, 129 “30, 134 “35, 188 “89

agile, 138 “39

choosing among, 22 “24

Evolutionary Development Model, 136

history of, 129 “39

information hiding, 129, 134 “35

Iterative Model, 135 “36

life cycle, 130 “32

lightweight vs. heavyweight, 25

objects, 138

prototypes , 133, 135

requiring, 24 “25

Spiral Model, 136 “37

Unified Process (UP), 138

Unified Process (UP) of, 16 “18

Waterfall Life Cycle, 131 “32, 135 “36

Spiral Model of, 15 “16

time-to-market , 247

software development teams , 29 “53

abstraction and, 189 “90

Bozo Effect and, 50 “51

Capability Maturity Model (CMM) and, 49 “50

Chief Programmer, 37

democratic , 31 “34

game theory perspective on, 45 “48

hierarchical, 34 “38

perspectives on, 115

Prisoner s Dilemma and, 45 “48

rewarding , 39 “45

student, 39 “45

Surgical Teams, 37 “38

types and structures of, 31 “39

virtual, 38 “39, 48 “49

software engineer

conventional example of, 5 “7

progressive example of, 7 “9

software engineering

See also software development

case studies, 269 “81

code of ethics, 73 “96

definitions of, 115 “17

history of, 125 “39

human aspects of, 187 “88

introduction of term , 4, 11, 130

learning processes in, 161 “79

nonlinear nature of, 9

perspectives on, 113 “23

agile vs. heavyweight, 119 “20

analogies to other professions , 121

failure and success of software projects, 121 “22

international, 97 “112

product vs. process, 117 “19

as a reflective practice, 162 “71

search for best solution in, 4 “5

Software Engineering Economics (Boehm), 304 “5

software engineering education

abstraction in, 197 “98

broadening, 295 “96

current state of, 298 “300

history of, 297 “98

relevance of, 297

teaching human aspects in, 300 “3

Software Engineering Ethics Research Institute, 315

Software Engineering Institute (SEI), xxiii, 49 “50, 247, 297, 315

Software Engineering-Report on a Conference Sponsored by the NATP Science Committee (Naur and Randell), 311

software industry. See high-tech industry

software projects

See also project management

customer requirements for, 55 “70

estimating and tracking, 225 “39

life cycle of typical, 9 “10

poor management of, 226 “36

reasons for failure of, 4 “5, 9 “11

slack time in, 238 “39

success or failure of, 121 “22

Software Psychology (Shneiderman), 312

software requirements

abstraction and, 190

background on, 57 “59

changing, 55 “57

data collection tools for, 59 “66

management of, 66 “69

spam, 262

Spiral Model, 15 “16, 22 “24, 136 “37

Statement of Work (SOW), 249 “50

status meetings, 234

stepwise refinement, 130

structured programming, 184

Structure of Scientific Revolutions (Kuhn), 309

student projects/presentations, 283 “94

student teams, 39 “45

successive refinement, 184 “86

Surgical Teams, 37 “38

SWEBOK (Software Engineering Body of Knowledge), xxiii

systems thinking, 172 “73