Erika Rodriguez
Zacatecas. January 21, 2016 (News Agency Conacyt) .- Pearl Velasco Elizondo co-authored the first book of architecture software in Spanish, entitled Software Architecture: Concepts and cycle development , written in collaboration with his colleagues, Dr. Humberto Cervantes and science teacher Luis Castro. This book, published by Cengage Learning, went on sale in the second half of 2015.
Dr Velasco Elizondo is also the founder and instructor of the Summer School of Software Engineering, which, since 2012, has four editions successful, bringing together stakeholders in the design and development of systems of several states.
Currently, he is a research professor at the Academic Unit Program Software Engineering Electrical Engineering at the University of Zacatecas (UAZ); Center for Research in Mathematics (Cimat) participates as a guest professor teaching the course of Architecture software in the master’s program.
Born in Xalapa, Veracruz. He studied at the Universidad Veracruzana degree and master’s degree in the Autonomous University of Tlaxcala. Subsequently, he was a research associate at the National Laboratory for Advanced Computing (Lania), located in his hometown. In 2008 he obtained his doctorate in computer science at the University of Manchester, UK. Upon his return, he joined as a research associate in the Cimat, Unit Zacatecas.
she Conducted a postdoctoral fellow at Carnegie Mellon University, Institute of Software Research (ISR) in the United States, where he helped to Dr. David Garlan, considered one of the founders of the area Architecture software. All his graduate has made a scholarship from the National Council for Science and Technology (CONACYT) and has performed all related to the design and implementation of systems software focused on architecture projects, which are currently the main topics of interest and expertise
Conacyt News Agency (CIA). What is the main content of the book Software Architecture: Concepts and development cycle
Pearl Velasco Elizondo (PVE): This book is a means to know how to design systems software focused on architecture. There was a book like this in Mexico, this is the first. There are many books on architecture software , but none that addresses the development life cycle of architecture, as addressed in this book. It is a book that takes you by the hand to understand simple and concrete concepts, techniques and methods of architecture design software .
The interesting thing about this book is that it includes material generated from the practical experience we have had authors in the development industry software . The three authors have had the opportunity to combine our academic activity with design activities and development of systems in companies in Mexico and other countries.
It is an interesting, well-written book was reviewed by professionals from Mexico and abroad before publication. The revised colleagues Software Engineering Institute in the United States, research institutions in Mexico, system architects Mexico and Argentina; then it is a book which was also enriched with suggestions of all these people
AIC. How to apply their knowledge in activities such as teaching and industry
PVE: I’ve been fortunate to be able to apply through various mechanisms, my knowledge in academia and industry. For example, use the summer to stay somewhere where systems development is done. In previous years I have been able to collaborate with companies in Colombia, with developers National Institute of Astrophysics, Optics and Electronics, and last summer collaborated with zacatecana company that is currently developing control systems for the mining industry.
I believe that these experiences have been instrumental in enriching as I teach; and vice versa, as I had the opportunity to work from a more academic point of view this issue of architectural design, when I go to the industry, I think I could make useful things product of other, more analytical, I developed my academic and research experience.
Today, as a teacher of Software Engineering Program of the UAZ, teach engineering requirements analysis and object-oriented software architecture design. These three courses are related to my topic of interest and expertise. For example, the requirements are the raw material to design an architecture and object-oriented design is a possible approach refinement of architecture
AIC. What is the importance of domain-centric systems architecture software in the industrial field?
PVE: The area of Architecture software has its origins in the early 70’s I think in Mexico is not entirely clear what is the architecture of software and still is not adopted this building focused on a systems architecture design.
Design and build a system is, in some ways, similar to design and build a house. For example, should have “good foundation” for a system to grow and provide service to many users without having to slow down or collapse. I guess you have lived the experience of using a system that is slow, it throws errors or that it no longer can be added new functionality. So back to the analogy of designing and building a house, an architect never start building without a design in which the main requirements of users, for example are addressed, support the eventual construction of more apartments in a building without from collapsing.
Generally, the model contains architectural design concepts that the architect used to meet these requirements. In the development of systems it is similar, when a complex system is not good start building without a design in which the main requirements are met is designed. Earlier it was not so obvious this, but now the systems are becoming more complex time and, therefore, have an architecture around which it carries out its construction is essential
AIC. What is lacking in Mexico to encourage the development focused on architecture
PVE: No doubt there are people very capable Mexico but still lack knowledge. So training in this topic is important. Ignoring architectural design concepts and thus design a complex system opportunistically without using them, can generate something called technical debt .
The technical debt concerns with lack of quality in the design or implementation of a system, due to the construction of this, more opportunistically, with no or little use of design concepts. It is constructed somewhat deficient, low quality, so if you have to repair or change anything in the system, you have to “pay” all that debt arranging many things that were done with little quality. Sometimes it is not possible to pay that debt because doing all repairs are more expensive to design and build part or a whole system again. The worst thing, I believe, can happen is to have inadvertent technical debt. This is not know that there is a better way to design and implement a system. Not to generalize, but there are often unaware that you can do better in the design and implementation of systems. Thus, training in this topic is important.
See text in pdf.
> This work authored Conacyt Information Agency is under license Attribution 4.0 Creative Commons International.
No comments:
Post a Comment