*Intense victory music playing in the background*
Congratulation, you have taken a very big step in you carrier and are now graduate to the next level. The real world! What does that mean exactly? Your application must do more than just work, it has to work so its fits into the real world so real people can use it in their everyday life.
As said it is important to understand that the software has to work in the real world, and not just in a perfect world! Which means there is a lot more and different context to it.
The key to making sure your application works properly and that the real world doesn’t screw up your application is analysis: Whish means figuring out potential problems, and then solving those problems – before you release your app out into the real world.
Step 1 – Identify the problem:
A good analysis starts with identifying the potential problems. This can sometimes crystal clear and other times very hard to identify.
Step 2 – Plan a solution:
Once we hade identify the problem it is time to plan a solution the problem. This can also sometimes be very easy meanwhile other times very hard
Step 3 – Update your use case:
If your use case is outdated it is now time to get back and update the diagram with the new steps that we figured out and then later on make the necessary changes to the code.
“A good use case clearly and accurately explains what a system does, in language that’s easily understood. With a good use case complete, textual analysis is a quick and easy way to figure out the classes in your system.”
REFERENCES
https://learning.oreilly.com/library/view/head-first-object-oriented/0596008678/ch04.html
https://realworldcoding.io/why-is-coding-so-hard-10af8a77ff18
Olles blog 
