Ir al contenido principal

The Elephant and the Blind Programmers + 4.6 SEM: 4+1 view into software architeture + Six Blind Men

4+1 view, displays the use-case view scenarios for a whole project, it is segmented in 4 counterparts: Logical View, Development View, Process View, and Physical View; with all this view it is possible to view the relations between each stage of the software development, and how it goes the requirements and data through each one of the process for developing software. Performing an analytical architecture. With this structure is possible to actually know what the software is doing.

The point of view determine the abstraction of what is observed, defines with certain knowledge what the observed is. The creation of simple models and techniques allows the comprehension of some topics to be easier, and manages to avoid misunderstanding and have a vast scope and complete vision of the whole entity.

In the programming criteria perception is an important key factor that creates interpretation by understanding what is observable. Without any resources to analyze the observed is impossible to get a common agreement for what is being solved. Interpretation lies into an individual role, the “collective interpretation” is performed by the tools that gets the idea requirements at a general level, with that is easy to manage comprehension from programmers and get a rapid involvement from other parties.

The individual comprehension is limited by the observer interpretation, but this interpretation is a key element for the conformation of the whole idea, the infinite combinations from a group of interpretations, is the puzzle that constructs the process of problem solving.

Observation is focused at some point, the repetitive action of observation from different angles generates a larger vision from what is observed, performing a deep analysis from what is recorded shows the complete scope. The integration of new ideas and opinions enrich the final product. Working with a group of people, has to have an agenda based on a model, an understandable agenda.

References:




Comentarios

Publicar un comentario

Entradas más populares de este blog

Ethical Reflection on Ready Player One

Morrow wrote in his autobiography that he’d left GSS because ... he felt that the OASIS had evolved into something horrible. “It had become a self-imposed prison for humanity,” he wrote. “A pleasant place for the world to hide from its problems while human civilization slowly collapses, primarily due to neglect.” (p. 120) (Halliday speaking) “I created the OASIS because I never felt at home in the real world. I didn’t know how to connect with people there. I was afraid, for all of my life. Right up until I knew it was ending. That was when I realized , as terrifying and painful as reality can be, it’s also the only place where you can find true happiness. Because reality is real.” (p. 364) It is an often topic that circulates now a days, about world domination, and what have we done to this planet we live in. Everyone has it’s own way to manipulate their reality and have different perspectives about the world. For some people it is video games, for other people is ...
Publicar un comentario
Leer más

Microservices

Adaptability is always the answer, depending on the environment is how everything else is going to adapt. In the case of micro services, it is known by a new model for the big monolith replacement, but it is not a replacement, is just another type of architecture that had its benefits because certain features it has, but ensuring that micro services is the only path to follow, causes a problem, this architecture is proper for specific scenarios. In the industry, the massive over use of a new technology is often, for newer creations comes the extended massive usage. At this point other creations or technology can be developed to enter the competition scenario, for now, the old monolithic model is left behind, while micro services models are more used and potential growth is heading that way. As mention before, for some scenarios is viable using micro services, but in not the only alternative, it always depend on what is being worked on. It is true that segmentation and modulation can d...
Publicar un comentario
Leer más

Software Craftsmanship

Software Craftsmanship can be seen as a methodology in order to create good software, which has strong key elements that established the measures and techniques to create professional software development. It is the strong and complete philosophy to practice and helping others learn this craft, and as the Software Craftsmanship Manifesto ( http://manifesto.softwarecraftsmanship.org/ ) established some “rules” that completes this task. Such as the work on software that has to be performed to a well-crafted software, the response to change and the steadily adding value, the relationship between individuals and interactions and through the community of professionals developing software and finally customer collaboration with also productive partnership. Software Craftsmanship has a strong structure that can help the software industry in order to produce software quality, this philosophy can be applied in other topics. During the podcast with Bob Martin, or well known as “Uncle Bo...
Publicar un comentario
Leer más