The following is the domain checklist:

• Has use been made of applied national and international standards, for instance, to exchange of data via networks (OSI, TCP/IP, XML), of applications in the IBM-environment (SAA), or of a standard programming language which can be compiled on a wide variety of hardware?
• Has a standard machine-interface been used?
• Is it possible to secure additional critical or essential functions?
• Have the systems to which data will be exchanged been specified?
• Has a generalized subsystem (interface) been specified for the interaction of data with other systems?
• Have standards (nomenclature, coding, structure, and so on) been used for the interaction of data?
• Have standards been used for the connection between hardware and infrastructure components?
• Maintainability influences the connectivity regarding the technical system architecture (see checklist for maintainability).
• How can users outside the native delivery environment access your applications and data?
• Does the system provide efficient application integration options to work with other back-end systems? Is there a description of integration architecture, including APIs, and where integration is tightly and loosely coupled?
• Does the system support industry standard data interchange standards, such as Polaris, EDI, and so on? Have you outlined data interchange standards supported and how data transformation occurs?
• What software design, development integration, and testing standards are used by the system?
• Have all the interfaces, including external ones, been identified and described?
• Are all the components interfaces defined?
• Does the integration strategy covers all the technology landscape including legacy platforms and existing applications, such as NSM, Device Management, Voucher Management, ALEPO, ERP, OIC, ODS, EDW, CWS, EAI, and so on?
• Is the architecture appropriately layered and can be realized through SOA?
• Does the system provide efficient application integration options to work with various systems; for instance, file systems, databases, applications, and so on?
• Does the integration architecture defined and describe an integration map?
• Are key capabilities like BPM, registry and repository, business rules identified and described?
• Does it leverage SOA principles and reference architecture?
• Does it support industry standard data interchange standards?
• Are e2e component interactions described?