https://www.golodiuk.com/service/about-architecture-and-design Introduction to Architecture and Design in IT and about "architect" role in the IT solution development..

1. golodiuk.com

2. ARCHITECTURE AND DESIGN
for Information Te chnology
Everything should be made
as simple as possible, but not simpler
Communicate complex things
by simple words

3. PreviousNext
3
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
I need a new IT product
t o a u t o m a t e … o f m y b u s i n e s s
▪ C a n m y p r o j e c t b e i m p l e m e n t e d
t h e r i g h t w a y ?
▪ W h e n ?
▪ W h a t w i l l b e t h e c h a r g e s f o r i t s
i m p l e m e n t a t i o n ?

4. PreviousNext
4
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
The
architect
will help
me
Requirements
Take a word with the
customer, figure out what
product is needed, for what
purpose
Proof of Concept
Build up a solution concept,
submit it to the customer,
make cost estimation
Architecture
Get feedback, process details,
call in subject matter experts
Design
Come up with a solution
design

5. PreviousNext
5
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Design
Thinking
Desirable
ITSolution
Designthe
rightSolution
Understand
theProblem
A customer centric development
process and the application of
specific tools.
Clear understanding of target market
and problems it’s facing.
© Scaled Agile, Inc.
01
02
03

6. PreviousNext
6
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Requirements
identification
Making IT architecture Design IT solution Document architecture
and design
Architectural analysis
Key highlights of architect's activities
b b b b1 2 4 5b3

7. PreviousNext
7
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
SYSTEM ARCHITECT SOFTWARE ARCHITECT SOLUTIONS ARCHITECT ENTERPRISE ARCHITECT
All of them are architects, but whereas they operate by different contexts
People mean different things
when they call themselves an
“architect"

8. PreviousNext
8
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
“a r c h I t e c t s”
SYSTEM ARCHITECT SOFTWARE ARCHITECT SOLUTIONS ARCHITECT ENTERPRISE ARCHITECT

9. PreviousNext
9
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
architect spends the
bulk of their time
thinking about “how” to
solve problems
engineer spends most
of the time
implementing solutions
The difference
between an
engineer and an
architect is their
focus

10. PreviousNext
10
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
golodiuk.com
10 Characteristics of a Good Architect
1. Solve
Problems
2. Focus on
“How”
3. Think
Holistically
4. Use
Technology
Creatively
5. Make
Decisions
6. Confidence
(don't confuse
with arrogance)
7. Make Things
Understandable
8. Make
Complex
Subjects Sound
Simple
9. Not Afraid to
Take Risks
10. Not Afraid to
Be “Wrong”

11. PreviousNext
11
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
▪ Determine an excellent solution to a
problem
▪ It's not to supply information
▪ It’s not to coordinate other people
▪ It’s not to do research
▪ It's to describe the solution
▪ The output – is a roadmap to solve a
problem
Solve Problems
10 Characteristics of a Good Architect

12. PreviousNext
12
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
To give a space to craft and choose
among the plenty of “good” solutions
and reject the “bad” ones
Focus on “How”
10 Characteristics of a Good Architect

13. PreviousNext
13
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
▪ An architect needs to understand the
context of the problem
▪ Assess and communicate impacts on
business
Think Holistically
10 Characteristics of a Good Architect

14. PreviousNext
14
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Not every good architecture is novel, but
the need for creativity often involves the
ability to see the current business with
fresh eyes
Use Technology
Creatively
10 Characteristics of a Good Architect

15. PreviousNext
15
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
▪ Decide which solution is the best fit for a
specific business or technical problem
▪ Acting in an architectural role, not in a
purely management / political role
▪ Considering the cost, feasibility, and
team preferences
Make Decisions
10 Characteristics of a Good Architect

16. PreviousNext
16
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
▪ Don't confuse with arrogance
▪ All good architects tend to be very sure
about their work
▪ Can explain and convince
Confidence
10 Characteristics of a Good Architect

17. PreviousNext
17
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
▪ Clearly describe a system to everybody
▪ Adjust explanation to an audience
Make Things
Understandable
10 Characteristics of a Good Architect

