MELJUN CORTES Sequence Diagram Interface Design Document

7/29/2019 MELJUN CORTES Sequence Diagram Interface Design Document

1/18

SEQUENCE DIAGRAM OF SCREEN CLASSES

Successful Club Staff Log-in

Sequence Diagram

Description1. A member of the club staff enters his/her username and

password in the LogIn screen.2. S/he subsequently clicks the okayButton.3. Control is passed to the CheckUser class, which checks if the

username and password are valid.4. The entered data are checked against a database of users,

their usernames, and the corresponding password5. If the username exists, and the password entered is valid, the

FindAthlete screen is opened.

Ang Bulilit Liga Athlete Record Maintenance System Page 1


2/18


Unsuccessful Club Staff Log-in

Sequence Diagram

Description1. A member of the club staff enters his/her username and

password in the LogIn screen.2. S/he subsequently clicks the okayButton.3. Control is passed to the CheckUser class, which checks if the


their usernames, and the corresponding password5. If the username does not exist or the password is not valid for

the username, an error is detected6. An error message is displayed.7. The user clicks okayButton.8. The dialog box containing the error message is closed, and

the UserLogIn screen appears again.



3/18


Successful search and retrieval of a single athlete record

Sequence Diagram

Description1. A member of the club staff or a coach enters his/her search

criteria in the FindAthleteUI fields2. S/he subsequently clicks the findAtlhleteButton.3. Control is passed to the AthleteRecordMaintenance class,

which checks for matches using the given search criteria4. The entered data are checked against a database of

containing athlete membership data5. A record is found, and a message is relayed to the control

class

6. A list containing the records that match the query is displayedin the matchList within the FindAthleteUI

7. The user selects an athlete from the list by double-clicking onit

8. The athlete record is retrieved from the database9. The corresponding record is displayed on a new screen

(AthleteRecordUI)



4/18


Unsuccessful athlete record retrieval

Description1. A member of the club staff enters his/her search criteria in the

FindAthleteUI fields2. S/he subsequently clicks the FindAthleteButton.3. Control is passed to the AthleteRecordMaintenance class,


containing athlete membership data5. No matches are found, and a message indicating this error is

relayed to the control class6. An error message is displayed, indicating that no matches

were obtained7. The user clicks the okay button8. The user is asked if s/he wants to add an athlete record9. The user opts not to, and clicks the NoButton

10. The dialog box displaying the error message is closed, andthe FindAthleteUI screen appears again.



5/18


Successful search and retrieval of multiple athlete records

Description1. A member of the club staff selects one of seven possible

athlete status as the search parameter2. S/he subsequently clicks the FindAthleteButton.3. Control is passed to the AthleteRecordMaintenance class,

which checks for matches using the given athleteStatus4. All athleteStatus fields of records are checked against the

user defined status5. One or more records is/are retrieved, and a message is

relayed to the control class6. A list containing the records that match the query is displayed

in the matchList within the FindAthleteUI

7. The user selects an athlete from the list by double-clicking onit; it is also possible for the user to make a multiple selectionby pressing the Ctrl key during selection. The user thendouble clicks the selection, and the records are returned

8. The athlete record(s) is/are retrieved from the database9. The corresponding record(s) is/are displayed on a new

screen (AthleteRecordUI)



6/18


Unsuccessful search and retrieval of multiple athlete records

Description1. A member of the club staff or a coach selects one of seven

possible athlete status as the search parameter2. S/he subsequently clicks the FindAthleteButton.3. Control is passed to the AthleteRecordMaintenance class,

which checks for matches using the given athleteStatus4. All athleteStatus fields of records are checked against theuser defined status

5. No records are found that match the given status (i.e. none ofthe athletes are injured)

6. A message indicating that no matches were found is returnedto the user

7. The user clicks the okayButton8. The dialog box containing the message is closed, and the

FindAthleteUI screen appears again



7/18


Successful Update of Single Athlete Record

Description1. A member of club opts to edit the athlete record that s/he

retrieved and clicks the EditButton

2. The choice to edit is relayed to the control class3. This activates the EditAthleteUI4. The EditAthleteUI is displayed; since the user is a member of

the club staff, all text fields are editable5. The user enters information on the text fields6. The user may also change the athlete status via the

AthleteStatusComboBox7. The user then selects the new status of the athlete, if

applicable8. S/he subsequently chooses to save the changes9. The information entered is checked by the control class,



8/18


which would check the validity and completeness of theinformation entered.

10. If all entries are valid, it returns a message to the

EditAthleteUI that the data is valid.11. A SaveConfirmationMessage dialog box is displayed12. The user clicks yes13. This closes the dialog box and returns true14. The changes are saved to the database15. A message is sent to the controller that all records have

