CHAPTER 10 – The OOA&D Lifecycle

--Originally published at Newbie Programmer

The last chapter is important, because is about putting all the things together, all the things that we learned through the chapters are revisited and make sense when they are together, and this makes the Object-Oriented Analysis & Design Project Lifecycle that is an Iterative Development that is applied to each small problem and is iterating with every problem. And this chapter explains the seven phases and a final one of this development.

Feature List: This is necessary to do write the things that the applications need to do, when this is finished we can move to the use of case diagrams.

Use Case Diagrams: This phase helps us to thing about how the application will be used without unnecessary details. In the diagrams we are dealing with interactions between actors and the system, the features reflect functionality and use cases the usage.

Break Up the Problem: With the use case diagrams we can break this problem in smaller pieces, then we can start iterating with these pieces until the application is complete with every use case, int this phase is an extra step that is Understand the Problem before we begin with the Requirements phase because we need to understand well the problem.

Requirements: Are the specific things that the system must do to work correctly, and this help to see if the use case works.

Domain Analysis: In this phase we need to do a textual analysis on the use case and figure out the nouns (candidate classes) and verbs (candidate operations).

Preliminary Design: This phase is about making design decisions, that should be based on how the application will be used and to apply object-oriented principles.

Implementation: Here we begin with the creation and testing of the code, with doing this based in the analysis, and we

choose a way of development explained in the chapter nine (Feature driven or use case driven), and this phase is not finished until the testing is completed and the code is completed and works well.

At this time we completed an iteration, if we have remaining use cases or features to implement we need to start again at the requirements phase, and is important to remember that we can have some code that can help us to solve the problem for the next iteration, if we don’t have more iterations to do and everything is working well we can go to the final phase Delivery.

Delivery: The final phase is when you done your product and can be released and more important get paid.

This was the final chapter, it’s a little short because all the topics that are in this are covered in past chapters, but its important to have an idea of how all of this are working together. This is the end of the lifecycle, but it never ends because we can make changes to make it better or to solve little details.


Photo by Hans Engel