### Determining the size of a project

The following criteria will be used to determine whether the size of a project is appropriate for a team.

- Size of the Requirements (Project Assignment #3). Count the
number of actors, use cases, inclusions, alternate flows and steps in
your use cases. In other words, count 1 point for each actor, 1 point
for each use case, 1 point for each step in a use case and 1 point
when one use case is included in another or is an alternate flow of
another. The steps of the included use case should be counted only
for the use case where it appears explicitly and not in any use cases
that include it. The total number of points must be 10 times the
number of students in the team.
- Size of the Design (Project Assignment #4). Count the number of
classes, enumerations, attributes, associations, association classes
and subclass relationships. Each of these constructs counts 1 point,
except that a many-to-many association and a multivalued attribute
counts 2 points. An association class counts only if it is nontrivial
(e.g., has an attribute). The total number of points must be 10 times
the number of students in the team.
- Size of an interface (Project Assignment #5). Count the number of
slots (e.g., data entry boxes, selection menus, radio buttons) of a
GUI or the number of variables in OData commands. Each of these
counts 1 point. The total number of points must be 10 times the
number of students in the team.

The posted Requirements example has approximately 125 points.