Epilog © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.

Slides:



Advertisements
Similar presentations
Dr. Rogelio Dávila Pérez
Advertisements

Enabling you for BIM (Building Information Modelling)
Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture Architecture in a Technical Context Architectures inhibit.
Systems Analysis and Design Feasibility Study. Introduction The Feasibility Study is the preliminary study that determines whether a proposed systems.
Case studies1. 2 Automating a law office Case studies3 Lessons learned Good intuition and technical skills are not enough to guarantee success Marketing.
MANAGING KNOWLEDGE WORKERS Lecture Twelve (Chapter 12, Notes; Chapter 15, Textbook)
Chapter 2: Why is Software Architecture Important?
Systems Development Life Cycle:
School of Computing, Dublin Institute of Technology.
Software Architecture in Practice
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
27/09/1999(c) Ian Davis1 Background material Software Architecture (Shaw & Garlan) Object modeling & design (Rumbaugh,Blaha..) Design Patterns (Gamma,
Organizational Project Management Maturity: Roadmap to Success
BPT 3113 – Management of Technology
The Many Contexts of Software Architecture
13-1 Information Technology Economics Information Technology: Economic and Financial Trends Internal IT versus outsourcing Expanding power / declining.
Chapter 15 Systems Development
Evaluating Architectures: ATAM
The Architecture Business Cycle. Software Architecture Definition The software architecture of a program or computing system is the structure or structures.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
EC15: Social Enterprise 2. Social Enterprise Networks Marcus Thompson University of Stirling.
BUSINESS INFORMATICS descriptors presentation Vladimir Radevski, PhD Associated Professor Faculty of Contemporary Sciences and Technologies (CST) Linkoping.
Basic of Project and Project Management Presentation.
Evaluating Architectural Options Simon Field Chief Technology Officer.
Lecture 11 Enterprise Systems Development ( CSC447 ) COMSATS Islamabad Muhammad Usman, Assistant Professor.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
How does money make the world go around? Unit Portfolio Presentation Jacqueline Kurtz.
Better health for rural Australia Nursing and Midwifery Management in What Does It Mean? Moyra Lewis ADONM GSAHS.
Scenario-Based Analysis of Software Architecture Rick Kazman, Gregory Abowd, Len Bass, and Paul Clements Presented by Cuauhtémoc Muñoz.
Object Oriented Methodology Course Introduction. Objectives A 3-credit hour graduate course explaining the development of object oriented software systems.
A POCKET GUIDE TO PUBLIC SPEAKING 4 TH EDITION Chapter 32 Technical Courses.
Chapter 12: Other Quality Attributes
Chapter 16: Architecture and Requirements
Information Technology Economics
Chapter 7: Modifiability
Lecture 03 Quality Attributes
Chapter 4: Understanding Quality Attributes
Quality Attribute Modeling and Analysis
Chapter 3: The Many Contexts of Software Architecture
Challenges and opportunities for the CFO
Software Architecture
Information Systems Development
Chapter 24: Architecture Competence
17. Managing GIS © John Wiley & Sons Ltd.
Chapter 17: Designing an Architecture
Lecture 17 ATAM Team Expertise
Innovation & Design in the Cultural Industries
The Systems Engineering Context
Software Architecture
Chapter 11: Usability © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.
Chapter 19: Architecture, Implementation, and Testing
INTRODUCTION OF PROPERTY MARKETING
Characteristics of Successful Entrepreneurs
Chapter 22: Management and Governance
Chapter 25: Architecture and Product Lines
Software engineering Lecture 21.
Software Quality Engineering
Informatics 121 Software Design I
Assist. Prof. Magy Mohamed Kandil
Chapter 6 HEALTHCARE MARKETING. Chapter 6 HEALTHCARE MARKETING.
Informatics 121 Software Design I
D7032E – Software Engineering
EC Strategy, Globalization, and SMEs
OO Design and Development
Informatics 121 Software Design I
Lecture 03 Quality Attributes
Software Quality Assurance 2015
Informatics 121 Software Design I
Segments Introduction: slides minutes
Software Architecture
Presentation transcript:

Epilog © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Important Take-Aways What architecture is, why it’s important, what influences it, and what it influences. The role that architecture plays in a business, technical, project, and professional context. The symbiosis between architecture and quality attributes, how to specify and achieve quality attribute requirements How to capture the architecturally significant requirements for an architecture. How to design it, document it, guide an implementation with it, evaluate it to see if it’s a good one for your needs, reverse-engineer it, and manage a project around it. How to evaluate an architecture’s cost and benefit, what it means to be architecturally competent, and how to use architecture as the basis for an entire software product line. Architectural concepts and patterns for systems on the current technological frontier – edge applications and the cloud. © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

How Do You Sell Your Organization on the Value of Architecture? Speak the right language. The decision-makers in your organization care about products, architectures. They care about ensuring that the products are competitive in the marketplace. You have to translate these market terms into technical decisions. Speak the right language, part 2: Project managers care about reduction of technical risk, reliable and realistic scheduling and budgeting, and planning the production of those products. Justify the use of architecture methods in these terms. Get involved. Get involved in requirements gathering, in testing, in operations. Understand how to sell your ideas in these environments. It’s the economy, stupid. Think in, and couch your arguments in, economic terms. Relish small victories. Organizational change is difficult and slow. Organizations have inertia. Enjoy those victories you achieve. © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License

Enjoy Your Profession You will spend many years working in your chosen profession. If you enjoy yourself; those years will go fast. © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License