Architecture of Business Systems Architecture and the Role of the Architect

Size: px

Start display at page:

Download "Architecture of Business Systems Architecture and the Role of the Architect"

Pamela Mathews
5 years ago
Views:

1 Sandro Schwedler Wolfram Richter Architecture of Business Systems Architecture and the Role of the Architect Lecture Outline Introduction (W) Lecture Overview Architecture & role of the Architect Views and Viewpoints Process of Software Architecting, Requirements (W) Building Block: Databases (S) Building Block: Content Management Systems (S) Building Block: Security Components (S) Architecture Design (W) Building Block: UI Server (S) SOA (W) Building Blocks: Introduction, Application Server (S) Building Block: Integration Technologies (W) Sandro Schwedler, Wolfram Richter 1

2 Goals of this presentation After this lecture, you... Understand the concept of IT architecture and how it differs from design Understand the role of the IT architect and the skill set required to fulfil it Can differentiate the role of an (IT) architect from other typical project roles Sandro Schwedler, Wolfram Richter What is Architecture? Architecture (Latin architectura, from the Greek ἀρχιτέκτων arkhitekton, from ἀρχι- "chief" and τέκτων "builder, carpenter, mason") is both the process and product of planning, designing and construction. [ ] "Architecture" can mean: A general term to describe buildings and other physical structures. The art and science of designing and erecting buildings and other physical structures. The style and method of design and construction of buildings and other physical structures. The practice of the architect, where architecture means the offering or rendering of professional services in connection with the design and construction of buildings, or built environments.[1] The design activity of the architect, from the macro-level (urban design, landscape architecture) to the micro-level (construction details and furniture). The term "architecture" has been adopted to describe the activity of designing any kind of system, and is commonly used in describing information technology Sandro Schwedler, Wolfram Richter 2

3 What is IT Architecture? Definitions according to ISO/IEC (IEEE 1477) (1/2) architect: The person, team, or organization responsible for designing systems architecture. architectural description (AD): A collection of products to document an architecture. architecture: The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution. designing: The activities of defining, documenting, maintaining, improving, and certifying proper implementation of an architecture Sandro Schwedler, Wolfram Richter What is IT Architecture? Definitions according to ISO/IEC (IEEE 1477) (2/2) system: A collection of components organized to accomplish a specific function or set of functions. The term system encompasses individual applications, systems in the traditional sense, subsystems, systems of systems, product lines, product families, whole enterprises, and other aggregations of interest. system stakeholder: An individual, team, or organization (or classes thereof) with interests in, or concerns relative to, a system. view: A representation of a whole system from the perspective of a related set of concerns. viewpoint: A specification of the conventions for constructing and using a view. A pattern or template from which to develop individual views by establishing the purposes and audience for a view and the techniques for its creation and analysis Sandro Schwedler, Wolfram Richter 3

4 What is IT Architecture? Definitions according to TOGAF / The Open Group TOGAF embraces but does not strictly adhere to ISO/IEC 42010:2007 terminology. In TOGAF, "architecture" has two meanings depending upon the context: A formal description of a system, or a detailed plan of the system at component level to guide its implementation The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time Sandro Schwedler, Wolfram Richter Architecture vs. Design All architecture is design, but not all design is architecture. Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change. -- Grady Booch, IBM Fellow Sandro Schwedler, Wolfram Richter 4

5 Why IT Architecture? Methodology to tackle unknown challenges Reduce project risk / higher probability of project success Improve quality of deliverables: enables sound decisions Time-to-market: do not have to reinvent the wheel with regards to documentation, project participants Long-term viability: allows others to understand what has been built Allow projects to scale: technique to distribute tasks over many shoulders Can do complex projects with less (expensive) resources Sandro Schwedler, Wolfram Richter The role of the IT architect 1. Architects understand end-to-end development Roles in typical client projects, mapped to RUP/OpenUP Disciplines Consultant: Identifies new business and technology environment opportunities. Aligns processes to technology using knowledge assets and experts. Teams with clients to provide lasting value IT Architect: Defines solutions to client business problems through the reasoned application of information technology IT Specialist: Supports solution construction working in a team with IT Architects Focuses on the detail of getting things done. Validates the solution in the context of the solution sale Project Manager: Initiates, plans, executes, controls, and closes projects. Ensures that projects are completed on time, within budget, and with high customer satisfaction Sandro Schwedler, Wolfram Richter 5

2012 Sandro Schwedler, Wolfram Richter The role of the IT

