36 Questions
Why is it necessary to manage changes in software development?
To adapt to changing market opportunities, regulations, and business needs
What can happen if a developer implements a change without communicating with the team?
The documented requirements will become inaccurate
Why is a change control policy necessary?
To define how project teams will handle proposed changes
What should happen to a change request that is not submitted according to the process?
It will not be considered
What is the purpose of feasibility exploration?
To explore the possibility of a change
What can occur if changes are not managed during development?
An expectation gap will occur
What is the purpose of tracking the total number of change requests received?
To evaluate the completeness of original requirements
What does a sustained high frequency of changes imply?
A risk of failing to meet project schedule commitments
What is the purpose of tracing requirements?
To ensure that customer needs are met
What is a benefit of tracing requirements?
Finding missing or unnecessary requirements
What is the purpose of a requirements traceability matrix?
To map requirements to implementation and testing
What is a type of requirements trace link?
All of the above
What is a benefit of change impact analysis?
Ensuring that changes do not affect system elements
What is the purpose of tracking the effort devoted to processing and implementing change requests?
To determine the cost of implementing changes
What is a benefit of requirements tracing in maintenance?
Ensuring that changes are made properly
What is the purpose of a chart that shows the number of change requests from different sources?
To discuss with stakeholders about the origin of change requests
What is the primary goal of a sensible change control process?
To provide the greatest customer and business value while controlling the product's life-cycle cost and the project's schedule
Why is it essential to perform impact analysis for every change?
To identify the consequences of accepting the change
What is the purpose of documenting the rationale behind every approval or rejection of a change request?
To record the reason for the decision
What is the role of the Change Control Board (CCB)?
To decide which changes to implement
What should happen after a change request is approved?
The request is assigned a priority, a target implementation date, or a specific release
What is the purpose of verification in the change control process?
To ensure that modified deliverables correctly address all aspects of the change
What is required for a change request to be considered complete?
The status of the request is Rejected, Closed, or Canceled, and all modified work products are updated and stored in the correct locations
Why is it essential to trace the contents of the change database?
To ensure that all stakeholders have access to the change database
What is the benefit of measuring change activity?
To assess the stability of the requirements
What is the purpose of evaluating a change request?
To ensure that the consequences of accepting the change are understood
What is the main purpose of a Requirements Traceability Matrix?
To define links between system elements
What type of relationship can exist between a functional requirement and tests?
One-to-many
What is the recommended approach to maintaining traceability information?
To focus on tracing between business requirements and user requirements
Why is requirements tracing necessary in certain industries?
To meet regulatory requirements
What is the purpose of auditing the trace information periodically?
To ensure that the trace information is being kept current
What is the recommended approach to applying requirements tracing?
To educate the team about the concepts and importance of tracing
What is the benefit of maintaining a Requirements Traceability Matrix?
To look for alignment, omissions, and unnecessary requirements
What is the purpose of defining labeling conventions for system elements?
To ensure that each system element has a unique identifier
What is the recommended approach to collecting trace information?
To have each participant provide the requested trace information as they complete small bodies of work
What is the importance of requirements tracing in certain projects?
It is necessary for certification of aviation software
Study Notes
Why Manage Changes?
- Software change is necessary and inevitable due to evolving business needs, market opportunities, and regulations.
- Managing changes helps prevent expectation gaps and associated problems, frustration, rework, and wasted time.
Change Control Policy
- A change control policy should be communicated to handle proposed changes in requirements.
- The policy should cover the process for submitting change requests, evaluating changes, and implementing approved changes.
Change Control Process
- The change control process helps project leaders make informed business decisions while controlling the product's life-cycle cost and project schedule.
- The process involves:
- Evaluating change requests to understand consequences and impact
- Making change decisions with consideration of technical feasibility, cost, and business requirements
- Implementing approved changes and updating affected work products
- Verifying changes through peer review
- The process ensures that suggested changes are not lost or overlooked and that stakeholders are informed of change requests and status.
Measuring Change Activity
- Measuring change activity helps assess the stability of requirements.
- Tracking aspects include:
- Total number of change requests received, open, and closed
- Cumulative number of added, deleted, and modified requirements
- Number of requests originating from each change origin
- Total effort devoted to processing and implementing change requests
Tracing Requirements
- Tracing requirements involves tracking the life of a requirement from origin to implementation.
- Trace links allow for forward and backward tracing of requirements.
- Requirements tracing helps:
- Find missing requirements
- Identify unnecessary requirements
- Perform change impact analysis
- Maintain software systems
- Reuse product components
- Track project implementation status
- A requirements traceability matrix can be used to represent trace information between system elements.
Applying Requirements Tracing
- Educate the team about tracing concepts and importance
- Select link relationships to define and choose a traceability matrix type
- Identify parts of the product for tracing and assign tracing responsibilities
- Modify development procedures to update links after implementing requirements or approved changes
- Define labeling conventions for unique identifiers
- Audit trace information periodically to ensure accuracy
Learn about the importance of managing changes in software development. Understand why it's necessary to adapt to new market opportunities, regulations, and business needs.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
