What do I need to start developing a software application?
By Declan Healey 25 June 2020 Way of Working
So, you have a rough idea for an app to address some problem in your business - what next? Getting started on any software project can often be overwhelming, so it is crucial to be equipped with the right artefacts prior to building your application.
As we explored in our article on Why is scoping important?, this is an essential process towards fully exploring your problem before proposing a viable solution. Only then will you have a clear understanding of how your end product should look, in addition to a comprehensive plan to ensure your project stays on track during the development lifecycle. What then are some of the most important artefacts to be generate as part of the scoping process?
1. A backlog of requirements
What is a product backlog? is ultimately a representation of what needs to be built as part of your solution, enabling shared understanding among the product team involved. Typically, these are divided into epics and user stories, otherwise representing high-level themes and fine-grained requirements respectively.
When it comes to the development phase, your backlog it critical as it will ultimately inform what is contained in the milestones and iterations that follow.
2. A behaviour identification spreadsheet
Behaviours are a core component of Codebots and can be utilised in your application, representing patterns of functionality which are often repeated across different software products. Behaviour Identification Guidelines, the key here is to recognise where a particular Behaviour can cover one of your own business patterns or requirements. Identifying Behaviours, you can easily map the relevant interactions in your application to Behaviours and determine the level of Behaviour coverage, prior to developing your solution.
During the scoping phase, you should find yourself generating a series of prototypes to help validate your idea and ideate on improved solutions. Whilst Rapid prototyping allows your team to quickly try and test new things, Prototypes are also necessary when it comes to conducting high-quality testing. Not only are these suitable for gathering user feedback, but they are also good to show the team and stakeholders involved exactly how the product should look when complete.
4. An entity diagram
As we have explored previously, an entity diagram is a visual representation of the underlying database structure of your application.
When creating an application using Codebots, you can utilise the Entity Diagram editor in the Platform to build this out, adding in any Behaviours where necessary. When you are ready, it's as simple as hitting the Build button to kick off development, and watch the bots work their magic!
5. Software estimations
Finally, software estimates can provide valuable insights into your project before starting development. As part of our own Way of Working, we have developed a tried and tested method to How do you calculate the length of a software project?. Armed with your estimates, you will be best equipped to set realistic expectations among the the different stakeholders involved in your project.