categories - Category Theory list
 help / color / mirror / Atom feed
From: Reiko Heckel <reiko.heckel@gmail.com>
To: categories@mta.ca" <categories@mta.ca>
Subject: FW: Invitation: GReTA online seminar, Friday December 3, 2021, 15:00 CET
Date: Mon, 29 Nov 2021 09:26:11 +0000	[thread overview]
Message-ID: <E1msyk0-0004w9-3S@rr.mta.ca> (raw)

FYI
Reiko

On 29/11/2021, 08:52, "GReTA Seminar organisers" <greta@irif.fr> wrote:

Dear colleagues,

It is our great pleasure to invite you to the next seminar of the “GReTA - Graph Transformation Theory and Applications” series:

     Friday December 3, 15:00 CET
     "Supporting Software Variability with Graph Transformations", D. Strüber
     (abstract, Zoom and YouTube links attached below)

The GReTA seminar series aims to serve as a platform for the international graph rewriting community, to promote recent developments and trends in the  field, and to permit a regular networking and interaction between members of this community. Seminars are scheduled twice a month (cf. https://www.irif.fr/~greta/#talks for a list of upcoming events).

With best regards,

Nicolas Behr, Andrea Corradini, Jean Krivine and Reiko Heckel
(GReTA organisers)


___________________________________________________

Date and time: Friday December 3, 2021, 15:00 CET
Title: Supporting Software Variability with Graph Transformations

Speaker:

Daniel Strüber (Department of Computer Science and Engineering, Chalmers University of Technology, University of Gothenburg, Sweden)

Abstract:

Software systems and the artifacts they consist of often exist in many different variants. When creating new variants, developers typically rely on the "clone and own" strategy of copying and modifying existing variants, a simple and intuitive approach with significant long-term disadvantages. In this talk, I present a line of work on supporting variants in software engineering by explicitly addressing variability as a feature in graph transformations. I focus on three transformation scenarios: one where the input graph  has variability (representing the established notion of a software product  line), one where rules have variability (leading to variability-based rules), and a combination of the first two scenarios. Each scenario is supported with formal constructions, efficient transformation algorithms, and tool support. Our work shows that a systematic way of supporting variability in transformations can improve the maintainability and the performance of a software system.

Zoom registration link:
https://u-paris.zoom.us/meeting/register/tZ0kcOqgrjsrHt2c7v0ElvEODTQn97b3RXU8

Link to YouTube live stream:
https://youtu.be/8j0LHp7zGrE


___________________________________________________


----------------------------------------------------------------------------
GReTA - Graph TRansformation Theory and Applications
                 International Online Seminar Series
----------------------------------------------------------------------------
Contact: greta@irif.fr
Webpage: www.irif.fr/~greta<http://www.irif.fr/~greta>
YouTube: https://www.youtube.com/channel/UC6j-G6oPmkqCgOx6UQOUhSQ
Twitter: https://twitter.com/GReTAseminars


[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


                 reply	other threads:[~2021-11-29  9:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1msyk0-0004w9-3S@rr.mta.ca \
    --to=reiko.heckel@gmail.com \
    --cc=categories@mta.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).