iBet uBet web content aggregator. Adding the entire web to your favor.
iBet uBet web content aggregator. Adding the entire web to your favor.



Link to original content: https://doi.org/10.1007/BFb0013511
Experiences applying a practical architectural method | SpringerLink
Skip to main content

Experiences applying a practical architectural method

  • Experience Reports
  • Conference paper
  • First Online:
Reliable Software Technologies — Ada-Europe '96 (Ada-Europe 1996)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 1088))

Included in the following conference series:

Abstract

Software architecture has come to be recognized as a discipline distinct from software design. Over the past five years, we have been developing and testing a practical software architecture method at the MITRE Software Center. The method begins with an initial statement of system goals, the purchaser's vision for the system, and needs, an abstraction of the system's requirements. Multiple views of the system are then developed, to address specific architectural concerns. Each view is defined in terms of components, connections and constraints and validated against the needs. This paper briefly introduces the method and describes our experiences with its “alpha” and “beta” applications to two U.S. Army management information systems.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. David Garlan, editor. Proceedings of the First International Workshop on Architecture for Software Systems, Seattle, WA, April 24–25 1995. Published as CMU-CS-TR-95-151.

    Google Scholar 

  2. P. B. Kruchten. The 4+1 view model of architecture. IEEE Software, 28(11):42–50, November 1995.

    Google Scholar 

  3. D. Perry and A. Wolf. Foundations for the study of software architecture. ACM SIGSOFT Sofware Engineering Notes, 17(4), October 1992.

    Google Scholar 

  4. W. E. Royce. Reliable, reusable Ada components for constructing large, distributed multi-task networks: Network Architecture Services (NAS). In TRI-Ada Proceedings, Pittsburgh, October 1989.

    Google Scholar 

  5. W. E. Royce. TRW's Ada process model for incremental development of large software systems. In Proceedings of the 12th International Conference on Softwar Engineering, Nice, France, March 26–30 1990.

    Google Scholar 

  6. P. B. Kruchten and C. J. Thompson. An object-oriented, distributed architecture for large scale Ada systems. In Proceedings TRI-Ada '94, Baltimore, MD, November 1994.

    Google Scholar 

  7. Dan DeJohn. The Tyndall Range Control System: bringing network computing to C2 systems. In Charles B. Engle, editor, TRI-Ada '94 Proceedings, pages 474–485. ACM, 1994.

    Google Scholar 

  8. David E. Emery and Richard F. Hilliard II. “Architecture,” methods and open issues. In Proceedings of the First International Workshop on Architectures for Software Systems, Seattle, WA, 1995.

    Google Scholar 

  9. Stephen C. Schwarm, Timothy B. Rice, and Richard F. Hilliard II. The architectural metaphor as a foundation for systems engineering. In Proceedings INCOSE 96 Symposium, July 1996. to appear.

    Google Scholar 

  10. Richard F. Hilliard II and D. Emery. Patterns: Design: Blueprints: architecture. IEEE Software, 1996. submitted to special issue on Patterns, Objects and Architectures.

    Google Scholar 

  11. Richard F. Hilliard II. The notion of ‘architecture’ in model-based software engineering. In Proceedings of the Workshop on Domain-Specific Architectures, Hidden Valley, PA, July 1990.

    Google Scholar 

  12. A. Burns and M. Lister. A framework for building dependable systems. The Computer Journal, 34(2), 1991.

    Google Scholar 

  13. Michael S. Deutsch and Ronald R. Willis. Software Quality Engineering. Prentice-Hall, 1988.

    Google Scholar 

  14. Douglas T. Ross and Kenneth E. Schoman. Structured Analysis for requirements definition. IEEE Transactions on Software Engineering, SE-3(1), January 1977.

    Google Scholar 

  15. Douglas T. Ross. Removing the limitations of natural language (with the principles behind the RSA language). In Herbert Freeman and Philip M. Lewis II, editors, Software engineering: proceedings of the Software Engineering Workshop held in Albany, Troy, and Schenectady, New York, from May 30–June 1, 1979. Academic Press, New York, 1980.

    Google Scholar 

  16. Mary Shaw. Comparing architectural design styles. IEEE Software, 28(11):27–14, November 1995.

    Google Scholar 

  17. DoD. Trusted computer systems evaluation criteria. Technical Report DoD 5000.28-STD, Department of Defense, 1985.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Alfred Strohmeier

Rights and permissions

Reprints and permissions

Copyright information

© 1996 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Emery, D.E., Hilliard, R.F., Rice, T.B. (1996). Experiences applying a practical architectural method. In: Strohmeier, A. (eds) Reliable Software Technologies — Ada-Europe '96. Ada-Europe 1996. Lecture Notes in Computer Science, vol 1088. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0013511

Download citation

  • DOI: https://doi.org/10.1007/BFb0013511

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-61317-6

  • Online ISBN: 978-3-540-68457-2

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics