Article

A notation for problematic architecture interactions

Authors:

G. Jónsdóttir,

D. UnderwoodAuthors Info & Claims

ESEC/FSE-9: Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering

Pages 132 - 141

https://doi.org/10.1145/503209.503228

Published: 01 September 2001 Publication History

Abstract

The progression of component-based software engineering (CBSE) is essential to the rapid, cost-effective development of complex software systems. Given the choice of well-tested components, CBSE affords reusability and increases reliability. However, applications developed according to this practice can often suffer from difficult maintenance and control, problems that stem from improper or inadequate integrate solutions. Avoiding such unfortunate results requires knowledge of what causes the interoperability problems in the first place. The time for this assessment is during application design. In this paper, we define problematic architecture interactions using a simple notation with extendable properties. Furthermore, we delineate a multi-phase process for pre-integration analysis that relies on this notation. Through this effort, potential problematic architecture interactions can be illuminated and used to form the initial requirements of an integration architecture.

References

[1]

Abd-Allah, A. Composing Heterogeneous Software Architectures. Ph. D. Dissertation, Computer Science, University of Southern California, 1996.

Digital Library

[2]

Abowd, G., Allen, A., Garlan, D. Formalizing Style to Understand Descriptions of Software Architecture. ACM TOSEM (1995), 4(4): 319-64.

Digital Library

[3]

Allen, R., Garlan, D. A Formal Basis for Architectural Connection. ACM TOSEM (1997), 6(3): 213-49.

Digital Library

[4]

Barret, D., Clarke, L., Tarr, P., Wise, A. An Event- Based Software Integration Framework 95-048. Laboratory for Advances Software Engineering Research, Computer Science Dept., Univ. of Massachusetts, 1995.

Digital Library

[5]

Boehm, B., Port, D., Egyed, A., Abi-Antoun, M. The MBASE Life Cycle Architecture Milestone Package: No Architecture is an Island. In, 1st Working International Conference on Software Architecture, (1999).

Digital Library

[6]

Compare, D., Inverardi, P., Wolf, A. Uncovering Architectural Mismatch in Component Behavior. Science of Computer Programming (1999), 33: 101- 31.

Digital Library

[7]

Davis, L., Gamble, R., Payton, J. The Impact of Component Architectures on Interoperability, Journal of Systems and Software, (to appear 2002).

Digital Library

[8]

Davis, L., Payton, J., Gamble, R. How System Architectures Impede Interoperability, 2nd International Workshop On Software and Performance, (2000).

Digital Library

[9]

Davis, L., Payton, J., Gamble, R. Toward Identifying the Impact of COTS Evolution on Integrated Systems. 2nd Workshop on Successful COTS, (2000).

[10]

Gacek, C. Detecting Architectural Mismatches During Systems Composition USC/CSE-97-TR-506. Center for Software Engineering, USC, 1997.

[11]

Garlan, D. Higher-Order Connectors, Workshop on Compositional Software Architectures, (1998).

[12]

Garlan, D., Allen, A., Ockerbloom, J. Architectural Mismatch, or Why it is hard to build systems out of existing parts, In ICSE-95 (Seattle, WA, 1995).

Digital Library

[13]

Garlan, D., Monroe, R., Wile, D. ACME: An Architectural Description Language. In CASCON (1997).

Digital Library

[14]

Inverardi, P., Wolf, A., Yankelevich, D. Static Checking of System Behaviors Using Derived Component Assumptions. ACM TOSEM (2000), 9(3): 239-72.

Digital Library

[15]

Jacobson, I., Booch, G., Rumbaugh, J. Unified Process Development Model. Addison Wesley, 1999.

Digital Library

[16]

Kazman, R., Klein, M., Clements, P. ATAM: Method for Architecture Evaluation, CMU, 2000.

[17]

Kelkar, A., Gamble, R. Understanding the Architectural Characteristics behind Middleware Choices. 1 st Int'l Conf. on Information Reuse & Integration (1999).

[18]

Keshav, R., Gamble, R. Towards a Taxonomy of Architecture Integration Strategies, 3rd ISAW (1998).

Digital Library

[19]

Luckham, D., Vera, J. An Event-Based Architectural Definition Language. IEEE TSE (1995), 21(9): 717- 34.

