Organization of modules, applications, and subsystems
Applications include the main BMC Remedy ITSM applications: Incident Management feature of BMC Service Desk, BMC Change Management, Problem Management feature of BMC Service Desk, and BMC Asset Management. These applications contain logic and user interfaces specific to those application areas.
The final layer consists of supporting systems. This common set of systems supports the applications. Supporting systems contain generic logic that is specific to an application's function without embedding functionality from other applications that use its services. Examples of supporting systems include Task Management System, Cost module, and Contract Management.
The following figure illustrates the relationships among the BMC Remedy ITSM applications and modules.
BMC Remedy ITSM applications and modules
Comments
I find the image somewhat confusing combined with the text description provided in the article. For example, the text mentions that the "top layer consist of modules such as the Requester Console which interact with back-office applications like BMC Service Desk". However, in the image these two are shown on the same level.
Another example: the "Applications and modules" section in the image shows that BMC Change Management makes use of BMC Atrium Core, BMC SLM, Release Management, Activity System etc. The "Modules and supporting systems" section mentions Release Management as a separate module relying on supporting systems BMC Atrium Core, Activity System, BMC SLM and more.
In the image, should BMC Atrium or BMC SLM be considered as a module or as a supporting system?.
Based on the text and the image it is still not entirely clear to me which is an application, module or a supporting system. Is it possible to provide some more clarification on the difference between these types?
Log in or register to comment.