Use case name: The Turing Award winners
Actors:
The persons who won the Turing prize (1966--2018)
visitors
Triggers:
An individual who has made an important contribution to the cause of computing
Preconditions:
Scientists are engaged in computers
Computer scientists submit their papers to the American computer society
Certified by the American computer association
Post-conditions:
Update the database of Turing award winners
A prize is awarded to the person who win the Turing prize
Normal Flow:
1. User access database
2. The winner and year of the Turing award will be displayed
3. Users will confirm which winners based on the information displayed in the system (name or year)
4. The system will show the winner’s information that selected by the user
5. The system records the number of users by each winner
6. User exit system
7. The system returns to its original state
Alternate Flows:
3A1: The user enters the name and year. If the user wants to continue looking for another Turing award winner, this alternate flow also applies.
1. The system returns the initial interface
2. Users again select the Turing prize winners they are looking for
3. System display information
3A2: If the user enters an incorrect name, the system retrieves the winner whose name is similar
1. System retrieval failed, prompting the user to change
2. The system returns the initial interface
3. The user reenters the name
4. The system displays the information again
UML class diagram: I have four classes in my UML diagram. The winners are the winners who have been recorded in the system, including the year and the category. The second is the winner's information. In this class, information about the winner you selected will appear. The third class tells the user the nationality of the winner. The last class is about the research subject of the winner and some information about bibliometrics for instance: publication years, citation count and so on.