Digital Library

[20]

Magee, J., Dulay, N., Eisenbach, S., Kramer, J. Specifying Distributed Software Architectures. 5th European Software Engineering Conference, (1995).

Digital Library

[21]

Medvidovic, N., Gamble, R., Rosenblum, D. Towards Software Multioperability: Bridging Heterogeneous Software Interoperability Platforms, 4th ISAW (Limerick, Ireland, 2000).

[22]

Medvidovic, N., Rosenblum, D., Taylor, R. A Language and Environment for Architecture-Based Software Development and Evolution. 21st ICSE (Los Angeles, CA, 1999).

Digital Library

[23]

Mehta, N., Medvidovic, N., Phadke, S. Towards a Taxonomy of Software Connectors. 22nd ICSE, (Limerick, Ireland, 2000).

Digital Library

[24]

Mularz, D. Pattern-Based Integration Architectures. In, PLoP, (1994).

[25]

Payton, J., Gamble, R., Kimsen, S., Davis, L. The Opportunity for Formal Models of Integration. 2nd Int'l Conf. on Information Reuse and Integration, (2000).

[26]

Payton, J., Keshav, R., Gamble, R. System Development Using the Integrating Component Architectures Process. 1st Workshop on Ensuring Successful COTS Development (1999), 49-51.

[27]

Perry, D., Wolf, A. Foundations for the Study of Software Architecture. ACM SIGSOFT (1992), 17(4):40-52.

Digital Library

[28]

Shaw, M., Clements, P. A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems, 1st Int'l Computer Software and Applications Conference (1997), Washington, D.C., 6-17.

Digital Library

[29]

Shaw, M., Garlan, D. Software Architecture: Perspectives on an Emerging Discipline, Englewood Cliffs, NJ, Prentice Hall, 1996.

Digital Library

[30]

Sitaraman, R. Integration of Software Systems at an Abstract Architectural Level. CS M.S. Thesis, University of Tulsa, 1997.

[31]

Stiger, P. An Assessment of Architectural Styles and Integration Components. CS M.S. Thesis, University of Tulsa, 1997.

[32]

Yakimovich, D., Bieman, J., Basili, V. Software Architecture Classification for Estimating the Cost of COTS Integration. 21st ICSE (Los Angeles, CA, 1999), 296-302.

Digital Library

[33]

Yakimovich, D., Travassos, G., Basili, V. A Classification of Software Components Incompatibilities for COTS Integration, (2000).

Cited By

Wu R(2007)Semantic mediation modelling in the service component designInternational Journal of Metadata, Semantics and Ontologies10.1504/IJMSO.2007.0176112:3(179-194)Online publication date: 1-Mar-2007
https://dl.acm.org/doi/10.1504/IJMSO.2007.017611
Hepner MGamble RKelkar MDavis LFlagg D(2006)Patterns of conflict among software componentsJournal of Systems and Software10.1016/j.jss.2005.11.21179:4(537-551)Online publication date: 1-Apr-2006
https://dl.acm.org/doi/10.1016/j.jss.2005.11.211
Hepner MGamble R(2005)Establishing Connectors as Integration ServicesProceedings of the 5th Working IEEE/IFIP Conference on Software Architecture10.1109/WICSA.2005.30(280-284)Online publication date: 6-Nov-2005
https://dl.acm.org/doi/10.1109/WICSA.2005.30
Show More Cited By

Index Terms

A notation for problematic architecture interactions
1. Software and its engineering
  1. Software notations and tools
    1. General programming languages
      1. Language features
        Modules / packages
  2. Software organization and properties
    1. Extra-functional properties
      1. Interoperability
    2. Software system structures
      1. Software architectures

Recommendations

A notation for problematic architecture interactions

The progression of component-based software engineering (CBSE) is essential to the rapid, cost-effective development of complex software systems. Given the choice of well-tested components, CBSE affords reusability and increases reliability. However, ...
Architecture-level modifiability analysis (ALMA)

Several studies have shown that 50-70% of the total lifecycle cost for a software system is spent on evolving the system. Organizations aim to reduce the cost of these adaptations, by addressing modifiability during the system's development. The ...
A Basis for Analyzing Software Architecture Analysis Methods

