Engineering Practices

Reviewed: 2025-10-09

Dr. Eriks Klotins

Questions regarding the research presented on this page? Contact Dr. Eriks Klotins.

SERL focuses on making modern software delivery sustainable, evidence-informed, and reusable. A central thread explains how continuous software engineering (CSE) changes planning, feedback, and governance, emphasizing “readiness” and the real friction teams face when adopting new ways of working. The work also foregrounds making costs and benefits of CSE visible so investments in automation, pipelines, and tooling can be calibrated to context, with user-feedback loops highlighted as uneven yet crucial in practice.

A second thread is strategic reuse. SERL clarifies what counts as a reusable “asset,” proposes a taxonomy, and examines how companies actually reuse - from automated acceptance tests to microservices and InnerSource components. Observations point to reuse working best as an organization-wide ecosystem supported by decision models, evidence, and context factors - not ad-hoc cherry-picking.

Security and quality are treated as pipeline-native concerns. Results explore automating compliance as part of continuous delivery, exercising non-functional requirements in CI, and enriching SBOMs so vulnerability information feeds operational decisions. Broader enablers include aligning CSE with digital transformation and value-vs-waste thinking, adapting to distributed work, and linking internal quality to customer-value signals - while recognizing software’s “half-life” in portfolio planning.

Current and Future Work

Emerging directions include operationalizing CSE readiness as lightweight diagnostics and tying them to cost-benefit tracking. Organizations are building reuse ecosystems that blend InnerSource, service catalogues, and evidence-based selection models. Pipelines are poised to integrate “compliance as code” with richer SBOM semantics, expand CI-based NFR exercising, and connect telemetry from internal quality to customer outcomes and lifecycle metrics such as software half-life.

Together, this work shows how to evolve delivery systems that are faster, safer, and more learnable - where reuse, evidence, and feedback turn everyday engineering into continuous improvement.

Important context

This text was generated by AI and edited by humans. It is based on SERL's research publications between January 2020 and September 2025. For technical questions, please contact Dr. Michael Unterkalmsteiner.