MELJUN CORTES Collaboration Diagrams

7/29/2019 MELJUN CORTES Collaboration Diagrams

1/13

COLLABORATION DIAGRAM

[Ang Bulilit Liga Athlete Record Maintenance System] Page 1

Successful Edit Athlete Record

Use Case Specification

1.2. Edit Athlete

Collaboration Diagram

DescriptionThis scenario describes one the main flow for club staff membersediting athlete records. In this scenario, a club staff member enters avalid user name and password, is identified as a member of the clubstaff, and is able to access the edit athlete user interface. It must benoted that a separate user interface for viewing an athlete record was

not provided, since the intended default of the athlete record viewwould be an non-editable window. A query is sent to the user if s/hewishes to edit the athlete record. When the user opts to edit the record,the user is allowed to change editable fields in the athlete record. Theuser subsequently enters the new data; the system checks if it iscomplete, and if all the data are valid. For this particular scenario, thedata is both complete and valid. As such, the EditAthlete class allowsthe data to be saved in the athlete record database.


2/13



Unsuccessful Edit Athlete Record


1.2. Edit Athlete


DescriptionThis describes a possible scenario wherein a member of the club staffis able to log-in successfully and access an existing athlete record. Atthis point, the user might attempt to save any changes that s/he madein the record. However, if the data entered is incomplete, or if someinvalid values are detected in some fields (i.e. alphanumeric characterswhere purely numeric characters are expected), the system returns anerror. Depending on user action after the error is noted (seesucceeding collaboration diagrams), the user may opt to return to theathlete record being edited. In this particular scenario, the user does

not choose to do anything, and the system exits.


3/13



Non-existent Athlete Record


1.2. Edit Athlete


DescriptionIn this scenario, a user is able to log-in successfully and access theAthleteRecordUI. At this point, it is possible for the user to enter a non-existent athlete name or athlete id. This may be a result of atypographical error; it is also possible that the athlete record does notyet exist.


4/13



Non-existent Athlete Record with enabled User Re-try


1.2. Edit Athlete


DescriptionThis is an elaboration of the previous scenario; here, the systemrecovers after the error is detected and asks the user if s/he would liketo enter another query. This procedure is repeated until the user entersa valid query, and proceeds in one of the previous scenarios, or whenthe user opts to cancel the operation.


5/13



Successful Add Athlete


1.1. Add Athlete


DescriptionThis scenario is a possible offshoot of the previous scenarios (non-existent athlete record). It may be possible in the system to provide anoption for members of the club staff (but not to coaches) to add anathlete record in the event that the athlete record does not exist. Thisfunctionality was added since the club staff are also responsible forcreating records. In this scenario, a member of the staff opts to createa new record. The system prompts the user to enter the relevant

athlete information. In this case, the information entered is bothcomplete and valid, and a new athlete record is saved in the database.


6/13



Unsuccessful Add Athlete


1.1. Add Athlete


DescriptionThis scenario is a possible offshoot of the previous scenarios (non-existent athlete record). It may be possible in the system to provide anoption for members of the club staff (but not to coaches) to add anathlete record in the event that the athlete record does not exist. Thisfunctionality was added since the club staff are also responsible forcreating records. In this scenario, a member of the staff opts to createa new record. The system prompts the user to enter the relevantathlete information. In this case, the information is either incomplete, ormay contain invalid data, and is not saved into the database.


7/13



Unsuccessful Club Staff Log-In


1.0. Maintain Athlete (a part of it)


DescriptionThis scenario may occur if a member of the club staff enters a non-existing user name, or an incorrect password. If the user does not optto try entering either fields again, the system exits.


8/13



Unsuccessful Club Staff Log-In with Repeated Log-In


1.0. Maintain Athlete (a part of it)


DescriptionThis scenario may occur if a member of the club staff enters a non-existing user name, or an incorrect password. In this scenario, the useropts to try again, and the procedure (i.e. that allows the user to repeatlog-in in case of a failure) is repeated until the user enters a valid username and password, or when the user decides to exit from the system.


9/13



Successful Edit Athlete Status


1.3. Edit Athlete Status


DescriptionThis scenario describes the basic flow of events for the successfulediting of an athlete's status. This particular functionality is a mainresponsibility of the coach, and a subset of the EditAthlete functionality.However, athlete status editing is not exclusive to the coach. In thisscenario, the coach enters a valid user name and password, enters thesystem, makes a successful query, and edits the athlete status fields.After this, the system checks if the entries are valid, and saves thechanges in the Athlete Status database. A parallel, alternative scenario(wherein the changes are not valid) is not included, because it is moreprobable that editing will be performed using a drop-down menu.


10/13



Non-existent Athlete Record




DescriptionThis scenario describes the possibility of entering a non-existent querythat may have resulted from a typographical error. The coach may optnot to enter another query, and the system exits.


11/13



Non-existent Athlete Record with Re-try




Description

This scenario describes the possibility of entering a non-existent querythat may have resulted from a typographical error. In this scenario, thecoach opts to enter another query. In the event that the query still doesnot exist, this cycle proceeds until the coach enters a valid query. Afterthis, the system would proceed through the main flow of events.


12/13



Unsuccessful Coach Log-in


1.0. Maintain Athlete (main)


Description

This scenario describes the possibility of a coach entering an invalidusername or password. Upon being prompted for log-in repetition, thecoach may opt not to re-enter log-in details, in which case the systemexits.


13/13


[Ang Bulilit Liga Athlete Record Maintenance System]

Unsuccessful Coach Log-in with re-try


1.0. Maintain Athlete (main)


Description

This scenario describes the possibility of a coach entering an invalidusername or password. Upon being prompted for log-in repetition, thecoach may opt to re-enter log-in details. The cycle will repeat until thecoach enters a valid username and password, or until s/he opts toterminate the procedure.

Maria Pamela C. David

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

Page 13

Documents

MELJUN CORTES Collaboration Diagrams