CPRE 486 HW #12 due Tuesday 12/9/03 by class time

100 pts

Elaboration Iteration #3 – Design Aspects

PLEASE START EARLY. There will be a need to coordinate within teams, to a degree. Each team member should do the following steps. The results should be posted on the project Web site as n URLs, one for each team member. Work independently, except that the results will all be posted to the same project site.

1) Modify an existing use case to use the “include” UML notation. Explain why “include” is appropriate to use the way you have used it. Each team member should work with a different use case.

2) Extend an existing class diagram (either domain model or design class diagram) to include at least one new superclass and one new subclass. Explain why it is appropriate to add the classes you have added. (Each team member should work with a different class diagram.)

3) Explain why the superclass you have added should be or should not be an abstract class.

4) Do you have subclasses that are alternate states of some entity? Explain why your subclasses are or are not, and state why they should or shouldn’t be.

5) Add an association class to your domain model. Now that you have done it, you have done what many modelers do. But think – does it contribute to the quality or not? Explain. (No loss of points if you feel it does not contribute.)

6) Add aggregation diamonds as appropriate. If you did not add any, explain why not for each association.

7) Add a qualifier to at least one association. Explain how it changes the multiplicity or does not change the multiplicity of the association.

8) Suppose you have an association between two classes, SalesLineItem and ProductSpec:

Does this state that each object of class ProductSpec is contained in 0-infinity SalesLineItem objects, and each object of class SalesLineItem contains one ProductSpec, or instead does it state that each object of class ProductSpec is contained in 0-infinity SalesLineItem objects and 0-infinity SalesLineItem objects are associated with each ProductSpec object?

9) In your class diagram, label associations with the appropriate UML notation when objects of multiplicity > 1 are ordered.

10) Create a statechart diagram for your use case.