="moz-txt-citetags">> 1. Author's names, affiliations, urls, and emails. > (if there's one designated "contact person", indicate which) Alexander Egyed Teknowledge Corporation http://sunset.usc.edu/~aegyed/ aegyed@acm.org Martin Glinz University of Zurich http://www.ifi.unizh.ch/~glinz/ glinz@ifi.unizh.ch Ingolf Kru"ger University of California, San Diego http://www-cse.ucsd.edu/users/ikrueger/ ikrueger@cs.ucsd.edu Tarja Systa", Tampere University of Technology, www.cs.tut.fi/~tsysta/ tsysta@cs.tut.fi Sebastian Uchitel <------------------------------Contact person Imperial College, http://www.doc.ic.ac.uk/~su2/ s.uchitel@doc.ic.ac.uk Albert Zu"ndorf University of Kassel, http://www.cs.tu-bs.de/ips/zuendorf/ albert.zuendorf@uni-kassel.de > 2. Title of tutorial/workshop 2nd International Workshop on Scenarios and State Machines: Models, Algorithms, and Tools > 3. Brief abstract (300-400 words) Behavior modeling plays an important role in the engineering of software-based systems; it is the basis for systematic approaches to requirements capture, specification, design, simulation, code generation, testing, and verification. A range of notations, techniques and tools supporting behavior modeling for these development tasks exists. Two complementary approaches for modeling behavior have proven useful in practice: state- and scenario-based modeling. UML statecharts have become popular as a description technique for the intended behavior of class instances in object-oriented systems. State-based formalisms are also widely used for modeling distributed and real-time systems, in particular because the corresponding models can be rigorously analyzed using model checking. Practitioners also use scenario-based notations and tools extensively; here, the focus of concern shifts from the complete behavior specification for individual components or objects to the (partial) specification of component collaboration. Use cases, interaction and sequence diagrams play an important role in scenario-based requirements elicitation. The International Telecommunication Union message sequence chart standard defines a cenario-notation for detailed specification of telecommunication system behavior. The use of state machines and scenarios, however, is not limited to capturing intended system behavior; reverse engineering techniques use them extensively to capture the behavior of existing sub-systems. Although there has been much research on both scenarios and state machines the relation between them has yet to be fully understood and, more importantly, exploited. The complementary nature of scenarios and state-machines suggests several avenues for combining the strengths of both modeling approaches. Scenarios can, for instance, be viewed as partial descriptions that are generalized through state machine specifications. Alternatively, scenarios can be thought to provide collaboration views while state machines stress local/component views. Finally, scenarios can be seen as use case realizations that aid in recognizing the operations and associations of classes and in specifying the behavior of objects as state machines. Scenarios can also be viewed as the source of test-cases, used to validate an implementation. This second workshop on scenarios and state machines has been motivated by the very successful first workshop on this topic at ICSE'02. Exploring the relation between scenarios and state machines can lead to new areas of research and to tools that can exploit the best of both worlds. Areas of interest include, but are not limited to: 1) Models and notations (requirements for different application areas, shortcomings in current notations, new suggestions for models or notations, categorizations) 2) Algorithms (e.g., synthesis, verification, simulations) 3) Tools (tool support for the issues above, different application areas) > 4. Brief author bios (100-200 words per author) Note: I am only including bios of "main organisers" rather than authors. If you need bios of all authors please use bios that appear in original proposal. Tarja Systa" is a professor at the Tampere University of Technology. She received her PhD from the University of Tampere, 2000. She was a co-organizer of the OOPSLA 2000 workshop on scenario-based round-trip engineering and of the predecessor of this workshop at ICSE^O`02. She is a co-organizer of a Dagstuhl seminar on scenarios: models, transformations and tools, to be held in September 2003. Her research interests include behavioral modeling, object-oriented software development, program understanding and visualization, reverse engineering, and software architectures. Sebastian Uchitel is a research associate at Imperial College, U.K., where he is in the process of completing his PhD. His previous computer science degrees are from the University of Buenos Aires, Argentina. He has been involved in the organization of several workshops, and in particular was a co-organizer of the predecessor of this workshop at ICSE'02. He is currently a committee member of the Requirements Engineering Specialist Group of the British Computer Society. His research interests include requirement engineering, design methods, analysis techniques, and behavior modeling, particularly as applied to the engineering of concurrent and distributed software-based systems. He is a member of the IEEE Computer Society and ACM. Dr. Albert Zu"ndorf is currently moving to a position as an associate professor in Computer Science at University of Kassel, Germany. He has a strong background in case tool construction and software design and software engineering and re-engineering. Dr. Zundorf is leader of the FUJABA (From Uml to Java And Back Again) CASE tool project that aims to provide tool support for round-trip engineering with structural and behavioral design diagrams (www.fujaba.de). In a number of tutorials on ICSE, FSE, and UML, Dr. Zundorf has proposed a new UML based rigorous object oriented software development process called Story Driven Modeling. Story Driven Modeling aims to provide technical guidance for turning textual requirements into UML scenario diagrams and for turning such UML scenario diagrams into operational behavior specifications and for turning such behavior specifications into an implementation (and back again). > 5. (optional but desirable) electronic photo of each author > 6. (optional) url to web pages maintained by authors, to > which we can point people for more information http://www.doc.ic.ac.uk/~su2/SCESM/ >Please provide your material to me by FRIDAY, DECEMBER 6, 2002, so that we can >have the web site up and running very soon. > >Thanking you for your cooperation, > >Stefan > >-- >Prof. Dr. Stefan Leue >Institute for Computer Science >Albert-Ludwigs-University Freiburg >Georges-Ko"hler-Allee Geb. 051 >D-79110 Freiburg, Germany >Office: Building 051, Room 02-007 > >Phone: +49 761 203 8181, ~8180 (secretary) Fax: +49 761 203 8182 >Home: +49 7661 98 90 92 >Email: leue@uni-freiburg.de >WWW: http://tele.informatik.uni-freiburg.de/leue >Mobile: S_t_e_f_a_n_._L_e_u_e_@_t_-_d_1_-_s_m_s_._d_e (SMS message) > >