🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

1 total messages Started by Melissa A. Kacik Fri, 15 Oct 1999 00:00
First Software Product Line Conference (SPLC1)
#19
Author: Melissa A. Kacik
Date: Fri, 15 Oct 1999 00:00
185 lines
10688 bytes
This is a multi-part message in MIME format.
--------------5AA1844428786BFBDF97A105
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

 
--------------5AA1844428786BFBDF97A105
Content-Type: text/plain; charset=us-ascii;
 name="SPLC.cfp.FULL.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="SPLC.cfp.FULL.txt"

First Software Product Line Conference (SPLC1)
August 28-31, 2000
Denver, Colorado

Call for Participation
http://www.sei.cmu.edu/plp/conf/SPLC.html

Software product lines are emerging as a new and critical paradigm for software development that is achieving impressive time-to-market gains and cost reductions. With the increasing number of product lines and product-line researchers and practitioners, the Software Engineering Institute is proud to announce its sponsorship of the First Software Product Line Conference (SPLC1).

You are personally invited to contribute to SPLC1 by submitting archival-quality technical papers, topical panels, tutorials, and/or workshops. We are very excited about SPLC1 and intend for it to be the first of many conferences that will provide the unique opportunity to exchange ideas and experiences related to software product lines and to broaden the community interest in product-line technology.


Linda M. Northrop
Software Engineering Institute 
SPLC1 Chair

Paul Clements 
Software Engineering Institute 
SPLC1 Program Co-Chair

Alexander Ran
Nokia
SPLC1 Program Co-Chair


IMPORTANT DATES
---------------
28-31 August 2000  Conference
31 March 2000	 Final camera-ready papers due to Proceedings Chair
15 February 2000   Paper authors and Panels notified of acceptance
15 January 2000	 Workshop and tutorial propsosers notified of acceptance
15 December 1999   All papers and panel, tutorial, and workshop proposals due


PROGRAM COMMITTEE
-----------------
* Sergio Bandinelli, European Software Institute
* Len Bass, Software Engineering Institute 
* Don Batory, University of Texas at Austin
* Jan Bosch, University of Karlskrona/Ronneby 
* Grady Campbell, Prosperity Heights Software
* TW Cook, MCC
* Mike Grier, Raytheon
* Emil Jandourek, Hewlett-Packard
* Mehdi Jazayeri, University of Vienna
* Jean Jourdan, Thomson-CSF
* Philippe Kruchten, Rational Software Canada
* Robert Nord, Siemens, USA
* Henk Obbink, Philips
* David Sharp, Boeing
* Karma Sherif, Temple University
* Theo von Bomhard, Robert Bosch Corporation
* Dave Weiss, Lucent Bell Labs


SEND
----
Research and Experience Paper submissions to:	clements@sei.cmu.edu
Panel proposals to:				clements@sei.cmu.edu
Tutorial proposals to: 				gjc@sei.cmu.edu
Workshop proposals to: 				fb@sei.cmu.edu

For general information contact Linda Northrop at lmn@sei.cmu.edu.


TECHNICAL PAPERS
----------------
Papers on all aspects of software Product lines describing research results, research in progress, case studies, and experience reports are being solicited for the conference. In particular, submissions from industry that present or analyze experiences in the development and fielding of software product lines for complex systems, and that expose problems in the design, development, or evolution of software product lines are highly encouraged.

Specific topics of interest include:

Enabling technologies for product lines
* system and software architectures 
* domain analysis and engineering 
* product-line scoping 
* tool support 
* mining and re-engineering 
* requirements engineering and management 
* performance engineering 
* variation points specification 

Business issues for product lines
* metrics and measures for improvement 
* costs and benefits 
* economic models 
* lowering the up-front investment 
* buying/building/mining/outsourcing assets 

Organizational issues for product lines
* organizational structure 
* training and skills development 
* personnel issues 
* role of management 
* institutionalizing product-line approach 
* process models 
* roles and responsibilities 
* risk management 

Product line life cycle issues 
* creating versus evolving 
* retiring a product line 
* technology refreshment and insertion 


There are two categories of submissions: research papers (describes work in progress) and experience papers (summarizes the results of past work). Each must describe original work that has not been previously published and must not exceed 7500 words.


