DSI233 Presentation

Solution and Enterprise Architecture

Group 2
Enterprise Architecture

 Enterprise Architecture (EA), as the name implies, considers the entire

enterprise. It can involve identifying the company's capabilities, workforce,
and prospective outcomes in addition to shaping the organisation.
 The process frequently begins with data collection and mapping out the
relationships between all the many entities of an organisation .
 An organisation can be equipped to handle change and sustain its core
applications with the aid of enterprise architecture. Application, business,
data, and infrastructure architectures are all used in conjunction with
enterprise architecture. The firm, business, departments, technology,
security, digital, and innovation are all covered by enterprise architecture.
Solution Architecture

 A solution architecture (SA) is an architectural description of a specific

solution. The solutions for particular business demands are the main emphasis
of solution architecture. Finding answers to emerging issues and resolving
current business obstacles are both covered by solution architecture.
 It outlines the structure of a solution and how to implement it. Projects,
capacities, features, etc. are all things that solution architecture is
concerned with. The same aspects are important to solution architects.
 Solution architecture is a practice to provide ground for software
development projects by tailoring IT solutions to specific business needs and
defining their functional requirements and stages of implementation.
 It is an architectural description of a specific solution.
 At its core, solution architecture is a structural design addressing a set of
functional and non-functional requirements.
Solution VS Enterprise Architecture

Solution architect Enterprise architect

Need to have a wide breadth of Need to have some technical

technical knowledge knowledge but may not be domain
experts
Focus is on business strategy and Focuses on bridging the gap between
requirements is less involved with business requirements and
technical details of the technological technological solutions that are to be
solutions created. designed based on them
Act as strategists who look at user Act as a link between business strategy
needs, business requirements and help and technology solutions to ensure
inform what kind of technical solutions business requirements are considered
needs to be developed for the business and communicated well when deciding
success. the solution design and implementation
Why do we need solution architecture?
 Solution architecture translates technical business needs into practical IT solutions while
establishing rules and instructions for proper implementation and delivery.
 It also considers all external factors that could have an impact on the development process. This
way, digital projects are less likely to fail and there is a consensus between EA teams and
development teams.
 SA can be seen as a support system that provides structure and reduces the scope of complexity
when developing and rolling out new systems and applications.
 Solution architecture is among the key methods that enable an enterprise architecture in delivering
value to its organisation. The activity of designing a solution architecture occurs during solution
ideation, solution design, and solution implementation.
 During solution ideation, solution architecture establishes the coherent business context for the
solution while defining the vision and requirements for the solution.
 During solution design, SA elaborates on potential options or prototype development. In this
process, SA selects the most optimal option and develops the roadmap for the selected solution.
 During solution implementation, SA communicates the architecture to the stakeholders while
guiding the implementation team.
Some illustrative examples of types of solution
architectures

Example1: Business Architecture

Business architecture is a solution architecture that maps a
solution to business objectives. It concerns itself with developing
an enterprise blueprint that can provide a common understanding
of an enterprise. It is used to align strategic objectives with
tactical demands.

Business architecture bridges the enterprise business model and
enterprise strategy with the business functionality of the
enterprise. It enables the value stream of Strategy to Execution.

Here a business capability map outlines the capabilities of a
solution
Some illustrative examples of types of solution architectures


Example1: Business Architecture

Business architecture is a solution architecture that maps a
solution to business objectives. It concerns itself with developing
an enterprise blueprint that can provide a common understanding
of an enterprise. It is used to align strategic objectives with
tactical demands.

Business architecture bridges the enterprise business model and
enterprise strategy with the business functionality of the
enterprise. It enables the value stream of Strategy to Execution.

Here a business capability map outlines the capabilities of a
solution
 Business Architecture Example


The business capabilities above would typically be referenced in requirements to provide
tracebility to things such as release, budget and technical component This allows for
dashboards to be created that demonstrate the business outcomes of technology
improvemnts.
Example 2: Information Architecture

Information Architecture is a solution architecture that represents the structrue of how
information flows from the perspective of the user. IA is the structural design of shared
information environments. It is an emerging practice which focuses on bringing principles of
design, architecture, and information science to the digital landscape.

The example below is a three layer structure for an ecommerce site.
Example 3: System Architecture

A system architecture is solution architecture that defines the structure, behaviour, and other
parameters of a system. It is a formal description and representation of a system. SAs may be a
representation of a system including a functionality map of hardware onto software components.
It is, for some, the description of the design and contents of a computer system.

The following example of System Architecture uses microservices to implement various
automations for an ecommerce firm.
Example 4: Application Architecture

An application architecture describes the behaviour of
applications used in a business.

It primarily focuses on how the applications interact with
each other and the users.

It highlights the data consumed and produced by the
applications and not their internal structures.

The application architecture is specified on the basis of
functional and business requirements.

This is inclusive of defining the interactions among
databases, application packages, and middleware systems
w.r.t. functional coverage.

The purpose of application architecture is to ensure that
the applications being used by an enterprise are
available, reliable, scalable, and manageable.

In the diagram is an example of a layered application
architecture:
Example 5: Technolgy Architecture

Technology architecture details the structural design of IT infrastructure to support
the solution.

The technology architecture below illustrates the technology infranstructure of a
lightweight ecommerce service that uses a cloud content delivery network (CDN),
cloud computing instances and a variety of platfoms and APIs for data processing.
Solution and Enterprise Architecture

 Enterprise architecture is regarded as one of the key ways of

achieving competitive advantage through information
technology. There is a growing demand to reduce costs, increase
flexibility, and regulate technology environments.
 Enterprise architecture guides an organization’s business,
information, process, and technology decisions to enable it to
execute its business strategy and meet customer needs.
 Enterprise architecture can be conceptually divided into
