Documenting Attributes

I l @ ve RuBoard

Attributes should also be documented with a clear, concise definition. The definition should state the purpose of the attribute, not the structure of the attribute. For example, a bad definition for the name attribute of the Course class could be "a character string of length 15." A better definition for the name attribute is "The title of the course that is used in all University publications ."

DOCUMENTING ATTRIBUTES IN RATIONAL ROSE

graphics/quatranirose_icon.gif
  1. Click the + next to the class in the browser to expand the class.

  2. Click to select the attribute.

  3. Position the cursor in the documentation window and enter the documentation for the attribute.

The documentation for the name attribute of the Course class is shown in Figure 7-5.

Figure 7-5. Attribute Documentation

graphics/07fig05.jpg

I l @ ve RuBoard


Visual Modeling with Rational Rose 2002 and UML
Visual Modeling with Rational Rose 2002 and UML (3rd Edition)
ISBN: 0201729326
EAN: 2147483647
Year: 2002
Pages: 134

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net