From: Sarah Nadi <snadi@uwaterloo.ca>
To: ecos-discuss@sourceware.org
Subject: [ECOS] Questions about CDL dependencies in eCos
Date: Wed, 02 Jul 2014 19:37:00 -0000 [thread overview]
Message-ID: <53B45F71.2080600@uwaterloo.ca> (raw)
Hi everyone,
I am a researcher at the University of Waterloo, Ontario, Canada. As
part of a research team with members from both the University of
Waterloo and Carnegie Mellon University, USA, we are interested in
creating automated tools for large configurable software. We are
currently working on automatically reverse engineering configuration
dependencies from code such that all dependencies between configuration
features are documented (similar to those documented in CDL files). This
is useful to automatically identify dependencies that need to be
enforced in the configuration files. These tools can also help with
consistency checks between the code and the dependencies specified in
configuration files (such as CDL files). We have tested our
infrastructure on four different open-source systems, including eCos,
and can already recover many of the existing dependencies [1]. We are
now doing a qualitative investigation of dependencies from the
perspective of developers. We want to understand the sources of such
configuration dependencies as well as the general reasons why developers
enforce dependencies in practice.
To improve our tools, and to better understand the configuration
dependencies enforced, we are interested in talking to developers who
are familiar with CDL dependencies and/or who use the configuration
features during coding (e.g., through #ifdef macro). This can take place
through an online questionnaire and/or phone/Skype interviews. Either of
these would take 15 min of your time. We would discuss when you enforce
dependencies in CDL, your usage of #ifdefs in the code, as well as
concrete examples of dependencies we could not automatically recover.
If you are willing to participate, please fill in the questionnaire
found at http://bit.ly/1mjy326 and/or reply to this email to set up an
interview time.
Thanks,
Sarah Nadi
University of Waterloo, ON, Canada
snadi@uwaterloo.ca
http://cs.uwaterloo.ca/~snadi
[1] Sarah Nadi, Thorsten Berger, Christian Kästner, Krzysztof Czarnecki.
Mining Configuration Constraints: Static Analyses and Empirical Results.
In ICSE'14: Proceedings of the 36th International Conference on Software
Engineering, Hyderabad, India, 2014.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2014-07-02 19:37 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=53B45F71.2080600@uwaterloo.ca \
--to=snadi@uwaterloo.ca \
--cc=ecos-discuss@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).