Object-Oriented Reading List
Edward Berard
Some people have asked me for a reading list on object-oriented
technology. What follows is a partial reading list. [My own current
list contains about 300 entries, and is by no means comprehensive.]
I hope you will find this list of use.
-- Ed Berard
(301) 353-9652
--------------------------
Readings In Object-Oriented Technology
by Edward V. Berard
Berard Software Engineering, Inc.
If you are interested in reading about any rapidly evolving
technology, it is best to keep the following in mind:
% Read more than one source. Look for sources which have different,
and possibly conflicting, views of the material. It is often
difficult to determine fundamental facts when only one
viewpoint is present.
% Very often, authors confuse concepts with implementations. Ask
yourself if the author is discussing a concept, or a
particular implementation of the concept.
% Always be on the lookout for new sources. In the software
technology arena in particular, significant changes can take
place in less than a month.
% Take care to distinguish between differing viewpoints and
conflicting viewpoints.
There are many topic areas in object-oriented software technology, and
literally thousands of books, articles, tutorials, and proceedings
devoted, in whole, or in part, to object-oriented software concepts.
What we will present here is some of the representative reading
material. Just because an item is included in this reading list does
not mean that it is recommended without qualifications, nor does it
mean that it is an authoritative source on a topic. However, the
material listed here is intended to help you understand more about the
technology.
Object-Oriented Programming
Object-oriented programming books most often tend to focus on
programming language aspects of object-oriented technology. However,
many fundamental concepts can be found in the books mentioned below:
[Cox, 1986]. B.J. Cox, Object Oriented Programming: An Evolutionary
Approach, Addison-Wesley, Reading, Massachusetts, 1986.
[Goldberg and Robson, 1983]. A. Goldberg and D. Robson, Smalltalk-80:
The Language and Its Implementation, Addison-Wesley, Reading,
Massachusetts, 1983.
[Meyer, 1988]. B. Meyer, Object-Oriented Software Construction,
Prentice-Hall, Englewood Cliffs, New Jersey, 1988.
[Keene, 1989]. S.E.Keene, Object-Oriented Programming in Common Lisp,
Addison-Wesley, Reading, Massachusetts, 1989.
[Stroustrup, 1986a]. B. Stroustrup, The C++ Programming Language,
Addison-Wesley, Reading, Massachusetts, 1986.
Object-Oriented Requirements Analysis
There are a number of publicly available courses on object-oriented
requirements analysis. Since the technology is still new, these
courses present many differing viewpoints and approaches. There is,
however, one book on the topic:
[Shlaer and Mellor, 1988]. S. Shlaer and S.J. Mellor, Object-Oriented
Systems Analysis: Modeling the World In Data, Yourdon Press:
Prentice-Hall, Englewood Cliffs, New Jersey, 1988.
Object-Oriented Design/Development
Most of the work which has been done in the area of object-oriented
life-cycle issues, outside of object-oriented programming, has been
accomplished within the Ada community. Some representative sources on
OOD are:
[Abbott, 1983]. R.J. Abbott, "Program Design by Informal English
Descriptions," Communications of the ACM, Vol. 26, No. 11, November
1983, pp. 882 - 894.
[Booch, 1982a]. G. Booch, "Object Oriented Design," Ada Letters, Vol.
I, No. 3, March- April 1982, pp. 64 - 76.
[Booch, 1986a]. G. Booch, "Object Oriented Development," IEEE
Transactions on Software Engineering, Vol. SE-12, No. 2, February
1986, pp. 211 - 221.
[Goldsack, 1985]. S.J. Goldsack, Ada for Specification : Possibilities
and Limitations, Cambridge University Press, Cambridge, United
Kingdom, 1985.
[Heitz, 1988]. M. Heitz, "HOOD: A Hierarchical Object-Oriented Design
Method," Proceedings of the Third German Ada Users Congress, January
1988, Gesellschaft fur Software Engineering, Munich, West Germany, pp.
12-1 - 12-9.
[Masiero and Germano, 1988]. P. Masiero and F.S.R. Germano, "JSD As An
Object-Oriented Design Method," Software Engineering Notes, Vol. 13,
No. 3, July 1988, pp. 22 - 23.
[Seidewitz and Stark, 1986b]. E. Seidewitz and M. Stark, General
Object-Oriented Software Development, Document No. SEL-86-002, NASA
Goddard Space Flight Center, Greenbelt, Maryland, 1986.
[Stark and Seidewitz, 1987]. M. Stark and E.V. Seidewitz, "Towards a
General Object-Oriented Ada Life-Cycle," Proceedings of the Joint Ada
Conference, Fifth National Conference on Ada Technology and Washington
Ada Symposium, U.S. Army Communications-Electronics Command, Fort
Monmouth, New Jersey, pp. 213 - 222.
Object-Oriented Databases
Object-oriented databases are not the same thing as relational
databases. In effect, object-oriented database technology today is at
the same point relational database technology was in the late 1970s.
(I know more than a few vendors who would disagree with this point.)
Some representative information on the subject can be found in:
[Babcock, 1987]. C. Babcock, "Object is DBMS Focus," ComputerWorld,
Vol. XXI, No. 40, October 5, 1987, page 25.
[Blaha et al, 1988]. M.R. Blaha, W.J. Premerlani, and J.E. Rumbaugh,
"Relational Database Design Using an Object-Oriented Approach,"
Communications of the ACM, Vol. 31, No. 4, April 1988, pp. 414 - 427.
[Bochenski, 1988]. B.A. Bochenski, "On Object-Oriented Programming,
Databases," Software, Vol. 8, No. 11, September 1988, page 42.
[Dittrich and Dayal, 1986]. K. Dittrich and U. Dayal, Editors,
Proceedings of the 1986 International Workshop on Object-Oriented
Database Systems, IEEE Catalog Number 86TH0161-0, IEEE Computer
Society Press, Washington, D.C., 1986.
[Scannell, 1988]. T. Scannell, "Freeform DBMS the 'Object' of Startup
Company's Affection," Mini-Micro Systems, Vol. XXI, No. 2, February
1988, pp. 16 - 22.
[Shriver and Wegner, 1987]. B. Shriver and P. Wegner, Editors,
Research Directions in Object-Oriented Programming, The MIT Press,
Cambridge, Massachusetts, 1987.
[Weiss, 1987]. R. Weiss, "Why Object-Oriented Databases?," Electronic
Engineering Times, No. 465, December 21, 1987, page 23.
[Wile and Allard, 1987]. D.S. Wile and D.G. Allard, "Worlds: an
Organizing Structure for Object-Bases," SIGPLAN Notices, Vol. 22, No.
1, January 1987, pp. 16 - 26.
Object-Oriented Computer Hardware
Even computer hardware can be constructed in an object-oriented
manner. Here are two references:
[Myers, 1982]. G.J. Myers, Advances in Computer Architecture, Second
Edition, John Wiley & Sons, New York, New York, 1982.
[Organick, 1983]. E. Organick, A Programmer's View of the Intel 432
System, McGraw-Hill, New York, New York,1983.
General Object-Oriented Technology References
There are a number of general references on object-oriented
technology, including:
[ACM, 1986a]. Association for Computing Machinery, Special Issue of
SIGPLAN Notices on th Object-Oriented Programming Workshop, Vol. 21,
No. 10, October 1986.
[ACM, 1986b]. Association for Computing Machinery, OOPSLA '86
Conference Proceedings, Special Issue of SIGPLAN Notices, Vol. 21, No.
11, November 1986.
[ACM, 1988a]. Association for Computing Machinery, OOPSLA '87 Addendum
to the Proceedings, Special Issue of SIGPLAN Notices, Vol. 23, No. 5,
May 1988.
[ACM, 1988b]. Association for Computing Machinery, OOPSLA '88
Conference Proceedings, Special Issue of SIGPLAN Notices, Vol. 23, No.
11, November 1988.
[Gill, 1988]. P. Gill, "MIS Slowly Warms Up to Object-Oriented
Programming," ComputerWorld, Vol. XXII, No. 8, February 22, 1988, pp
71 - 76.
[Millikin, 1989]. M.D. Millikin, "Object Orientation: What It Can Do
For You," ComputerWorld, Vol. 23, No. 11. March 13, 1989, pp. 103 -
113.
[Peterson, 1987a]. G.E. Peterson, Tutorial: Object-Oriented Computing,
Volume 1: Concepts, IEEE Catalog Number EH0257-6, IEEE Computer
Society Press, Washington, D.C., 1987.
[Peterson, 1987b]. G.E. Peterson, Tutorial: Object-Oriented Computing,
Volume 2: Implementations, IEEE Catalog Number EH0257-6, IEEE Computer
Society Press, Washington, D.C., 1987.
[Shriver and Wegner, 1987]. B. Shriver and P. Wegner, Editors,
Research Directions in Object-Oriented Programming, The MIT Press,
Cambridge, Massachusetts, 1987.
Jim Burke
> Object-Oriented Requirements Analysis
>There are a number of publicly available courses on object-oriented
>requirements analysis. Since the technology is still new, these
>courses present many differing viewpoints and approaches. There is,
>however, one book on the topic:
>[Shlaer and Mellor, 1988]. S. Shlaer and S.J. Mellor, Object-Oriented
>Systems Analysis: Modeling the World In Data, Yourdon Press:
>Prentice-Hall, Englewood Cliffs, New Jersey, 1988.
Just a note, or semi-review, on the above book. As Edward Berard says
above, there are few books on OO analysis. I have the above mentioned
book and I was rather disappointed. The book did not get to what I would
consider the meat of the OO paradigm. My personal opinion is that the
book appeared to be a repackaging of the Structured Analysis and Design
book previously published by Yourdon, but with OO buzz words instead.
I don't mean to be unkind, its just that there is a great need for books
and articles that address the fundamental differences between thinking in
oo terms as opposed to tradition structured design thinking. Brad Cox's
book went much further in expressing the oo mind-set to the reader
than did the OO systems analysis book mentioned above. Of course, Cox's
book has its shortcommings as well since he tends to look at the world
as one big smalltalk and/or Objective-C environment. Still, I am hoping
for better, more in depth books on oo design and analysis than the one
mentioned above. OO is old enough now for better books, methodologies,
and case tools. Where are they?
--
****** Views expressed herin are my own *******
Jim Burke - consultant 408) 734-9822 | I'll stop posting when they pry my
ji...@Atherton.COM | cold, dead fingers from the smoking
{decwrl,sun,hpda,pyramid}!athertn!jimb | keyboard.
Richard Locke
>In article <5...@ajpo.sei.cmu.edu> ebe...@ajpo.sei.cmu.edu (Edward Berard) writes:
[this followup directed to OO lang groups, in addition to comp.software-eng]
>> Object-Oriented Requirements Analysis
>...My personal opinion is that the [Shlaer and Mellor] book [OO Systems
>Analysis: Modelling the Wold In Data] appeared to be a repackaging of
>the Structured Analysis and Design book previously published by Yourdon,
>but with OO buzz words instead.
Beware! There seems to be a lot of this going on. I attended an
"Object-Oriented Symposium" in June, at which a number of speakers
plugged inappropriate old ideas (IMHO) dressed up with the new
buzz words. Grady Booch, Bertrand Meyer, and Burt Rubenstein
were the exceptions to this!. [disclaimer: I didn't attend
every presentation, many were concurrent!]
Indeed, too much of the literature suffers from the "OO is almost the
same as [old method]" syndrome. Paul Ward's article in IEEE Software
(March 89), for example, purports to show the "there is no conflict"
between "structured analysis and design" and the use of OO languages.
I certainly disagree. [But hey, don't trust me! Decide for yourself! 8^)]
(To be fair, many "standard" software engineering concepts apply
equally well to OO development and traditional development. However, I
feel that successful OO design & implementation requires a different mindset.)
Always be aware of an individual's influences. People with a
strong investment in structured A & D (i.e., they've written books,
sell tools, etc) are the ones likely to tell you that OO techniques
are the same as structured techniques. They are salesmen. (Yes,
you can still use my CASE tool for OO stuff!)
>[The Cox] book has its shortcomings ... he tends to look at the world
>as one big smalltalk and/or Objective-C environment. Still, I am hoping
>for better, more in depth books on oo design and analysis than the one
>mentioned above. OO is old enough now for better books, methodologies,
>and case tools. Where are they?
I hope you've read Meyer's "Object-oriented Software Construction".
Yes his book is influenced by Eiffel, just as the Cox book is language-
influenced. Meyer claims it is naive to think OO concepts can be
discussed in a completely language independent manner. Despite this,
his book does a fine job with generic OO (and generic software engineering)
concepts, showing how OO supports modularity, reusability, etc.
As for case tools, I'm not convinced there are any *good* case tools
for plain old 'C' stuff, much less for OO development 8^) Correct
me if I'm wrong.
<my opinions only>
--
Dick Locke AT&T Paradyne Corporation
{uunet,peora}!pdn!locke Mail stop LG-133
Phone: (813) 530-8241 P.O. Box 2826
Largo, FL 34649-2826 USA