Software development has changed over the years and the methodologies used have changed along with it, advancing as new tools become available.
The development cycle has mostly remained unchanged:
- Meet with the customer to get requirements
- Develop something
- Show the customer
- Goto step 1
Developing using the Waterfall methodology meant the cycle could take months or even years depending how complex the software was. If something was wrong there would be a change request or a trouble report created and the code would (hopefully) be fixed and then shown to the customer again.
Agile development was transformational and has led to much higher quality software, but the cycle hasn't really changed. Our communication, development and tracking tools now allow us to work faster and show the customer our progress more frequently, usually every two weeks or so. Customer communication and buy-in leads to less errors and less time between fixes.
We can assume then that whatever comes in the future will most likely keep this cycle in place, only looping faster. If our tools can enable us to build things in real time, we might be able to move to a new form of interactive development. Imagine sitting with the customer and building software in real time, getting immediate feedback and making changes on the fly.
This is one of the benefits we hope to achieve with simplicityEngine. By breaking up software requirements into blocks in a logical flow simplicityEngine takes away the repetitive nature of coding, allowing you to quickly turn ideas into a working piece of software.
We’re excited about where software is heading, nothing would make us happier than opening the door for new developers or helping seasoned developers deliver their ideas faster than ever before.