Associate an application service to a software model

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read

    • Business applications have multiple instances such as development, QA, and production. Instances are nothing but application services. Application services must be associated with software models (to the respective full versions) to know the risk of the application service.

    Before you begin

    Important:

    Starting with the Xanadu release, the legacy business applications module is moved to the Enterprise Architecture Workspace. To learn more, see Managing the Technology Portfolio Management (TPM) in Enterprise Architecture Workspace.

    Role required: sn_apm.apm_user

    Procedure

    1. Navigate to All > Enterprise Architecture > Technology Portfolio Management (TPM) > Application Services.
    2. Select the service record, which is the application service, to which you want to associate the software models.
    3. Select the Application Service Software Models related list.
    4. Select New.

      The Application Service Software Models [sn_apm_tpm_service_software_model] database table stores the application service software model information. You can also navigate directly to the Application Service Software Models table from the application navigator. Data from this table is rendered as the software model timeline in the By Software Model view of the TPM screen.

    5. On the form, fill in the fields.
      For field information, see Application Service Software Model form.
    6. Select Submit.

    What to do next

    Create risk parameter scores to evaluate the risk of the software model. Based on the risk of the software model you can calculate the risk of the application service. Finally, based on the risk of the application service you can evaluate the risk of the business application.