Software Model Versioning effect of EA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2025 08:30 PM
Can someone tell me the advantages and disadvantages of creating software models with only the major version. I want to know how does that affect the enterprise architecture TPM and TRM if a software model contains multiple discovery models with different life cycles.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Then how do you get software models installed on desktops traversed up to TPM. I thought there was a way to utilize the discovery model. We have SAM PRO not sure if that plays in. I'm coming up to speed on knowledge of the Product Model table and its visibility and use across the platform. Appreciate your insight. Trying to ingest this documentation and translate to see if the service mapping is truly needed. For the tables listed in the above documentation is that assuming the use of service mapping?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
29m ago
What if the software products are typical desktop products such as Visio, SnagIt etc that aren't going to be associated to a business application and really are just end-user applications. We wouldn't need to do any kind of service mapping for those correct? I understand the need for Service mapping for your business applications and their software components but not sure on the end-user desktop products that are not a component of a business application.
