Steps You Should Be Automating in the SDLC - Part 2
November 06, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 2 covers the coding process.

Start with Steps You Should Be Automating in the SDLC - Part 1

CODING

Companies should automate development as much as possible without compromising security. Key to this is reducing the amount of manual coding through low-code platforms, or eliminating it entirely with a no-code system.
Colin Earl
CEO, Agiloft

Automation has permeated many aspects of the software development life cycle. You need infrastructure? Operating systems? Applications? No problem — all it takes is the click of a button. Testing? Deployment? Monitoring? Plenty of automation going on there also. But what about that large bit in the middle — the development. Most organizations still write code by hand and this is biggest opportunity when we're talking about automation. Low-code or high-productivity platforms help organizations bring automation to this, the most significant part of the SDLC, through a visual assembly approach to development. This isn't about replacing developers. This is automation to empower developers to do more — to focus on delivering business value instead of the syntax of a language that, in a few years, will probably be considered "legacy technology."
Mike Hughes
Principal Platform Evangelist, OutSystems

CODE CHECK IN AND CHECK OUT

As part of your DevOps process, an area that would benefit from automation: Code check in and check out process to eliminate circumventing critical tests and steps in the CICD pipeline.
Jeanne Morain
Author and Strategist, iSpeak Cloud

FIXING ERRORS

The bureaucratic toil associated with large-scale software efforts should be fully automated. Adherence to policy and governance practices is important for scaling software development, but it often results in a lot of toil for human developers. This toil — fixing small errors detected by linters, almost-but-not-quite adhering to the style guide — is the kind of thing that is tedious to do manually. It adds friction to development, which slows things down. It's important, but not urgent, so it tends to get put off unless you have super-human levels of discipline.We have robots to vacuum the lint off our floors, so why not do the same thing with the codebase? Automated repairs of common errors are like Roombas for code: they keep things clean so developers are free to work on other, more interesting, tasks.
Ryan Day
Co-Founder and COO, Atomist

THE BUILD

The most straightforward and valuable area to automate is the build, deploy. These tasks provide the greatest opportunity to remove waste and also highlight potential friction points when deploying into production. Removing people from these activities not only increases quality but improves the architecture by shining a spotlight on the way in which the software is constructed. Great way to test this automation is to get EVERYONE in the team to do the build and NOT leave it to a single person, or small group. That would ensure that the kick off process is simple, documented and with luck transparent to everyone.
Dave West
CEO and Product Owner, Scrum.org

DevOps groups should seek to automate processes that eliminate "spaghetti code" that agile programming is supposed to address in the code-building practice itself. Lack of standardized workflows can slow down the overall development process with bad check-ins, integration errors and Q/A out of sync with production. To begin with, they should automate the multitude of objects, packages and pieces of code that need to stay working together.
Steve Garrison
VP Marketing, ZeroStack

API MANAGEMENT

Automating the API management process will help developers increase their velocity of pushing out new API releases as well as streamline access to partner API clients. Developers should look to API automation for creating or importing their own API definitions when rapid releases are demanded. Developers should choose an API gateway that can effortlessly scale with their business needs as well snap into their existing DevOps workflow.
Nick Tran
VP, Developer Relations, Akamai

When an API signature changes, or an API version is retired, the application could become unstable or lose functionality. Implementing automated identification of API dependencies and monitoring for changes in signature and availability help insulate from API contract issues. When coupled with an understanding of data flowing to and from the API, supporting increasingly complex data management and privacy regulations becomes simpler.
Tim Mackey
Technology Evangelist, Synopsys

APPLICATION WORKFLOW

Companies should automate testing of workflows, making sure these processes function properly and nothing is broken or missed when the code comes together.
Anand Subramanian
SVP of Delivery, Ness

One area getting more focus from DevOps teams is automating and orchestrating the workflows that actually run the application in the operational stage. Too often application workflow orchestration is still being done right before release to production. This typically causes a fire-drill because the workflows were not tested with the rest of the code through the earlier phases. DevOps teams are now adopting a Jobs-as-Code approach that simply adds application workflow instrumentation as a code artifact with the business logic. This means one complete code set flows through the full CI/CD automation pipeline and is ready for production, with automation and orchestration governance already built it. Avoiding the fire-drill means DevOps teams avoid unplanned rework and deliver the business service into production faster.
Gur Steif
President, Digital Business Automation, BMC Software

PROJECT MANAGEMENT

Other non-obvious, but extremely helpful automation can be applied around software project management like automated state transition for tasks on a project board (e.g. move all newly added issues to "To-do" or to move all reopened issues to "In-Progress").
Lee Calcote
Head of Technology Strategy, SolarWinds

Read Steps You Should Be Automating in the SDLC - Part 3, covering the development environment and the infrastructure.

Share this

Industry News

July 29, 2021

Couchbase announced the general availability of Couchbase Server 7.

July 29, 2021

Cycloid has unveiled Infra Import, a tool that automatically reverse engineers Terraform Infra-as-Code (IaC) from manually deployed infrastructure.

July 29, 2021

Launchable closed a $9.5 million Series A investment.

July 29, 2021

Rafay Systems announced automation and monitoring enhancements to its flagship Kubernetes Management Cloud (KMC).

July 28, 2021

Progress announced the R2 2021 release of Progress Telerik Test Studio, the enterprise UI test automation platform.

July 28, 2021

Synopsys announced the availability of new Rapid Scan capabilities within the company's Coverity static application security testing (SAST) and Black Duck software composition analysis (SCA) solutions.

July 28, 2021

Bitdefender announced GravityZone Security for Containers, expanding its cloud workload security (CWS) offering with run-time support for containers and Linux kernel independence.

July 28, 2021

Armory announced Armory Enterprise on AWS Quick Starts, automated reference deployments built by Amazon Web Services (AWS) solutions architects and AWS Partners.

July 27, 2021

Katalon introduced Katalon TestOps, an open and comprehensive test orchestration platform designed to help enterprises scale test automation and streamline DevOps pipelines.

July 27, 2021

Digital.ai achieved Federal Risk and Authorization Management Program (FedRAMP) “In Process” status for an Enterprise Agile Planning (EAP) tool.

July 27, 2021

Aqua Security rolls out the availability of its new Aqua Platform, with a unified console to ease the journey from scanning and visibility to workload protection in cloud native environments.

July 26, 2021

Parallel Agile announced a new version of CodeBot, a low-code MERN stack application generator.

July 26, 2021

Appian unveiled its new Appian Japan regional office.

July 26, 2021

CloudTruth raised $5.25 million in seed funding led by Glasswing Ventures and Gutbrain Ventures, with additional funding from Stage 1 Ventures and York IE.

July 22, 2021

Postman successfully obtained the System and Organization Controls (SOC) 2 Type 2 and SOC 3 Type 2 reports for the Postman API platform, meeting critical industry standards relative to the Trust Services Criteria for security, availability, and confidentiality.