St.
Louis Ballroom D [Floor
Plan]
Session Chair: George Heineman
>
Predictors
of Customer
Perceived Software Quality Audris Mockus, Ping Zhang, and Paul Li
>
Automated Support for Process-aware Definition
and Execution of Measurement Plans Luigi Lavazza and Giancarlo Barresi
>
A Quality-Driven Systematic Approach for
Architecting Distributed Software Applications Tariq Al-Naeem, Ian
Gorton, Muhammed Ali Babar, Fethi Rabhi, and Boualem Benatallah
Software Evolution
19 May @ 11:00 AM
St.
Louis Ballroom E [Floor
Plan]
Session Chair: André van
der Hoek
>
Object Naming Analysis for
Reverse-Engineered Sequence Diagrams Atanas Rountev and Harkness Connell
>
Binary Refactoring: Improving Code Behind
the Scenes Eli Tilevich and Yannis Smaragdakis
>
CATCHUP! Capturing and Replaying Refactorings
to Support API Evolution Johannes Henkel and Amer Diwan
State of the Art
& Practice
19 May @ 11:00 AM
St.
Louis Ballroom C [Floor
Plan]
Session Chair: Paola
Inverardi and Mehdi Jazayeri
>
Some Myths of Software Engineering Education Hans van Vliet
>
Software Engineering 2004: ACM/IEEE-CS
Guidelines for Undergraduate Programs in Software Engineering Joanne
M. Atlee, Richard J. LeBlanc, Jr., Timothy C. Lethbridge, A. Sobel,
and
J. Barrie Thompson
>
Towards Increasing the Compatibility of
Student Pair Programmers Neha Katira, Laurie Williams, and Jason Osborne
>
Using Peer Reviews in Teaching Framework
Development Amir Zeid and Moemen Elswidi
>
Process Issues in Course Projects
Wilson Paula Filho
>
Towards
an Effective Software Engineering Course Project Zakarya Alzamil
>
Conducting Empirical Software Engineering
Research in Nigeria: The Posing Problems Olalekan Akinola
James D. Herbsleb (Carnegie
Melon University)
Beyond Computer Science
19 May @ 11:00 AM
St.
Louis Ballroom A & B [Floor
Plan]
Session Chair: Anthony
Finkelstein
[Slides]
Biography: James
D. Herbsleb is the A. Nico Haberman Associate Professor of
Computer Science at Carnegie Mellon University. His research
interests lie primarily in the intersection of software engineering
and computer-supported cooperative work, focusing on such areas as
geographically-distributed development teams, open source software
development, and more generally on oordination in software
engineering. He holds a JD (1980), and a PhD (1984) in psychology
from the University of Nebraska, and a MS (1991) in computer science
from the University of Michigan.
After completing a post-doctoral
fellowship at the University of Michigan, he moved to Carnegie Mellons Software
Engineering Institute, where he led an effort to empirically validate the
CMM for Software. He then joined the Software Production Research Department
at Lucent Technologies, where he initiated and led the Bell Labs Collaboratory
Project, which conducted empirical studies
and designed collaborative technologies and practices for global software development.
Abstract: Computer science is necessary but not
sufficient to understand and overcome the problems we face in software
engineering. We need to understand not only the properties of the software
itself, but also the limitations and competences humans bring to the engineering
task. Rather than rely on commonsense notions, we need a deep and nuanced
view of human capabilities in order to determine how to enhance them. I
discuss what I regard as promising examples of cognitive and organizational
theories and propose research directions to develop new ways of representing
run-time behavior and ways of thinking about project coordination. I conclude
with observations on creating an interdisciplinary culture.
Stephen Fickas (University
of Oregon)
Clinical Requirements Engineering
19 May @ 11:00 AM
St.
Louis Ballroom A & B [Floor
Plan]
Session Chair: Anthony Finkelstein
[Slides]
Biography: Stephen
Fickas is a Full Professor in the Computer Science Department at the
University of Oregon. He began his interest in software engineering
while a research assistant at USC/ISI in the early 1980s.
Over the last ten years, he has focused on requirements engineering.
During that time he helped establish the RE conference series and chaired
the IFIP 2.9 Working Group on Requirements Engineering. Beyond the
work reported in this paper, Fickas has an interest in GORE (goal-oriented
RE), requirements monitoring, and the place of formal methods in the
RE process.
Abstract: In this paper,
I make a case for integration of requirements engineering (RE) with clinical
disciplines. To back my case, I look at two examples that employ a clinical
RE approach, first, that of introducing email into the life of a brain-injured
individual, and second, introducing digital darkroom tools into my life.
The former uses a Brownfield approach by starting with an existing clinical
process, cognitive rehabilitation, and then defining an RE process that
fits. The latter uses a Greenfield approach that postulates a new clinical
RE process that focuses on the problems some of us have using digital
darkroom tools.
