Software Product Engineering Management › Software Construction Management

Software Construction Management

BC-4200.40 Level 2 Software & Technology 18 providers 46 API surfaces 13 rated strong or better

Implementation practice including source control, code review, and collaborative coding disciplines.

Software Construction Management (BC-4200.40) is a level-2 business capability under Software Product Engineering Management in the Software & Technology model. The catalog holds 46 API surface(s) from 18 provider(s) that can perform some part of it, 13 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Source Code Management BC-4200.40.10

Stewardship of source repositories, branching policy, and code ownership.

no catalog coverage

Code Review Practice BC-4200.40.20

Peer review of code changes against engineering and security standards.

no catalog coverage

Pair & Mob Programming Practice BC-4200.40.30

Collaborative coding practices used to share knowledge and lift quality on selected work.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 9 Complete, well-documented, and agent-ready
SentryRepositories1 API77.4GitHubGitPullsRepos3 APIs77.2Adobe SuiteBranches1 API75.7Azure DevOpsCommitsPull RequestsPushesRefs5 APIs74.4PluralsightPull Requests1 API73.9iOSScmGitReferencesScmProvidersScmPullRequestsScmRepositories4 APIs73.1PostmanpullRequests1 API72.4GitLabProjects1 API72.0BitbucketBranch restrictionsCommitsPullrequestsRefs6 APIs67.8
Strong 4 Solid coverage with minor gaps
AtlassianBranch RestrictionsCommitsPullrequestsRefs6 APIs65.6MicrosoftGit1 API58.8UpsunRepository1 API56.9Platform.shRepository1 API54.7
Developing 4 Usable, with meaningful gaps to close
TeamCityVCS Roots1 API46.1GitLab CI/CDbranchescommitsdraft_notesfiles10 APIs45.3QoveryGit repositories1 API43.2JetBrainsCode Reviews1 API39.3
Emerging 1 Early or largely undocumented
Amazon Web ServicesCodereviews1 API24.2
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Software Construction Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →