The implications of network-centric software systems on software architecture: a critical evaluation

ABSTRACT

The purpose of this paper is to evaluate the impact of emerging network-centric software systems on the field of software architecture. We first develop an insight concerning the term "network-centric" by presenting its origin and its implications within the context of software architecture. On the basis of this insight, we present our definition of a network-centric framework and its distinguishing characteristics. We then enumerate the challenges that face the field of software architecture as software development shifts from a platform-centric to a network-centric model. In order to face these challenges, we propose a formal approach embodied in a new architectural style that supports overcoming these challenges at the architectural level. Finally, we conclude by presenting an illustrative example to demonstrate the usefulness of the concepts of network centricity, summarizing our contributions, and linking our approach to future work that needs to be done in this area.

REFERENCES

• 1: David Garlan, Software architecture: a roadmap, Proceedings of the Conference on The Future of Software Engineering, p.91-101, June 04-11, 2000, Limerick, Ireland [doi>10.1145/336512.336537]
• 2: Wilson, C., Network Centric Warfare: Background and Oversight Issues for Congress, D.o. D, Editor. 2004.
• 3: D. Fay, An Architecture for Distributed Applications on the Internet: Overview of Microsoft's .NET Platform, Proceedings of the 17th International Symposium on Parallel and Distributed Processing, p.90.1, April 22-26, 2003
• 4: Real World Influences on Software Architecture - Interviews with Industrial System Experts, Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA'04), p.101, June 12-15, 2004
• 5: Balci, O., Network Centric Software Architecture, 2005 Blacksburg, VA. p. PowerPoint Presentation. http://manta.cs.vt.edu/balci
• 6: Paul Clements , David Garlan , Len Bass , Judith Stafford , Robert Nord , James Ivers , Reed Little, Documenting Software Architectures: Views and Beyond, Pearson Education, 2002
• 7: SDSC, GEON Infrastructure for the Geosciences. 2005, San Diego Supercomputer Center: San Diego, CA. p. 20.
• 8: Bass, L., B. E. John, and J. Kates, Achieving Usability Through Software Architecture, in Architecture Tradeoff Analysis Initiative. 2001, Carnegie Mellon University: Pittsburg, PA.
• 9: Bachmann, F., L. Bass, and M. Klein, An Application of the Architecture-Based Design Method to the Electronic House, in Product Line Systems. 2000, Carnegie Mellon University: Pittsburgh, PA.
• 10: Philippe Kruchten, The 4+1 View Model of Architecture, IEEE Software, v.12 n.6, p.42-50, November 1995 [doi>10.1109/52.469759]
• 11: Kazman, R., M. Klein, and P. Clements, ATAM: Method for Architecture Evaluation, in Product Line Systems. 2000, Carnegie Mellon University: Pittsburg, PA.
• 12: sOracle, Building a Network-Centric Warfare Architecture. 2004, Oracle Corporation. p. 7.
• 13: Fuzak, C., et al., C4ISR Imperatives---Cornerstones Network-Centric Architecture. 2001, SPACE AND NAVAL WARFARE SYSTEMS CENTER San Diego, CA p. 9.
• 14: Dewayne E. Perry , Alexander L. Wolf, Foundations for the study of software architecture, ACM SIGSOFT Software Engineering Notes, v.17 n.4, p.40-52, Oct. 1992 [doi>10.1145/141874.141884]
• 15: Director, The Implementation of Network-Centric Warfare, D.o.D. Office of Force Transformation, Editor. 2005, Government Printing Office.
• 16: David Garlan , Mary Shaw, An Introduction to Software Architecture, Carnegie Mellon University, Pittsburgh, PA, 1994
• 17: Matthew Stillerman , Carla Marceau , Maureen Stillman, Intrusion detection for distributed applications, Communications of the ACM, v.42 n.7, p.62-69, July 1999 [doi>10.1145/306549.306577]
• 18: Nenad Medvidovic , David S. Rosenblum , David F. Redmiles , Jason E. Robbins, Modeling software architectures in the Unified Modeling Language, ACM Transactions on Software Engineering and Methodology (TOSEM), v.11 n.1, p.2-57, January 2002 [doi>10.1145/504087.504088]
• 19: Alberts, D. S. and J. J. Garstka, Network Centric Warfare, D.o. D, Editor. 2001.
• 20: David E. Culler , Jason Hill , Philip Buonadonna , Robert Szewczyk , Alec Woo, A Network-Centric Approach to Embedded Software for Tiny Devices, Proceedings of the First International Workshop on Embedded Software, p.114-130, October 08-10, 2001
• 21: Paul Grünbacher , Alexander Egyed , Nenad Medvidovic, Reconciling Software Requirements and Architectures: The CBSP Approach, Proceedings of the 5th IEEE International Symposium on Requirements Engineering, p.202-211, August 27-31, 2001
• 22: Mysore, S., Securing Web Services - Concepts, Standards, and Requirements, S. Microsystems, Editor. 2003, Sun Microsystems: Santa Clara, CA. p. 28.
• 23: Robert T. Monroe , Andrew Kompanek , Ralph Melton , David Garlan, Architectural Styles, Design Patterns, and Objects, IEEE Software, v.14 n.1, p.43-52, January 1997 [doi>10.1109/52.566427]
• 24: Asundi, J., R. Kazman, and M. Klein, Using Economic Considerations to Choose Among Architecture Design Alternatives, in Product Line Systems. 2001, Carnegie Mellon University: Pittsburg, PA

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures

General Terms:
Design, Documentation, Standardization

Keywords:
architectural design, architectural style, component-and-connector, network-centric, software architecture, system of systems, viewtypes