been updated16. The AthleteRecordUI is displayed again.



9/18


Unsuccessful Update of Single Athlete Record

Description1. A member of club opts to edit the athlete record that s/he

retrieved and clicks the EditButton2. The choice to edit is relayed to the control class3. This activates the EditAthleteStatusUI4. The EditAthleteStatusUI is displayed; since the user is a

member of the club staff, all text fields are editable5. The user enters information on the text fields6. The user may also change the athlete status via the

AthleteStatusComboBox7. The user then selects the new status of the athlete, if



10/18


applicable8. S/he subsequently chooses to save the changes9. The information entered is checked by the control class,

which would check the validity and completeness of theinformation entered.

10. Fields are found to contain incomplete information, invalidentries, or both, and the error is detected.

11. An Error Message is displayed12. The user clicks the okayButton13. This closes the dialog box and results in the restoration of

the AthleteRecordUI



11/18


Successful Add Athlete



12/18



FindAthleteUI fields

2. S/he subsequently clicks the FindAthleteButton.3. Control is passed to the AthleteRecordMaintenance class,




were obtained7. The user clicks the okay button8. The user is asked if s/he wants to add an athlete record

9. The user opts to do so, and clicks the YesButton10. The choice to add an athlete is relayed to the control class11. The control class communicates with the AddAthleteUI12. The AddAthleteUI subsequently appears13. The user types information into the text fields14 16. The user may also opt to change default values of the

athlete status and athleteGender.17. S/he subsequently chooses to save the record.18. The information is passed to the control class, where these

are checked for completeness and validity.19. A message is returned that the information is complete.

20. A SaveConfirmationMessage now appears.21. The user clicks the YesButton.22. This returns true23. The athlete record is saved to the database.24. A message is returned that the database update has been

completed25. Another message is relayed to the controller26. This results in the reappearance of the AthleteRecordUI.



13/18


Unsuccessful Add Athlete



14/18



FindAthleteUI fields

2. S/he subsequently clicks the FindAthleteButton.3. Control is passed to the AthleteRecordMaintenance class,




were obtained7. The user clicks the okay button8. The user is asked if s/he wants to add an athlete record

9. The user opts to do so, and clicks the YesButton10. The choice to add an athlete is relayed to the control class11. The control class communicates with the AddAthleteUI12. The AddAthleteUI subsequently appears13. The user types information into the text fields14 - 16. The user may also opt to change default values of the

athlete status and athleteGender.17. S/he subsequently chooses to save the record.18. The information is passed to the control class, where these

are checked for completeness and validity.19. An error message is returned, indicating that some of the

information are either incomplete, invalid, or both.20. The error message is displayed21. The user clicks the okayButton22. This closes the dialog box, and results in the reappearance

of the AddAthleteUI.



15/18


Successful Coach Log-in

Sequence Diagram

Description1. A coach enters his/her username and password in the LogIn

screen.2. S/he subsequently clicks the okayButton.3. Control is passed to the CheckUser class, which checks if the


their usernames, and the corresponding password5. If the username exists, and the password entered is valid, the

FindAthlete screen is opened.



16/18


Unsuccessful Coach Log-in

Sequence Diagram

Description1. A coach enters his/her username and password in the LogIn

screen.2. S/he subsequently clicks the okayButton.3. Control is passed to the CheckUser class, which checks if the


their usernames, and the corresponding password5. If the username does not exist or the password is not valid for

the username, an error is detected6. An error message is displayed.

7. The user clicks okayButton.8. The dialog box containing the error message is closed, and

the UserLogIn screen appears again.



17/18


Successful EditAthleteStatus

Description

1. A coach opts to edit the athlete record that s/he retrieved andclicks the EditButton

2. The choice to edit is relayed to the control class3. This activates the EditAthleteStatusUI4. The EditAthleteStatusUI is displayed; since the user is a

coach, only the athlete status is editable.

5. The user changes the athlete status via theAthleteStatusComboBox6. The user selects the new status of the athlete7. S/he subsequently chooses to save the changes8. A SaveConfirmationMessage dialog box is displayed; there is

no need for checking, since all possible changes are valid.9. The user clicks yes10. This closes the dialog box and returns true11. The changes are saved to the database12. A message is sent to the controller that all records have

been updated



18/18


13. The AthleteRecordUI is displayed again.

Maria Pamela C. David

Submission Details:Version: 1.0Date of Submission: 01/28/2006


MELJUN CORTES Sequence Diagram Interface Design Document

Documents

Transcript of MELJUN CORTES Sequence Diagram Interface Design Document