Requirements management is an important activity in the process of designing and managing enterprise architectures. Requirements from various stakeholders form the basis for any change to an organization and its architecture. The quality of these requirements, the extent to which they are realized, and the ease with which they can be changed, determine the quality of any enterprise architecture.

Nonetheless, many enterprise architecture modeling techniques focus on what the enterprise should do by representing “as-is” and “to-be” architectures in terms of informational, behavioral, and structural models at the different architectural layers (e.g., business, application, and technical infrastructure). Little or no attention is paid to represent (explicitly) the reasons; i.e., the why, behind the to-be architectures in terms of motivations, rationale, goals, and requirements.