6 The role of the IT architect 2. Architects understand their Role Sandro Schwedler, Wolfram Richter The role of the IT architect 3. Architects Manage Risk and Manage Change Sandro Schwedler, Wolfram Richter 6

Architecture Stability %Resources derived from

7 Architecture Stability %Resources derived from information in Software Project Management A Unified Framework [Royce] Sandro Schwedler, Wolfram Richter The role of the IT architect 4. Architects Communicate with Stakeholders Sandro Schwedler, Wolfram Richter 7

8 The role of the IT architect 5. Architects Reuse Assets Sandro Schwedler, Wolfram Richter The role of the IT architect 6. Architects Right-Size their Involvement Sandro Schwedler, Wolfram Richter 8

9 The role of the IT architect 6. Architects Right-Size their Involvement Role Small Project A single person is assigned to play the roles of Lead Architect, Application Architect, Infrastructure Architect and Data Architect. Large Project Different individuals are assigned to each of the architecture roles of Lead Architect, Application Architect, Infrastructure Architect and Data Architect. In addition, the team also includes a Security Architect. Task Work product An Architecture Overview is created as a sketch on a whiteboard and then photographed (it is not kept up to date). Requirements, Functional, Deployment and Performance viewpoints are used to document the architecture. An Architecture Overview is created as a formal work product that is maintained. Requirements, Functional, Deployment, Validation, Performance and Security viewpoints are used to document the architecture. An Viewpoint is added to emphasize this particular aspect of the architecture Sandro Schwedler, Wolfram Richter The role of the IT architect 7. Architects Influence the Requirements Stakeholder input Scalability Performance Schedule Resources Maintainability Portability Distribution Platforms Sandro Schwedler, Wolfram Richter 9

10 The role of the IT architect 8. Architects Derive Solutions from Business Needs Attribute Driven Design (ADD) Method Siemens 4 Views (S4V) method The Rational Unified Process (RUP) Developed at the Software Engineering Institute Quality attributes drive the architecture Underpinned by architectural tactics and patterns Developed at Siemens Corporate Research An analysis of global factors drives the architecture Iteratively addresses challenges across four views (conceptual, execution, module and code architecture) Developed at Rational Software (now IBM Rational) Architecturally-significant requirements drive the architecture Each iteration considers the key architectural elements of the solution, before realizing the requirements across them Sandro Schwedler, Wolfram Richter Within the industry there are several IT architect disciplines * The Enterprise Architect focuses on IT concerns that must be addressed consistently across the entire enterprise. Coverage is comprehensive though generally not highly detailed. Generally expressed as principles, models and standards (and possibly services) Sandro Schwedler, Wolfram Richter 10

11 Within the industry there are several IT architect disciplines The Solution Architect focuses on the architecture of a complete IT solution, including business process implications, to a business problem, need or opportunity, consistent with the principles, models, standards and shared services defined by an Enterprise Architecture Sandro Schwedler, Wolfram Richter Within the industry there are several IT architect disciplines Business Architect Software Architect Architect Architect Application Architect Infrastructure Architect Sandro Schwedler, Wolfram Richter 11

T-Shape / Skills required to become an architect Breadth Depth Know a wide range of technologies and be able to discuss it with the various specialists Know how to develop in a

Acumen Cost Licensing An IT Architect should not be: A top-level software designer The project manager A technology expert A product expert A lone scientist B r e a d t h D e p t

wikipedia.org/wiki/iso/iec_42010 http://en.wikipedia.org/wiki/software_architecture The Tao of the Software Architect http://www.ibm.com/developerworks/rational/library/4032.

12 T-Shape / Skills required to become an architect Breadth Depth Know a wide range of technologies and be able to discuss it with the various specialists Know how to develop in a technology Soft Skills Working with people Communication Build consensus Conceptual thinking Project Management (needs to know PM but should not act as PM) Politics Business Acumen Cost Licensing An IT Architect should not be: A top-level software designer The project manager A technology expert A product expert A lone scientist B r e a d t h D e p t h Sandro Schwedler, Wolfram Richter Further Reading ISBN ISBN The Tao of the Software Architect Software Engineering Radio Episode 110: Roles in Software Engineering I Sandro Schwedler, Wolfram Richter 12

13 Sandro Schwedler, Wolfram Richter 13

The Process of Software Architecting

IBM Software Group The Process of Software Architecting Peter Eeles Executive IT Architect IBM UK peter.eeles@uk.ibm.com 2009 IBM Corporation Agenda IBM Software Group Rational software Introduction Architecture,