different architectural layers that involve Business Architecture
and IT Architecture (Data, Application and Technology
Architecture).

The Four Architecture Domains
 There are typically four architecture domains and they are often
interconnected:



Business Architecture describes how the enterprise is organizationally structured and what
functional capabilities are necessary to deliver the business vision. Business architecture addresses
the questions WHAT and WHO:

• WHAT is the organization’s business vision, strategy, and objectives that guide the creation of
business services or capabilities?

• WHO is executing defined business services or capabilities?


Application architecture describes the individual applications, their interactions, and their
relationships to the core business processes of the organization. Application architecture addresses
the question HOW:

• HOW are previously defined as business services or capabilities implemented?



Data architecture describes the structure of an organization’s logical and physical data assets and
data management resources. Knowledge about your customers from data analytics lets you improve
and continuously evolving business processes.


Technology architecture describes the software and hardware needed to implement the business,
data, and application services.
Three levels of architecture and design

1.Enterprise Architecture

This takes a cross-organizational and strategic view of business activity systems. It works
to integrate business system planning with business planning


2.Solution Architecture

The term solution architecture is used at a narrower and more tactical level; often in
relation to one particular system, or a process that requires system integration.


3. Detailed design

Solution architecture leads to more detailed design work and to software development
projects. A solution architect may shape and steer a project (be it agile or not), keep it on
the rails and in step with more strategic cross-organizational thinking.

A software architect may elaborate a given solution architecture, complete the
component structure and APIs of an application, and address the detailed design of
messaging between applications or components.
The scope to be covered

Given the 4 architecture domains and 3 levels, every enterprise has to work out for itself
how its roles cover the 12 cells of the table below.

The weight given to each of the domains and levels differs between initiatives, and
influences which architects are assigned to it.
Enterprise Architecture (EA), Solution Architecture(SA) and Technical
Architecture(TA)

Setting up a technology stack requires a combination of three pillars:
1.Holistic strategies both in technical choices and direction of business (EA)
2.Well-thought-out roadmaps working towards the above identified direction (SA)
3.And the technical know-how for its implementation (TA)

Enterprise Architecture is about the overall look and focus of your technology
stack according to business strategy and IT landscape.

Enterprise and Solution Architecture are complementary, where solution
architecture is a subset of enterprise architecture. The difference is business
architecture which connects data application and technology architectures with
business strategy and goals.


A typical question for the Enterprise Architecture:

Question: How can we realize our business strategy, making sure that our future
operating model fits the future state at all levels? How can we create a
transformation roadmap to get there from our current operating model?
 
Solution Architecture is about identifying and describing which IT solutions address which
business needs.

It takes a problem, and proposes building blocks to solve it. It often reuses other elements
made available by the Enterprise Architecture (Enterprise Building Blocks, Enterprise
Capabilities, Architectural standards and guideline)

It comprises of many subprocesses that draw guidance from various enterprise architecture
viewpoints.(business, information and technical), as well as from the enterprise solution
architecture (ESA).

A typical question mainly for the Solution Architecture:

Question: In the next year we expect our eCommerce user base to grow 5 fold. We don’t
have integration of it with existing back-end systems: eCommerce doesn’t update the stock
inventory realtime causing delays in shipments and inconsistency with ERPs. How do we
solve this with our existing systems in mind, causing little to no disruption to existing
operations?

Technical Architecture deals with defining and implementing a specific software solution
or IT project. All three are equally important.
Solution,Technical and Enterprise Architect
 Solution architects technical architects and enterprise architects work together to
ensure the flexibility, scalability, and security of the entire system that functions
according to a company’s business and technical requirements.
 As architects, they are all responsible for business strategy as well as solution
implementation, but in their unique ways.

 An enterprise architect is more focused on business strategy and requirements.

 A technical architect focuses more on designing and implementing technical
solutions.
 A solution architect serves as the link between business needs and technological
solutions: serves as the bridge without which almost 50% of all IT projects fail.
Which is the most Important Architecture between EA, SA and TA

All three architectures play a major part in the success of a company’s
digital journey. They are not independent fractions, they are interconnected
and play off each other.

Therefore you should design them as such. With all three in mind from the
start.

The three cannot be seperated. We have to start with all three architectures
in mind.

IT Teams have to be able to collaborate and be aware of all the links in the
chain. This is where IT Governance is crucial. ITG ensures that your teams
engage with each other’s focus and are able to collaborate based on a
system of checks and balances.

Solution architecture without business architecture creates silos by focusing
only on business requirements which means that enterprise architecture is
essential to organizations seeking to create scale across the enterprise.

Strategy and technical know-how both play a key part in each pillar.
Which is the most Important Architecture between EA, SA and TA
cont

For example, if you would only be focused on strategy on an enterprise
level with low technical know-how, then that could prove to be an
expensive mistake when you figure out that your technical architects run
into problems implementing applications that don’t fit in the overall
framework.

Then your teams are likely forced to take shortcuts, accruing technical
debt. From an EA point of view you’ll be forced to go back to the drawing
board, which is a costly manner and could involve changing operating
systems or entire integration solutions.

These scenarios – of technical issues influencing strategy – happen more
often than not.

References


https://www.visual-paradigm.com/guide/enterprise-architecture/
enterprise-architects-vs-solution-architects-vs-domain-architects/

https://medium.com/@genesishack/understanding-solution-architecture-
for-genesis-hack-77c2922b24d4

https://www.leanix.net/en/wiki/ea/solution-architecture#form

https://www.gartner.com/en/information-technology/glossary/solution-
architecture

http://grahamberrisford.com/00EAframeworks/01Fundamentals/
Enterprise%20architecture%20versus%20solution%20architecture.htm

https://www.yenlo.com/blogs/enterprise-vs-solution-architecture/
End of presentation

Thank you for your attention