Why is Requirements Management considered "orthogonal" to the other RE activities?

Because it runs across all the other activities continuously, rather than being one sequential step you finish and move past.

Requirements Management is not a phase — it's a continuous concern threaded through elicitation, documentation, and validation. It involves:

• Structuring requirements so they can be used by different roles
• Preparing requirements for various stakeholders
• Maintaining consistency after changes occur
• Ensuring requirements are properly implemented

This means management activities happen continuously throughout elicitation, documentation, and validation - not as a separate phase.

Practical implications:

• You need version control from day one
• Traceability links must be maintained as requirements evolve
• Change impact analysis happens whenever requirements change
• Requirements status tracking (proposed → approved → implemented → verified)