PAPER SUBMISSION GUIDELINES
----------------------------
Submissions should be created and saved in Microsoft Word 97 and sent either via email as an attachment (preferred) to clements@sei.cmu.edu or by mail on a 3.5-inch diskette to:

Paul Clements, Program Chair
Carnegie Mellon
Software Engineering Institute
Pittsburgh, Pennsylvania 15213-3890

All submissions should include the following information (in plain ASCII format) in the body of the email message or on a printed page accompanying the diskette:
* Submission category (research paper or experience paper)
* Title of Paper
* Names and affiliations of all authors
* Primary contact information: name, address, phone number, fax number, and email address.

Selected research papers and experience papers will be published in conference proceedings.  Information about the format of the final submissions selected for inclusion in the proceedings will be made available on the conference web site.


PANELS
------
The program will include one or more panel sessions where participants are encouraged to share their views on a specific topic or debate both sides of a stated resolution. The goal of a panel is to stimulate thought on related topics and encourage lively and engaging discussion among the participants of the conference. 

Panel proposals must not exceed 100 words and should be emailed in plain text ASCII format to clements@sei.smu.edu. 

Each panel proposal should contain:
* A precise statement of the topic to be discussed or debated.
* The names of up to seven panelists (for those participation who you are willing to be responsible).
* A short statement about each panelist's qualifications to discuss/debate the proposed topic.
* The steps the panel will take to actively engage the audience.


TUTORIALS
---------
Tutorials provide a valuable opportunity for the conference participants to expand their product line knowledge and skills. Tutorials can focus on introductory product line topics, such as how to introduce a product line approach into an organization, or on more advanced applied topics such as industrial product line engineering practices. 

Tutorials will be held on Monday and Tuesday of the conference week, and will be presented in half-day or full-day sessions. 

A tutorial proposal consists of two to three pages describing the topic, the plan for conducting the tutorial, and the presenters' background. 

* The Topic section should include the title, the goals, and the intended audience for the tutorial. The topic should be described in detail, stressing its importance and timeliness. 

* The Plan section should include the length of the proposed tutorial (half or full day), a preliminary schedule of events including estimated times, a breakdown of the subtopics within the general topic (i.e. a detailed description of what the tutorial will cover), a justification of the tutorial for a product line audience, and an explanation of how the tutorial will be conducted, including sample materials to be included in the tutorial notes 

* The Presenters' Background section should include relevant biographical information, a summary of the presenter's technical and presentation experience, and past experience with tutorials. Sample Tutorial Proposals are available on the SPLC website http://www.sei.cmu.edu/plp/conf/SPLC.html. 

Submit tutorial proposals electronically in plain text ASCII format or as Word-97attachments to gjc@sei.cmu.edu.


WORKSHOPS
---------
Workshops provide a valuable opportunity for small communities of people with diverse perspectives to engage in rich discussions about a topic of common interest. Interaction among participants is important, so participants must have informed positions based on prior experience. 

Workshops can focus on research or applied topics. Innovative, controversial, or highly practical topics are particularly suitable for workshops. Workshop proposals in all aspects of product line development, particularly specialized in vertical domains like telecommunication, embedded systems, etc. are welcomed. Each workshop will result in a SPLC workshop report that gives the product line community an organized way of thinking about the topic and that suggests promising direction or future research. Each workshop organizer will give a summary of the workshop discussions as part of a plenary panel on Thursday, August 31. 

Workshops will be held on Monday and Tuesday of the conference week and will be one whole day. Most workshops should have 20 or fewer participants. Workshop proposals should be 2-3 pages, submitted electronically to fb@sei.cmu.edu. Sample Workshop Proposals are available as examples of each workshop submission component on the SPLC website http://www.sei.cmu.edu/plp/conf/SPLC.html.


DENVER
-------
Located in a spectacular setting near the Rocky Mountains, Denver is one of America's fastest growing cities with over 8.8 million visitors a year. In addition to its beauty, appealing weather, and warm hospitality, Denver is filled with cultural and historical sites, lively entertainment and eating establishment, and wonderful shopping opportunities.

For more information on Denver and local events check out http://www.denver.org.
Join us in the Mile High City!

--------------5AA1844428786BFBDF97A105--
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads