Software Product Engineering Management

BC-4200 Level 1 Software & Technology 38 providers 187 API surfaces 20 rated strong or better

Discovery, specification, design, implementation, code review, and quality engineering of SaaS products from idea through release-ready build.

Software Product Engineering Management (BC-4200) is a level-1 business capability in the Software & Technology model. The catalog holds 187 API surface(s) from 38 provider(s) that can perform some part of it, 20 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

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Product Discovery & Backlog Management BC-4200.10

Opportunity research, ideation, validation, and backlog stewardship that translate market and customer signals into a prioritised body of work.

1 provider, 3 API surfaces

Product Specification Management BC-4200.20

Capture of intended behaviour, constraints, and acceptance criteria so that engineering work can be executed predictably.

3 providers, 7 API surfaces

Software Design Management BC-4200.30

User experience, system, and accessibility design for software products, anchored in shared design systems.

2 providers, 5 API surfaces

Software Construction Management BC-4200.40

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

18 providers, 46 API surfaces

Software Quality Engineering BC-4200.50

Test strategy, automated test suite stewardship, and defect management for software products.

20 providers, 113 API surfaces

Open Source Stewardship BC-4200.60

Inbound use, outbound contribution, and supply-chain artefacts for open-source software embedded in the product.

2 providers, 9 API surfaces

Engineering Productivity Management BC-4200.70

Internal developer platforms, tooling, and engineering performance measurement that lift sustained delivery throughput.

1 provider, 3 API surfaces

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 11 Complete, well-documented, and agent-ready
SalesforceRuns1 API89.3SentryIssuesRepositoriesTest Results3 APIs77.4GitHubGitIssuesPullsRepos4 APIs77.2Adobe SuiteBranches1 API75.7Azure DevOpsCommitsPull RequestsPushesRefs8 APIs74.4PluralsightCoding MetricsCollaboration MetricsDORA MetricsPull Requests4 APIs73.9Microsoft AzureTest Base PackageTest Result2 APIs73.3iOSCiTestResultsScmGitReferencesScmProvidersScmPullRequests5 APIs73.1PostmanpullRequests1 API72.4GitLabProjects1 API72.0BitbucketBranch restrictionsCommitsIssue trackerPullrequests7 APIs67.8
Strong 9 Solid coverage with minor gaps
AtlassianBranch RestrictionsCommitsPullrequestsRefs6 APIs65.6OutSystemsAnalysis StatusAssets Quality MetricsCode AnalysesFindings5 APIs64.9TricentisAttachmentsCyclesDatasetsParameters28 APIs64.9MicrosoftGit1 API58.8FigmaComponent SetsComponentsFiles3 APIs57.9UpsunRepository1 API56.9tessl.ioEvals1 API56.5Platform.shRepository1 API54.7Salesforce AutomationTesting1 API54.7
Developing 16 Usable, with meaningful gaps to close
MendLibrary - Organization1 API53.0Amazon CodeBuild#X Amz Target=CodeBuild 20161006.BatchGetReports#X Amz Target=CodeBuild 20161006.DescribeCodeCoverages#X Amz Target=CodeBuild 20161006.DescribeTestCases3 APIs52.9Amazon Device Farm#X Amz Target=DeviceFarm 20150623.CreateDevicePool#X Amz Target=DeviceFarm 20150623.CreateTestGridProject#X Amz Target=DeviceFarm 20150623.DeleteDevicePool#X Amz Target=DeviceFarm 20150623.DeleteRemoteAccessSession32 APIs52.8PostHogvisual_review1 API51.1BluejayCreate SimulationDigital HumansEvaluateGenerate Digital Humans16 APIs50.1Siemens PLMTest RecordsTest RunsTest Step ResultsTest Steps4 APIs47.9Dream SportsConfigurationRunsTests3 APIs47.6SonatypeComponentsCycloneDXFirewallLicense Legal Metadata Report8 APIs47.5SonarSourceissuesqualitygatesqualityprofilesrules4 APIs46.2TeamCityInvestigationsProblemsTestsVCS Roots4 APIs46.1GitLab CI/CDbranchescommitsdraft_notesfiles10 APIs45.3QoveryGit repositories1 API43.2Retell AIList Test Case DefinitionsList Test RunsUpdate Test Case Definition3 APIs42.0Aha.ioEpicsFeaturesIdeasRequirements4 APIs41.3CoreStoryprdprd_versionsectionstech_spec4 APIs39.4JetBrainsCode ReviewsIssues2 APIs39.3
Thin 1 Limited public surface area
PenpotCreate FileDelete File2 APIs36.4
Emerging 1 Early or largely undocumented
Amazon Web ServicesCodereviews1 API24.2

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

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 Product Engineering 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 →