OK. I see what you're saying. It does seem to list things the way you had them in your table implying that the destination depends on the source. Perhaps we were doing things completely backwards... And that just further confuses the whole idea of what's the parent and what's the child, because which direction would you expect the arrow to go for a dependency, to the thing being depended on, or to the item that depends on it?
Concerning Components, I suppose it depends a bit on how you think of component. While a system is architected of many "components", I'm not sure that they're components in the same sense as the types of things they're listing in their examples. The components they list here seem to either be logical (conceptual) components of a logical system (an Application System is a component of an Application Infrastructure) or physical components of a more complete physical whole (e.g., a Computer System - perhaps a VM - being a component of a Mainframe). The other separate types of "components" that make up a system (databases, computer systems, etc.) seem to be separate items that merely depend on each other. That makes more sense to me in my mind. For example, if you wanted to have something akin to an generic Remedy Application System (think, Remedy from a customer's perspective), I think that might actually have two components from the perspective of the system, the User tool (or maybe the Mid Tier) and the AR Server. Those are the two components of the system from the perspective of the overall Application System. However, behind each of those are sub-components that are separate but that depend on each other. E.g., the AR server depends on the Computer System it runs on and on the Database, the Database depends on the Computer System the DB server is running on, etc. Does that make sense at all. I don't know if I'm conveying what I'm thinking very well. It seems like you're headed in the right direction, though. Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Martinez, Marcelo A Sent: Thursday, December 10, 2009 4:44 PM To: [email protected] Subject: Re: CMDB mapping question: dependency vs. component ** The reason I had them backwards is because that is how I interpret this document (see attached).. Look at line 21 on page 8. But since I don't use BMC_SoftwareServer I substituted it for BMC_ComputerSystem. It isn't clear to me if the source depends on the destination OR if the source is a dependency of the destination... Also, according to this document, there are very few "components". I would of thought that a "system" had many components (i.e. servers, database, jobs, etc). Thanks Lyle Marcelo (my msg was getting rejected so I removed the previous txt) From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Lyle Taylor To: [email protected] Subject: Re: CMDB mapping question: dependency vs. component I would say that your first table seems more correct, except that I think you probably have the Source and Destination columns backwards (the Source depends on the Destination, not the other way around, IIRC). In addition, I don't think that your Rem001server computer system depends on the database - only your AR server depends on the database. So, I would change "Rem001server" in the second line in the table to "Remedy System". So I think the table would actually look like this in the end: _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

