Evaluating Architectural Options Simon Field Chief Technology Officer.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

A BPM Framework for KPI-Driven Performance Management
Our Vision : To be Provider of Choice RISK MANAGEMENT WITHIN EQUITY HOUSING GROUP David Fisher Chief Executive.
OCTAVESM Process 4 Create Threat Profiles
S3-1 © 2001 Carnegie Mellon University OCTAVE SM Process 3 Identify Staff Knowledge Software Engineering Institute Carnegie Mellon University Pittsburgh,
Leader Or Manager? Adrian Taylor St. Mary’s High School Building Leadership Capacity Setting Your Compass Middle Manager Or Middle Leader?
Pedigreed Attribute eLicitation Method (PALM) Onno Dijkstra.
Creative Commons Attribution-ShareAlike 3.0 Unported License - you may use and share this file, but please attribute it to
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
S2-1 © 2001 Carnegie Mellon University OCTAVE SM Process 2 Identify Operational Area Management Knowledge Software Engineering Institute Carnegie Mellon.
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 2001 by Carnegie Mellon.
Sponsored by the U.S. Department of Defense © 2007 by Carnegie Mellon University 1 Pittsburgh, PA The Duties, Skills, and Knowledge of Software.
© 2001 by Carnegie Mellon University PPA-1 OCTAVE SM : Participants Briefing Software Engineering Institute Carnegie Mellon University Pittsburgh, PA
Evaluating a Software Architecture By Desalegn Bekele.
S5-1 © 2001 Carnegie Mellon University OCTAVE SM Process 5 Identify Key Components Software Engineering Institute Carnegie Mellon University Pittsburgh,
A Process for the Direct Assessment of Program Learning Outcomes Based on the Principles and Practices of Software Engineering Robert W. Lingard California.
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
CMMI Overview Quality Frameworks.
Lecture 3 Strategic Planning for IT Projects (Chapter 7)
Project Management Body of Knowledge PMBOK
Architecture Tradeoff Analysis Method Based on presentations by Kim and Kazman
Enterprise Architecture
The Many Contexts of Software Architecture
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
What is Business Analysis Planning & Monitoring?
Process-based IT Organisation at Statistics New Zealand Prepared by Matjaž Jug.
EVALUVATING SOFTWARE ARCHITECTURES FOR REAL-TIME SYSTEMS R.Kazman, M.Klein, P.Clements Software Engineering Institute Carnegie Mellon University.
Evaluating Architectures: ATAM
A Culture of Evaluation – A Key to Effective Governance & Management of DFIs? UN DESA Seminar on Re-thinking the Role of National Development Banks, New.
Program Performance Accountability & Measurable Results Kevin Keaney, Chief Pesticide Worker Safety Programs U. S. EPA 2005.
© 2001 by Carnegie Mellon University PSM-1 OCTAVE SM : Senior Management Briefing Software Engineering Institute Carnegie Mellon University Pittsburgh,
ATAM –Cont’d SEG 3202 N. Elkadri.
© 2001 Carnegie Mellon University S8A-1 OCTAVE SM Process 8 Develop Protection Strategy Workshop A: Protection Strategy Development Software Engineering.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Systems Analysis Lecture 2 Analysing the Business Case Feasibility Scope 1 BTEC HNC Systems Support Castle College 2007/8.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Creative Commons Attribution-ShareAlike 3.0 Unported License - you may use and share this file, but please attribute it to
Lecture-3.
L21: Project Steering Committee Kickoff Meeting 9/4/12.
Let Ascension take your business to new heights Tender Manager Scott Warnock Andrew Smillie.
Designing software architectures to achieve quality attribute requirements F. Bachmann, L. Bass, M. Klein and C. Shelton IEE Proceedings Software Tzu-Chin.
University of Southern California Center for Systems and Software Engineering Agile Project Management Tools Supannika Koolmanojwong CSCI 577a.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
From Red to Green: the role of Enterprise Architecture in the ONS Corporate IT Strategy Simon Field Chief Technology Officer.
Local Governance & Sectors Subcommittee Regions recommendation.
Fermilab Presentation Greg Bock, Pepin Carolan, Mike Lindgren, Elaine McCluskey 2014 SC PM Workshop July 2014.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Chapter 5 The project manager, sponsor and other stakeholders.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Policy And Strategy. Policy Meaning A policy is a general statement which is formulated by an organisation for the guidance of its personnel. The objectives.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Project management Topic 4 Starting up a project.
Investment decision making
Evidence about the Benefits of CMMI ® What We Already Know and What We Need to Know Joe Jarzombek, PMP Deputy Director for Software Assurance Information.
EVALUATING AND SELECTING IT INVESTMENT Pertemuan 5-6 Matakuliah: A0824/IT Investment Portfolio Tahun: 2009 The problems of today will not be solved by.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
The ATAM method. The ATAM method (1/2) Architecture Tradeoff Analysis Method Requirements for complex software systems Modifiability Performance Security.
Training on Safe Hospitals in Disasters Module 3: Action Planning for “Safe Hospitals”
Future City Orientation Laura Lorenzo, PMP President ; PMI-SVC.
S7-1 © 2001 Carnegie Mellon University OCTAVE SM Process 7 Conduct Risk Analysis Software Engineering Institute Carnegie Mellon University Pittsburgh,
Chapter 24: Architecture Competence
Chapter 17: Designing an Architecture
Lecture 17 ATAM Team Expertise
Epilog © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.
Project Roles and Responsibilities
How to Design and Implement Research Outputs Repositories
Portfolio, Programme and Project
5+1 5+2 5+3 5+4 5+5 5+6 5+7 5+8 5+9 1 2 3 4 6 5 7 8 9 9+1 9+2 9+3 9+4 9+5 9+6 9+7 9+8 9+9 2+1 2+2 2+3 2+4 2+5 2+6 2+7 2+8 2+9 3+1 3+2 3+3 3+4 3+5 3+6 3+7.
Project Management Method and PMI ® PMBOK ® Roles
Presentation transcript:

