 | 2006 |
| 14 |  | Leigh A. Davis,
Jamie Payton:
Discovery and Composition of Services in Dynamic Mobile Environments.
ICCBSS 2006: 5 |
| 13 |  | Michelle Hepner,
Rose F. Gamble,
Manasi Kelkar,
Leigh A. Davis,
Daniel Flagg:
Patterns of conflict among software components.
Journal of Systems and Software 79(4): 537-551 (2006) |
| 2005 |
| 12 |  | Leigh A. Davis,
Rose F. Gamble,
Michelle Hepner,
Manasi Kelkar:
Toward Formalizing Service Integration Glue Code.
IEEE SCC 2005: 165-172 |
| 2004 |
| 11 |  | Leigh A. Davis,
Rose F. Gamble:
Understanding Services for Integration Management.
ICCBSS 2004: 84-93 |
| 10 |  | Leigh A. Davis,
Rose F. Gamble,
S. Kimsen:
A patterned approach for linking knowledge-based systems to external resources.
IEEE Transactions on Systems, Man, and Cybernetics, Part B 34(1): 222-233 (2004) |
| 2003 |
| 9 |  | Gerður Jónsdóttir,
Leigh A. Davis,
Rose F. Gamble:
Designing Secure Integration Architectures.
ICCBSS 2003: 112-122 |
| 8 |  | Leigh A. Davis,
Daniel Flagg,
Rose F. Gamble,
C. Karatas:
Classifying Interoperability Conflicts.
ICCBSS 2003: 62-71 |
| 7 |  | M. Todd Gamble,
Rose F. Gamble,
Leigh A. Davis:
Defining Change Management Properties for Component Interoperability Assessment.
SEKE 2003: 475-482 |
| 2002 |
| 6 |  | Leigh A. Davis,
Rose F. Gamble:
Identifying Evolvability for Integration.
ICCBSS 2002: 65-75 |
| 5 |  | Rose F. Gamble,
Leigh A. Davis:
A Framework for Interaction in Software Development Training.
JITE 1(3): 223-232 (2002) |
| 4 |  | Leigh A. Davis,
Rose F. Gamble,
Jamie Payton:
The impact of component architectures on interoperability.
Journal of Systems and Software 61(1): 31-45 (2002) |
| 2001 |
| 3 |  | Leigh A. Davis,
Rose F. Gamble,
Jamie Payton,
Gerður Jónsdóttir,
Dennis J. Underwood:
A notation for problematic architecture interactions.
ESEC / SIGSOFT FSE 2001: 132-141 |
| 2 |  | Leigh A. Davis,
Rose F. Gamble:
Conflict Patterns: Toward Identifying Suitable Middleware.
IRI 2001: 121-126 |
| 2000 |
| 1 |  | Leigh A. Davis,
Jamie Payton,
Rose F. Gamble:
How system architectures impede interoperability.
Workshop on Software and Performance 2000: 145-146 |