IT Methodologies such as TOGAF, Zachman, FEAF, RUP, and Agile are all important tools for the enterprise and software architect. But it turns out that all of these methodologies share a common limitation: they don't scale. Each of these works well for projects less than about $1 million, but try to use any of them for projects in the $10M range, and you will find yourself in a murky land with dangers around every curve.
If you are building or maintaining a large IT system, you must start by understanding the principles of partitioning. This Web Short gives an overview of the SIP methodology, the only methodology focused exclusively on the issue of partitioning. SIP doesn't compete with these existing methodologies, it completes them. SIP is the missing ingredient in scalability.
You can see a full list of Roger's Web Shorts here.
Would you like to be notified of future Web Shorts and White Papers by Roger Sessions? Sign up here.
And thanks to AuthorStream for hosting this presentation.
Subscribe to:
Post Comments (Atom)
3 comments:
Hi Roger,
Great presentations, keep up the good work.
Johan Theunissen
The Netherlands
Any resources on how to decompose ABCs and capabilities? Im assuming its based on business volatility, and should map somehow to what the business does.
Lee:
Sorry, I didn't see this comment awaiting moderation.
The ultimate goal of the decomposition is to identify the atomic business functions, that is, the lowest level description of what the business does.
Once we have this collection of business functions, that we recompose them using synergistic partitioning.
Post a Comment