SOFTWARE PROJECT TA MATCHING SYSTEM

TA USE CASE DIAGRAM

TA REQUIREMENTS DIAGRAM

USE CASE VS REQUIREMENT

NOTE: DO IT BY YOUR HAND

To do: 3. Leveraging the static modeling heuristics shown in Fig. 2 create a conceptual static class diagram for your software lab/project Her fata. State both operational and data responsibilities. Assign modules at most one operational and one data responsibility. Assign complementary data and operational responsibilities. Make sure module responsibilities do not overlap. Place operations and data in a module only if they help fulfill the module's responsibilities. Place all operations and data needed to fulfil a module responsibility in that module. Use inheritance only when there is a generalization relationship between the sub-class and its super-classes ). Combine common attributes and operations in similar classes into a common super-class. Use delegation to increase reuse, flexibility, and configurability. Fig. 2. Static modeling heuristics