A leading software manufacturing company has appointed a business analyst (BA) to ensure that requirements are managed effectively and efficiently. The BA discovered some missing functionality as well

Defining requirements architecture organizes and structures the relationships among requirements but does not validate whether implementation aligns with or covers those requirements.

Eliciting requirements again gathers new or additional information from stakeholders but does not systematically compare existing documented requirements against what has already been implemented.

Evaluating requirement changes assesses the impact and validity of proposed modifications to requirements, not the alignment between existing requirements and current solution implementation.

Tracing requirements maps each requirement to its corresponding solution component and vice versa. A forward trace reveals requirements with no matching implementation (missing functionality), while a backward trace reveals implemented features with no originating requirement (unsupported functionality), making both classes of issues discoverable through this single task.