Managing Software Deliverables: A Software Development Management Methodology

B

Best practices, 205–27

construction integrity, 214–23

continuous program risk management, 206–8

cost and schedule estimation, 208–9

data/database interoperability, 219–20

defects tracking, 212–13

defined, 205

design twice, code once, 221–22

earned value tracking, 210–12

interface definition/control, 220–21

life cycle CM, 214–16

metrics for management, 209–10

people treatment, 213–14

product stability/integrity, 223–27

project integrity, 206–14

requirements and design inspection, 223–24

requirements management/tracing, 217

reuse risks and costs, 222–23

system-based software design, 218–19

testing management, 224–26

Best practices decisions, 40–41

change management, 40–41

continuous improvement/project assessment, 41

project file, 40

Bid/proposals (BP), 64

Boundary-related errors, 128

Business fit, 164–65

Business need, 177

Business Requirements Oversight Committee (BROC), 25–28

defined, 25

functions, 26

members, 27–28

project criteria, 25–26

project proposal guidelines, 26

roles and responsibilities, 27–28

SPMO role in, 28

Sponsor, 27

Business Systems Analyst (BSA), 3–4

defined, 3

responsibilities, 3–4