Software Product Engineering Management

BC-4200 Level 1 Software & Technology 146 providers 409 API surfaces 57 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 409 API surface(s) from 146 provider(s) that can perform some part of it, 57 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.

8 providers, 12 API surfaces

Product Specification Management BC-4200.20

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

4 providers, 8 API surfaces

Software Design Management BC-4200.30

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

4 providers, 15 API surfaces

Software Construction Management BC-4200.40

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

49 providers, 104 API surfaces

Software Quality Engineering BC-4200.50

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

71 providers, 213 API surfaces

Open Source Stewardship BC-4200.60

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

9 providers, 30 API surfaces

Engineering Productivity Management BC-4200.70

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

9 providers, 16 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 30 Complete, well-documented, and agent-ready
Strong 27 Solid coverage with minor gaps
Developing 44 Usable, with meaningful gaps to close
KubeshopArtifactsExecutionsTest SuitesTests8 APIs52.9WarpAgent1 API52.1PostHogvisual_review1 API51.5NuGetPackage Publish1 API50.6MockarooGenerate1 API50.3Dream SportsConfigurationRunsTests3 APIs50.2Rainforest QAFeaturesFoldersGeneratorsRuns7 APIs48.5PerforceChangesCommentsReviews3 APIs48.2Amazon CodeCatalystSpaces1 API48.0TesterarmyGroupsTest RunsTests3 APIs47.7Siemens PLMTest RecordsTest RunsTest Step ResultsTest Steps4 APIs47.5SourcebotGitSearch & Navigation2 APIs47.5SonarSourceissuesqualitygatesqualityprofilesrules4 APIs47.2Val Townvals1 API47.1Emerge ToolsGetPerfTestSnapshots2 APIs46.8RelaceCodeRepo2 APIs46.4Amazon CodeGuru ReviewerCodereviews1 API46.3PlandexDiffsExecution2 APIs46.3TrunkFlaky Tests1 API46.1Bitbucket PipelinesBranch RestrictionsCommitsIssue TrackerPull Requests7 APIs45.7TeamCityInvestigationsProblemsTestsVCS Roots4 APIs45.7GitLab CI/CDbranchescommitsdraft_notesfiles10 APIs45.6Sauce LabsJob AssetsJobs2 APIs44.9SOFYApplicationsScheduled Runs2 APIs44.5Scott AiReviews1 API44.4Spring FrameworkProject Generation1 API44.4LambdaTestAutoheal Command LogsBuildFetch Build ScreenshotsSession7 APIs44.2RadiclePatchesRepositoriesSource3 APIs44.1Socketlicense-policy1 API43.6OpenHandsConversations1 API42.7QoveryGit repositories1 API42.5SonarIssuesMeasuresQuality Gates3 APIs42.1ZeplinColorsComponentsConnected ComponentsDesign Tokens9 APIs42.0SourceForgeTracker1 API41.2ZallyApi Violations1 API41.0Aha.ioEpicsFeaturesIdeasRequirements4 APIs40.7Vellum AIsubpackage_testSuiteRunssubpackage_testSuites2 APIs40.7CoreStoryprdprd_versionsectionstech_spec4 APIs40.6Retell AIList Test Case DefinitionsList Test RunsUpdate Test Case Definition3 APIs40.4TestimBranchesExecutionsLabelsSuites6 APIs40.2MailtrapMessages1 API39.7Craft.ioFeedback itemsWork Items and OKRs2 APIs39.5SwarmiaBuilt-in reports1 API39.5SwitstackTest1 API39.4
Thin 39 Limited public surface area
Emerging 3 Early or largely undocumented
Minimal 3 Almost no public developer surface

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 →