Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture Architecture in a Technical Context Architectures inhibit.

Slides:



Advertisements
Similar presentations
IT Governance & Quality Management
Advertisements

Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
Mastering Object-Oriented Analysis and Design with UML Module 4: Analysis and Design Overview.
Chapter 2: Why is Software Architecture Important?
Enterprise Architecture at Curtin University Maureen Murray.
Applications (Software) Technology (Infrastructure) InformationBusiness.
The Transforming Power of the ITIL Framework for the Project Manager Patrick von Schlag Deep Creek Center November 10, 2010.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
Enterprise Architecture The Arkansas Approach. Key Areas What is enterprise architecture? Why is it important? How you can participate Current status.
Software Architecture in Practice
TEMPUS ME-TEMPUS-JPHES
Aust. AM Collaborative Group (AAMCOG) An introduction to ISO “What to do” guide 20th October 2014.
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
1 Computer Systems & Architecture Lesson 1 1. The Architecture Business Cycle.
Business Transformation Health Check
Architecture and Requirements
The Many Contexts of Software Architecture
Software Architecture in Practice (3rd Ed) Introduction
MANAGING STRATEGY INTRODUCTION TO STRATEGIC MANAGEMENT.
Strategic Information Systems Planning
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
Investment Portfolio Methodologies Pertemuan Matakuliah: A Strategi Investasi IT Tahun: 2009.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
The Architecture Business Cycle. Software Architecture Definition The software architecture of a program or computing system is the structure or structures.
Architecture Business Cycle
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
The Challenge of IT-Business Alignment
Using a Project Model for Assessment of CDIO skills Tomas Svensson, Svante Gunnarsson Linköping University Sweden June
4.1 SIE: Progress Report on Implementation. An Opportunity SIE provides UNAIDS with the opportunity to reposition itself within the changing context Response.
IAM REFERENCE ARCHITECTURE BRICKS EMBEDED ARCHITECTS COMMUNITY OF PRACTICE MARCH 5, 2015.
Basic of Project and Project Management Presentation.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
SOFTWARE ARCHITECT – DESIGN.  Introduction  Architecture Drivers  POS System Architecture  Mapping Between Perspective  Evaluate Architecture  Project.
IT Governance: COBIT, ISO17799 & ITIL. Introduction COBIT ITIL ISO17799Others.
Office of Technical Assistance (OTA)1 FIU Development Supporting FIU Operations with effective Information Technology 2004.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Experiences from the Architectural Change Process Josef Nedstam Even-André Karlsson Martin Höst Dept of Telecom, Lund University, Sweden
Starting Perspective: Product Planning WG 02. Our ‘Context’ for Defining Proficiency Necessary Elements for Proficiency –Iteration and release plans –Architecture.
Overview of SAIP and LSSA. Software Architecture in Practice Provides a set of techniques, not a prescriptive method for architectural design. Based on.
Draft Presentation for Communicators Kruger National Park 13 th September 2006.
ITIL VS COBIT 06 PLM - Group 9
eSciDoc Community Model Draft eSciDoc Community Model Overview 1.Introduction 2.Requirements on the Community Model 3.Organizational.
Program Management Office ͏ Project Management
Governance: ICT and Beyond Governance is "the process of decision-making and the process by which decisions are implemented (or not implemented)”
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.
Business Intelligence Pathway Method 5 th Meeting Course Name: Business Intelligence Year: 2009.
Towards an Enterprise Architecture for Wits In the context of the new Student Information System programme Prof Derek W. Keats Deputy Vice Chancellor (Knowledge.
BSA 385 Entire Course FOR MORE CLASSES VISIT BSA 385 Week 1 DQ 1 BSA 385 Week 1 DQ 2 BSA 385 Week 2 Individual Assignment Frequent.
Managing Enterprise Architecture
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
College Success Program John Cowles, Ph.D. Dean of Student Success and Retention Grand Rapids Community College Grand Rapids, Michigan.
IT Service Transition – purpose and processes
Federal Enterprise Architecture (FEA)
Chapter 3: The Many Contexts of Software Architecture
FRA Building Development 2015
Chapter 24: Architecture Competence
Lecture 17 ATAM Team Expertise
Epilog © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.
Measuring Outcomes of GEO and GEOSS: A Proposed Framework for Performance Measurement and Evaluation Ed Washburn, US EPA.
SOFTWARE ARCHITECTURE AND DESIGN
Meet Your Classmates….
Architecture and Agile
Introduction to Software Process Models
Architecture and Agile
Portfolio, Programme and Project
DRAFT ISO 10015:20XX Revision Overview Quality management — Guidelines for competence management and people development ISO/TC176 TG 01.
Systems Architecture and Engineering
Presentation transcript:

Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture Architecture in a Technical Context Architectures inhibit or enable the achievement of quality attributes Architectures and the technical environment The technical environment that is current when an architecture is designed will influence that architecture. Architecture in a Project Life-Cycle Context Conventional/common software development processes: Waterfall, Iterative, Agile, Model-Driven development Activities that are involved in (1) creating a software architecture, (2) using that architecture to realize a complete design, and (3) implementing or managing the evolution of a target system: 1.Making a business case of the system 2.Understanding the architecturally significant requirements 3.Creating or selecting the architecture 4.Documenting and communicating the architecture 5.Analyzing or evaluating the architecture 6.Implementing and testing the system based on the architecture 7.Ensuring that the implementation conforms to the architecture

Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture Architecture in a Business Context Architectures and business goals Architectures and the development organization A Development organization contributes many of the business goals that influence an architecture. An organization often has an investment in assets, such as existing architectures and the products based on them. An organization may wish to make a long-term business investment in an infrastructure to pursue strategic goals and may view the proposed system as one of means of financing and extending that infrastructure. The organizational structure can shape the software architecture, and vice versa. Architecture in a professional context Architect’s duties Architect’s background and experience

Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture Stakeholders A stakeholder is anyone who has a stake in the success of the system being developed.

Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture How is Architectures Influenced

Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture What do Architectures Influence Technical context The architecture can affect stakeholder requirements for the next system similar to the current system Project context The architecture affects the structure of the developing organization. Business context The architecture can affect business goals of the developing organization. Professional context The process of system building will affect the architect’s experience with subsequent systems.