Scott Ambler has been a prominent critic of the OMG's Model-Driven Architecture, but has started to examine some scenarios for "Agile MDA" here.
I think many of Scott's insights are useful, and admire his sense of history - it's rare to see people of our generation understand the history of CASE. One thing he doesn't make the connection on - the OMG's MDA can trace its lineage directly back to the failure of 1980s CASE tools, via interim standards such as CDIF, AD/Cycle, PCTE, and IRDS.
Newcomers to this blog, and my friends in the IT Service Management community, may not realize the challenges faced by the discipline of data management. In order to effectively manage an enterprise's data, robust control points are required so that the contents of all databases are effectively documented and their structures are built to standards...
John Singer of Mastercard wrote Part 1 and Part 2 of "Metadata Repository Redux" in DM Review Direct. This is the best metadata writing I've read all year; concise (3 pages each) yet rich. Highly recommended; covers the "use cases" for metadata -- "common patterns of process and technology." This man has lived the problem and thought deeply about it. "Twenty-first century metadata management for IT has morphed into knowledge and content management with the goal of capturing, classifying, and categorizing all things IT."
It's apparent that I need to understand more about the Semantic Web and how it may impact the evolution of standards for the enterprise IT problem domain. Here is an interesting article for starters, from Enterprise Architect. Note the skepticism of one presenter, for what appears to be similar reasons to my own.
Same newsletter, different article: notice that David Linthicum's presention here seems to imply that metadata will be RDF-based.
I finally broke down and purchased the online copy of the ITIL "Data Management" volume. This is part of their "Back Catalogue," available through TSO. (Data management is in volume 2, "The complementary guidance set.")
I was going to write a longer review of this 170-page volume, but it is simply so good that all I can say is Buy It, if you are in data management, or an IT Service Manager trying to figure out where Data Management might fit in. (Unfortunately the price is a little high, and you get 6 other books you may not need.) It's an excellent, thoughtful, concise yet nuanced overview of Data Management, covering...
This part is concerned with the architectural implications for tools, processes, and data structures implied by this volume.
The application portfolio, as depicted in this volume, is itself an information system, database-based, which stores attributes about applications that are enterprise assets. Its purpose is to “fully realise the benefits of their IT investments.”
On the question “what is an application,” the volume defines it as “the software program(s) that perform those specific functions that directly support the execution of business functions, processes, and/or procedures. Applications, along with data and infrastructure components, such as hardware, the operating system, and middleware, make up the technology components of IT systems that in turn are part of an IT service.”
The reader is encouraged to examine this article from my “Fundamentals of Integration Metadata” series for technical background on precisely defining the concept of application. Note that distinguishing between application, data, infrastructure, and middleware may be easier said than done…