- Understand or assess the current system or business flow process first (I personally think this is the most important one, most often overlooked, underestimated, or even worse, skipped, and need to be given more time/resource allocation)
- Creating an application description. It contains an explanation of the main functions of the application we will develop. Also, write down the users involved and an overview of the business processes provided by the application.
- Creating a feature list.
- For commercial projects, we will translate this feature list into cost and time estimates. If you are a programmer and not involved in financial matters, please skip this step. You can learn more in here: https://software.endy.muhardin.com/… or mirror: https://web.archive.org/web/2023052…
- Creating a database schema. (I personally prefer to do this before UI mockups, so that I can picture the UI mockups better)
- Creating UI mockups.
- Creating a list of classes and their relationships.
- Creating the application framework in the form of source code.
- Implementing the source code in detail until completion.
- User Acceptance Test, both internally and externally.
Modified from: https://software.endy.muhardin.com/ma…
Mirror: https://web.archive.org/web/20230521062…
ma610 