So far have we learned a lot about building a software the right way and in OOA&D we have bunch of different tools to use to help out. But how do we use those tools when building something really big? Domain analysis and use case diagrams will become very handy when handling big projects
You may ask, how do I actually solve big problems? The answer is pretty simple, you solve big problems the same way you solve small problems. Think about how you work on big problems, in big software applications. You usually look at the big picture, but it is better to see a lost of individual pieces and treat each of those pieces as an individual problem to solve. One step at a time applying the basic principles to each individual problem and then move on to another when once one part is finished.
Example of basic principles that are important to use that we have learned so far:
- Encapsulating
- Coding to an interface
- Get good requirement
- Analysis
- Well build software is easy to change and extend in the future
References
Head First object-oriented analysis and design – chapter 6
https://www.logicalshift.co.uk/articles/building-bigger-software/index.html
Olles blog 