Component Based SW Development and Domain Engineering 1 Component Based Software Development and Domain Engineering.

Slides:



Advertisements
Similar presentations
The 20th International Conference on Software Engineering and Knowledge Engineering (SEKE2008) Department of Electrical and Computer Engineering
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Reference ontologies for manufacturing Bob Young - R Young, N Hastilow, M Imran, N Chungoora Z Usman and A-F Cutting-Decelle.
Domain Engineering Silvio Romero de Lemos Meira
Chapter 22 Product Line Engineering Week 1 CIS 673.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
AN APPLICATION SPECIFIC TECHNIQUE FOR RETRIEVAL AND ADAPTATION OF TRUSTED COMPONENTS Benny Thomas Master of Computer Science Supervised by Dr. David Hemer.
Programmierung verteilter Systeme Lab Institut für Informatik Universität Augsburg Universitätsstraße 14, Augsburg Tel.: (+49) 821/ , Fax:
Research topics Semantic Web - Spring 2007 Computer Engineering Department Sharif University of Technology.
IBM Business Consulting Services © Copyright IBM Corporation 2006 Unified Process March 27, 2006 Chris Armstrong.
Object-Oriented Analysis and Design
Rational Unified Process
Software Testing and Quality Assurance
Software Testing and Quality Assurance
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Software IMprovement using Product LinEs Project Presentation (I) - Domain Analysis Results Liana Lisboa - PM Project: Starship Games PL.
DAIMIHenrik Bærbak Christensen1 Product Lines Architectural Reuse.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Project Name Group Name: Customer: Name of Customer Project Manager: Student Name1 Project Facilitator: Student Name1 Customer Liaison/Domain Expert:Student.
Article by: Farshad Hakimpour, Andreas Geppert Article Summary by Mark Vickers.
Iterative development and The Unified process
Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture.
Integrating Problem-Solving and Educational Software
NON-FUNCTIONAL PROPERTIES IN SOFTWARE PRODUCT LINES: A FRAMEWORK FOR DEVELOPING QUALITY-CENTRIC SOFTWARE PRODUCTS May Mahdi Noorian
Architecture and Software Product Lines A software architecture represents a significant investment of time and effort, usually by senior talent. So it.
Domain-Specific Software Engineering Alex Adamec.
SIEVE—Search Images Effectively through Visual Elimination Ying Liu, Dengsheng Zhang and Guojun Lu Gippsland School of Info Tech,
Chapter : Software Process
Carlos Lamsfus. ISWDS 2005 Galway, November 7th 2005 CENTRO DE TECNOLOGÍAS DE INTERACCIÓN VISUAL Y COMUNICACIONES VISUAL INTERACTION AND COMMUNICATIONS.
Formalizing and Analyzing Feature models in Alloy
Teaching Metadata and Networked Information Organization & Retrieval The UNT SLIS Experience William E. Moen School of Library and Information Sciences.
CPIS 357 Software Quality & Testing
Rational Unified Process Fundamentals Module 4: Disciplines II.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
RUP Design RUP Artifacts and Deliverables
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
Michael Soffner A Variability Model for Query Optimizers Michael Soffner 1, Norbert Siegmund 1, Marko Rosenmüller 1, Janet Siegmund 1, Thomas.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 6 Duplication.
Generative Programming. Automated Assembly Lines.
Page 1 Alliver™ Page 2 Scenario Users Contents Properties Contexts Tags Users Context Listener Set of contents Service Reasoner GPS Navigator.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Supporting Scenario-Based Requirements Engineering IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER, 1998 A. G. Sutcliffe, N. A. M.
1 Vulnerability Assessment Elisa Heymann Computer Architecture and Operating Systems Department Universitat Autònoma de Barcelona
Software innovation theoretical model. the model: outputs (outcomes) product/service innovation process innovation factors (drivers) outputs (outcomes)
Why have an Ontology for DoT? The difficult questions.
Topic Maps introduction Peter-Paul Kruijsen CTO, Morpheus software ISOC seminar, april 5 th 2005.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Approach to building ontologies A high-level view Chris Wroe.
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.
Quality Assurance in the Presence of Variability Kim Lauenroth, Andreas Metzger, Klaus Pohl Institute for Computer Science and Business Information Systems.
PDS4 Demonstration Management Council Face-to-Face Flagstaff, AZ August 22-23, 2011 Sean Hardman.
Concepts/ definitions/ meanings of program plan, program scheme, program development, concept paper Program plan is a systematic arrangement of elements.
Knowledge Support for Modeling and Simulation Michal Ševčenko Czech Technical University in Prague.
OWL Web Ontology Language Summary IHan HSIAO (Sharon)
Chapter 7 Lecture 1 Design and Implementation. Design and implementation Software design and implementation is the stage in the software engineering process.
IPDA Architecture Project International Planetary Data Alliance IPDA Architecture Project Report.
1 Ontological Foundations For SysML Henson Graves September 2010.
Experience Report: System Log Analysis for Anomaly Detection
Improvement Science Thinking
Semantic Web Project Status
Lecture #11: Ontology Engineering Dr. Bhavani Thuraisingham
Software Maintenance
Jazz/DM Architecture with respect to the conceptual framework
OVERVIEW Debate in engineering design community: Should design be taught as: Establishing a foundation of theory? or Engaging students in loosely supervised.
Adrian Diaz Eric Clark Tim Peek
Domain Specific Product Description Exchange
Rafael Almeida, Inês Percheiro, César Pardo, Miguel Mira da Silva
Constructing MDA-based Application Using Rational XDE for .NET
Informatics 121 Software Design I
Semantic Web Towards a Web of Knowledge - Outline
Presentation transcript:

