07.04.2014 Views

SPLC 2009 - SPLC.net l Software Product Line Conferences

SPLC 2009 - SPLC.net l Software Product Line Conferences

SPLC 2009 - SPLC.net l Software Product Line Conferences

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>SPLC</strong> <strong>2009</strong> | The 13th International <strong>Software</strong> <strong>Product</strong> <strong>Line</strong> Conference<br />

Inner source is a way to exploit the advantages of distributed development in the open<br />

source way but in a wish to avoid problems with planning, ownership, and control. Several<br />

companies have adopted an inner source development model. In inner source development,<br />

a set of teams collaborates in a cooperative eco-system. Similar to open source<br />

development, inner source development applies an open, concurrent, model of<br />

collaboration. It implies distributed ownership and control of code, early and frequent<br />

releasing, and many continuous feedback channels. It makes use of organization<br />

mechanisms already in place; for example, for escalation of conflicts or setting up<br />

roadmaps. Inner source enables flexibility in (starting, stopping, and changing of)<br />

collaborations and in timing and setting priorities of development teams across<br />

organizational (and geographical) boundaries.<br />

The tutorial is mainly structured along the basic dimensions of BAPO and the FEF:<br />

business, architecture, process, and organization.<br />

The tutorial starts with an overview of BAPO and the FEF. This is a rehearsal of the basic<br />

ideas presented in the tutorial T4: “Introducing and Optimizing <strong>Software</strong> <strong>Product</strong> <strong>Line</strong>s<br />

Using the FEF.” Next, the idea of inner source is presented, followed with a detailed<br />

explanation of inner source in each of the four BAPO dimensions.<br />

Presenter Biography:<br />

Frank van der Linden, PhD, works at Philips Healthcare CTO Office. He received his Ph.<br />

D. in pure Mathematics in 1984 at the University of Amsterdam. He was then employed by<br />

Philips Research and since 1999 by Philips Medical Systems. During this time, his main<br />

interest was in software product lines. He was the project leader of four relevant ITEA<br />

projects: ESAPS, CAFÉ, FAMILIES, and COSI. During these projects, he organized as<br />

program chair a series of SWAPF & PFE workshops. He then served as general chair of the<br />

<strong>SPLC</strong> 2005 and as program co-chair of the <strong>SPLC</strong> 2006.<br />

T11<br />

Building Reusable Testing Assets for a <strong>Software</strong> <strong>Product</strong> <strong>Line</strong><br />

John D. McGregor, <strong>Software</strong> Engineering Institute, USA<br />

Testing consumes a significant percentage of the resources required to produce softwareintensive<br />

products. The exact impact on the project is often hard to evaluate, because testing<br />

http://www.sei.cmu.edu/splc<strong>2009</strong>/tutorials.html (14 of 18) [11/4/<strong>2009</strong> 12:06:26 PM]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!