software architects creed

14
Software Architect’s Creed Presented by Chris Deweese Photography by Jeremy West

Upload: chris-deweese

Post on 11-Jun-2015

1.896 views

Category:

Technology


0 download

DESCRIPTION

Nine action statements you can take with you and apply to be a better software architect.

TRANSCRIPT

Page 1: Software Architects Creed

Software Architect’s Creed

Presented by Chris Deweese

Photography by Jeremy West

Page 2: Software Architects Creed
Page 3: Software Architects Creed

Accepting my responsibility as an architect I will strive daily to learn and perfect my trade.

Page 4: Software Architects Creed

Readily will I defend my organizations IT investments from complexity, our greatest enemy.

Page 5: Software Architects Creed

Changing requirements will not break my design for it will be flexible and able to change with the requirements.

Page 6: Software Architects Creed

Helping developers to understand the reasons for the architecture and seeking their input is of great importance to our success.

Page 7: Software Architects Creed

I will never use acronyms or suggest technologies that are not pertinent to the problem at hand.

SOA

TDD

MVC

SRP

WS-*

MSMQ

DDD

BDD

RESTATOM IoC

TOGAF

FEA MEF

Page 8: Software Architects Creed

Technologies evolve and I know that solid architectures should accommodate and enable these evolutions.

Page 9: Software Architects Creed

Every day I will strive to help our software achieve ideals that will make it flexible and easy to maintain.

Page 10: Software Architects Creed

Concern for the success of my organizations IT investments will drive me to make appropriate decisions.

Page 11: Software Architects Creed

Teaching others about my trade will be an overarching responsibility that I accept as part of my duties.

Page 12: Software Architects Creed

The Software Architect’s Creed Accepting my responsibility as an architect I will strive daily to learn

and perfect my trade. Readily will I defend my organizations IT investments from complexity,

our greatest enemy. Changing requirements will not break my design for it will be flexible

and able to change with the requirements. Helping developers to understand the reasons for the architecture and

seeking their input is of great importance to our success. I will never use acronyms or suggest technologies that are not

pertinent to the problem at hand. Technologies evolve and I know that solid architectures should

accommodate and enable these evolutions. Every day I will strive to help our software achieve ideals that will make

it flexible and easy to maintain. Concern for the success of my organizations IT investments will drive

me to make appropriate decisions. Teaching others about my trade will be an overarching responsibility

that I accept as part of my duties.

Page 13: Software Architects Creed

Questions / Discussion

Page 14: Software Architects Creed

Contact / Photo Credits

Chris Deweese http://christopherDeweese.com Twitter: @cdeweese

Photo Credits Jeremy West

http://www.flickr.com/photos/28119858@N07/