18. PreviousNext
18
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Don't throw obscure TLA's (“Three-Letter
Acronyms”) to show off
Make Complex
Subjects Sound
Simple
10 Characteristics of a Good Architect

19. PreviousNext
19
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Architecture is a craft. To make a
masterpiece an author (read architect)
should run risks
Not Afraid to Take
Risks
10 Characteristics of a Good Architect

20. PreviousNext
20
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Do. Apologize after. © Dmytro Golodiuk
Not Afraid to Be
“Wrong”
10 Characteristics of a Good Architect

21. PreviousNext
21
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
What
Architect
Do
Take your
business
requirements,
and determine
how to embody
those in
software
Communicate
with customer
Identify and
design
architectural
components Analyze and
select the right
architecture
patterns
Diagram and
document an
architectural
solution
Communicate
architecture
decisions to
developers and
stakeholders
Investigate new
technologies
and make
prototypes
Control on
helicopter view
(common
context)
Worry about
cohesion
Worry about
maintainability

22. PreviousNext
22
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
golodiuk.com
Researcher Evaluator
or Analyst
Technical
Expert
Knowledge
Orchestrator
01 02 03 04
Roles
Mislabeled as
“Architect”

23. PreviousNext
23
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Researcher
While architects spend time
doing research, the fundamental
difference between a researcher
and an architect is that the
architect decides.
Evaluator or Analyst
Technical Expert
Roles Mislabeled as “Architect”
Knowledge Orchestrator

24. PreviousNext
24
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Researcher
While architects spend time
doing research, the fundamental
difference between a researcher
and an architect is that the
architect decides.
Evaluator or Analyst
A key differentiator between an
evaluator/analyst and an
architect is that the architect
ultimately makes a choice or
single recommendation as a
result of these evaluations.
Technical Expert
Roles Mislabeled as “Architect”
Knowledge Orchestrator

25. PreviousNext
25
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Researcher
While architects spend time
doing research, the fundamental
difference between a researcher
and an architect is that the
architect decides.
Evaluator or Analyst
A key differentiator between an
evaluator/analyst and an
architect is that the architect
ultimately makes a choice or
single recommendation as a
result of these evaluations.
Technical Expert
However, there are many cases
where technical experts are not
architects, even if they have that
title.
Roles Mislabeled as “Architect”
Knowledge Orchestrator

26. PreviousNext
26
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
Researcher
While architects spend time
doing research, the fundamental
difference between a researcher
and an architect is that the
architect decides.
Evaluator or Analyst
A key differentiator between an
evaluator/analyst and an
architect is that the architect
ultimately makes a choice or
single recommendation as a
result of these evaluations.
Technical Expert
However, there are many cases
where technical experts are not
architects, even if they have that
title.
Roles Mislabeled as “Architect”
Knowledge Orchestrator
An architect is a person who
originates from a proposed
solution; the knowledge
orchestrator role serves as an
editor and critic of the
recommended ideas. In terms of
architecture, the knowledge
orchestrator is “involved,” while
the architects are “committed.”

27. Next
G O O D S O F T W A R E A R C H I T E C T U R E a l l o w s y o u r c o m p a n y t o :
Rapidly
pivot
and evolve
Minimize
maintenance
and operations
cost
Scale
robustly
and smoothly
to millions
of users
Deliver value
to your end-users,
and to bring
revenue to
your business
Previous
27

28. PreviousNext
28
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
I believe in the
success of your
business or “digital
transformation”
company provided
software is designed
and developed
correctly.
Dmytro Golodiuk
Why IT solution’s architecture is important

29. PreviousNext
29
golodiuk.com
ARCHITECTUREANDDESIGNforInformationTechnology
The way the IT
solutions help your
business to prosper is
grounded in a useful
software product
architecture.
Dmytro Golodiuk
Why IT solution’s architecture is important

30. golodiuk.com
Dmytro Golodiuk

31. Music By:
Landras Dream by Audionautix is licensed under a
Creative Commons Attribution license
(https://creativecommons.org/licenses/by/4.0/)
Artist: http://audionautix.com/