Technical reference architectures

IBM Systems Journal

Volumn 38, Issue 1, 1999, Pages 51-75

  Lloyd, P T L ^a,b,c   Galambos, G M ^d,e  

^a IBM   (United Kingdom)

^b IBM United Kingdom Object Technology Practice   (United Kingdom)

^c ESS Operations team   (United Kingdom)

^d IBM CANADA LTD   (Canada)

^e e Business Architecture Consulting Practice   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

ADMINISTRATIVE DATA PROCESSING; COMPUTER SYSTEMS PROGRAMMING; ELECTRONIC COMMERCE;

LARGE-SCALE ENTERPRISE DEPLOYMENT;

COMPUTER ARCHITECTURE;

EID: 0032653702     PISSN: 00188670     EISSN: None     Source Type: Journal    
DOI: 10.1147/sj.381.0051     Document Type: Article

References (19)

1. A "silo" is a part of an IT solution that is not integrated with other parts. The name comes from the visualization of such a solution - the different applications stand apart from each other, like farm silos in silhouette against a prairie sky. Another name for this kind of solution is "stovepipe." A good explanation of stovepipes as an "antipattern" can be found in W. J. Brown, R. C. Molveau, H. W. McCormick, and T. J. Mowbray, Antipatterns: Refactoring Software, Architectures, and Projects in Crisis, John Wiley & Sons, Inc., New York (1998).
2. In a fat-client solution, client systems perform most of the data processing operations. The data may be stored locally or on a server.
3. R. Schulte, Architecture and Planning for Modern Application Styles, Gartner Group Strategic Analysis Report SSA: R-ARCH-104 (April 28, 1997).
4. I. Jacobson, M. Griss, and P. Jonsson, Software Reuse: Architecture, Process and Organization for Business Success, Addison-Wesley Publishing Co., Reading, MA (1997).
5. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, Addison-Wesley Publishing Co., Reading, MA (1998).
6. E. C. Plachy and P. A. Hausler, "Enterprise Solutions Structure," IBM Systems Journal 38, No. 1, 4-11 (1999, this issue).
7. B. Boehm, "Engineering Context," First International Workshop on Architecture for Software Systems, April 1995, Seattle, WA.
8. M. Shaw and D. Garlan, Software Architecture: Perspectives on an Emerging Discipline, Prentice Hall, Upper Saddle River, NJ (1996).
9. R. Youngs, D. Redmond-Pyle, P. Spaas, and E. Kahan, "A Standard for Architecture Description," IBM Systems Journal 38, No. 1, 32-50 (1999, this issue). This paper contains a glossary with more detailed definitions of terms used here.
10. F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, and M. Stal, Pattern-Oriented Software Architecture: A System of Patterns, John Wiley & Sons, Inc., New York (1996).
11. E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley Publishing Co., Reading, MA (1995).
12. C. Alexander, S. Ishikawa, M. Silverstein, M. Jacobson, I. Fiksdahl-King, and S. Angel, A Pattern Language: Towns, Buildings, Construction, Oxford University Press, New York (1977).
13. K. A. Bohrer, "Architecture of the San Francisco Frameworks," IBM Systems Journal 37, No. 2, 156-169 (1998).
14. Information about IBM Component Broker Series is available at http://www.software.ibm.com/ad/cb.
15. With "back-end scripting" the mid-tier server (the "hub") takes a request for information and decomposes it into a script of multiple, discrete tasks, each appropriate for an individual legacy application, and manages all of the associated workflow.
16. Early, Cloud & Company is now part of the new Customer Relationship Solutions (CRS) software company, an independent subsidiary of IBM. For more information see http: //www.ibm.com/services/crs/index.html.
17. R. Prins, Developing Business Objects: A Framework-Driven Approach, McGraw-Hill Publishing Company, London (1996).
18. See http://www.omg.org for link to UML specifications.
19. T. Harris, J. W. Rothwell, and P. T. L. Lloyd, "Experiences in Reusing Technical Reference Architectures," IBM Systems Journal 38, No. 1, 98-117 (1999, this issue).