lee@softbase.math.uwaterloo.ca, Stefan Leue Subject: ICSE Workshop STRAW'03 Cc: roelw@cs.utwente.nl, kazman@sei.cmu.edu >Hi Dan, >We are happy to inform you that your workshop proposal >was well received and has been accepted as an ICSE 2003 >workshop. Thank you.. Oy! now the work begins.. >There are some issues that we need to discuss and some >information that we need from you: >* You proposed a closed workshop involving a small number of >attendees. To help make sure that the workshops are profitable, >we are asking all workshop organizers to open their workshops >to at least 30 attendees. With respect to your workshop, this >means that we're asking you to keep the workshop registration >open until there are at least 30 registrants. We are looking into OK.. will do.. >how to give workshop participants (or really, anyone on the >workshop organizers' invitation list) first priority for these 30 open >slots, so that these slots are not filled by those that register first. >We would probably do this up until a particular date (e.g., the >deadline for early registration). After this date, your workshop >registration would remain open to all registrants until it had 30 >attendees. After registration reached 30 attendees, registration >would be closed to only those on the organizers' invitation list, >which can vary. Let me know if this is a problem that affects >whether you are willing to put on the workshop. Not a problem.. >* Your workshop is tentatively scheduled for May 3. This avoids >a conflict with Rick's SE/HCI workshop that is scheduled for >May 9-10. Hopefully this means that Rick can participate in both >workshops. There are five other workshops planned for May 3, He can.. >so your workshop is not alone in be scheduled so far in advance >of ICSE. Also, in addition to tutorials and other events that will >fill the time between your workshop and the ICSE technical >program, there are a number of day-trip excursions that >your attendees can go on; you can read about these on the ICSE >web page: http://cs.oregonstate.edu/icse2003/ >Let me know if May 3 works for you, although there are not many >alternatives if it doesn't. 3 May is OK. However.. the three of us would prefer 4 May.. Is that possible? >* We need a 300-400 word abstract for your workshop ASAP. The >abstract that you provided as part of your proposal is only 80 words we were constrained by lengths.. and actually had something longer.. >and we're aiming for a common look and feel among the workshop >write ups. Please send abstracts in text or HTML. :-) I did mine at first in ASCII.. but it did not fit.. so I converted it to troff (still mostly ascii) to get it to fit.. So I will sent the text.. >* Could you also send us 100-150 word bios from each of the three >organizers? You can send us the same ones that you provided as part >of your proposal, but we need them in text or HTML format. >Please send these and the abstract to Stefan Leue (leue@uni-freiburg.de). >* We need the URL for your workshop website, which describes the >workshop in detail, including goals, themes, format, submission guidelines, >review process, important dates, etc. I will have to get back to you >on the deadline for when we need camera-ready submissions for >proceedings. http://se.uwaterloo.ca/~straw03 >* We will need a 2-page summary of your workshop to be included >in the ICSE conference proceedings. This needs to conform to >the ICSE 2003 paper format, which you will find on the ICSE 2003 >web page: http://cs.oregonstate.edu/icse2003/ >We ask that you send us a camera-ready copy of this paper by >January 15. OK... >SUMMARY OF ACTION ITEMS: >* ASAP: Indication that a semi-closed workshop is OK OK.. >* ASAP: Indication that date May3 works for you. It works but 4 May would be better.. >* ASAP: Abstract and bios for you and the other organizers; send these to > Stefan Leue (leue@uni-freiburg.de) sent under separate cover >* Dec 15: URL of your workshop web site http://se.uwaterloo.ca/~straw03 >* Jan. 15: 2-page camera-ready summary of workshop for ICSE proceedings >Looking forward to working with you! like wise.. >Jo and Stefan Dan Roel and Rick >From Stefan: >The requested information is as follows: > 1. Author's names, affiliations, urls, and emails. Done.. > (if there's one designated "contact person", indicate which) None.. > 2. Title of tutorial/workshop Done.. > 3. Brief abstract (300-400 words) Done.. > 4. Brief author bios (100-200 words per author) Done.. > 5. (optional but desirable) electronic photo of each author Done > 6. (optional) url to web pages maintained by authors, to > which we can point people for more information Done.. >Please provide your material to me by FRIDAY, DECEMBER 6, 2002, so that Impossible.. the first message set a deadline of 15 December.. so I put it away to do on 9 December after some deadlines during first week of December.. Dan Abstract: There is a clear relationship between requirements engineering and architecture design in software engineering. However, for the most part, the two disciplines have evolved independently from each other, and promising areas of mutual interest remain to be explored. The goal of the Second International Workshop on Software Requirements and Architectures (STRAW '03) is to bring together researchers from the requirements engineering and architecture communities to exchange views and results that are of mutual interest, and to discuss topics for further research. Description: Over the past 10 years, software requirements engineering and software architecture have been the topic of fastly growing research disciplines. Requirements engineering has seen the advent of * goal-oriented approaches, * scenario-based requirements engineering, * sociology- and linguistics-based techniques, and * formal techniques for identifying and specifying requirements. Architecture design has seen the advent of * patterns research, * architectural style research, * attribute-based architecture design, * architecture description languages, * component-based approaches, and * product-line architectures. There is a clear relationship between requirements engineering and architecture design. However, for the most part, the two disciplines have evolved independently from each other, and promising areas of mutual interest remain to be explored. For example, an important type of design research consists of relating classes of problems to classes of solutions. In software engineering, there are interesting connections between software problem patterns and software solution patterns. Recent research in problem frames could therefore be extended by including architecture patterns and investigating relationships between the two kinds of patterns. The patterns paradigm may be extended by including the wider business context, consisting of business processes, actors, and strategies. In this wider context, the problem is one of alignment of software architecture with business architecture. Here, domain knowledge may be codified using reference architectures. A third area of potential fruitful interaction is that of component-based development. Assembling components into a system requires an architecture that mediates between the system requirements and the requirements on the components. More generally, when we extend our view from a single system to a hierarchy of systems, the interplay between requirements and architectures is a central guiding principle in system design. The goal of the Second International Workshop on Software Requirements and Architectures (STRAW '03) is to bring together researchers from the requirements engineering and architecture communities to exchange views and results that are of mutual interest, and to discuss topics for further research. Topics of interest include, but are not limited to, the following list. * Deriving architecture descriptions in concert with requirements specification * Attribute-based architecture design * Tracing architectural decisions to requirements * Evolving architectures and requirements * Alignment between software architecture and business architecture * Relating architecture patterns to requirements patterns * Reference architectures * Reuse of requirements and architectures * Systems engineering approaches * Formal foundations of the requirements-architecture relationship * Requirements and architecture specification languages * Tools and environments for requirements engineers and software architects Organizers: Daniel M. Berry School of Computer Science University of Waterloo Waterloo Canada Phone: None, use fax or e-mail FAX: +1-519-746-5422 http://se.uwaterloo.ca/~dberry dberry@uwaterloo.ca Roel Wieringa Department of Computer Science University of Twente the Netherlands phone: +31 53 489 4189 fax: +31 53 489 2927 http://www.cs.utwente.nl/~roelw roelw@cs.utwente.nl Rick Kazman Software Engineering Institute Carnegie Mellon University Pittsburgh, PA USA Phone: +1-412-268-1588 Fax: +1-412-268-5758 http://www.sei.cmu.edu/staff/rkazman/ kazman@sei.cmu.edu Participants: To realize lively discussions, we aim at about 30 participants (min. 10, max. 35). The workshop will be closed. Participation will be based upon position papers that will be reviewed by a program committee. Best papers will be presented. All papers will be distributed to the participants before the workshop starts. Each paper will be assigned an opponent, who should present a brief counterpoint to the point of view of the presenter of the paper. During the day, participants can propose issues to be discussed at the end of the day. The workshop should lead to a list of issues discussed, conclusions reached, disagreements identified, and topics to be researched further. Background of Daniel M. Berry: Daniel Berry is a professor in the School of Computer Science at the University of Waterloo, Waterloo, Ontario, Canada. His research interests are software engineering in general, and requirements engineering and electronic publishing in the specific. He has supervised 21 PhDs, numerous Master students and has received a Noted Instructor Award in Computer Science at Technion. He has consulted extensively in industry. He has served as associate editor for two journals and has been a referee for numerous journals. He has participated on programming committees for many conferences and workshops. He was Program Committee Co-chair for ICRE'98. He is a member of the Steering Committee for the RE series of conferences. He has published extensively in refereed journals and contributed to many refereed conferences, symposia, and books. Background of Roel Wieringa: Roel Wieringa is Chair of Information Systems at the University of Twente, the Netherlands. His book ``Requirements Engineering: Frameworks for Understanding'' was published by Wiley in 1996, and a book ``Design Techniques for Reactive Systems'' will be published by Morgan Kaufmann in 2002 or early 2003. In 1989, he organized the first International Workshop on Deontic Logic, and in 1994, he was Tutorials Chair for CAiSE '94. He is the Exhibitions chair for RE '02 and the Program Chair for RE '03. Background of Rick Kazman Rick Kazman is a Senior Member of the Technical Staff at the Software Engineering Institute of Carnegie Mellon University and Associate Professor at the University of Hawaii. His primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. He also has interests in human-computer interaction and information retrieval. He is the author of over 70 papers, and co-author of several books, including "Software Architecture in Practice", and "Evaluating Software Architectures: Methods and Case Studies". Kazman received a B.A. and M.Math from the University of Waterloo, a M.A. from York University, and a Ph.D. from Carnegie Mellon University.