Putting Software Architecture in its Place classifying the - PDF document

Putting Software Architecture in its Place classifying the architectural species Eoin Woods, Barclays Global Investors www.barclaysglobal.com/careers www.eoinwoods.info V2.20080414 Introductions � S oftware architect at BGI • lead software architect for the Apex portfolio management system � S oftware engineering for ~18 years • S ystems & architecture focus for ~12 years � Background includes system software products, consultancy and applications • Tuxedo, S ybase, InterTrust, bespoke capital markets work � All information systems based work • “ real time” to me means “ fast as possible please” 2 B A R C L A Y S G L O B A L I N V E S T O R S 1

Content � The Context � Classifying the Architects � Defining Each S pecies � Inter-S pecies Relationships � Conclusions 3 B A R C L A Y S G L O B A L I N V E S T O R S Architecture Soup Enterprise Architect Oracle Architect IT Architect Applied Architect Functional Architect Microsoft Architect Database Architect S torage Architect Network Architect Methods Architect Business Architect Executive Architect Consultant Architect S ybase Architect S tream Architect S oftware Architect S ystems Architect Infrastructure Architect Java Architect .NET Architect Domain Architect Information Architect Data Architect S olutions Architect 4 B A R C L A Y S G L O B A L I N V E S T O R S 2

Where Did Architects Come From? � S low emergence of role • early sightings in 1970s • more common from 1990s onward • today, they’ re everywhere! � Wide confusion over definitions • architecture vs. design? • architecture vs. engineering? • technical or management j ob? 5 B A R C L A Y S G L O B A L I N V E S T O R S Essence of Architecture � S takeholder focus • serving a wide constituency • clarifying poorly defined problems • identification of risks and opportunities � Design centric activity • designing a system, an infrastructure, a process, …is core to the activity � Balancing of concerns • no right answer / least worst option � S ystem-wide concerns • e.g. qualities rather than detailed functions � Leadership 6 B A R C L A Y S G L O B A L I N V E S T O R S 3

Why Architects Anyway? � Organisational factors • retain and develop talent • manage risk in technology environment • exert control over environment, vendors, … • focus best engineering talent where needed � Personal factors • technical career path • organisational gravitas and status 7 B A R C L A Y S G L O B A L I N V E S T O R S Organisational Context � This talk is primarily about architects within an end-user organisation � Architects live within “ IT” or “ IS ” organisation • support area rather than business area • usually part of the COO empire • often seen as cost centre rather than profit centre • usually little understanding of technology within business areas � S enior IT managers may or may not be ex-IT staffers • often seen as a “ rotation” opportunity for fast track executives � This context requires communication skills, political sensitivity & tact! 8 B A R C L A Y S G L O B A L I N V E S T O R S 4

Content � The Context � Classifying the Architects � Defining Each S pecies � Inter-S pecies Relationships � Conclusions 9 B A R C L A Y S G L O B A L I N V E S T O R S Common Taxonomies � Microsoft � Open Group • Infrastructure • IT Architect • S olutions � Martin Fowler • Technology (recent addition) • Architectus Reloadus � IBM • Architectus Oryzus • Enterprise � And many, many more … • Application • see the Internet! • Information • Infrastructure • Integration • Operations 10 B A R C L A Y S G L O B A L I N V E S T O R S 5

A Simple Activity-Based Classification System Focus Multi Enterprise Infrastructure Architecture Architecture System Architecture System Single Focus Problem/Domain Focus Solution/Technology Focus 11 B A R C L A Y S G L O B A L I N V E S T O R S A Simplification � Fundamentally three groups • enterprise, systems & infrastructure architects � Classified by • focus on the domain vs. the technology • the number of systems considered � S ystems under consideration also implies • Time horizon (many systems => longer timescales) • Abstraction level (more systems => higher abstraction level) • Relationships (many systems => senior management stakeholders) 12 B A R C L A Y S G L O B A L I N V E S T O R S 6

