This is related to the previous posts of mine about software design, so hopefully you know about this. What does this all have to do? A lot, really. One very cool sentence I saw on the Internet on it: “design completes the how that architecture doesn't (and shouldn't) talk about”.
Architecture is the bigger picture. It specifies frameworks, languages, scope, goals and methodologies. On the other hand, design is more specific; design plans how the code will be organized and how different parts of the system will look.
Software architecture is responsible for providing:
- rules for how components and modules will be combined and how they’ll communicate.
- reusability and partitioning solutions to frequent problems.
The common thing for these two things is that they should, SHOULD always be made after goals and requirements have been defined. It makes no sense to do it before. Any attempt to doing it before will most likely lead to necessary changes that will surely affect the efficiency of all your team.
Do you want to become a software architect? Here’s the intro to a short course for doing so!
If you wish to continue reading about this, you can! The sources I used might lead you somewhere:
No hay comentarios:
Publicar un comentario