To do:

1.Pick a key use case of the lab/project from Lab #1 and create a textual description of the scenario of the TA matching system, include this use case in your lab report.

2.Using the guidelines listed in Fig. 1 creates a table, similar to table 2, that lists the candidate classes and responsibilities of those classes.

Fig. 1 Theme-based decomposition heuristics

Table 1. Example of candidate classes generated from Themes for the Aqualush example (reproduced from Table 11-3-3 of reference [1]).

Problem to do based on the Example above

LAB PROJECT OF TA MATCHING SYSTEM

CASE DIAGRAM

TA REQUIREMENTS DIAGRAM

USE CASE VS REQUIREMENT

NOTE: DO IT BY YOUR HAND

Generating Classes from Themes * Look for entities in charge of program tasks Look for actors, * Look for things about which the program stores data. * Look for structures and collection of objects Evaluating and Selecting Candidate Classes Discard classes with vague names or murky responsibilities. ork candidate classes with overlapping responsibilities to divide their responsibilities clearlv Discard classes that do something out of scope * Check each class for important but overlooked * Combine common attributes and operations from similar Evaluating and Improving the Class Diagram attributes, operations, or associations. classes into a common super-class. Apply design patterns where appropriate (omit this heuristic since it will be covered in more detail later) Generating Classes from Themes * Look for entities in charge of program tasks Look for actors, * Look for things about which the program stores data. * Look for structures and collection of objects Evaluating and Selecting Candidate Classes Discard classes with vague names or murky responsibilities. ork candidate classes with overlapping responsibilities to divide their responsibilities clearlv Discard classes that do something out of scope * Check each class for important but overlooked * Combine common attributes and operations from similar Evaluating and Improving the Class Diagram attributes, operations, or associations. classes into a common super-class. Apply design patterns where appropriate (omit this heuristic since it will be covered in more detail later)