Component Based SW Development and Domain Engineering 1 Component Based Software Development and Domain Engineering

Component Based SW Development and Domain Engineering 2 Outline Main Ideas Detailed Map Problem Description Potential Approach Related Work

Component Based SW Development and Domain Engineering 3 Main Ideas

Component Based SW Development and Domain Engineering 4 Detailed Map

Component Based SW Development and Domain Engineering 5 Problems problem domainHow to scope the “problem domain”? domain analysis processHow to define “domain analysis process” in agile way? human factorWhat is the significance of “human factor”? conceptual reuseHow to achieve “conceptual reuse” in CBSD? variation pointsHow to identify and represent “variation points”? domain engineeringHow to automate the “domain engineering”?

Component Based SW Development and Domain Engineering 6 How to scope the “problem domain”? Problem Description:  Current product line scoping approaches fail to appropriately define the right set of alternatives with respect to business requirements. Potential Approach:  Design Space Modeling Related Work:  Product lines scoping  Design space modeling  Domain engineering

Component Based SW Development and Domain Engineering 7 How to define “domain analysis process” in agile way? Problem Description:  Domain analysis is a heavy process which requires lots of time and effort and inherently seems to contradict with agile approaches. On the other hand for deriving the right concepts we need to still apply domain analysis in agile methods. In this problem we focus on the integration of agile and domain analysis processes. Potential Approach:  Applying agile practices in domain analysis practices and vice versa (integrating). Related Work:  Domain analysis  Method engineering  Process engineering  Meta-modeling

Component Based SW Development and Domain Engineering 8 What is the significance of “human factor”? Problem Description:  How to assess the expertise of the domain engineering team of the project? Potential Approach:  Assessment and metrics of human expertise Related Work:  Metrics  Knowledge management  Human factors engineering  Participatory design and teamworking

Component Based SW Development and Domain Engineering 9 How to achieve “conceptual reuse” in CBSD? Problem Description:  after cataloging domain models (assets) it is very hard to identify and search the assets with respect to the given semantic requirements. Potential Approach:  Smart querying and indexing of data  Smart (semantic) matching algorithm  Integrating (google) like approaches in domain analysis process. Related Work:  Knowledge management & engineering  Conceptual modeling  Semantic spaces  Semantic search

Component Based SW Development and Domain Engineering 10 How to identify and represent “variation points”? Problem Description:  Current variability analysis represents statically but we would like to address conditional variation.  Conditions may vary on time, requirements, etc. Potential Approach:  Rule-based definition of variability  Extending feature diagrams Related Work:  Configuration and reconfiguration management  Modeling conditional variation  Exploiting automated tools

Component Based SW Development and Domain Engineering 11 How to automate the “domain engineering”? Problem Description:  Existing domain engineering approaches focus on manually identification, specification and evaluation of knowledge sources. In order to support the domain engineer with routine activities we aim to develop tools. Potential Approach:  Defining Meta-Models for Knowledge Sources, Concepts and Catalogs.  Tool development Related Work:  Ontology  Knowledge engineering  Meta-modeling