Last time we talked about braking big problems into small problems, but that means you have a lot of small problems instead. So today we are going to discuss where to start, and make sure that you don’t waste any time working on wrong things.
”You have to start somewhere, But you better pick the right somewhere”
The best way to tackle this problem is by an architecture of the program. This helps a lot with the design structure and order things.
The structure of architeture is built by 3 very important questions:
- Is this part of the essence of the system?
- If so, what does it mean?
- How do I do it?
Is this part of the essence of the system
Is the feature really core to what a system actually is? Think about it this way: can you imagine the system without that feature?
If so, what does it mean?
If you are not sure what the description of a particular feature really means, it is probably pretty important that you pay attentio to that feature. Anytime you’re unsure about what something is, it could take lost of time.
How do I do it?
Another place to focus your attention early on is on features that seem really hard to implement, or are totally new programming task for you. If you have no idea how you are going to tackle a particular problem, you better spend some time up front looking at that feature, so it doesn’t create lost of problems down the road
References
Head First object-oriented analys and design – chapter 7
Olles blog 