Method Engineering Floris Brouwer (3496457). Rule-Based Maintenance of Post- Requirements Traceability Relations P. Mäder, O. Gotel, I. Philippow (2008)

Slides:



Advertisements
Similar presentations
CASE tools Upper CASE tools: support for the analysis and design Lower CASE tools: support for construction and maintenance 1980s… Nowadays… Integrated.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
© Siemens Product Lifecycle Management Software Inc. All rights reserved Siemens PLM Software Solid Edge ST4 Training Assembly systems libraries.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
IEC Substation Configuration Language and Its Impact on the Engineering of Distribution Substation Systems Notes Dr. Alexander Apostolov.
Chapter 12 Information Systems Chapter Goals Define the role of general information systems Explain how spreadsheets are organized Create spreadsheets.
Chapter Information Systems Database Management.
Requirements Specification
SE 555 Software Requirements & Specification Requirements Management.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.
© 2007 by Prentice Hall 1 Chapter 1: The Database Environment Modern Database Management 8 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Chapter 7: The Object-Oriented Approach to Requirements
Author: Lornet LD team Reuse freely – Just quote Cognitive Science Education Science Software Engineering The basis.
Chapter 1: The Database Environment and Development Process
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Information Systems: Databases Define the role of general information systems Describe the elements of a database management system (DBMS) Describe the.
Software Processes lecture 8. Topics covered Software process models Process iteration Process activities The Rational Unified Process Computer-aided.
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
Systems Analysis and Design in a Changing World, Fifth Edition
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Lecture 3 Uses Cases Topics UML Use Cases pop quiz Readings: Chapter 3 January 24, 2008 CSCE 492 Software Engineering.
Systems Analysis and Design in a Changing World, 3rd Edition
Faculty of Computer & Information
Chapter 1 Chapter 1: The Database Environment Modern Database Management 8 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden © 2007 by Prentice.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
© ABB University - 1 Revision C E x t e n d e d A u t o m a t i o n S y s t e m x A Chapter 4 Engineering Workplace Course T314.
Supporting Scenario-Based Requirements Engineering IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER, 1998 A. G. Sutcliffe, N. A. M.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Design Jon Walker. More UML ● What is UML again?
CS251 – Software Engineering Lecture 9: Software Design Slides by Mohammad El-Ramly, PhD
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
1 Database Systems Instructor: Nasir Minhas Assistant Professor UIIT PMAS-AAUR
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
1 OO Analysis & Design - Introduction to main ideas in OO Analysis & design - Practical experience in applying ideas.
Systems Analysis and Design in a Changing World, Fourth Edition
Lesson 13 Databases Unit 2—Using the Computer. Computer Concepts BASICS - 22 Objectives Define the purpose and function of database software. Identify.
Chapter 5 System Modeling (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
1 Here are some quotations to get an overview of the kinds of issues of interest.
Yu, et al.’s “A Model-Driven Development Framework for Enterprise Web Services” In proceedings of the 10 th IEEE Intl Enterprise Distributed Object Computing.
Tools for Navigating and Analysis of Provenance Information Vikas Deora, Arnaud Contes and Omer Rana.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
SE Seminar – IS Department Mazor Maya & Yuval Efrat December 2010 Griss, M.L.; Favaro, J.; d'Alessandro, M.;
Software Engineering: Models David Millard
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
Page 1 An Overview of The COTS-Aware Requirements Engineering and Software Architecting Project (CARE/SA) The University of Texas at Dallas Department.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Chapter 5 – System Modeling
Component and Deployment Diagrams
Chapter 5 – System Modeling
Overview of MDM Site Hub
Chapter 12 Information Systems.
Software Documentation
Business Decision Modeling
Object Oriented Analysis and Design
CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS
Analysis models and design models
CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS
PPT1: Basics of software engineering
Chapter 1: The Database Environment
The Database Environment
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Chapter 22 Object-Oriented Systems Analysis and Design and UML
EHR System Function and Information Model (EHR-S FIM) Release 2
UML Design for an Automated Registration System
Presentation transcript:

Method Engineering Floris Brouwer ( )

Rule-Based Maintenance of Post- Requirements Traceability Relations P. Mäder, O. Gotel, I. Philippow (2008) Approach to maintain traceability relations in the face of evolutionary change.

Contents Authors Method overview Example Related Literature Process-Deliverable Diagram

Authors P. Mäder Specialization in software engineering and development of embedded systems. O. Gotel System requirements engineering. Ph.D on the topic of traceability. I. Philippow Working on tool supported software reuse and traceability concepts for the last decade.

Method Overview (1/2) Method for automatically updating of traceability relationships in UML models. Rule-based Executed by a system Consists of 3 main steps: 1.Capturing change events 2.Recognizing development activities 3.Maintaining traceability relations

Method overview (2/2) Capturing change events There are 4 elementary change events ADD (adding a new element), DEL (deleting an element) preMOD (property of an element before modification), postMOD (property after modification) Recognizing development activities Change event is put in a cache (the EventCache). The change event consists of several events that describe the change, these events are stored in a rulebase (OpenRules). According to a set of predefined rules (the RuleCatalog) a trigger event is matched to the change event. Maintaining traceability relations

Example Description: A PC configurator (system) is edited to give the capability to select a type of graphics card for a PC build. The old situation was just a yes/no situation.

Related Literature Origin of the paper Customization of traceability links in UP Mäder, P., Philippow, I., & Riebisch, M. (2007). Customizing traceability links for the unified process. Software Architectures, Components, and Applications, Subsequent research More elaborated paper on the proposed prototype from the paper (traceMaintainer) Mäder, P., Gotel, O., Kuschke, T., & Philippow, I. (2008). traceMaintainer-Automated Traceability Maintenance. International Requirements Engineering, RE'08. 16th IEEE, Architectural overview from the same prototype. Mäder, P., Gotel, O., & Philippow, I. (2009). Semi-automated traceability maintenance: An architectural overview of traceMAINTAINER. Software Engineering-Companion Volume, ICSE-Companion st International Conference on,

Process-Deliverable Diagram

Questions?