lab on Maintenance, Construction and Intelligence of Software


Slide 1 jFlow Plus Research is your Destiny
You never give up, and don't mind making your hands dirty. The truth is out there,
and you will find it. Honesty and ethics are not hollow terms for you. Chaos only exists
to bring back order. You keep notes of everything you do, just in case. Always think
before you do, and do before you report.Join MCIS!
Slide 2 jFlow Plus Knowledge is your Favourite Type of Food
You're a curious person by nature. Once you start reading a book, you can't put it down without
finishing it. Learning is an incremental process, every tidbit helps. Google is your best friend.Join MCIS!
Slide 3 jFlow Plus Are You a Code Ninja?
You know the essential concepts of >10 programming languages and exploit them
as needed. You think before you code. Reuse is your middle name. You use Perl
scripts for regular expressions, Prolog code for querying, Java for its huge
array of libraries, and even C++ if that's what it takes to finish a project successfully.Join MCIS!
Slide 4 jFlow Plus Teacher is your Middle Name
From kindergarten on, you've had this irresistible urge to explain things to others. Knowledge
means nothing without sharing it with others. You hate memorization. You translate complex
definitions into funny anecdotes, abstract structures into simple graphics, tables full of numbers
into smart graphs.Join MCIS!


MCIS helps practitioners maintain their software systems. For example, which files should be tested or fixed first and by who? Which bug to fix first? Did the performance of our system degrade compared to the previous release? How can we improve the energy consumption of our system? Will this change have nasty consequences on other features?
Read More


MCIS helps practitioners release their products faster, but without sacrificing quality. For example, how healthy is the build system? How are implementation changes by different development teams integrated and tested towards inclusion in the next release? How can we prepare our development process and software system for continuous delivery?
Read More


MCIS' helps practitioners understand their software systems and construction infrastructure. For example, how does the concrete architecture of this software component look like? What features and functionality has the development team been working on? Which contributors have been the most productive? How does our construction infrastructure work?
Read More

Want to know all about our research?

Check our publications page!

Over Here!

  • Build Maintenance

    Did you know that build files like makefiles, ant files and configuration files change relatively more than source code files do? And did you know that in up to 27% of the work items in which a source code file is changed, a build file needs to be updated?

    Check out our ICSE 2011 paper »

  • Release Engineering

    What is release engineering and which activities need to be performed? What are today's challenges for the build and integration phases of release engineering? How does our work fit with these challenges?

    Check out our ICSE 2012 technical briefing on release engineering »

  • Concern Mining

    Identifying crosscutting concerns is tedious. Existing tools only return a set of function names, cannot deal with noise in identifiers, and merely yield a set of words without structure. We propose to use the system's development history to address these three shortcomings.

    Check out our ICSE 2010 paper »

Latest Work

FERREIRA, I., CHENG, J. and ADAMS, B. (2021). The “Shut the f**k up” Phenomenon: Characterizing Incivility in Open Source Code Review Discussions, in Proceedings of the 24th ACM Conference on Computer-Supported Cooperative Work and Social Computing, CSCW (virtual), to appear. BibTeX

FOUNDJEM, A., EGHAN, E.E. and ADAMS, B. (2021). Onboarding vs. Diversity, Productivity and Quality -- Empirical Study of the OpenStack Ecosystem, in Proceedings of the 43rd International Conference on Software Engineering, ICSE (Madrid, Spain), to appear. (Acceptance ratio: 138/602=22.92%) BibTeX

BARRAK, A., EGHAN, E., ADAMS, B., and KHOMH, F. (2021). Why do Builds Fail? - A Conceptual Replication Study, Journal of Software and Systems (JSS), Elsevier, to appear. BibTeX

BARRAK, A., EGHAN, E.E. and ADAMS, B. (2021). On the Co-evolution of ML Pipelines and Source Code - Empirical Study of DVC Projects, in Proceedings of the 28th IEEE International Conference on Software Analysis, Evolution, and Reengineering, SANER (Hawaii, USA), to appear. (Acceptance ratio: 42/165=25%) BibTeX