This presentation briefly discusses the manifestation of bad architecture and design. It then suggests what should one care about the architecture and the overall role of a software architect while developing products. It also mentions the role of an architect in agile product development.

1. © Quovantis Technologies Pvt. Ltd.
Who is an Architect
&
Why care about Architecture?
By
Tarun Kohli

2. © Quovantis Technologies Pvt. Ltd.
Manifestation of fly by the seat of one’s pants
 No Scaffolding
Incoherent system design
 Inconsistent development practices
 High Probability of Spaghetti code
 High Probability of Project Failure
 High Probability of Non-compliance of non-functional requirements
 Everyone is a technical Leader

3. © Quovantis Technologies Pvt. Ltd.
Your worst nightmare?

4. © Quovantis Technologies Pvt. Ltd.
An attempt to define architecture
Blueprint
Seeing the forest for the trees i.e. the big picture
Components and their inter dependencies
Governance(only used in big Enterprises)
Building Blocks
Abstract/Conceptual View of the System
Framework
The things you do initially in the project so that changes aren’t that
expensive

5. © Quovantis Technologies Pvt. Ltd.
ar·chi·tec·ture
noun
The software architecture of a program or computing system is the structure or structures
of the system, which comprise software elements, the externally visible properties of those
elements, and the relationships among them
verb
The process of creating a conceptual model of realizing a business vision by understanding
both functional and non-functional requirements. The act of decomposing those
requirements into technical components and how they interact together to deliver desired
functionality

6. © Quovantis Technologies Pvt. Ltd.
Your dream?

7. © Quovantis Technologies Pvt. Ltd.
Role of an Architect
Understand the business vision
Understand functional/non-functional requirements
 Do Build vs. Buy
 Select the technology stack
 Do the estimates
 Create conceptual architecture and design components
Work with engineering team to realize the technical vision
Make sure the product evolves per the specification i.e. Death By Testing
 Select the right platform to deploy the product

8. © Quovantis Technologies Pvt. Ltd.
In a nutshell
Your Exhausted Architect
QA Lead
Product
Manager
Technical
Lead

9. © Quovantis Technologies Pvt. Ltd.
ar·chi·tect
noun
1.a person qualified to design buildings and to superintend their erection
2.a person similarly qualified in another form of construction: a naval architect
3.any planner or creator: the architect of the expedition
verb
to plan or create

10. © Quovantis Technologies Pvt. Ltd.
Principles of an Agile Architect*
1. Value People
2. Communicate
3. Less is More
4. Embrace Change
5. Choose the right solution
6. Deliver Quality
7. Model and Document in an Agile Fashion expedition
* - http://www.agilearchitect.org/agile/principles.htm

11. © Quovantis Technologies Pvt. Ltd.
Characteristics of an Architect
1. Knows how to communicate effectively with various stakeholders
2. Can see the forest for the trees
3. Can design systems which can embrace change
4. Doesn’t believe in “Not invented Here” syndrome
5. Is Flexible and can easily make trade-offs
6. Is Focused highly on Quality

12. © Quovantis Technologies Pvt. Ltd.
The architect doesn't talk, he acts.
When this is done,
the team says, "Amazing:
we did it, all by ourselves!"
The architect concerns himself
with the depth and not the surface,
with the fruit and not the flower.
Tao of Architecture

13. © Quovantis Technologies Pvt. Ltd.
Thank you!
Presentation By –
Tarun Kohli