The Essential Project Forum

We are using more and more SaaS services or PaaS services. The application as such is represented as Application Service, but we do have usually staging like DEV, QA, PROD and these do have not different hardware (as we don't know), but different tenant IDs and sometimes different endpoints to access the SaaS service.
Are there any best practices or documentation about how to document these endpoints and different instances of application services in the meta model?

When you say different endpoints, I presume you mean different physical addresses. If so, then I would suggest that you actually model your SaaS Services as instances of Composite Application Providers with the D`elivery Model slot set to SaaS. Youi can then capture each of your DEV, QA and PROD instances of each SaaS service as instances of Application Deployment with the Deployment Role slot set to one of DEV, QA and PROD. The purpose of the Application Service class is to describe the funtionality that is provided by, in this case, your SaaS services