Active Components a Software Product Line Infrastructure Bas Geertsema Slinger Jansen Information and Computing Sciences University Utrecht VARI-ARCH Workshop.

Slides:



Advertisements
Similar presentations
Connected Health Framework
Advertisements

GenArch: Automatic Product Derivation in Multi-agent Systems Product Line Elder Cirilo.
The e-Framework Bill Olivier Director Development, Systems and Technology JISC.
Armel Lefebvre – 09/04/2014.  Model-driven approach to enterprise interoperability at the technical service level  2013  First author: Ravi Khadka.
VARIABILITY IN SOFTWARE PRODUCT LINE ARCHITECTURES VARI-ARCH 2010 ECSA 4th European Conference on Software Architecture Copenhagen, August 23, 2010.
Domain Engineering Silvio Romero de Lemos Meira
Domain Engineering Arie van Deursen May Software Product Line  Group of products  sharing a common, managed set of features  to satisfy the.
Software Reuse SEII-Lecture 28
Sponsored by the U.S. Department of Defense © 2004 by Carnegie Mellon University page 1 Pittsburgh, PA Integrating Domain Specific Modeling.
WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web Stefano Butti, Marco Brambilla, Piero Fraternali Web Models Srl, Italy.
Programming Distributed Systems Lab Institute of Computer Science University of Augsburg Universitätsstraße 14, D Augsburg Tel.: (+49) 821/ ,
Formal Techniques in Software Engineering Universiteit AntwerpenIntroduction 1.1 Formal Techniques in Software Engineering 3de BAC Informatica Chapter.
Variability Oriented Programming – A programming abstraction for adaptive service orientation Prof. Umesh Bellur Dept. of Computer Science & Engg, IIT.
Automated Analysis and Code Generation for Domain-Specific Models George Edwards Center for Systems and Software Engineering University of Southern California.
Azad Madni Professor Director, SAE Program Viterbi School of Engineering Platform-based Engineering: Rapid, Risk-mitigated Development.
Site Skin Structure Services Space plan Stuff Software Architecture and Software Architecture Patterns (1)
A Model-Driven Framework for Architectural Evaluation of Mobile Software Systems George Edwards Dr. Nenad Medvidovic Center.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
CSE 300: Software Reliability Engineering Topics covered: Software metrics and software reliability.
Product Line Architecture for a Family of Meshing Tools María Cecilia Bastarrica, Nancy Hitschfeld-Kahler, Pedro O. Rossel Computer Science Department,
Planning for Middleware Rose Gamble Leigh Davis Jamie Payton University of Tulsa.
Institute for Software Research©2001, University of California, Irvine Product-Line Architectures André van der Hoek Institute for Software Research University.
Course Instructor: Aisha Azeem
LUCENTIA Research Group Department of Software and Computing Systems Using i* modeling for the multidimensional design of data warehouses Jose-Norberto.
Software Product Line Engineering Andrew Burmester SE 4110 Section 2 4/14/11.
Autonomic Software Product Lines (ASPL) Nadeem Abbas, Jesper Andersson, Welf Löwe Linnaeus University, Sweden Monday, August 23, st International.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Spectra Software Defined Radio Products Applying Model Driven Design, Generative Programming, and Agile Software Techniques to the SDR Domain OOPSLA '05.
Wrestling with Windows Workflow Foundation Simon Thurman Jeremy Stimson.
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
A Generative and Model Driven Framework for Automated Software Product Generation Wei Zhao Advisor: Dr. Barrett Bryant Computer and Information Sciences.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
1 The Architectural Design of FRUIT: A Family of Retargetable User Interface Tools Yi Liu, H. Conrad Cunningham and Hui Xiong Computer & Information Science.
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
A Domain-Specific Modeling Language for Scientific Data Composition and Interoperability Hyun ChoUniversity of Alabama at Birmingham Jeff GrayUniversity.
Juha Mykkänen University of Kuopio, HIS R&D Unit Health Kuopio seminar Brussels, 5 November 2004 SerAPI project: Service-oriented architecture and Web.
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
August/2007 Helton Souza Lima SBCARS 1 Automatic Generation of Platform Independent Built-in Contract Testers Helton Souza Lima Franklin Ramalho Patricia.
Ahmed M. Gamal, J2EE Mohamed Maaty, Information hp INTRODUCING JBPM.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
Chapter 6 Architectural Design.
consumerization of IT new social & app patterns cloud computing data explosion.
INRIA - LaBRICharles Consel Jan-06 1 Domain-Specific Software Engineering Charles Consel Phoenix Research Group LaBRI /INRIA-Futurs January 2006.
CSC 532 Term Paper Presentation Hybrid approach to component based Engineering  Introduction.  Component based development (CBD).  Pros and Cons of.
OOPSLA workshop on Domain-Specific Visual Languages 1 Framework for Domain-Specific Visual Languages Juha-Pekka.
Automated Transformation of Statements Within Evolving Domain Specific Languages Peter Bell CEO/CTO, SystemsForge 7th OOPSLA Workshop on Domain-Specific.
Toward a Semantic Anchoring Infrastructure for Domain-Specific Modeling Languages Kai Chen Janos Sztipanovits Sandeep Neema Matthew Emerson Sherif Abdelwahed.
OOPSLA workshop on Domain-Specific Modeling (DSM’03) 1 Vasco Amaral, Univ. of Mannheim Steve Cook, Microsoft Daniel Dvorak, JPL/Cal Tech Lars Grunske,
Lecture 11 Introduction to Information Systems Lecture 12 Objectives  Describe an information system and explain its components  Describe the characteristics.
EMEA Beat Schwegler Architect Microsoft EMEA HQ Ingo Rammer Principal Consultant thinktecture
OOPSLA workshop on Domain-Specific Visual Languages 1 Juha-Pekka Tolvanen, Steven Kelly, Jeff Gray, Kalle Lyytinen.
03/01/20161 A MODEL FOR VARIABILITY DESIGN RATIONALE IN SPL Ismênia Galvão, Pim van den Broek & Mehmet Akşit VARI-ARCH 2010, Copenhagen,
Designing a Product Line Architecture Jan Bosch Professor of Software Engineering University of Groningen, Netherlands
Solution Supply Chains Jack Greenfield. Overview Learning from Other Industries Mass Customization in Software Development Implementing Supply Chains.
Developing Product Line Components Jan Bosch Professor of Software Engineering University of Groningen, Netherlands
UML Profile BY RAEF MOUSHEIMISH. Background Model is a description of system or part of a system using well- defined language. Model is a description.
Slide no. 1  =====!"§!“!Nova§ ITU-T work on technical languages and general software issues Amardeo Sarma Chairman, ITU-T Study Group 10.
February 19, February 19, 2016February 19, 2016February 19, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific.
Toward product architecture oriented requirements analysis for product line development in systems engineering Kei Kurakawa Nara Institute of Science and.
George Edwards Computer Science Department Center for Systems and Software Engineering University of Southern California
Informatics for Scientific Data Bio-informatics and Medical Informatics Week 9 Lecture notes INF 380E: Perspectives on Information.
Software Factories - Today and Tomorrow
Web Ontology Language for Service (OWL-S)
Designing Software for Ease of Extension and Contraction
Model-Driven Analysis Frameworks for Embedded Systems
The Extensible Tool-chain for Evaluation of Architectural Models
Functions and Their Graphs
A Semantic Type System and Propagation
Automated Analysis and Code Generation for Domain-Specific Models
Presentation transcript:

Active Components a Software Product Line Infrastructure Bas Geertsema Slinger Jansen Information and Computing Sciences University Utrecht VARI-ARCH Workshop August 23, 2010

Introduction app for healthcare organisations app for insurance vendors Software Product Population Software Product Family

How to.. Define the variant ? (design) Reuse the design (with small adaptations)?

Question Which software product line infrastructure supports software product populations and step-wise refinements of software products? Case: A Dutch ISV developing for a wide range of industries using an application generator

Active Components Very adaptive, self-describing components Active because invoked during derivation (empowered!) Domain-specific models to express variability Propagate variability using transformations (MDE)

Applications Applications consist of: component composition design in domain-specific models Applications are incrementally defined (pos. variability)

Derivation

Variability in models Domain-specific models Variability specified close to problem domain Flexible (graph) Orthogonal variability models Ease of use (features) Standardized in SPL Composition of components Component model

Stakeholders SPL developer Orchestrate variability mechanisms Develop integration framework of SPL Component developer Define domain-specific meta-models Propagate variability in component Application developer Decision maker or modeler

Architectural Views Architecture can be expressed in a DSL architectural meta-models defined in the SPL Transformation of architectural models/views based on (variability) models upon derivation

Discussion