Sponsored by ComputerWeekly.com
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. Access >>>
Table of contents
- Architecting Requirements – Way of Working
- Requirements Concepts – Way of Modeling
- Techniques and Tools – Way of Supporting
Premium Content for Free.
More Premium Content Accessible For Free
What went wrong with the IT for farmers' rural payments?
In this week's Computer Weekly, we examine the real reasons behind the failure of the government's rural payments digital service. We look at how ...
A Computer Weekly buyer's guide to data science
In this 10-page buyer's guide, Computer Weekly looks at how, with the open data movement taking hold and data analytics technology becoming ...
Staying the course as a CIO
In this extract from his book, Staying the Course as a CIO, Jonathan M. Mitchell looks at the challenges of managing IT projects.