As shown in bold letters in the figure above, RALTeam Member extends RALTeam Core to include conditions for team selection. To this end, it adds a new type of expression TeamMemberExpr that uses a MembershipConstraint to specify mandatory team members, and optionally the team role type(s) that they must play. Specifically, it allows specifying (i) a concrete person, resulting in sentences such as TEAM WHOSE MEMBERS INCLUDE Marc, or TEAM WHOSE MEMBERS INCLUDE Marc PLAYING TEAM ROLE TYPE Coordinator; (ii) a number of people, e.g. TEAM WHOSE MEMBERS INCLUDE EXACTLY 2 PEOPLE PLAYING TEAM ROLE TYPE Implementer; or (iii) a certain number of people with specific characteristics defined with PeopleSelection, which include:
- properties specified with a RAL ODDAH expression, e.g. TEAM WHOSE MEMBERS INCLUDE ONLY PEOPLE WHO HAVE UNIT DoG specifies that all the member of the team must belong to the DoG, where HAVE UNIT DoG comes from RAL ODDAH and unit refers to an organisational unit. The link with RAL involves all the RAL expressions but one (IsAssignmentExpr).
- people that do (or do not) belong to other teams defined by a SelectTeamExpr, e.g. TEAM WHOSE MEMBERS INCLUDE BETWEEN 1 AND 2 PEOPLE WHO ARE MEMBERS OF (TEAM Perm_AT_1), or TEAM WHOSE MEMBERS INCLUDE AT LEAST 1 PERSON WHO IS NOT MEMBER OF (TEAM Perm_RE_2).
The CreatorConstraint is also extended to provide more details about the team creator by means of a RAL expression.
