1 / 8

CSC340: Class Analysis and Finding Classes from Use Cases

This tutorial covers the process of identifying classes in a system and analyzing their attributes, behaviors, relationships, and semantics. It also explores the use of UML class diagrams and associations.

washingtonj
Download Presentation

CSC340: Class Analysis and Finding Classes from Use Cases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CSC340: Tutorial 5Requirements Analysis TA: Y. An Date: 9:00-10:00am, Fri. Nov 7, 2003 Location: BA1130 CSC340

  2. Classes • A class describes a group of objects with: • Similar properties (attributes), • Common behaviors (operations), • Common relationships to other objects, • And common meaning (“semantics”). • For example, “employee” has a name, employee# and department; an employee is hired, and fired; an employee works in one or more projects. CSC340

  3. Finding classes from use cases CSC340

  4. Identifying classes • You don’t model objects which are beyond the scope of the system. • It is not usually necessary for a model to contain classes that represent the entire system. • You should remove class which is really a synonym of others. • Avoid too vague names which you cannot write description. • Avoid too specific names which are really a generalization. • Don’t tie up with physical inputs and outputs. CSC340

  5. Classes and attributes • “A member of staff has one grade at a time, but members may have several previous grades, and several members may have a same grade.” • “A grade has only one rate at a time, and each rate has a money value. Grade may have a rate attribute.” CSC340

  6. Classes and attributes • “A grade may have several previous rates, which suggests either that Grade has multiple rate attributes, or that Rate and Grade are distinct classes.” • “Rate must have a date attribute.” CSC340

  7. UML class diagram Where to put the attributes gradeStartDate And gradeFinishDate? CSC340

  8. Association class CSC340

More Related