Evaluating Architectural Options Simon Field Chief Technology Officer

The development lifecycle context First Architecture Review Second Architecture Review

Architecture Trade-off Analysis Method Developed by: Software Engineering Institute, Carnegie Mellon University Sponsored by the US Department of Defense Review team develop a utility tree showing trade-off among quality attributes for solution options References: ATAM:Method for Architecture Evaluation ATAM:Method for Architecture Evaluation (technical report from Software Engineering Institute, CMU) Evaluating Software Architectures Evaluating Software Architectures by Paul Clements, Rick Kazman and Mark Klein

Review Structure Completion of Matrix 1 Review preparation The Review workshop Describe business problem Outline solution options Review Matrix 1 Populate Matrices 2 & 3 Throughout: build list of issues, mitigations etc. Write Report Duration of workshop varies from ½ day to 2 days depending on size and complexity of project

Governance Reviews mandated in ONSide development method Conducted on behalf of the ONS Architecture Review Board (ARB) Report signed of by ARB Accepted in writing by Project Board / Project Manager, or contested in an “appeal” Appeal heard by the ONS IM Committee (on behalf of the Executive Management Group)

Matrix 1 – Quality Attributes Relates quality attributes to project business requirements

Matrix 2 – Risk Trade-off Examines risk of failure to achieve each business requirement for each solution option

Matrix 3 – Architectural Fit Examines extent to which each solution option satisfies a selected set of key architectural principles Scoring Guide 0=Doesn't meet principle, 3=Falls short of principle, 5= Satisfactory/Compliant, 7=-Good/Very Good, 10=Fully meets principle/goes beyond it

Conclusions Structured reviews help you: get the right focus on all requirements (including NFRs) select the right architecture for each project steer projects towards your corporate vision reduce project risk and costs Make sure you get the governance right Involve the right stakeholders Link to existing corporate methods and processes