The understanding of requirements has been one of the most contentious issues between IT and Business. To resolve this conflict, many disciplines have emerged but progress to resolve this conflict has been minimal. Our view is that the root cause of this conflict has been two-fold:
- A lack of common vocabulary, and
- Clear accountability of the outcome
The Business often expresses requirements as characteristics of the solution rather than characteristics of the problem, and when they build a system based on the provided requirements, the system often fails to address the organization’s business opportunities. Re-definition and rework further increases time and cost to the project and to the dismay of everyone involved, the results get marked as one more failed IT project.
In this paper, we are separating the notion of requirements into two perspectives. For each perspective we have defined roles, responsibilities, and how requirements are elicited, analyzed, communicated, and tested. Most importantly, accountability for the completeness and accuracy is explicitly defined. To ensure clear communication, we have provided a set of architecture requirements for a major Business Transformation program.
- Additional Information
Reference W136 Author(s) Jason Uppal and Tamim Rahman Published 6 Nov 2013 Pages 17 Type White Papers Subject TOGAF