architecture:solution

Differences

This shows you the differences between two versions of the page.


Previous revision
architecture:solution [2023/03/30 15:38] (current) – [Solution Architecture vs. Software Architecture] Henrik Yllemo
Line 1: Line 1:
 +<button type="primary" size="xs" icon="glyphicon glyphicon-bookmark">[[architecture:architecture|Architecture]]</button>
 +====== Solution Architecture ======
 +Solution architecture is a practice of designing, describing, and managing the solution engineering in relation to specific business problems.
  
 +A [[roles:solution_architect|Solution Architect]] is the person in charge of leading the practice and introducing the overall technical vision for a particular solution.
 +
 +<callout type="primary" title="What is Solution Architecture?" icon="fa fa-quote-right">
 +
 +A solution architecture (SA) is an architectural description of a specific solution. SAs combine guidance from different enterprise architecture viewpoints (business, information and technical), as well as from the enterprise solution architecture (ESA)
 +\\
 + --- [[https://www.gartner.com/en/information-technology/glossary/solution-architecture|Gartner]]
 +\\
 +----
 +\\
 +A description of a discrete and focused business operation or activity and how IS/IT supports that operation. A Solution Architecture typically applies to a single project or project release, assisting in the translation of requirements into a solution vision, high-level business and/or IT system specifications, and a portfolio of implementation tasks.
 +\\
 + --- [[https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html#tag_03_69|TOGAF]]
 +\\
 +----
 +\\
 +Solution Architect/Engineering is responsible for defining and communicating a shared technical and architectural vision across multiple ARTs to help ensure the system or Solution under development is fit for its intended purpose.
 +\\
 + --- [[https://www.scaledagileframework.com/system-and-solution-architect-engineering/|SAFe]]
 +\\
 +</callout>
 + 
 +<accordion>
 +<panel type='' title='What is solution architecture?'>
 +Solution architecture is the process of designing and implementing technology solutions that meet the needs of a specific business or organization. It involves understanding the business requirements, identifying technical solutions, and designing a system architecture that meets those requirements.
 +</panel><panel type='' title='What does a solution architect do?'>
 +A solution architect is responsible for designing and implementing technology solutions that meet the business needs of an organization. They work closely with business stakeholders to understand their requirements, and then develop a solution architecture that meets those requirements. They also work with development teams to ensure that the solution is implemented correctly and meets the desired quality standards.
 +</panel><panel type='' title='What are the key components of solution architecture?'>
 +The key components of solution architecture include understanding business requirements, designing the solution architecture, selecting appropriate technologies and platforms, creating technical specifications, overseeing development and implementation, and ensuring that the solution meets quality and performance standards.
 +</panel><panel type='' title='How is solution architecture different from enterprise architecture?'>
 +Solution architecture focuses on designing technology solutions that meet the specific needs of a business or organization, while enterprise architecture is concerned with the overall technology strategy and alignment of an organization. Enterprise architecture takes a broader view of technology, considering how different systems and technologies work together to support the overall business goals.
 +</panel><panel type='' title='What are the benefits of good solution architecture?'>
 +Good solution architecture can lead to better performance, improved scalability, increased reliability, and lower costs. It can also help organizations to more effectively meet their business goals and respond to changing market conditions.
 +</panel></accordion>
 +
 +
 +
 +
 +{{wp>Solution_architecture}}
 +
 +<jumbotron>
 +<WRAP group>
 +<WRAP row>
 +{{youtube>zB9WuYE1REI?full}}
 +</WRAP>
 +<WRAP row>
 +<WRAP column right><fs 12px>Source: [[https://www.youtube.com|YouTube]]</fs></WRAP>
 +</WRAP>
 +</WRAP>
 +</jumbotron>
 +
 + 
 +===== Solution Architecture vs. Software Architecture  =====
 +
 +  * https://dzone.com/articles/solution-architecture-vs-software-architecture
 +
 +
 +
 +
 +
 +<panel type='primary' title='Solution vs Software (Architecture)' icon='fa fa-globe' >
 +Solution architecture is concerned with designing and implementing technology solutions that meet the needs of a specific business or organization. It involves understanding the business requirements, identifying technical solutions, and designing a system architecture that meets those requirements. Solution architecture takes into account not just the software components, but also the hardware, network, and other infrastructure components required to deliver the solution.
 +Software architecture, on the other hand, is focused specifically on the design and organization of software components within a larger system. It involves identifying the software components required to implement a solution, defining their interfaces and interactions, and ensuring that they work together effectively to meet the desired performance and quality standards.
 +\\
 +\\
 +While solution architecture encompasses software architecture as a component, it is broader in scope and includes considerations beyond just software. Solution architecture also takes into account the overall business goals and objectives, as well as the broader technical and infrastructure components required to deliver a complete solution.
 +In summary, solution architecture is focused on the overall design and implementation of a technology solution that meets specific business needs, while software architecture is focused specifically on the design and organization of software components within that solution.
 +</panel>
 +
 +=== IT Architecture ===
 +Compare to:
 +  * [[architecture:enterprise|Enterprise Architecture (EA)]]
 +  * [[Solution Architecture vs. Software Architecture]] 
 +
 +<callout title="Related articles:">
 +  * Non-functional requirements
 +  * [[enterprise|Enterprise Architecture]]
 +  * [[method:sad|Solution Architecture Document (SAD)]]
 +
 +
 +</callout> 
 +<callout title="External links:">
 +  * https://www.altexsoft.com/blog/engineering/solution-architect-role/
 +  * https://www.scaledagileframework.com/system-and-solution-architect-engineering/
 +</callout> 
 +
 +===== Architecture Articles =====
 +
 +<nspages -title -textPages="" -exclude:architecture   >
 +
 +{{tag> skill architecture solution}}