Pedigreed Attribute eLicitation Method (PALM) Onno Dijkstra.

Slides:



Advertisements
Similar presentations
OCTAVESM Process 4 Create Threat Profiles
Advertisements

S3-1 © 2001 Carnegie Mellon University OCTAVE SM Process 3 Identify Staff Knowledge Software Engineering Institute Carnegie Mellon University Pittsburgh,
Information Technology Project Management
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
Lero© 2010 Software Process & Quality Improvement Dr. Ita Richardson Lero – the Irish Software Engineering Research Centre and Department of Computer Science.
Software Architecture – Centric Methods and Agile Development by Craig Castaneda.
FEMA’s Guidelines and Standards Strategy ASFPM Conference May 23, 2012.
Instructor: Tasneem Darwish
Active Review for Intermediate Designs [Clements, 2000]
Evaluating Software Architectures for Real- Time Systems R. Kazman, M. Klein, P. Clements Software Engineering Institute Carnegie Mellon University.
©2011 Rolls-Royce plc The information in this document is the property of Rolls-Royce plc and may not be copied or communicated to a third party, or used.
Lecture 17 Architecture Tradeoff Analysis Method ATAM
Software Architecture in Practice RiSE’s Seminars Bass’s book :: Chapters 07 Eduardo Santana de Almeida.
The Survivable Network Analysis Project: Project Introduction Nancy R. Mead CERT/Coordination Center Software Engineering Institute Carnegie Mellon University.
Principles of Software Architecture Evaluation and Design
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
Version # Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1999 by Carnegie.
Software architecture evaluation
Architecture and Requirements
A Survey of Software Architecture Viewpoint Models Nicholas May
Software Architecture premaster course 1.  Israa Mosatafa Islam  Neveen Adel Mohamed  Omnia Ibrahim Ahmed  Dr Hany Ammar 2.
Architecture Tradeoff Analysis Method Based on presentations by Kim and Kazman
EVALUVATING SOFTWARE ARCHITECTURES FOR REAL-TIME SYSTEMS R.Kazman, M.Klein, P.Clements Software Engineering Institute Carnegie Mellon University.
Evaluating Architectures: ATAM
CPSC 871 John D. McGregor Module 4 Session 3 Architecture Evaluation.
© 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.
“Simulation Approach for Impact Analysis of Requirement Volatility Considering Dependency Change” Tiemen Roest.
Architecture Evaluation Evaluation Factors Evaluation by the designer Every time the designer makes a key design decision or completes a design milestone,
© 2001 Carnegie Mellon University S8A-1 OCTAVE SM Process 8 Develop Protection Strategy Workshop A: Protection Strategy Development Software Engineering.
F – VIVAN Kourosh. Authors Universidad de Murcia Ambrosio TOVAL, Reader in Software Engineering in the Department of Computing Joaquin NICOLAS Begona.
Welcome Synthesis Report on Assessment and Feedback with Technology Enhancement.
An Online Knowledge Base for Sustainable Military Facilities & Infrastructure Dr. Annie R. Pearce, Branch Head Sustainable Facilities & Infrastructure.
Scenario based analysis of COTS acquisition impacts (Feblowitz & Greenspan, 1998) Johan Meppelink.
Some perspectives in teaching Software Architecture Prabhakar T.V., Kiran Kumar {tvp, IIT Kanpur SATURN 2008.
Managing Product Development Prepared by: Ayesha Sarfraz(group leader) Madiha ashiq Aneeka akram Tanzila khawar.
Risk Management in Software Project Riskit Method and SEI Method Introduction *The Definition of risk in software project? Webster defines “risk” as “
Software Safety Risk Evaluation Process Yorick Bouma, , Group III.
SOFTWARE ARCHITECT – DESIGN.  Introduction  Architecture Drivers  POS System Architecture  Mapping Between Perspective  Evaluate Architecture  Project.
Lecture 7: Requirements Engineering
Evaluating Architectural Options Simon Field Chief Technology Officer.
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
CSCI 6231 – Final Lecture Additional Resources and Topics.
CRAC++ Risk-Based Confidentiality Requirements Specification for Outsourced IT Systems.
Systems Engineering Simulation Modeling Maintenance Analysis Availability Research Repair Testing Training Copyright © 2009, David Emery & D&S Consultants,
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Project Charter
Networked Systems Survivability CERT ® Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA © 2002 Carnegie.
Database Development Data Analysis: The Entity Relationship Powered by DeSiaMore1.
CERT Centers, Software Engineering Institute Carnegie Mellon University Pittsburgh, PA SEI is sponsored by the U.S. Department of Defense ©
Architecture Tradeoff Analysis Method Software Engineering Institute Carnegie Mellon University Presented by: Senthil ayyasamy CS 590l- winter 2003.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Software Engineering Seminar Proposal Name: Mr.Prachya Plasananya ID: Major: Software Engineering Seminar Advisor: Aj. Nikorn Rongbutsri.
The Value of USAP in Software Architecture Design Presentation by: David Grizzanti.
The ATAM method. The ATAM method (1/2) Architecture Tradeoff Analysis Method Requirements for complex software systems Modifiability Performance Security.
CPSC 872 John D. McGregor Session 31 This is it..
Lecture 15 Attribute Driven Design Again Topics ATAM – team expertise and experience needed Chapter 24 Next Time: June 22, 2016 CSCE 742 Software Architecture.
Lecture 15 Attribute Driven Design Again Topics ATAM – team expertise and experience needed Chapter 24 Next Time: June 22, 2016 CSCE 742 Software Architecture.
Chapter 16: Architecture and Requirements
Lecture 08 Architecturally Significant Requirements
Lecture 12 Attribute Driven Design Again
CS4311 Spring 2011 Process Improvement Dr
Lecture 17 ATAM Team Expertise
Participative Process Reviews
Vanilson Burégio The Battlefield Control System – The First Case Study in Applying the ATAM Chapter 4 of: Clements, Paul et al., Evaluating.
Standard 10 Research(**) البحث العلمي )**(.
Presentation transcript:

Pedigreed Attribute eLicitation Method (PALM) Onno Dijkstra

Authors P. Clements J.D. McGregor L. Bass Clements, P., McGregor, J.D., & Bass, L. (2010). Eliciting and Capturing Business Goals to Inform a Product Line's Business Case and Architecture. Proceedings of the 14th international conference on Software Product Lines: Going Beyond, doi: / Research and development center at Carnegie Mellon University, established in 1984 by the U.S. Department of Defense.

Origins Problem: one of the major causes of system- development problems and failure is the omission of important requirements or the inclusion of unreasonably rigid requirements. Solution: relate requirements to business goals in a systematic way.

Origins (2) The method's name is derived from the outcome of quality attribute requirements with a pedigree rooted in business goals. PALM uses: ▫the standard business goal categories of ATAM. ▫the concept of Quality Attribute Scenarios for Business Goal Scenarios.

Purpose PALM facilitates better capture and expression of high-pedigree, architecturally significant requirements (Clements et al., 2010). Tying business goals to architecture by using quality attribute requirements.

Process steps 1.PALM overview presentation 2.Business drivers presentation 3.Architecture drivers presentation 4.Business goals elicitation 5.Identifying potential quality attributes from business goals 6.Assignment of pedigree to existing quality attribute drivers 7.Exercise conclusion

PDD

PDD (2)

Example Business goals ▫Easy to maintain system ▫Fast responding system ▫Reduce costs Architecture drivers ▫Security ▫Database-driven Quality attribute requirements ▫Maintainability ▫Performance Non-architectural solutions ▫Lowering the facility’s thermostats in the winter ▫Reducing employees’ pensions

Related literature Software Engineering Institute (SEI) developed and published a series of architecture-centric methods. ▫Quality Attribute Workshop (QAW) for eliciting and articulating detailed quality attribute requirements for a system. ▫Architecture TradeOff Analysis Method (ATAM) relies on stakeholder participation and scenario generation to gather data. ▫Standard business goal categories.

Questions?