Driving Quality — The LCSDLC
As a developer, I’m pretty used to the good old traditional Systems Development Life Cycle (SDLC). It really did help IT developers crank out reliable and secure software for more than 20 years. It’s structured, understandable, and auditable. It’s been what IT has hung its hat on for a long, long time. Developers are schooled on it. Managers are certified in it. It’s the way IT does software.
However, I don’t think the old SDLC quite fits the new no/low-code world, “as is”.
The traditional IT SDLC assumes a consistent level of expertise, training, certification, and experience across developers—something not always present in the no/low-code world. So a bit more oversight is probably in order.
The traditional SDLC process looks something like this, as it applies to a professional IT developer developing an online application:
- Maintain (sometimes included, sometimes not)
Makes sense, right? There are various versions of this SDLC, but you probably get the gist.
The SDLC is a powerful tool. As part of a wider quality framework it should be part of your no/low-code world, it’s the centerpiece of quality assurance.
“But, ‘Low-code is not traditional web development’,” you say. Yep, you’re right.
Unlike traditional IT web development, no/low-code development moves at the speed of thought. So, the question is, can we adapt the traditional SDLC, pare it down here, bulk it up there, and dust it off for no/low-code success? Yes. Because software quality is all about process, we can create a new LCSDLC (Low-code Systems Development Life Cycle).
So, at VeilSun we’ve done this—and at 10,000 feet it looks something like this:
- Design Review
- Build/Security Review
- Ongoing Audit
Though we’ve added 3 (audit) LCSDLC steps, we’ve also drastically reduced the depth of detail of the original 6 SDLC steps to require far less effort. Low-code builders won’t go as deep—nor do they need to.
In practice, your LCSDLC process should be lightweight and nimble. It should never slow progress and should result in Web software quality that far exceeds the quality of traditional development. Whether it’s 3 steps or 12, it should be template-driven, and easy to use.