What Architects Aren’t � Managers • CIO • CTO • Development manager � Technology consultants • Oracle technologist • Java technical lead • BEA product specialist • … 13 B A R C L A Y S G L O B A L I N V E S T O R S Synonyms � Enterprise Architecture • enterprise architect, functional architect, business architect, strategic architect, domain architect, stream architect, … � S ystem Architecture • software architect, solutions architect, application architect, systems architect, technical architect, … � Infrastructure Architecture • infrastructure architect, technical architect, technology architect, database architect, middleware architect, network architect, storage architect, … 14 B A R C L A Y S G L O B A L I N V E S T O R S 7

Organisational Context CIO / COO Enterprise Architect CTO / Infrastructure Architect Infrastructure Head Department Head / Functional Head/ S ystem Architect Process Owner 15 B A R C L A Y S G L O B A L I N V E S T O R S Content � The Context � Classifying the Architects � Defining Each S pecies � Inter-S pecies Relationships � Conclusions 16 B A R C L A Y S G L O B A L I N V E S T O R S 8

Enterprise Architects � Domain rather than technical focus • business alignment is a maj or interest � Cross system focus • responsibilities, integration & interfaces • little interest in internal workings • oversight rather than design (“ governance” ) � Long term (strategic) view � Usually ex-system or infrastructure architects or ex-business analysts 17 B A R C L A Y S G L O B A L I N V E S T O R S Enterprise Architect Activities � Functional (business domain) modelling & system specification � Corporate data modelling � EA framework modelling and management • current and future state modelling • Inventories (“ portfolio management” ) � Technology S trategy � Integration architecture and design � Organisational technical standards � Assessment / oversight / governance 18 B A R C L A Y S G L O B A L I N V E S T O R S 9

Enterprise Architect Example Methods and Tools � Modelling � Information Architecture • UML, Archimate (possibly), B&L • Metadata repositories (e.g. AS G Rochade) • Architecture viewpoints (possibly) � Inventories • BizzDesign Architect, CaseWise, RS M • EA inventory products • PowerPoint, Visio and Excel (e.g. Metaverse) � S � Assessment ystem S pecification • QAW style analysis (possibly) • ATAM (possibly) • CBAM style analysis (possibly) � EA Framework usage • Frameworks (TOGAF, Zachman) • EA toolsets (e.g. Troux Architect) 19 B A R C L A Y S G L O B A L I N V E S T O R S System Architects � Balance of domain and technical interest • both are crucial to building good systems � S ingle system focus • function and internal design of “ their” system • system wide concerns • interested in other systems primarily as “ black boxes” (dependencies) � S hort to medium term view • know where they think they’ re going • but expecting lots of change along the way � Almost always grown from developers 20 B A R C L A Y S G L O B A L I N V E S T O R S 10

System Architect Activities � Architectural design and modelling � Technical standards � Prototyping � S oftware and database design � Reviewing (design, implementation, testing, … ) � Assessment (own and other systems) 21 B A R C L A Y S G L O B A L I N V E S T O R S System Architect Example Methods and Tools � Architecture & Design � Development • Domain driven design • IDEs, usual development tools • S tyles and patterns � Assessment • ADD (possibly) • ATAM (possibly) • Viewpoints and Perspectives & � Reviewing V&B Viewtypes (possibly) • QAW style analysis (possibly) • Inspections, reviews, … � Modelling • UML, ERD, B&L • Viewpoints, V&B Viewtypes • MagicDraw, Together, RS M 22 B A R C L A Y S G L O B A L I N V E S T O R S 11

Infrastructure Architects � Technical rather than domain focus • broad understanding of business area priorities • deep expertise in technology domain � Cross system focus • providing services to many applications • relationships often via S LAs � Long term (strategic) view • simplicity, standardisation, stability, cost management • roadmaps and vendor management 23 B A R C L A Y S G L O B A L I N V E S T O R S Infrastructure Architect Activities � Infrastructure Environment Design � Technology S trategy � Technical S tandards � Reviews of Proj ects � Consultancy to Proj ects � Vendor Liaison and Management � Proj ect Management 24 B A R C L A Y S G L O B A L I N V E S T O R S 12