I thought I’d share this post with Iasa members.
About the Author: Scott Whitmire
Scott Whitmire is a senior enterprise architect with over 35 years of system architecture and development experience, including lead architect on a number of major applications. His interest in software engineering and architecture began 30 years ago as he recognized the weaknesses of the systems on which he worked, as well as those he had built. He has built or designed applications for several industries, including aerospace, manufacturing, professional practice management, financial services, wholesale, retail, and telecommunications.
Mr. Whitmire chairs the Iasa Board of Education, with overall responsibility for the education, training, certification and accreditation programs for Iasa. He is one of the original members of the Curriculum Committee, is one of the initial authors of Iasa’s definitions of software and infrastructure architecture, and led the committee’s efforts to define business architecture as an architecture specialty.
Mr. Whitmire is a Senior Member of the IEEE, an Iasa Fellow, and holds the CITA-P certification. He has mentored many architects and engineers, and has served on many CITA-P boards. He has published one book (so far), "Object Oriented Design Measurement," as well as numerous papers, articles, and presentations.
Related Posts
One Comment
Comments are closed.
I agree with you that the profession has focused more on the software design patterns that address solutions alone. Interestingly, an architect having the toolbox of software design patterns and acceptable best practices, and not knowing which problems to apply them to, ultimately defeats the effort of that architect. Architects are valuable for their ability to identify and match a problem pattern to a corresponding solution pattern, leading to the design of a blueprint for crafting the right solution to the problem.