Skip to main content

8 Specifying the Architecture of Implementations

  • Chapter
  • 197 Accesses

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

Abstract

Architectural specifications impose structure on implementations, whereas specification-building operations only structure the text of specifications.

As explained in the previous chapters, the specification of a complex system may be fairly large and should be structured into coherent, easy to grasp, pieces. Casl provides a number of specification-building operations to achieve this, as detailed in Chap. 6. Moreover, generic specifications, described in Chap. 7, provide pieces of specification that are easy to reuse in different contexts, where they can be adapted as desired by instantiating them.

Specification-building operations and generic specifications are useful to structure the text of the specification of the system under consideration. However, the models of a structured specification have no more structure than do those of a flat, unstructured, specification. Indeed, most examples given in the previous chapters could have been structured differently, with the same meaning (i.e., with the same models). Structured specifications are usually adequate at the requirements stage, where the focus is on the expected overall properties of the system under consideration.

In contrast, the aim of architectural specifications is to prescribe the intended architecture of the implementation of the system. Architectural specifications provide the means for specifying the various components from which the system will be built, and describing how these components are to be assembled to provide an implementation of the system of interest. At the same time, they allow the task of implementing a system to be split into independent, clearly-specified sub-tasks. Thus, architectural specifications are essential at the design stage, where the focus is on how to factor the implementation of the system into components.

The aim of this chapter is to discuss and illustrate both the role of architectural specifications and how to express them in Casl.

This is a preview of subscription content, access via your institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • DOI: 10.1007/978-3-540-44397-1_8
  • Chapter length: 17 pages
  • Instant PDF download
  • Readable on all devices
  • Own it forever
  • Exclusive offer for individuals only
  • Tax calculation will be finalised during checkout
eBook
USD   74.99
Price excludes VAT (USA)
  • ISBN: 978-3-540-44397-1
  • Instant PDF download
  • Readable on all devices
  • Own it forever
  • Exclusive offer for individuals only
  • Tax calculation will be finalised during checkout
Softcover Book
USD   99.00
Price excludes VAT (USA)

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and Permissions

Copyright information

© 2004 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Bidoit, M., Mosses, P.D. (2004). 8 Specifying the Architecture of Implementations. In: Bidoit, M., Mosses, P.D. (eds) CASL User Manual. Lecture Notes in Computer Science, vol 2900. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-44397-1_8

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-44397-1_8

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-20766-5

  • Online ISBN: 978-3-540-44397-1

  • eBook Packages: Springer Book Archive