Browse thread
RE: CFP 2007 Third International Predictor Models in Software Engineering (PROMISE) Workshop
- Gary D. Boetticher
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | 2006-12-14 (01:12) |
| From: | Gary D. Boetticher <gboetticher@h...> |
| Subject: | RE: CFP 2007 Third International Predictor Models in Software Engineering (PROMISE) Workshop |
<BASE href="https://webmail.uhcl.edu/exchange/boetticher/Inbox/PROMISE.EML/" /> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="MSHTML 6.00.2900.2995" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face="Courier New" size=2>Hi ,</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New" size=2>I would like to invite you to consider submitting a paper to the 2007 PROMISE workshop which will be held in conjunction with ICSE. <BR><BR> The CFP is given below. </FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New" size=2>Thanks!</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New" size=2>Gary</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"></FONT> </DIV><FONT face=Arial size=2> <DIV><BR><FONT face="Courier New">Call For Papers (CFP) (ICSE related workshop): Third International Workshop - <BR>PredictOr Models In Software Engineering (PROMISE)</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">Third International Workshop on Predictor Models in Software Engineering<BR> (PROMISE 2007)<BR> </FONT><A href="http://promisedata.org/2007/CFP.html" target=_blank><FONT face="Courier New">http://promisedata.org/2007/CFP.html</FONT></A><BR><FONT face="Courier New"> Sunday May 20, 2007<BR> Minneapolis, Minnesota USA</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> In conjunction with 29th Int. Conf. on Software Engineering<BR> </FONT><A href="http://web4.cs.ucl.ac.uk/icse07/" target=_blank><FONT face="Courier New">http://web4.cs.ucl.ac.uk/icse07/</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Objectives<BR>----------</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">As in any engineering field, realistic prior assessment<BR>of the potential cost, problems, timing, performance,<BR>safety, security, and numerous other properties of software<BR>projects is essential for effective and efficient planning,<BR>design, and implementation of those projects.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">A mature engineering discipline needs to have a standard<BR>set of predictive methods that practitioners can use, as<BR>well as standards for interpreting the results of those<BR>methods. To become widely accepted and used in the field,<BR>models need to be validated on data from a wide range<BR>of applications, in different development environments,<BR>and with different reliability and performance goals.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">The PROMISE workshop aims to broaden knowledge of<BR>predictive models that have been successfully developed,<BR>to provide a forum for the discussion of new models,<BR>to provide a catalog of system data that researchers can<BR>use to evaluate proposed models so that practitioners can<BR>use these models to compare predicted results to their<BR>own projects.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">As a follow-up to last year's workshop, this workshop<BR>focuses upon "issues and challenges surrounding building<BR>predictive software models." Predictor models already exist<BR> for software development effort and fault injections as<BR>well as co-update or change predictors, software quality<BR>estimators and software escalation ("escalation" predictors<BR>try to guess what bug reports will require the attention of<BR>the senior experts). However, in most cases they have been<BR>presented in venues that cover a diverse set of interests.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">Goals of the Workshop<BR>---------------------<BR>The goals of this one-day workshop are:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* To expand the current public repository of data sets<BR> related to software engineering in order to conduct repeatable, <BR> refutable or improvable experiments. Such an empirical<BR> process is essential to the maturity of the field of<BR> predictive software models and software engineering<BR> in general. After only two years, the current PROMISE<BR> repository already contains 24 data sets.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* To deliver to the software engineering community useful<BR> and usable and verified models or methods:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> o "Models" predict software properties of interest to<BR> 21st century software practitioners. Numerous such <BR> models are already under development, including models <BR> that predict software quality, development effort, <BR> requirements/design/code<BR> traceability etc.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> o "Methods" are learning systems for building particular<BR> models for particular situations.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* To compile a list of open research questions that are<BR> deemed essential by the researchers in the field.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* To show, by example, to the next generation of software<BR> engineering researchers that empiricism is useful, <BR> practical, exciting, and insightful.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* To bring together researchers and practitioners with<BR> the aim of sharing experience and expertise.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* To steer discussion and debate on various aspects and<BR> issues related to building predictive software models.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">Public Data Policy<BR>------------------</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">PROMISE 2007 gives the highest priority to case studies,<BR>experience reports, and presented results that are based<BR>on publically available datasets. To increase the chance<BR>of acceptance, authors are urged to submit papers that<BR>use such datasets. Data can come from anywhere including<BR>the workshop Web site. Such papers should include the URL<BR>address of the dataset(s) used.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">A copy of the public datasets used in the accepted papers<BR>will be posted on "The PROMISE Software Engineering<BR>Repository. " Therefore, if applicable, the authors should<BR>obtain the necessary permission to donate the data prior<BR>to submitting their paper. All donors will be acknowledged<BR>on the PROMISE repository Web site.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">The use of publicly available datasets will facilitate<BR>generation of repeatable, verifiable, refutable, and<BR>improvable results, as well as providing an opportunity<BR>for researchers to test and develop their hypothesis,<BR>algorithms, and ideas on a diverse set of software<BR>systems. Examples of such datasets can be found at</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> </FONT><A href="/exchweb/bin/redir.asp?URL=http://promisedata.org/repository" target=_blank> <FONT face="Courier New">http://promisedata.org/repository</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">We ask all researchers in the field to assist us with<BR>expanding the PROMISE repository by donating their data<BR>sets. For inquiries regarding data donation please send<BR>an email to </FONT><A href="mailto:mail@promisedata.org" target=_blank><FONT face="Courier New">mail@promisedata.org</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">Topics of Interest<BR>------------------<BR>In line with the above mentioned goals, the main topics<BR>of interest include:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Applications of predictive models to software <BR> engineering data.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* What predictive models can be learned from <BR> software engineering data?</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Strengths and limitations of predictive models.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Empirical Model Evaluation Techniques. <BR> o What are best baseline models for different classes of<BR> predictive software models?<BR> o Are existing measures and techniques to evaluate<BR> and compare model goodness such as precision, recall, <BR> error rate, or ROC analysis adequate for evaluating software<BR> models? Or are more specific measures geared toward<BR> software engineering domain needed?<BR> o Are certain measures better suited for certain <BR> classes of models?<BR> o What are the appropriate techniques to test the <BR> generated models e.g. hold-out, cross-validation, or <BR> chronological splitting?</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Field evaluation challenges and techniques.<BR> o What are the best practices in evaluating the generated <BR> software models in the real world?<BR> o What are the obstacles in the way of field testing a <BR> model in the real world?<BR> o How to overcome obstacles in the acceptance of <BR> predictive models in the real world?</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* How to test the generated models? </FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* What are the obstacles in the way of field testing <BR> a model in the real world?<BR> o What predictive models are more prone to <BR> model shift? (Concept drift).<BR> o When does a model need to be replaced?<BR> o What are the best approaches to keeping the model <BR> in sync with software changes? </FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Building models using machine learning, statistical <BR> methods, and other methods.<BR> o How do these techniques lend themselves to building <BR> predictive software models?<BR> o Are some methods better suited for certain <BR> classes of models?<BR> o How do these algorithms scale up when handling <BR> very large amounts of data?<BR> o What are the challenges posed by the nature of data<BR> stored in software<BR> repositories that make certain techniques less<BR> effective than the others?</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Cost benefit analysis of predictive models<BR> o Is cost-benefit analysis a necessary step in evaluating<BR> all predictive models?<BR> o What are the requirements for one to be able to perform<BR> a cost benefit analysis?<BR> o What particular costs and benefits should be considered<BR> for these models?</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Case studies on building predictive software models.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">Benchmark Dataset Papers<BR>------------------------</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">To encourage data sharing and/or publicize new and<BR>challenging research direction, a special category of<BR>papers will be considered for inclusion in the workshop.<BR>Papers submitted under this category should at least<BR>include the following information:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* The public URL to a new dataset<BR>* Background notes on the domain<BR>* What problem does the data represent?<BR>* What would be gained if the problem was solved?</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Proposes a measure of goodness to be used to judge the<BR> results; for instance a good defect detector has a <BR> high probability of detection and a low probability <BR> of false alarm.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* A review of current work in the field (e.g. what is <BR> wrong with current solutions or why has no one solved <BR> this problem before?)</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Description of data format.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> Recommended format is Attribute-Relation File Format (ARFF)</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> </FONT><A href="/exchweb/bin/redir.asp?URL=http://www.cs.waikato.ac.nz/~ml/weka/arff.html" target=_blank><FONT face="Courier New">http://www.cs.waikato.ac.nz/~ml/weka/arff.html</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> For an example of such a dataset see </FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> "Cocomo NASA/Software cost estimation"</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> on the "PROMISE Software Engineering Repository"</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> </FONT><A href="/exchweb/bin/redir.asp?URL=http://promisedata.org/repository" target=_blank> <FONT face="Courier New">http://promisedata.org/repository</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> However, if ARFF is not an appropriate format for<BR> your data, please provide a detailed description of<BR> your data format in the paper. A guideline from UCI<BR> Machine Learning repository for documenting datasets<BR> can be found in</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> </FONT><A href="ftp://ftp.ics.uci.edu/pub/machine-learning-databases/DOC-REQUIREMENTS" target=_blank><FONT face="Courier New">ftp://ftp.ics.uci.edu/pub/machine-learning-databases/DOC- REQUIREMENTS</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> This information is placed before the actual data<BR> when using ARFF format. However, if you are using an<BR> alternative format that does not support comments in<BR> the dataset, provide this information in a separate file<BR> with extension .desc, and submit the URL of this file.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Preferably some baseline results</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">Submission Process<BR>------------------</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Submissions are five to ten pages long (max). Papers must<BR>be original and previously unpublished. SUBMISSIONS WHICH<BR>INCLUDE EMPIRICAL RESULTS BASED ON PUBLICLY ACCESSIBLE<BR>DATASETS WILL BE GIVEN THE HIGHEST PRIORITY.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Accepted papers and other materials for the Proceedings<BR>must be revised to conform to IEEE style guidelines<BR>defined at:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><A href="/exchweb/bin/redir.asp? URL=http://www.computer.org/portal/site/ieeecs/menuitem.c5efb9b8ade9096b8a9ca0108b cd45f3/index.jsp?%26pName=ieeecs_level1%26path=ieeecs/publications/cps% 26file=cps_format1.xml%26xsl=generic.xsl" target=_blank><FONT face="Courier New"> http://www.computer.org/portal/site/ieeecs/menuitem.c5efb9b8ade9096b8a9ca0108bcd45 f3/index.jsp?&pName=ieeecs_level1 &path=ieeecs/publications/cps&file=cps_format1.xml&xsl=generic.xsl </FONT></A><FONT face="Courier New">&</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Templates for submissions are found at:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">* Latex: </FONT><A href="/exchweb/bin/redir.asp?URL=http://promisedata.org/2007/style/latex/" target=_blank><FONT face="Courier New">http://promisedata.org/2007/style/latex/</FONT></A><BR><FONT face="Courier New">* Word: </FONT><A href="/exchweb/bin/redir.asp?URL=http://promisedata.org/2007/style/word/" target=_blank><FONT face="Courier New">http://promisedata.org/2007/style/word/</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Accepted file formats are Postscript and PDF. The details<BR>of paper and data submission process are available at:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><A href="/exchweb/bin/redir.asp?URL=http://promisedata.org/2007/CFP.html" target=_blank><FONT face="Courier New">http://promisedata.org/2007/CFP.html</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">To submit papers: </FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New"> * Email them to: </FONT><A href="mailto:2007@promisedata.org" target=_blank><FONT face="Courier New">2007@promisedata.org</FONT></A><BR><FONT face="Courier New"> * Make the title of that email <BR> "[SUBMISSION]: your paper title" </FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Each paper will be reviewed by the program committee in<BR>terms of their technical content and their relevance to<BR>the scope of the workshop, as well as its ability to<BR>stimulate discussion. At least one author of accepted<BR>papers is required to register and attend the workshop.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Prior to the workshop the accepted papers will be posted<BR>on the workshop web page at:</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><A href="/exchweb/bin/redir.asp?URL=http://promisedata.org/2007" target=_blank><FONT face="Courier New">http://promisedata.org/2007</FONT></A></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">This is to facilitate a more fruitful discussion during<BR>the workshop.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Journal of Empirical Software Engineering: Special Issue<BR>--------------------------------------------------------</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Papers accepted to PROMISE 2007 (and 2006) will be<BR>eligible for submission to a special issue of the Journal<BR>of Empirical Software Engineering on repeatable experiments<BR>in software engineering.</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">The issue will be edited by Tim Menzies. </FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><BR><FONT face="Courier New">Important Dates<BR>---------------<BR>Submission of workshop papers January 20, 2007<BR>Notification of workshop papers February 10, 2007<BR>Publication ready copy March 5, 2007</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">General Chair<BR>-------------<BR>Gary Boetticher Univ. of Houston - Clear Lake</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Steering Committee<BR>------------------<BR>Gary Boetticher Univ. of Houston - Clear Lake<BR>Tim Menzies West Virginia University, US<BR>Tom Ostrand AT&T</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV><FONT face="Courier New">Program Committee<BR>-----------------<BR>Vic Basili University of Maryland, US<BR>Dan Berry University of Waterloo, Canada, US<BR>Barry Boehm University of Southern California <BR>Gary Boetticher Univ. of Houston - Clear Lake, US<BR>Lionel Briand Carleton University, Canada<BR>Bojan Cukic West Virginia University, USA<BR>Alex Dekhtyar University of Kentucky, US<BR>Martin Feather NASA JPL, US<BR>Norman Fenton Queen Mary (U. of London), UK<BR>Jane Hayes University of Kentucky, USA<BR>Jairus Hihn NASA JPL's Deep Space Network, US<BR>Gunes Koru U. of Maryland, Balt. Cty US<BR>Tim Menzies West Virginia University, US<BR>Martin Neil Queen Mary(U. of London), UK<BR>Allen Nikora NASA JPL, US<BR>Tom Ostrand AT&T, US<BR>Daniel Port University of Hawaii, USA <BR>Julian Richardson NASA ARC, US<BR>Guenther Ruhe University of Calgary, Canada<BR>Martin Shepperd Brunel University, UK<BR>Forrest Shull Fraunhofer Centre Maryland, USA <BR>Willem Visser NASA ARC, US<BR>Elaine Weyuker AT&T, US<BR>Laurie Williams North Carolina State Univ., USA<BR>Marv Zelkowitz University of Maryland, US<BR>Du Zhang Cal. State Univ., Sacramento, USA</FONT></DIV> <DIV><FONT face="Courier New"></FONT> </DIV> <DIV></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>