CSC440 Chapter 9: Software Evolution (Software Engineering,
Sommerville, 10th Edition) questions with verified answers
Reasons for Software Change Ans✓✓✓-- New requirements emerge when the
software is used
- The business environment changes
- Errors must be repaired
- New computers and equipment is added to the system
- The performance or reliability of the system may have to be improved
Software Timeline (Life Cycle) Ans✓✓✓-1. Software Development
2. Software Evolution
3. Software Servicing
4. Software Retirement (Phase-out)
Software Evolution Ans✓✓✓-The stage in a software system's life cycle where it
is in operational use and is evolving as new requirements are proposed and
implemented in the system.
,Software Servicing Ans✓✓✓-At this stage, the software remains useful but the
only changes made are those required to keep it operational i.e. bug fixes and
changes to reflect changes in the software's environment. No new functionality is
added.
Software Retirement (Phase-out) Ans✓✓✓-The software may still be used but no
further changes are made to it.
Software Evolution Processes depend on: Ans✓✓✓-- The type of software being
maintained
- The development processes used
- The skills and experience of the people involved
General Steps in the Software Evolution Process Ans✓✓✓-1. Change Requests
2. Impact Analysis
3. Release Planning (Includes fault repair, platform adaptation, and system
enhancement)
4. Change Implementation
5. System Release
, Change Implementation Ans✓✓✓-Iteration of the development process where
the revisions to the system are designed, implemented and tested.
General Steps in Change Implementation Ans✓✓✓-1. Proposed changes
2. Requirements analysis
3. Requirements updating
4. Software development
Reasons for urgent change requests Ans✓✓✓-- If a serious system fault has to be
repaired to allow normal operation to continue
- If changes to the system's environment (e.g. an OS upgrade) have unexpected
effects
- If there are business changes that require a very rapid response (e.g. the release
of a competing product).
Handover problems when software is handed over to another development team
Ans✓✓✓-- Where the development team have used an agile approach but the
evolution team is unfamiliar with agile methods and prefer a plan-based
approach. The evolution team may expect detailed documentation to support
evolution and this is not produced in agile processes.
Sommerville, 10th Edition) questions with verified answers
Reasons for Software Change Ans✓✓✓-- New requirements emerge when the
software is used
- The business environment changes
- Errors must be repaired
- New computers and equipment is added to the system
- The performance or reliability of the system may have to be improved
Software Timeline (Life Cycle) Ans✓✓✓-1. Software Development
2. Software Evolution
3. Software Servicing
4. Software Retirement (Phase-out)
Software Evolution Ans✓✓✓-The stage in a software system's life cycle where it
is in operational use and is evolving as new requirements are proposed and
implemented in the system.
,Software Servicing Ans✓✓✓-At this stage, the software remains useful but the
only changes made are those required to keep it operational i.e. bug fixes and
changes to reflect changes in the software's environment. No new functionality is
added.
Software Retirement (Phase-out) Ans✓✓✓-The software may still be used but no
further changes are made to it.
Software Evolution Processes depend on: Ans✓✓✓-- The type of software being
maintained
- The development processes used
- The skills and experience of the people involved
General Steps in the Software Evolution Process Ans✓✓✓-1. Change Requests
2. Impact Analysis
3. Release Planning (Includes fault repair, platform adaptation, and system
enhancement)
4. Change Implementation
5. System Release
, Change Implementation Ans✓✓✓-Iteration of the development process where
the revisions to the system are designed, implemented and tested.
General Steps in Change Implementation Ans✓✓✓-1. Proposed changes
2. Requirements analysis
3. Requirements updating
4. Software development
Reasons for urgent change requests Ans✓✓✓-- If a serious system fault has to be
repaired to allow normal operation to continue
- If changes to the system's environment (e.g. an OS upgrade) have unexpected
effects
- If there are business changes that require a very rapid response (e.g. the release
of a competing product).
Handover problems when software is handed over to another development team
Ans✓✓✓-- Where the development team have used an agile approach but the
evolution team is unfamiliar with agile methods and prefer a plan-based
approach. The evolution team may expect detailed documentation to support
evolution and this is not produced in agile processes.
