---
sourceDocument: Australia Enterprise Architecture (formerly Application Portfolio Management)
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-portfolio-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Enterprise Architecture (formerly Application Portfolio Management)

ft:clusterId :

    - appportman

bundleId :

    - appportman

workflow :

    - Technology


---

# Associate an application service to a software model

# Associate an application service to a software model {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

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.

## Antes de Iniciar

Importante:  
Starting with the Xanadu release, the legacy business applications module has been deprecated from Enterprise Architecture (formerly Application Portfolio Management). However, if you're an existing user of Enterprise Architecture (formerly Application Portfolio Management), you can still use the legacy business applications module. If you're a new activation user, the legacy business applications module isn't available.

You can leverage the same features by using the Enterprise Architecture Workspace. To learn more, see [Manage the Technology Portfolio Management (TPM) in Enterprise Architecture Workspace](https://servicenow-prod.fluidtopics.net/vZeIuVX2B9KIsaFKO508Vw "Technology Portfolio Management helps Enterprise Architects to manage technology life-cycle risks and technology life-cycle exceptions. Enterprise Architects can evaluate all their business applications and application services by accessing the discovered technologies and auditing information in the Enterprise Architecture Workspace.").

Role required: sn_apm.apm_user

## Procedimento

1. Navigate to AllEnterprise ArchitectureTechnology 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](https://servicenow-prod.fluidtopics.net/pwphD6zNLgXZ10UQfa3mUw "Business applications have multiple instances such as development, QA, and production. Instances are nothing but application services. Hence application services must be associated with software models (to the respective full versions) to know the risk of the application service.").
6. Select Submit.

## O que Fazer Depois

[Create risk parameter
scores](https://servicenow-prod.fluidtopics.net/8dNk5bf~7AM4Kq2k~k6jMQ "The risk on a software model is calculated based on four preconfigured parameters such as external aging risk, internal aging risk, external stage risk, and internal stage risk.") 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.