Session 5.1 - Implementation Overview & Standards
Chapter 8: Product Implementation | Duration: 1 hr
Learning Objectives
By the end of this session, you will be able to:
- State the entry criteria for starting implementation (IMP1/IMPn)
- Identify coding, configuration, and message standards needed
- Explain the role of personal discipline (PSP) during coding
- Connect implementation work to prior design outputs
Introduction
Implementation turns the SDS into code. Chapter 8 emphasizes discipline: start only when design is baselined, use defined standards, review your work, and record data for postmortem learning.
Entry Criteria & IMP Scripts
Before Coding (IMP1/IMPn)
- Baselined, inspected SDS and integration test plan
- Design standards, glossary, and coding standards available
- Environment/tools ready; CM procedures defined
- Tasks scheduled; personal plans (TASK/SCHEDULE) prepared
Coding & Configuration Standards
| Standard | Purpose |
|---|---|
| Coding conventions | Consistency and readability; align with product naming/message standards. |
| Configuration management | Baseline code, control changes, prevent unauthorized edits. |
| Error/message formats | Usable, consistent system and error outputs. |
| LOC counting & metrics | Enable size/effort tracking for postmortem and planning. |
Personal Discipline (PSP)
Implementation uses PSP habits to ensure quality and data integrity:
- Log time, size, and defects as you work
- Perform personal code reviews before inspections
- Follow checklists from past defects
- Keep TASK/SCHEDULE and WEEK current for visibility
Summary
- Start coding only after design and standards are baselined.
- IMP1/IMPn rely on clear entry criteria, coding/CM standards, and ready tools.
- PSP discipline (reviews, logs) is essential to quality and learning.
- Implementation extends the SDS faithfully—no ad-hoc redesign during coding.