Who's building your software? How bubble could address the disconnect between business needs and the SDLC process

Software is hard. Designing software to meet rigorous and constantly changing business needs is even harder. SDLC was introduced decades ago in an attempt to add some structure and order to the chaos. But it is often a slow process, and if it isn't implemented well, well lead to frustrating delays to the delivery of a product.

What is SDLC? It's an acronym for Software/Systems Development Lifecycle. It is core part of any project management methodology, and the process can be applied to processes beyond just developing software and systems. There are many ways of approaching SDLC, like Agile, Waterfall, or Scrum, but a typical process will include the following:

1. Gather Requirements - what do the users expect the product to do?

2. Designing/Wireframing - with given requirements, decide what the product will look like.

3. Implementation - develop the product.

4. Testing - run tests to verify that the product meets requirements and the design specifications.

5. Deploy, Train, and Support - the product is released for the users to begin use.

6. Feedback - document how is the product being received by the users. Does is meet their needs? What should be added or adjusted?

7. Repeat steps 3-6 - begin improving the product based on feedback.

SDLC Software Development Lifecycle in Software and Systems Development

How could bubble help with this process, specifically for systems development?

1. Bubble is a visual programming framework that combines all of the components of full stack web development into one straightforward development system. The database, front end, and workflows can be managed in one place. Business applications and databases can be built on bubble at a far more rapid rate.

2.  Bubble makes the developer more accessible. The person developing a bubble application can be a business savvy generalist who understands the business case better than a traditional developer. They potentially could sit down with users and stakeholders and speak to them in their language, then implement quick changes or bug fixes in days (not months), or even in real time. This is revolutionary.

3. A  system for managing SDLC could actually be built on bubble itself to collect requirements from stakeholders and feedback from end users. This could come in the form of a tooltip that appears next to certain modules of an application, periodically requesting feedback or allowing the user to quickly report bugs in real time. The developer could be notified; they would also know where exactly to look.

4. Bubble developers can collaborate in real time.

5. Every new release is stored and fully re-deployable in seconds.