Version Control in Requirements Management

Correct Answer: A fixed reference point marking an approved set of requirements at a specific time

Baseline versioning in requirements management represents a fixed reference point in time when a set of requirements has been formally reviewed and approved. This serves as an official foundation for future project work. The correct answer best captures this concept by emphasizing that it's a fixed reference point for approved requirements at a specific time. This is crucial for change control and project stability. The other options are incorrect because: - Sequential numbering of modifications describes version control in general, not specifically baseline versioning - Real-time collaborative review describes a workflow process rather than baseline versioning - Maintaining separate versions for different stakeholders describes version branching, which is different from baseline versioning Baseline versioning is essential because it: - Provides a stable foundation for project development - Enables effective change management - Creates a clear historical record - Helps maintain project scope control - Facilitates impact analysis of proposed changes

Correct Answer: To track major and minor changes to requirements over time

Version numbers in requirements management serve the essential purpose of tracking changes to requirements throughout the project lifecycle. The format x.y (like 1.0, 1.1, 2.0) is a standard way to indicate both major changes (first number) and minor changes (second number) to requirements. This versioning system allows teams to: - Track requirement evolution over time - Maintain a clear history of changes - Reference specific versions of requirements - Support impact analysis of changes The other options are incorrect because: - Stakeholder approval levels use different tracking mechanisms, typically through approval workflows or sign-offs - Implementation priority is usually indicated through separate priority fields or rankings - The number of stakeholder reviewers is tracked in stakeholder matrices or approval logs, not through version numbers

Correct Answer: Using a centralized repository with baseline versioning and change approval workflows

A centralized repository with baseline versioning and change approval workflows is the best practice for managing requirements changes because: - It provides a single source of truth for all project artifacts - It enables controlled change management through formal approval workflows - It maintains complete version history and traceability - It allows for concurrent access and collaboration while maintaining consistency - It supports baseline management for proper requirements versioning The other options are inadequate because: Sequential backups in separate folders are prone to errors, lack proper version control, and make it difficult to track relationships between artifacts. Spreadsheet tracking is manual, error-prone, and doesn't provide real-time synchronization or proper version control capabilities. Automated version numbering alone doesn't provide the necessary controls, approvals, or traceability needed for proper requirements management, and may lead to unauthorized changes.