home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.object
- Path: sparky!uunet!rational.com!thor!rmartin
- From: rmartin@thor.Rational.COM (Bob Martin)
- Subject: Re: Booch question: new class relationship?
- Message-ID: <rmartin.728268285@thor>
- Sender: news@rational.com
- Organization: Rational
- References: <894@ulogic.UUCP> <rmartin.727740331@thor> <1k6783INNka9@info2.rus.uni-stuttgart.de>
- Date: Fri, 29 Jan 1993 00:44:45 GMT
- Lines: 45
-
- LANG@nvdv.e-technik.uni-stuttgart.dbp.de (MARTIN LANG) writes:
-
-
- |> Contains by Value
- |> *=========#
- |>
- |> Contains by Reference
- |> *=========[]
- |>
- |> Uses
- |> O=============
-
-
- |Which class relationship is appropriate if you have two relations at the
- |same time, e.g.
-
- |class ValueAndUse {
- | void AddValue(Value & val);
- |
- | Value X;
- |};
- |
-
- It is perfectly fair to put both relationships on a a diagram.
- Typically however each relationship would appear on a different class
- diagram since each relationship represents a different aspect of the
- class.
-
- This is an important point. In Booch notation you do not try to
- completely document a class in a single diagram. You try to convey a
- single idea in each diagram. It may take many diagrams, both object
- and class digrams to completely describe the class.
-
- This is why you should also keep Booch's templates (or some other
- record like a CRC card or even in incomplete software description like
- a class header in C++). The diagrams are meant for showing concepts
- not completeness. This makes the diagrams easy to create and easy to
- follow.
-
-
- --
- Robert Martin | Design Consulting | Training courses offered:
- R. C. M. Consulting | rmartin@rational.com | Object Oriented Analysis
- 2080 Cranbrook Rd. | Tel: (708) 918-1004 | Object Oriented Design
- Green Oaks, Il 60048| Fax: (708) 918-1023 | C++
-