Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Requirements of an object-oriented design method

Requirements of an object-oriented design method

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
Software Engineering Journal — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

This paper attempts to identify those necessary characteristics that an object-oriented design method ought to exhibit in order to merit that appellation. By examining the key concepts associated with the object-oriented approach, important design issues are identified; these are related to current work in the area of design methodology. A list of criteria for the evaluation of the suitability of any proposed object-oriented design method is constructed, and several current and proposed methods (both conventional and object-oriented) are evaluated in respect of that list. The pessimistic conclusion is reached that, at present, there are some significant gaps in the facilities/support provided to the potential object-oriented designer, particularly in the evaluation and management of the design process; by contrast, there are substantial advances being made in technical design methods.

References

    1. 1)
      • Diederich, J., Milton, H.: `An object-oriented system shell', OOPSLA'87 Conf. Proc., December 1987, Orlando, Florida, ACM Press, p. 61–77, (SIGPLAN Not., 1987, 22, (12)).
    2. 2)
      • B. Meyer . (1988) , Object-oriented software construction.
    3. 3)
      • J. Cameron . (1984) , Developing systems methodically.
    4. 4)
      • R. Wirfsbrock , B. Wilkerson , L. Wiener . (1990) , Designing object-oriented software.
    5. 5)
      • D. Harel . Statecharts: a visual formalism for complex systems. Sci. Comput. Prog. , 231 - 274
    6. 6)
      • A.I. Wasserman , P.A. Pircher , R.J. Muller . (1989) , An introduction to object-oriented structured design.
    7. 7)
      • J. RUMBAUGH , M. BLAHA , E. PREMERLANI , E. EDDY , W. LORENSEN . (1991) , Object-oriented modeling and design.
    8. 8)
      • A.J. Wasserman , R.J. Muller . The object-oriented structured design notation for software design representation. Computer , 50 - 63
    9. 9)
      • C. Gane , T. Sarson . (1979) , Structured systems analysis: tools and techniques.
    10. 10)
      • G. Cutts . (1987) , Structured systems analysis and design methodology.
    11. 11)
      • Pun, W., Winder, R.L.: `Automating class hierarchy graph construction', RN/89/23, Research Note, March 1989.
    12. 12)
      • S. Danforth , C. Tomlinson . Type theories and object-oriented programming. Comput. Surv. , 1 , 29 - 72
    13. 13)
      • F.P. Brook . (1975) , The mythical man-month — essays on software engineering.
    14. 14)
      • P. Coad , E. Yourdon . (1991) , Object-oriented analysis.
    15. 15)
      • Winder, R.L., Pun, W.W.Y.: `Towards a design method for object-oriented programming', RN/88/1, Research Note, January 1988.
    16. 16)
      • A.L. Winblad , S.D. Edwards , D.R. King . (1990) , Object-oriented software.
    17. 17)
      • Alabiso, B.: `Transformation of data flow analysis models to object oriented design', OOPSLA'88 Conf. Proc., November 1988, San Diego, California, 23, ACM Press, p. 335–353, SIGPLAN No., 1988, (11).
    18. 18)
      • Pun, W., Winder, R.L.: `A design method for object-oriented programming', ECOOP'89, Proc. Third European Conf. on Object-Oriented Programming, 1989, Nottingham , Cambridge University Press, p. 225–240.
    19. 19)
      • M. Mullin . (1989) , Object-oriented program design with examples in C + +.
    20. 20)
      • M. Jackson . (1983) , System development.
    21. 21)
      • G. Booch . Object-oriented development. IEEE Trans. , 2 , 211 - 221
    22. 22)
      • T. Demarco . (1978) , Structured analysis and system specification.
    23. 23)
      • E. Yourdon , L. Constantine . (1979) , Structured design—fundamentals of a discipline of computer program and systems design.
    24. 24)
      • G. Booch . (1983) , Software engineering with Ada.
    25. 25)
      • W.P. Stevens , G.J. Myers , L.L. Constantine . Structured design. IBM Syst. J. , 2 , 115 - 139
    26. 26)
      • G. Booch . (1991) , Object oriented design with applications.
    27. 27)
      • P.P. Chen . The entity-relationship model — toward a unified view of data. ACM Trans., Database Syst. , 1 , 9 - 36
    28. 28)
      • R.J. Abbot . (1986) , An integrated approach to software development.
    29. 29)
      • Wirfs-Brock, R., Wilkerson, B.: `Object-oriented design: a responsibility-driven approach', OOPSLA'89 Conf. Proc., October 1989, New Orleans, Louisiana, ACM Press, p. 71–75, (SIGPLAN NOT., 1989, 24, (10)).
    30. 30)
      • (1989) , HOOD Manual Issue 2.3 Draft A.
    31. 31)
      • S. Shlaer , S.J. Mellor . (1988) , Object-oriented systems analysis.
    32. 32)
      • Matthews, D.: `Programming language design with polymorphism', 1983, PhD Thesis, University of Cambridge, Computer Laboratory, UK, (cited in [10]).
    33. 33)
      • Mills, H.: `Chief programmer teams, principles, and procedure', FSC 71-5108, Division Report, 1971.
http://iet.metastore.ingenta.com/content/journals/10.1049/sej.1992.0011
Loading

Related content

content/journals/10.1049/sej.1992.0011
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
This is a required field
Please enter a valid email address