2. Design and Architecture
PHASE OBJECTIVE
Design your Compass implementation to achieve your organizations goals.
2.1 Connected Toolchain
Connecting Compass to your developer toolchain is one key way Compass reduces the cognitive load on your developer community. Having access to information from across your toolchain in a single place reduces the need to context switch between applications and the time spent looking for information.
The below table outlines some of the types of tools we suggest you connect to Compass.
| Category of tool | Compass extension point |
| Plan and track work (e.g., Jira) | Issues tab, components (within Jira) |
| Source code repository (e.g., BitBucket, GitHub, GitLab) | Software catalog, scorecards, metrics, templates, activity feed |
| Build and deployment (e.g., Jenkins) | Scorecards, metrics, activity feed |
| Documentation (e.g., Swagger UI) | Apps |
| Monitoring (e.g., New Relic, Datadog) | Scorecards, metrics, activity feed, tags, link to dashboard |
| Security (e.g., Snyk) | Scorecards, metrics |
| Service Management (e.g., Jira Service Management) | Activity feed |
The table below suggests a format for capturing this activity's output. It will be used during the setup and integration phase of this guide.
| Tool/application name | Deployment | Category | Owner |
| Bitbucket | Cloud | Source code repository | Jessica Smith |