People from IT industry often ask me what is the difference between roles and responsibilities of Architect and Project Manager. While the overlap in responsibilities is unavoidable and both are equally accountable for the overall success of the project. While an Architects should focus on quality of the solution, PMs should concentrate on quality of the program.
The Architect’s Job is to: (a) maximize the value and quality of the solutions we deliver and (b) to maximize the potential of your technical team Understanding the current landscape is the key - Understand client stake holders and decision makers and understand existing environment, sub-systems and dependencies.
1 Comment
b) O (Open/closed principle)- software entities … should be open for extension, but closed for modification. c) L (Liskov substitution principle) - objects in a program should be replaceable with instances of their sub-types without altering the correctness of that program. d) I (Interface segregation principle) - many client-specific interfaces are better than one general-purpose interface. e) D (Dependency inversion principle) - one should Depend upon Abstractions. Do not depend upon concretions.
|
AuthorAshish Abrol is a Technical Evangelist at heart. As a Web Architecture Consultant he specializes in IT Management Consulting and Enterprise Architecture with a speciality in High Performance SOA and Open Source Frameworks. I sure did take a long time to enter actively into blogosphere. Honestly, as a passive player all this time, I have gained a lot from the adept content of some serious bloggers. That strongly encouraged me to contribute back to the community, and learn in the process as well.
-Ashish Archives
July 2020
Categories |