Journal of Systems Integration

, Volume 3, Issue 3–4, pp 273–302 | Cite as

Layered specifications to support reusability and integrability

  • Roland T. Mittermeir
  • Evelin Kofler


Building systems by integrating components and building systems by reusing components are but two sides of the same coin. In both cases one faces the problem of producing systems out of prefabricated parts, either parts which have been designed for a different environment than the one they will be used in now, or parts which have been designed for a yet undefined target system.

This situation differs from classical software design situations. It demands that in parts engineering as well as in systems engineering, certain interface decisions are postponed to a rather late point in time. This is only permissible, though, if other aspects are very precisely specified. Having the right model of specification of both, the target (system) and source (component) will substantially aid the retrieval and integration problem.

This article argues for a layered approach towards system specification. It will show, how relational specifications will help system designers not to bind themselves too early into premature decisions and how designs aiming for heavy reuse can grow by stepwise enriching specifications.

Key words

Software reuse software integration software specification 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    T.J., Biggerstaff and A.J. Perlis (eds.), “Software reusability,” vol. I and vol. II, Addison-Wesley and ACM press, New York, NY, 1989.Google Scholar
  2. 2.
    W. Tracz (ed.), “Software Reuse: Emerging Technology,”IEEE Tutorial, IEEE-CS press, Washington, D.C., 1988.Google Scholar
  3. 3.
    P. Freeman, (ed.), “Software reusability,”IEEE Tutorial, IEEE-CS press, Washington, D.C., 1987.Google Scholar
  4. 4.
    T.J. Biggerstaff and C. Richter, “Reusability framework, assessment, and directions,”IEEE Software, vol. 4/2, pp. 41–49, March 1987.Google Scholar
  5. 5.
    E. Hochmüller and R. Mittermeir, “Rahmenbedingungen für erfolgreiches Software-Reuse,” in: “Informations- und Kommunikationstechnologie für das neue Europa,” Proc. ADV-Kongreß 1993, Vienna, pp. 269–284.Google Scholar
  6. 6.
    R. Prieto-Diaz and P. Freeman, “Classifying software for reusability,”IEEE Software, vol. 4/1, pp. 6–16, Jan. 1987.Google Scholar
  7. 7.
    W. Rossak and R.T. Mittermeir, “A dbms based archive for reusable software components,” Proc. 2ieme J.I. “Le Genie Logiciel & ses Applications,” Toulouse, Dec. 89, pp. 501–516.Google Scholar
  8. 8.
    R.T. Mittermeir and W. Rossak, “The role of generalization hierarchies in requirements modelling,”Proc. Algorithmy '87, High Tatras, CSFR, April 1987, pp. 182–191.Google Scholar
  9. 9.
    N. Boudriga, A. Mili, and R. Mittermeir, “Semantic-based software retrieval to support rapid prototyping,”Structured Programming, vol. 13, pp. 109–127, 1992.Google Scholar
  10. 10.
    B. Meyer, “Reusability: the case of object-oriented design,”IEEE Software, vol. 4/2, pp. 50–64, March 1987.Google Scholar
  11. 11.
    G. Kappel, J. Vitek, O. Nierstrasz, S. Gibbs, B. Junod, and M. Stadelmann, “An object-based visual scripting environment,” inObject Oriented Development, D. Tschritzis (ed.), C.U.I., Univ. de Geneve, 1989, pp. 123–142.Google Scholar
  12. 12.
    O. Nierstrasz, L. Dami, V. de Mey, M. Stadelmann, D. Tsichritzis, and J. Vitek, “Visual scripting towards interactive construction of object-oriented applications,” in:Object Management, D. Tsichritzis (ed.), C.U.I., Univ. de Geneve, 1990, pp. 315–331.Google Scholar
  13. 13.
    O. Nierstrasz, D. Tsichritzis, V. de Mey, and M. Stadelmann, “Objects +Scripts = Applications,” inObject Composition, D. Tsichritzis, (ed.), C.U.I., Univ. de Geneve, 1991, pp. 11–29.Google Scholar
  14. 14.
    Y. Matsumoto, “A software factory: an overall approach to software production,”Proc. of the ITT Workshop on Reusability in Programming, Newport, RI, Sept. 1983 (reprinted in [3] P. Freeman, (ed.), “Software reusability,”IEEE Tutorial, IEEE-CS press, Washington, D.C., 1987.).Google Scholar
  15. 15.
    V. Basili, “Viewing maintenance as reuse-oriented software development,”IEEE-Software, vol. 7/1, pp. 19–25, Jan. 1990.CrossRefGoogle Scholar
  16. 16.
    G. Caldiera andV. Basili, “Identifying and qualifying reusable software components.”IEEE Computer, vol. 24/2, pp. 61–69, Feb. 1991.Google Scholar
  17. 17.
    E. Yourdon and L.L. Constantine,Structured Design, Prentice-Hall: Englewood Cliffs, NJ, 1979.Google Scholar
  18. 18.
    B. Curtis, “What you have to understand: This isn't the way we develop software at our company,” invited speech delivered at 11th ICSE, Pittsburgh, PA, May 1989.Google Scholar
  19. 19.
    G.M. Weinberg, “You say your design's inexact? Try a wiggle,”Datamation, vol. 25/9, pp. 146–149, Aug. 1979.Google Scholar
  20. 20.
    R.T. Mittermeir, “Normalization of software to enhance its potential for reuse,”TR UBW, 6/89, 1989.Google Scholar
  21. 21.
    R.T. Mittermeir and W. Rossak, “Reusability,” inModern Software Engineering, P. Ng and R.T. Yeh (eds.), van Nostrand, 1990, pp. 205–235.Google Scholar
  22. 22.
    R.T. Mittermeir and M. Oppitz, “Software bases for the flexible composition of application systems,”IEEE Trans. on Software Engineering, vol. SE-13/4, pp. 440–460, April 1987.Google Scholar
  23. 23.
    E. Hochmüller,AUGUSTA-Eine reuse-orientierte Software-Entwicklungsumgebung zur Erstellung von Ada-Applikationen. Ph.D. Dissertation, Univ. Wien, May 1992.Google Scholar
  24. 24.
    A. Mili, 1987, “A relational approach to the design of deterministic programs,”Acta Informatica, vol. 20/4, pp. 315–328, 1983.Google Scholar
  25. 25.
    A. Mili, J. Desharnais, and F. Mili, “Relational heuristics for the design of deterministic programs,“Acta Informatica, vol. 24/3, pp. 239–276, 1987.Google Scholar
  26. 26.
    A. Mili, N. Boudriga, and F. Mili,Towards Structured Specifying, Ellis Horwood Publ., Chichester, England, 1989.Google Scholar
  27. 27.
    A. Mili, X.-Y. Wang, and Q. Yu, “Specification methodology: an integrated relational approach,”Software-Practice and Experience, vol. 16/11, pp. 1003–1030, Nov. 1986.Google Scholar
  28. 28.
    A. Mili, J. Desharnais, and J.R. Gagne, “Formal models of stepwise refinement of programs,”ACM Computing Surveys, vol. 18/3, pp. 2431–2476, Sept. 1986.Google Scholar
  29. 29.
    H.D. Mills, “The new math of computer programming,”CACM, vol. 18/1, pp. 43–48, Jan. 1975.Google Scholar
  30. 30.
    N. Boudriga, F. Elloumi, and A. Mili, “The lattice of specifications,”SIAM Conference on Discrete Mathematics, Atlanta, Georgia, June 1990.Google Scholar
  31. 31.
    R.T. Mittermeir, “Design-aspects supporting software reuse,” inSoftware Re-use, Utrecht 1989, L. Dusink and P.A.V. Hall (eds.), Springer, 1991, pp. 115–119.Google Scholar
  32. 32.
    A. Stopper,Spezifikation und Normalisierung objekt-orientierter Systeme, Thesis, Univ. Klagenfurt, Dec. 1991.Google Scholar
  33. 33.
    L.R. Power, “Post-facto integration technology: new discipline for old practice,”Proc. 1st ICSI, Morristown, New York, pp. 4–13, Apr. 1990.Google Scholar
  34. 34.
    A. Mili, R. Mili and R. Mittermeir, “A formal approach to software reuse: design and implementation,”Proc. WISR '92, 5th Annual Workshop on Software Reuse, Palo Alto, CA, 1992.Google Scholar
  35. 35.
    R.T. Mittermeir and K. Kienzl, “Intra-object schemas to enhance adaptive software maintenance,” inProc. Joint Austrian-Hungarian Seminar on Systems Engineering, Budapest, February 1993.Google Scholar
  36. 36.
    J.M. Spivey,The Z Notation—A Reference Manual, Prentice-Hall International: Hemel Hempstead, UK, 1989.Google Scholar
  37. 37.
    J.A. Goguen, “Parameterized programming,”IEEE Trans. on Software Engineering, vol. SE-10/5, pp. 528–543, Sept. 1984.Google Scholar
  38. 38.
    J.A. Goguen and D. Wolfram, “On Types and FOOPS,”Proc. IFIP WG 2.6, DS-4 Conf, Windermere '90, North Holland, Amsterdam, NL, 1990.Google Scholar
  39. 39.
    J.A. Goguen, “Reusing and interconnecting software components,”IEEE Computer, vol. 19/2, pp. 16–28, Feb. 1986.Google Scholar
  40. 40.
    H. Mili, J. Sibert, and Y. Intrator, “An object oriented model based on relations,”Journal of Systems and Software, vol. 12/2, pp. 139–156, May 1990.CrossRefGoogle Scholar

Copyright information

© Kluwer Academic Publishers 1993

Authors and Affiliations

  • Roland T. Mittermeir
    • 1
  • Evelin Kofler
    • 1
  1. 1.Institut für InformatikUniversität KlagenfurtAustria

Personalised recommendations