As seen in Part 1 of this article series, there is sufficient reason to always have a good system development methodology for any project that you are working on. Ideally, what will distinguish you as a good developer from the rest of other bandwagon developers is best practices
Additionally, we went ahead to specify two common types of development methodologies; namely: Object-oriented analysis and design (OOAD) and structure-oriented analysis and design. The former is quite common given it's robust nature as well as the elements of object-orientation and abstraction which are quite an influencing factor for a programmer's work.
This article seeks to break down the differences between the two so as to bring the element of clarity.
Object Oriented Analysis and Design
- Uses an incremental methodology.
- Has a very low risk
- Mainly focused on objects, their names, and their variables.
- Mostly suitable for large risky projects with changing user requirements
structure-oriented analysis and design.
- Uses a methodology based on the software development life cycle.
- Focused on processes only.
- Mostly suitable for well defined projects with stable user requirements.
And there it is. Before settling on either of the two, it is important to architect the system being developed theoretically first, ideate around it such that the choice of methodology would be rational.