Software Architecture

Software Architecture

This week I read the chapter 14 of the book "Code Craft: The Practice of Writing Excellent Code" titled " SOFTWARE ARCHITECTURE Laying the Foundations of Software Design"

the first thing we should do is define what is software architecture, as we use the word architecture sounds logical that a building comes to our mind, but talking about software we can take the idea of a structure, so the author told us we can join the concepts to create in our brain the idea of high level design but of course the reason of the “similarity” in the concepts comes because the software architecture is used to create a propitious place to make code, at the end this can be used as a guide for the development.

Some benefits of the software architecture are that this helps to validate requirements and conditions of a project so it can be used in a more free way for the different areas like design and development and can help to “talk the same language”, what this means is that they have a common vision of the project, the way it is going to be constructed and how the construction will work.

One of the thing that I keep in mind from the chapter was the idea of simplicity, we should not try to make ridiculous complex solutions that will make the problem to solve even more complex, or bare solutions which will not be enough to solve what we want, we need to make a proportional solution to the problem, that is what I understand for simplicity.

The author mentions four kinds of views that will help building the architecture:

  • The conceptual view:  It shows the principal parts of the system and the connections between them
  • The implementation view: this one shows the implementation modules
  • The process view: It shows the dynamic structure
  • The deployment view: which shows the allocation of task 

Comentarios

Publicar un comentario

Entradas populares de este blog

Is Design Dead?

Is Design Dead? I am going to write about the article “is Design Dead?” By Martin Fowler, it was a interesting article and was written in a unfamiliar way considering the title. He starts talking about the extreme programming and how it is one of the causes of the poor pre design that nowadays is (barely) used for big or small development. Software development needs like almost everything a design which defines not only how it will work, but how to make the specific modules and what job they are going to perform to accomplish a global goal. And well he basically explains the differences between planned design an evolutionary design, that is the reason why I think the title is funny, two kinds of design but he says it is dead, basically what happens is that, the extreme programming and the constant use of the technique pushes the developers to use the evolutionary design. Why? Easy, the extreme programming is a practice thas searchs the simplicity in the creation of...
Leer más

Understanding the SOLID Principles

This week the blog will talk about the article "Understanding the SOLID Principles" written by Edward Guiness, this is a brief summary that presents the definition of the SOLID Principles. The general objective of the SOLID principles, and so the author in the article, is to implement best practices in the creation of objects and classes in specific cases depending on the situation that is presented. And with you, the 5 principles *drumroll*: • Single Responsibility Principle • Open/Closed Principle • Liskov Substitution Principle • Interface Segregation Principle • Dependency Inversion Principle The first of this is the Single Responsibility Principle, it says that a class, should have just exactly one responsibility, just one reason or an only class of reason to exist. This responsibility should be implemented to the class, so for this reason a class just has one reason to be modified. Why implement this? Easy, in a big project you will have lots of classes ...
Leer más