Project 006 – Detailed Class Diagrams
CS/SE3430 / CS5430 - Object-Oriented Analysis and Design
Detailed Class Diagram Deliverable
Due noon 11/29, 8:00am for in class review. Final version due 12/2, 8:00am
1.
2.
3.
4.
5.
6.
Detailed (refined) Class Diagram – We are switching from Rhapsody to Rose.
Please place the Rose MDL file at the root level of your SourceSafe repository.
In the Class Diagram refining relationships, add all major and some minor class
attributes, all public interfaces and main methods, and some minor methods. You
will probably need to add more classes than your Analysis Level Class Diagram.
Specification – Make sure that each Class, Operation/Method, Attribute is fully
specified (documented).
The goal – of this diagram is to have sufficient detail that you could give it to a group
of good programmer and end up with a functional system.
A Project report – same as usual. The report file shall in a SourceSafe directory
called Project06 and the report file named “Proj06_[teamName]_WPES”. Copy the
grading Rubric to the top of the Project Report.
Timelog – make sure it is accurate and consistent. All team members should share in
the work unless mention is made under the Issues section.
Task
Significant Progress by noon, 11/29
checked into your repository
Detailed Class Diagram
o -5 pts if this model is not a
continuation of the previous
models
Detailed Class Diagram
o Use of appropriate Associations
and navigation (don’t reuse the
same identifier in a class).
Detailed Class Diagram
o Use of appropriate Class types
and appropriately documented
Detailed Class Diagram
o Attributes: documented with type
and default values
Detailed Class Diagram
o Methods: documented with typed
parameters and returns
Detailed Class Diagram
o Coupling: minimize – classes
should have minimal reliance on
other classes. CRUD plus Save
and Display. No single setters or
© 2011 Mike Rowe
Points
100%
1
Points Earned / Comments
0
2
2
2
2
3
Page 1
2/9/2016
Project 006 – Detailed Class Diagrams
CS/SE3430 / CS5430 - Object-Oriented Analysis and Design
getters needed.
Detailed Class Diagram
o Cohesion: maximize – classes
should have a singular purpose
for the system.
Detailed Class Diagram
o Multiplicities
UMLint
o Run UMLint on your MDL file
and describe any benefits and/or
problems.
Project Report
o Completeness
o Format and style
o TimeLog
Total
© 2011 Mike Rowe
3
2
0
2
19.0
Page 2
2/9/2016