Terry Moriarty saw it coming
Credit where due - Terry Moriarty in this 1998 article asserted that the metadata repository is the data store for configuration management.
-Charlie
Recent Posts
- Meditations on Lean for IT
- New directions: TOC for IT
- Web 2.0 Enterprise Architecture tools
- The CMDB is an Operational Data Store
- Systems dynamics: a challenge to "enterprise" architecture?
- Barbecue is a noun...
- Why and how I blog
- Profound PMBOK/PMI skepticism
- MPC for the large IT organization
- Entity lifecycles & ITSM process architecture
Why ERP for IT?
- The next frontier of enterprise automation (click here for introduction)
This site is dedicated to the emerging subject of enterprise IT automation, otherwise called Enterprise Resource Planning for IT. This is not the automation of business process by IT; rather it is IT automating itself. If you are concerned with IT governance, enterprise architecture, metadata, application portfolio management, or IT Service Management - read on! - Subscribe to the erp4it list!
Click to subscribe to erp4it
Greatest Hits
- erp4it: Element versus enterprise configuration management
- A value chain approach to IT
- A Data Architecture for IT Service Management
- A simplified ERP for IT architecture
- IT portfolios, service catalogs, and enterprise architecture
- Fundamentals of integration metadata
- A story of too many tools
- A metadata rant
- CMDB Chaos and Confusion: Making Sense of the Madness
« ADML: A good idea come and gone too soon? | Main | CMDB Chaos and Confusion: Making Sense of the Madness »
TrackBack
TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341bf8f153ef00d83438c83653ef
Listed below are links to weblogs that reference Terry Moriarty saw it coming:
Comments
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Recent Comments
- Jacob Hall on Barbecue is a noun...
- Jacob Hall on The CMDB is an Operational Data Store
- Anders Vesterberg on Systems dynamics: a challenge to "enterprise" architecture?
- Neil Hepburn on Systems dynamics: a challenge to "enterprise" architecture?
- alphasong on Systems dynamics: a challenge to "enterprise" architecture?
- Jiri Ludvik on Systems dynamics: a challenge to "enterprise" architecture?
- Tim on Entity lifecycles & ITSM process architecture
- BlahBlahBlah on Barbecue is a noun...
- Antonio Valle on Entity lifecycles & ITSM process architecture
- gentleolas on Toastmasters Competent Communicator
The Book
- At last!
Whitepapers
- ERP for IT article in BI Journal
Published article in BI Journal covering the basics. - TDAN.com: A System That Manages Our Systems?
Response to David Marco. I like David, especially for adding additional proof to my thesis.
Charlie -
I depended on Terry Moriarity's wonderful columns in "Database Programming & Design" in the late 1980s to ramp up my knowledge of what to do with data dictionaries (now known as metadata repository). It was a time of much excitement & anticipation for CASE tools & IBM's illfated RepositoryManager (aka RepoMan) effort.
From a real--still running today--I published this very lonely success story in 1994... http://www.tdan.com/i013hy01.htm in Ed Yourdon's "American Programmer"
You are 100% on the money about the necessity of hooking up modeling/development with operations.
The key is to automate the scanning tasks--of programs, JCL (or functional equivalent), and data structures--during the configuration management steps.
Allegedly "new" data elements are defined in the Repository (after due diligence to find synonyms) and exported to developers work space.
When finished with development, and promoted to acceptance level, programs are compiled from the Repository's data structure (if programmer has altered the data structure/copybook outside of the dictionary, such changes will not be recognized (must research & make such changes in Repository).
When promoted to production all 3 forms of source code--programs, data structures/copybooks, JCL--are scanned into repository so that all relationships are automagically maintained.
Programmers MUST be removed from the Repository update loop... simply tooooo many moving pieces.
- David
Posted by: David Eddy | October 07, 2004 at 10:22 PM