Issue: How should the Graphical User Interface (GUI) screen for a Member appear to the user?

Discussion: As normal, the ID field is visible but not editable.  The First name and last name fields are also visible but not editable.  The Nickname may be left blank, in which case the names entered into the Bowler object will be used.  The Team Number, Team Position, and Bowler ID fields are visible but not editable.  The Team information comes from the Teams screen.  The Bowler ID corresponds to the matching Bowler object for this Member.  The Entering fields can be edited, however, they will be disabled if the Entering Average Used is No on the League screen.

The Find button will bring up a list of Members of this League, so the user can go directly to that Member for editing.  The remove option, with a confirmation dialog, removes the Member from this League, but not the Bowler.  The Add button allows a user to create a new Member for this League.  The user is first prompted to select the matching Bowler for this new Member, then the member object is populated and the user may edit the information.  It is possible for a single Bowler object to be used more than once for Members of a League.  This can happen if a Member changes delivery during the season.  Each delivery method must have separate statistics kept, so in effect, it is a different Member, but the same Bowler.

Embedded within the Member object are references to a Team object, which provides the Team number and Team position information.  Also embedded is a reference to the matching Bowler object, which provides the Bowler ID and name information.  These are not visible on the screen.

Conclusion: Here is what I envision the Member screen to look like:

Season Name
League Name

ID
First Name
Last Name
Nickname
Personal Phone
Sanction ID
Delivery
Team
Team Position
Entering Pins
Entering Games











Here is what I envision the Select Member screen to look like:
   
 
Season Name
League Name
Select Member: