Session 14
Change Control Process for Railway Reservation System
This session introduces change management. After showing the Railway Reservation System to another person, suggested changes should be recorded, analyzed, approved, implemented, tested, and demonstrated again.
Problem Statement
Demonstrate the software developed in Session 13 to another person and make a list of changes suggested by him/her. Implement changes in the software following the change control process and demonstrate the updated software to the same person.
Expected Deliverable
Prepare a change request list, impact analysis, implementation notes, and updated demonstration report.
Change Control Steps
- Record change request.
- Classify change type.
- Analyze impact on requirements, design, code, tests, and schedule.
- Approve or reject change.
- Implement approved change.
- Retest affected modules.
- Demonstrate updated software.
Change Request Format
| Field | Description |
|---|---|
| Change ID | Unique identifier |
| Suggested By | Name of reviewer/user |
| Description | Requested change |
| Reason | Why change is needed |
| Impact | Affected module/document |
| Status | Proposed, approved, implemented, tested |
Submission Checklist
- Include original feedback.
- Include change request table.
- Include impact analysis.
- Include updated screenshots or notes.
- Include retesting result.