Project 005 – High-Level Class Diagrams
CS/SE3430 / CS5430 - Object-Oriented Analysis and Design
High-level (Analysis Level) Class Diagram Deliverable
Due 11/10 8:00 am for in class review. Final version due 11/17 by noon
1. Noun Identification for Candidate Classes –
 Use the noun identification technique for identifying possible classes.
 Use the table to evaluate each candidate class. (Generate at least 10 Candidates per
team member – see further constraints below). Many of the candidates will, when
analyzed, prove to be poor candidates.
 Use this table in MS Word as Word handles text-based data better than Excel. Identify
who generated each of the candidates.
2. Develop CRC cards –
 Select 2 Class Candidates per team member and develop CRC Cards.
 These should all be domain classes.
 See the template below.
 Identify author of each CRC card.
3. High-level Class Diagram –
 This deliverable shall be done in Rhapsody.
 Create a class diagram using the classes from Step # 2.
 Include domain classes, relationships between the classes, and multiplicities.
 Use the same Model file as you used for the Use Case Model.
 You do not need (should not have) methods or attributes in the class diagram yet.
 All classes should have documentation similar to what you would have for a class in C++
or Java in 263 and 243.
4. A Project report – same as usual.
 Make sure that you remember to copy the grading rubric to the top of the project
report.
 Name the report name “Lab05_[teamName]_Analysis Level Class Model”. All other files
(except for the model files) for this deliverable shall be maintained in a SourceSafe
subproject named “Proj05”.
5. Timelog.
 Make sure that each member is participating on this project.
 Make sure that is accurate!
Noun Identification and Object Qualification Table
NOUN
Tuna
color
Squirrel
State/
Attributes
Yes
Respons- Behavior
ibility
No
No
Redundant
No
Within
Scope
Yes
Yes
Yes
No
Yes
© 2011 Mike Rowe
Yes
Page 1
Comment / Decision
Not a good candidate -probably add to object X
Good candidate for a
class!
2/6/2016
Project 005 – High-Level Class Diagrams
CS/SE3430 / CS5430 - Object-Oriented Analysis and Design
...
CRC Card
Class:
Superclass or Subclass :
Responsibilities
Collaborators
Add more rows if necessary
Grading for Detailed High-level Class Diagram
Task
Candidate Classes (noun list)
 Analysis
Candidate Classes (noun list)
 completeness
CRC Cards
High Level Class. Diagram
 Classes
Max Pts
2
2
3
2
High Level Class. Diagram
 Relationships
1
High Level Class. Diagram
 Multiplicities
1
High Level Class. Diagram
 NO attributes or
methods
Project Report and time
Reporting
Style, Spelling and Grammar
UMLint work
TOTAL
1
© 2011 Mike Rowe
Points and Comments
3 pts will be deducted if the class model is not in the
same model files as your previously developed Use
Case Diagram. This should be evidenced by the
SourceSafe history (I should be able to query the file
history back to the Use Case model).
2
1
1
16
Page 2
2/6/2016