Last week I wrote an Advisor for our Business & Enterprise Architecture practice about the role of the solution architect. I thought I’d share my overview of how that role compares to the enterprise architect’s. Is this how the roles are delineated in your company?
|Topic||Solution Architecture||Enterprise Architecture|
|Scope||Single solution or set of related solutions||All current and future solutions and COTS|
|Primary Goals||Ensure that the solution fits within the enterprise context||Define the enterprise context including business, information, application, and technology|
|Responsibility||Translates nonfunctional and functional requirements into design, within enterprise context||Translates strategies into target architectures and roadmaps|
|Tradeoffs||Enterprisestrategy and goals vs. solution tactical and delivery requirements||Prioritization and rationalization of conflicting business, information, and technology requirements|
|Primary Artifacts||Solutions architectures and designs||Enterprisereference architectures, patterns and standards|
|Primary Stakeholders||Solutions owners, EA, development team, technology||Executive leadership, business leaders, CIO, solutions|
|Characteristics||Credibility with solutions teams and owners||Broad knowledge and experience, vision|
|Skills||Conceptualization, patterns, modeling, design, communications||Contextualization, conceptualization, abstraction, modeling, communications|
|Reporting Structure||Assigned to and functions as part of solution team; may report to solution owner or line of business, development, or EA||Reports to EA team, typically part of CIO organization|
I’m happy to send you a copy of the Advisor with some of my rationale. Just leave a comment or send me a message (mrosen at cutter dot com).