Software Architectural Assumptions in Software Architecting Chen Yang a,b, Peng Liang a, Paris Avgeriou b a State Key Lab of Software Engineering, Wuhan.

Slides:



Advertisements
Similar presentations
Rational Unified Process®
Advertisements

A Comparison of Implicit and Explicit Links for Web Page Classification Dou Shen 1 Jian-Tao Sun 2 Qiang Yang 1 Zheng Chen 2 1 Department of Computer Science.
The 20th International Conference on Software Engineering and Knowledge Engineering (SEKE2008) Department of Electrical and Computer Engineering
Engineering Medical Information Systems
Computer Security Lab Concordia Institute for Information Systems Engineering Concordia University Montreal, Canada A Novel Approach of Mining Write-Prints.
May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
Difference between project and other assignments  real customer  before programming: negotiations with client to clarify requirements  often.
Antony Tang 1, Ann Nicholson 2, Yan Jin 1, Jun Han 1 1 Faculty of ICT, Swinburne University of Technology 2 School of Computer Science and Software Engineering,
| 1 › Department of Mathematics and Computing Science, Software Engineering and Architecture Group / Matthias Galster Describing Variability in.
University of Minho School of Engineering ALGORITMI Uma Escola a Reinventar o Futuro – Semana da Escola de Engenharia - 24 a 27 de Outubro de 2011 Introduction.
Study Period Report: Metamodel for On Demand Model Selection (ODMS) Wang Jian, He Keqing, He Yangfan, Wang Chong State Key Lab of Software Engineering,
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
CS 501: Software Engineering Fall 2000 Lecture 5 (a) Documentation (b) Requirements Analysis.
HFSD Methods Nov HFSD Methods Objectives –To consider types of systems –To characterise methods for HF input into SD –To identify HF contributions.
Software Assurance CBK and University Curricula Matt Bishop Sophie Engle.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
University of Jyväskylä – Department of Mathematical Information Technology Computer Science Teacher Education ICNEE 2004 Topic Case Driven Approach for.
Software Architecture. Agenda " Why architect? " What is architecture? " What does an architect do? " What principles guide the process of architecting?
‘ KNOWLEDGE MANAGEMENT ’ ACCORDING TO B USINESS S CIENCE Omwoyo Bosire Onyancha University of South Africa Department of Information Science.
August 19, August 19, 2015August 19, 2015August 19, 2015 Azusa, CA Sheldon X. Liang Ph. D. CS 470 Software Engineering I Azusa Pacific University,
QUPER Paper Outline Yuri Sprockel. Update Unfortunate CCV date pick Cost view elaboration New QUPER PDD almost finished.
Solution Architecture
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
@VOLCROWE Develop new models of motivations for volunteering in the context of non-commercial crowdsourcing projects. Evaluate a range.
Copyright © 2013 Curt Hill The Zachman Framework What is it all about?
A Taxonomy of Evaluation Approaches in Software Engineering A. Chatzigeorgiou, T. Chaikalis, G. Paschalidou, N. Vesyropoulos, C. K. Georgiadis, E. Stiakakis.
Computer Systems & Architecture Lesson Software Architecture in the Future.
Athena, a large scale programming lab support tool Anton Jansen, Ph.D. Student Software Engineering and ARCHitecture (SEARCH) University of Groningen The.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie.
1. Systems, Science, and Study. Outline What is geographic information? Definition of data, information, knowledge and wisdom Kinds of decisions that.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Unit 1 University of Sunderland COMM80 Risk Assessment of Systems Change Risk Aspects and Context Covered in the Module COMM80: Risk Assessment of Systems.
1 Security in the Context of Dependability Tacksoo Im John D. McGregor School of Computing Clemson University ORNL Presentation.
Basic Concepts Software Architecture. What is Software Architecture? Definition: – A software architecture is the set of principal design decisions about.
A Web-based Tool for Managing Architectural Design Decisions Rafael Capilla, Francisco Nava, Sandra Pérez Universidad Rey Juan Carlos de Madrid Juan C.
Yang Hu University of Pittsburgh Department of Computer Science.
Latent Tree Models & Statistical Foundation for TCM Nevin L. Zhang Joint Work with: Chen Tao, Wang Yi, Yuan Shihong Department of Computer Science & Engineering.
How to Read Research Papers? Xiao Qin Department of Computer Science and Software Engineering Auburn University
Lecture 1 The University of Lahore Software Engineering Saeed Akhtar
Accuracy and Precision Created by The North Carolina School of Science and Math.The North Carolina School of Science and Math Copyright North Carolina.
Practical Experiences of Agility in the Telecom Industry XP 2003 conference Jari Vanhanen Helsinki University of Technology Software Business.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Chapter 3: Software Project Management Metrics
Dr. Young J. Kim.  INCOSE Definition ( ◦ “An interdisciplinary approach & means to enable the realization of successful systems. It focuses.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
On the design and development of program families Presented by: M. Deng and J. Zhang 4/15/2002 CSE870 Advanced Software Engineering, Spring 2002.
| 1 › Matthias Galster › Paris Avgeriou Handling Variability in Software Architecture – Problems and Implications.
RE-ENGINEERING AND DOMAIN ANALYSIS BY- NISHANTH TIRUVAIPATI.
Adopting the Practice of Enterprise Analysis in a Mid-Sized Company Mary Burns Furr Adaptis, Inc Seattle, Washington USA.
Configuration of a support- plateform for data collection using Mobile technologies African Regional Conference on the use of mobile technology for statistical.
Be.wi-ol.de User-friendly ontology design Nikolai Dahlem Universität Oldenburg.
1 An Execution-Driven Simulation Tool for Teaching Cache Memories in Introductory Computer Organization Courses Salvador Petit, Noel Tomás Computer Engineering.
March 19, March 19, 2016March 19, 2016March 19, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University,
Are you a computer science enthusiast? Want to attend a conference within your reach?
Florida International University VIP Consortium Meeting ● May 12-13, 2016 Francisco R. Ortega, Ph.D. Masoud Sadjadi, Ph.D. Mohsen Taheri.
Page 1 An Overview of The COTS-Aware Requirements Engineering and Software Architecting Project (CARE/SA) The University of Texas at Dallas Department.
Introduction to Project Management
Chapter 24: Architecture Competence
A Fault Tolerance Protocol for Uploads: Design and Evaluation
Systems Design.
Lecture 17 ATAM Team Expertise
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
Goal, Question, and Metrics
Human Face of Big Data Project
How Are Spreadsheet Templates Used in Practice: A Case Study on Enron
Topics discussed in this section:
Topics discussed in this section:
Presentation transcript:

Software Architectural Assumptions in Software Architecting Chen Yang a,b, Peng Liang a, Paris Avgeriou b a State Key Lab of Software Engineering, Wuhan University, China b Department of Computing Science, University of Groningen, The Netherlands

Outline 2  Concept  Motivation  Questions  Related work  Our work  Future work

What is Architectural Assumption (AA)? 3  A type of architectural knowledge A type of Architectural Design Decision as well as the reasons for making the decisions Explicit documentation of the unknowns or the expectations to provide a context to decision making Typically assumptions about the structure of the system under development

What is AA? 4  The AA concept is not new  No widely accepted definition of this concept! Academia Industry

Why should we manage AAs? 5  Uncertain things (e.g., requirements)  Numerous AAs exist in projects  Usually implicit and undocumented  Originally invalid AAs Personal experience and knowledge  Valid AAs turn to be invalid Changed requirements, architecture, and project context  Different understanding Different stakeholders Researchers vs. Practitioners

Why should we manage AAs? 6  Problems of not managing AAs Architectural mismatch Misunderstanding of architecture Considerable time and effort

What, When, and How 7  What kinds of projects are suitable for introducing AA management?  What AAs should be managed?  When to manage AAs?  How to manage AAs? Context dependent

Related work 8  AA definition  AA classification  AA activities  Methods and tools for AA management (e.g., identification, recording, and recovering)  Lessons learned for AA management

Our work 9  Chen Yang, Peng Liang. Identifying and Recording Software Architectural Assumptions in Agile Development. In: Proceedings of the 26th International Conference on Software Engineering and Knowledge Engineering (SEKE), pp ,  Chen Yang, Peng Liang, Paris Avgeriou. A Systematic Mapping Study on the Combination of Software Architecture and Agile Development. Journal of Systems and Software, (under review)  Chen Yang, Peng Liang, Paris Avgeriou. A Survey of Software Architectural Assumptions. Information and Software Technology, (under submission)

Future work 10  The state of the art of AA management from the practitioners’ perspective?  How to identify and record AAs in software development?  What is the process of AA management?  How to trace AAs in software development?  How to combine AA management and agile development?

11 Thanks!