land The Ootumlia Elections Commission is designing a system to manage elections. The system will manage elections for a variety of different elected bodies (e.g. school boards, city councils, etc.). Each elected body can have various positions (also called seats, e.g. mayor, councilor, etc.). Elections are scheduled for a specific date, and usually several (or all) positions are voted on together; however, sometimes there may be the need for a by-election (e.g. to elect a particular councilor because the incumbent - the previous person who held the position - has resigned). The system will keep track of candidates for each seat. The system will also record who is the incumbent for a seat, since newspaper reporters are interested in reporting whether incumbents have won again or lost. The system records the name and address of each candidate and incumbent. The system will also keep track of the list of eligible voters. Each voter can only vote for certain positions (e.g. a particular council seat that represents their System descriptions | 4 area). Each voter is also assigned to vote at a specific poll each poll has a number and is located in a polling station. The system records the name and address of each voter. Finally, the system will keep track of the number of votes for each candidate at each poll. However, under no circumstance will it record which voter voted for which candidate, nor whether a voter voted at all. (a) Correct class model, showing all attributes with correct types), associa- tions (with correct multiplicities, role names, and association names, where necessary) and generalizations. Marks will be given for effort, even if you do not have a perfect solution. Marks will be lost for the common types of mis- takes we talked about in class (e.g. poor generalizations, wrong multiplicity, etc.). [30 points) (b) A syntactically correct Umple model of the system. (5 points) (c) Each valid suggested requirements (under reasonable assumption of the system. (2 points) land The Ootumlia Elections Commission is designing a system to manage elections. The system will manage elections for a variety of different elected bodies (e.g. school boards, city councils, etc.). Each elected body can have various positions (also called seats, e.g. mayor, councilor, etc.). Elections are scheduled for a specific date, and usually several (or all) positions are voted on together; however, sometimes there may be the need for a by-election (e.g. to elect a particular councilor because the incumbent - the previous person who held the position - has resigned). The system will keep track of candidates for each seat. The system will also record who is the incumbent for a seat, since newspaper reporters are interested in reporting whether incumbents have won again or lost. The system records the name and address of each candidate and incumbent. The system will also keep track of the list of eligible voters. Each voter can only vote for certain positions (e.g. a particular council seat that represents their System descriptions | 4 area). Each voter is also assigned to vote at a specific poll each poll has a number and is located in a polling station. The system records the name and address of each voter. Finally, the system will keep track of the number of votes for each candidate at each poll. However, under no circumstance will it record which voter voted for which candidate, nor whether a voter voted at all. (a) Correct class model, showing all attributes with correct types), associa- tions (with correct multiplicities, role names, and association names, where necessary) and generalizations. Marks will be given for effort, even if you do not have a perfect solution. Marks will be lost for the common types of mis- takes we talked about in class (e.g. poor generalizations, wrong multiplicity, etc.). [30 points) (b) A syntactically correct Umple model of the system. (5 points) (c) Each valid suggested requirements (under reasonable assumption of the system. (2 points)
