Index_S

 < Day Day Up > 



S

Security Access Sheet (SAS), 34–35

Service Level Agreements (SLAs), 151–55

acceptance, 154

components, 152–55

creation process, 151

as customer satisfaction key, 151

defined, 151

Limitations section, 153

Nonperformance section, 153–54

Objectives section, 153

Optional Services section, 154

Parties to the Agreement section, 153

Scope section, 153

Smoke testing, 227

Software configuration management plan (SCMP), 149–51

configuration control, 150

defined, 149

deltas, 150

tasks, 149

Software Development Life Cycle (SDLC), 168–69

alternative work patterns, 170

model identification, 168–69

models, 168

Software Development Plan (SD), 87–88

defined, 87

items, 87–88

Software Installation Manual (SIM), 96–97

Software process improvement organizations, 21–23

component focus, 22

elements, 21

goals, 23

Software Program Management Office. See SPMO

Software Reengineering Assessment (SRA), 59–60

defined, 59

intangible benefits, 60

tangible benefits, 60

Software Requirements Specification (SRS), 84–85

Software Test Plan (STP)

defined, 104

test variants, 104

in TPC, 114

Software Transition Plan (SWTP), 148

Software User Manual (SUM), 96

Source errors, 131–32

SPMO

BROC role, 28

Business Systems Analyst (BSA), 3–4

change management, 23–25

Executive Stakeholder, 2

financial management, 8–9

implementation thoughts, 230–32

issue management, 13–14

mission statement, 1

most significant activity, 230

organization structure, 4–5

performance reporting, 5–8

Program Manager, 2

Project Coordinator, 3, 181

Project Manager (PM), 3, 9, 14, 33–34, 202

Project Sponsor, 2

quality management, 14–23

roles and responsibilities, 1–4

scope and methodology domain, 231

service areas, 5

staff, 232

test/certification plans, 102–6

understanding, 1–30

vendor management, 9–13

Sponsor Formalization Letter (SFL), 32

Staged deliveries, 169

Status reports (SR), 71–72

Stress Test Plan (SsTP), 103, 113

Subject matter experts (SMEs), 165

Success

factors, 163

as team effort, 166–67

Summary WBS, 186

Support phase, 147–56

completion, 155–56

defined, 147

deliverables checklist, 148

hardware life cycle management plan, 148–49

help desk checklist, 155

MIS hardware/software handoff letter, 148

plan development, 149

roadmap, 147

SLAs, 151–55

software configuration management plan (SCMP), 149–51

Software Transition Plan (SWTP), 148

System-based software design, 218–19

System Infrastructure Requirements (SIR), 82–84

defined, 82

requirements document TOC, 82–84

Systems Engineering Process (SEP), 2

choice of, 229

Microsoft Project with, 180–82

Phase I, 31–51

Phase II, 53–75

Phase III, 77–93

Phase IV, 95–108

Phase V, 111–33

Phase VI, 135–45

Phase VII, 147–56

Phase VIII, 157–61

project plan using, 181

step-by-step process, 180



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net