A software architecture is a key asset for any organization that builds complex software-intensive systems. Because of an architecture's central role as a project blueprint, organizations should analyze the architecture before committing resources to ...

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences

ESEC/FSE-9: Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering

September 2001

329 pages

ISBN:1581133901

DOI:10.1145/503209

Conference Chairs:
A. Min Tjoa
Vienna Univ. of Technology, Vienna, Austria
,
Volker Gruhn
Univ. of Dortmund, Dortmund, Germany

ACM SIGSOFT Software Engineering Notes Volume 26, Issue 5
Sept. 2001
329 pages
ISSN:0163-5948
DOI:10.1145/503271
Issue’s Table of Contents

Copyright © 2001 ACM.

Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

CEPIS: Council of European Professional Informatics Societies
VIENUT: Vienna University of Technology
SIGSOFT: ACM Special Interest Group on Software Engineering

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 September 2001

Permissions

Request permissions for this article.

Request Permissions

Check for updates

Author Tags

Qualifiers

Article

Conference

ESEC/FSE01

Sponsor:

CEPIS
VIENUT
SIGSOFT

ESEC/FSE01: European Software Engineering Conference 2001/ Foundations on Software Engineering 2001

September 10 - 14, 2001

Vienna, Austria

Acceptance Rates

ESEC/FSE-9 Paper Acceptance Rate 29 of 137 submissions, 21%;

Overall Acceptance Rate 112 of 543 submissions, 21%

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

9
Total Citations
View Citations
532
Total Downloads

Downloads (Last 12 months)3
Downloads (Last 6 weeks)0

Reflects downloads up to 16 Oct 2024

Other Metrics

View Author Metrics

Citations

Cited By

Wu R(2007)Semantic mediation modelling in the service component designInternational Journal of Metadata, Semantics and Ontologies10.1504/IJMSO.2007.0176112:3(179-194)Online publication date: 1-Mar-2007
https://dl.acm.org/doi/10.1504/IJMSO.2007.017611
Hepner MGamble RKelkar MDavis LFlagg D(2006)Patterns of conflict among software componentsJournal of Systems and Software10.1016/j.jss.2005.11.21179:4(537-551)Online publication date: 1-Apr-2006
https://dl.acm.org/doi/10.1016/j.jss.2005.11.211
Hepner MGamble R(2005)Establishing Connectors as Integration ServicesProceedings of the 5th Working IEEE/IFIP Conference on Software Architecture10.1109/WICSA.2005.30(280-284)Online publication date: 6-Nov-2005
https://dl.acm.org/doi/10.1109/WICSA.2005.30
Becker SOverhage SReussner R(2004)Classifying Software Component Interoperability Errors to Support Component AdaptionComponent-Based Software Engineering10.1007/978-3-540-24774-6_8(68-83)Online publication date: 2004
https://doi.org/10.1007/978-3-540-24774-6_8
Davis LFlagg DGamble RKaratas C(2003)Classifying Interoperability ConflictsCOTS-Based Software Systems10.1007/3-540-36465-X_6(62-71)Online publication date: 30-Jan-2003
https://doi.org/10.1007/3-540-36465-X_6
Jonsdottir GDavis LGamble R(2003)Designing Secure Integration ArchitecturesCOTS-Based Software Systems10.1007/3-540-36465-X_11(112-122)Online publication date: 30-Jan-2003
https://doi.org/10.1007/3-540-36465-X_11
Davis LGamble R(2001)Identifying Evolvability for IntegrationCOTS-Based Software Systems10.1007/3-540-45588-4_7(65-75)Online publication date: 20-Dec-2001
https://doi.org/10.1007/3-540-45588-4_7
Payton JJónsdóttir GFlagg DGamble R(2001)Merging Integration Solutions for Architecture and Security MismatchCOTS-Based Software Systems10.1007/3-540-45588-4_19(199-208)Online publication date: 20-Dec-2001
https://doi.org/10.1007/3-540-45588-4_19
Land RCrnkovic I(2018)Software systems in-house integrationInformation and Software Technology10.1016/j.infsof.2006.07.00249:5(419-444)Online publication date: 29-Dec-2018
https://dl.acm.org/doi/10.1016/j.infsof.2006.07.002

View Options

Get Access

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Media

Figures

Other

Tables

View Table of Contents