Build & Integration domain in the CSDM model
Summarize
Summary of Build & Integration domain in the CSDM model
The Build & Integration domain in the Common Service Data Model (CSDM) supports development teams during the build phase of the software development life cycle, especially within Agile methodologies. It focuses on representing the logical development details of enterprise applications or digital products that your organization will deploy and use. These records are not operational Configuration Items (CIs) and are distinct from those used in IT Service Management (ITSM) processes.
Show less
Key Features
- Agile Development Component: This CI represents a discrete development effort or software element within a larger business application or digital product. It is recorded in the Agile Development Component table ([cmdbcisdlccomponent]) which supports enhanced visualization and management of the application development pipeline within DevOps products.
- Non-operational Records: Agile Development component records are not involved in Incident, Problem, or Change Management and do not require specific configuration for those processes.
- Integration with DevOps: The DevOps Change Data Model connects your DevOps tool chain with existing platform data to accelerate changes and maintain transparent risk management.
- Table Relationships: The domain includes relationships such as Business Application (in the Service Consumption domain) containing Agile Development components, which in turn relate to Service Instances within the Service Delivery domain.
- AI System Digital Asset: Represents software/application components, including third-party or custom assets, that feed into build and integration pipelines and AI governance. These assets may be deployed or not yet deployed.
- Types of Agile Development Components:
- Application: Deployed instances of Agile development application components, such as microservices and APIs, typically built on behalf of the Service Owner.
- Infrastructure: Infrastructure CIs capturing configuration snapshots, such as databases or security configurations, representing deployed infrastructure components.
Practical Application for ServiceNow Customers
ServiceNow customers can leverage the Build & Integration domain to effectively model and manage the development efforts of digital products within their CMDB without impacting operational ITSM processes. Using the Agile Development Component table and its relationships enables better visibility and control over application build pipelines and integration points, supporting DevOps initiatives and fostering alignment between development and service delivery teams. Additionally, the inclusion of AI system digital assets helps manage AI-specific software components within the build lifecycle.
Development teams use the tables in the Build & Integration domain during the build effort (systems development life cycle — AGILE DEVELOPMENT) of digital products. The tables represent the logical development details of the enterprise applications (digital products) to be deployed and used by your organization. These are not operational CIs.
Tables and relationships in the Build & Integration domain
An AGILE DEVELOPMENT component is a CI that represents a unique development effort of code. It represents parts of a larger business application or digital product broken down into its individually developed components. In other words, the AGILE DEVELOPMENT component is a software element of a larger application or technology. AGILE DEVELOPMENT component CI records in the AGILE DEVELOPMENT Component [cmdb_ci_sdlc_component] table enable the DevOps product to provide enhanced capabilities for visualizing and managing your application development pipeline.
Records in the table are not operational and are not direct targets of the ITSM Incident Management, Problem Management, or Change Management processes. You therefore are not required to configure Agile development component records. The Agile development component table is available through the CMDB schema version 1.33.
The DevOps Change Data Model is built on a powerful data model that connects your DevOps tool chain to the work and data already in the platform. The model provides the ability to accelerate changes while ensuring effective and transparent risk management.
The Build & Integration domain includes the following tables and relationships:
- Business application (Service Consumption domain) Contains::Contained By Agile development component
- Agile development component has a Contains::Contained By relationship with the Service instance table in the Service Delivery domain.
Tables used during the Build & Integration phase of the service life cycle
The Al System Digital Asset represents the Software/ Application components for Al and Gen Al services. For the purposes of build, integration, and Al governance, the Al System Digital Asset (ServiceNow, third-party asset, or custom) represents the deployable software source, binaries, and components that feed into the Build & Integration pipelines. An asset can be deployed or not currently deployed.
Types of Agile development component
- Application: A service instance is a deployed instance of the Agile development application component. Examples include micro services and APIs. The build team typically builds service instances on behalf of the Service
Owner (as described in Manage Portfolio domain in the CSDM model).
See Use Service instance (Application Services) dashboard to monitor health.
- Infrastructure: Any infrastructure CI that represents a snapshot of its configuration details is a deployed instance of the Agile development infrastructure component. Examples include database and security configurations.