Notice that big circle in the middle?
EVERYTHING in the ecosystem SHOULD map to requirements.
You may have noticed that the Capability Matrices in the previous posts sorta-kinda did.
In an ideal world (which I don’t happen to live in right now), the order in which things would go would be:
– Problem definition
– Requirements collection
– Solution design and development based on requirements and guided by architectural principles
– Did it solve the problem yes/no?
The capability matrix for the resulting solution set would be based on the requirements collected.
The next series of posts will demonstrate how to create a capability matrix in my personal utopian fantasyland. And talk about requirements and requirements collection.
In TOGAF, when they talk about requirements, they are talking about the requirements for the entire architecture.
These requirements are shaped / guided by the principles underlying your architecture.
As more requirements surface, the principles of the architecture may shift.
For the time being, the 2 principles we are using to guide our Learning Architecture still work.
– As needed performance support
– Continuous professional development
When we put together our requirements for any solution in the Learning Ecosystem, we will be keeping those 2 principles in mind.
Side note: Some other organizations use the requirements they have collected over the years to help define their Architecture Principles. That works too. Requirements collection in our organization is still very immature.