20 May - Friday
Session 2
11:00 AM

  Research Papers   Keynotes & Invited Talks
  Experience Reports   Panels
  Education & Training Reports   Research Demonstrations
  Awards & General Remarks   Meetings

Requirements and Specifications
20 May @ 11:00 AM

St. Louis Ballroom D [Floor Plan]
Session Chair: Anthony Finkelstein

> Goal Centric Traceability for Managing Non-Functional Requirements
Jane Cleland-Huang, Raffaella Settimi, Oussama BenKhadra, Eugenia Berezhanskaya, and Selvia Christina
> Real-time Specification Patterns
Sascha Konrad and Betty Cheng
> Monitoring and Control in Scenario-Based Requirements Analysis
Emmanuel Letier, Jeff Kramer, Jeff Magee, and Sebastian Uchitel


Empirical Evaluation of Testing
20 May @ 11:00 AM

St. Louis Ballroom E [Floor Plan]
Session Chair: S. C. Cheung

> One Evaluation of Model-Based Testing and its Automation
Alexander Pretschner, Wolfgang Prenninger, Stefan Wagner, Christian Kuehnel, Martin Baumgartner, and Bernd Sostawa
> Is Mutation an Appropriate Tool for Testing Experiments?
James Andrews, Lionel Briand, and Yvan Labiche
> An Empirical Evaluation of Test Case Filtering Techniques Based On Exercising Complex Information Flows
David Leon, Wes Masri, and Andy Podgurski


Challenges & Future Directions
20 May @ 11:00 AM

St. Louis Ballroom C [Floor Plan]
Session Chair: Paola Inverardi and Mehdi Jazayeri

> The Making of a Software Engineer: Challenges for the Educator
Clemens Szyperski
> The Challenges of Software Engineering Education
Carlo Ghezzi and Dino Mandrioli
> Information Systems Development at the Virtual Global University: An Experience Report
Victor Pankratius and Wolffried Stucky
> A B.S. Degree in Informatics: Contextualizing Software Engineering Education
Andre van der Hoek, David Kay, and Debra Richardson
> Software Engineering Education in the Era of Outsourcing, Distributed Development, and Open Source Software: Challenges and Opportunities
Matthew Hawthorne and Dewayne Perry
> The Role of a Project-Based Capstone Course
Yael Dubinsky and Orit Hazzan
> Teaching Human Aspects of Software Engineering
Orit Hazzan and Jim Tomayko
> On the Education of Future Software Engineers
Paolo Ciancarini

St. Louis Ballroom C [Floor Plan]

Jon Siegel (OMG)
Why Use the Model Driven Architecture to Design and Build Distributed Applications?
20 May @ 11:00 AM

St. Louis Ballroom A & B [Floor Plan]
Session Chair: Wolfgang Emmerich

Biography: Dr. Jon Siegel, OMG's Vice President of Technology Transfer, heads OMG's technology transfer program with the goal of teaching the technical aspects and benefits of the Model Driven Architecture (MDA) based on OMG's industry-standard Unified Modeling Language (UML) and its foundation standards: the MetaObject Facility (MOF), XML Metadata Interchange (XMI), and the Common Warehouse Metamodel (CWM).

Siegel's scope also includes OMG's industry-standard middleware, the Common Object Request Broker Architecture (CORBA), and the Object Management Architecture (OMA) comprised of the CORBAservices, the CORBAfacilities, and the Domain specifications in vertical markets ranging from life sciences and telecommunications to manufacturing and financial systems. In this capacity, he presents tutorials, seminars, and company briefings around the world, and writes magazine articles, web pages, and books including the popular "CORBA 3 Fundamentals and Programming" and "Quick CORBA 3". With OMG since 1993, Siegel previously chaired the Domain Technology Committee responsible for OMG specifications in the vertical domains.

Dr. Siegel moved to OMG after twelve years with Shell Development Company, the research arm of Shell Oil, where his last position was in the Computer Science Research Department. Siegel's background includes extensive experience in distributed computing, object-oriented software development, and geophysical computing, as well as theoretical and computational work done at Argonne National Laboratory. While at Shell, he served as that company's representative to OMG, playing an active role in several OMG subgroups, chairing the Life Cycle Services Evaluation working group and the End User SIG, and serving on the Object Services Task Force. He holds a doctoral degree in Theoretical Physical Chemistry from Boston University.

Abstract: OMG's Model Driven Architecture® (MDA®) defines an application fundamentally in terms of its business functionality and behavior instead of its technology, and supports a sound IT architecture that lowers the barriers to enterprise integration. Software development in the MDA starts with a technology-independent model of an application, built in the Unified Modeling Language (UML). This model remains stable as technology evolves, extending and thereby maximizing software ROI. MDA development tools, already available from vendors, convert the technology-independent model to a working implementation on virtually any middleware platform: Web Services, XML/SOAP, EJB, C#/.Net, OMG's own CORBA, or others. Portability and interoperability are built into the architecture. OMG's industry-standard modeling specifications support the MDA: UML, now at Version 2.0; the MetaObject Facility (MOF); the Common Warehouse Metamodel (CWM); and XML Metadata Interchange (XMI). Version 2.0 of UML enhances Component, Architectural, Behavioral, and Business Modeling, and integrates representation of structure and behavior. OMG Task Forces organized around industries including Telecommunications, Finance, Manufacturing, Biotechnology, and others use the MDA to standardize facilities in their domains.

Michael Hirsch (Zühlke Engineering)
Moving from a Plan Driven Culture to Agile Development
20 May @ 11:00 AM

St. Louis Ballroom A & B [Floor Plan]
Session Chair: Wolfgang Emmerich

Biography: Michael Hirsch is partner and software engineering consultant with Zuehlke Engineering AG in Zurich, Switzerland. He has been active in software development for more than 20 years in various roles, including project manager, software architect and software developer. His current interests are agile development methods, software architectures, and open source software. He holds a degree in Electrical Engineering from HTL Bregenz in Austria and a degree in Software Engineering from HTL Bern in Switzerland.
Abstract: Plan driven cultures are characterized by a strong belief in the plannability and predictability of software development projects. The SEI-CMM, software process improvement initiatives, and software metrics programs are some of the hallmarks of this school of thought. The more recent trend towards agile development places the emphasis on constantly adapting to a project's changing goals rather than on detailed upfront planning. The majority of reports from pracitioners of agile development are positive and confirm the advantages of this approach. However, moving from a plan driven culture to agile development is not easy. Making the transition requires changes to many established practices and may even touch core values held by stakeholders. Areas affected are requirements and change management, user involvement, willingness to take on responsibility, contract management, and the ability to live with many uncertainties. This talk looks at what it takes to make the transition and presents lessons learned from organizations and projects which have successfully completed the switch to agile development.