index_S

S

Safety, software

damage types, 182–83

documentation, 210

key issues, 183–86

management, 189–90

overview, 20, 181–82

requirements, 186–89

Safety and risk management plan, 70

Scatter diagram, 117

Schedule risk, 194–95

Scheduling implementation, 229

Security, 161

database, 152–153

disaster recovery, 156–58

overview, 17–18, 151, 158

teleprocessing, 154–55

user education, 162–63

viruses, 155–56

Seminars, educational, 165

Sequential numbering, 138

Severity, defect, 112

SHARE, 42

Shewart, Walter, 121

Simplicity, metrics, 127

Simulator software, 87, 89

Single-element implementation, 239–40

Single-project implementation, 238–40

Smallest replaceable component. See Unit

Soft measures, defect analysis, 115

Software, 4

Software change notice, 104–5, 134, 144

Software defect report, 56

Software development file. See Unit development folder

Software development life cycle

definition, 4–5

enhancements, 177

maintenance phase, 173

phases, 31–32

reviews, 10–11

Software development methodology, 32

Software development notebook, 57

Software development plan, 70, 207, 208–9, 245–46

Software Engineering Institute Capability Maturity Model, 4, 99, 241

Software Engineering Standards Committee, 30

Software languages, 34

Software library, 131, 144–45

Software life cycle, 5

divisions, 6–7

standardization, 30–32

Software maintenance plan, 221

Software misuse, 197

Software quality assurance, 111

Software quality control, 111

Software quality group, 4, 233–34

Software quality group chart, 229

Software quality practitioner, 18–19, 23, 47

certification, 242

change control role, 142, 143

defect analysis role, 92, 99, 104, 115

design reviews role, 215

documentation roles, 92, 208, 209–10, 212, 216, 220, 221, 222

education roles, 158–59, 160, 162, 163, 164, 166, 167, 222–23

maintenance roles, 173, 175, 177, 178, 179, 232–33

openness, 237

reporting roles, 234–36

risk management roles, 194, 195, 196, 197

review roles, 52, 57, 59, 61, 65, 70–71

safety roles, 183

security roles, 151, 158

task performance roles, 233–234

testing roles, 74, 75–76, 77, 78, 79, 80, 82, 86, 88, 90, 91, 93, 218

vendor management roles, 167, 168–69, 170–71, 172–73

Software quality system, 4

adaptation, 240–41

elements, 6–20

goal-oriented metrics, 109–11

implementation, 237–41

improvement, 241–42

organizational issues, 231–36

planning, 227–29

Software quality system plan, 70, 207, 208, 209–10, 247–48

Software requirements review, 57–58, 60, 64, 135

Software safety plan, 210, 269–70

Software system, 5

Software trouble report, 99, 101–6, 113–14, 115, 134

Source listing document, 221

Standard, 5

Standardization

availability, 46–47

coding, 33–34

configuration identification, 138

defect reporting, 104, 124

documentation, 32–33, 38, 223

maintenance, 47–48

naming, 34–35, 131, 133, 145

operating procedures, 36

overview, 7–10, 29–30, 47

selection, 45

software life cycle, 30–32

software safety, 186–87

sources, 38–45

user development, 36–38

Standards Australia AS 3563, 40

Standards committees, 44

Standards coordinator, 44–45

Standards groups, 43–44

Standards manual, 46–47

Stimulator software, 87, 89

Stress testing, 80–81

Structured coding, 33–34, 159, 160

Subsystem, 5, 133

Subtest case, 85

Successors, 135–36

Supplier, 5

Support training, 160–62, 165, 167

System, 133

Systems programming, 161