Design an Architecture
Your specification tells you what you are going to build, but it does not tell you how. The specification doesn’t help you fit all the pieces together. In fact, specifications rarely include details about the different pieces that make up a program. It’s time to design an architecture for your program after you have created the spec but before you start writing code.
When designing your software’s architecture, you should identify all the different parts of your program and then decide how those different parts will fit together. Architectural decisions are, in my opinion, the hardest part of planning. You have to use your imagination to see what your software will be like when it is complete. You have to identify all ...
Get Learning to Program now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
