Create the following:

- A class diagram showing the participant screen

- A sequence diagram showing the screen flow

- A class diagram update of your participant screens with navigation paths

for the use case Update Account.

Use case name: Update Account Summary: The Update Account use case allows a User to update the information maintained in his or her account. If new credit card information is entered, the system attempts to pay any pending payment notices via the Credit Service Bureau using the entered information. Actor: Registered User Precondition: Registered User is signed in (see the Sign In use case as shown below) Steps 1. This use case starts when a registered user selects to update the information maintained in his/her account 2. The System presents the existing information in an updatable form. 3. The User performs the updates and submits the new account information. 4. The System update the User's account. 5. The use case ends. Alternatives A1. Occurs at Step 3. If a new credit card information is entered 1. The system attempts to pay any pending payment notices via the Credit Service Bureau using the entered information. 2. The System update the User's account. 3. The use case ends. Postcondition: User account information was updated.

Use case name: Sign In Summary: The Sign In use case allows the User to identify him- or herself to the system. If the User already has an account in the system, the User supplies a username and password for authentication purposes. If the User does not have an account in the system, the system gives the User the opportunity to create one (see the Create Account use case). All sign in attempts, whether successful or not, are logged. If the User has pending payment notices, the system informs the User that payment for the notices must be made before the User can participate in any auction (as either the Buyer or the Seller). Actor: User Precondition: System Main page is shown Steps 1. This use case starts when a User supplies a username and password for signing-in. 2. The system presents the user his/her account information including all his currently open auctions (Seller) and provide access account management functions. 3. If the User has pending payment notices, the system informs the User that payment for the notices must be made before the User can participate in any auction (as either the Buyer or the Seller). 4. The System logs a succesful login attempt. 5. The use case ends. Alternatives A1. Occurs at step 1. If the entered username/password doesn't match a registered user. 1. The System notifies the user of the wrong username/password entry. 2. The System logs a failed login attempt. A2. Occurs at step 1. If the user chooses to register 1. Include use case Create Account 2. Resume at Step 2. Postcondition: Registered User is signed in

Participant Screens screen screen Auction System Screen Sign In browse catalog ( create account ( ) user status msg navigate to ( display user not found msg ( ) sign in ( ) screen User Information input form sign In Form user name payments status msg password email navigate to ( display pending payment msg ( ) user name password submit ( ) o..1 compartment -Credit Card Info compartment Auction Informations type start date number expiry month expiry year name on card end date start time end time minimum bid category name title description street number unit number street city country postal code Participant Screens screen screen Auction System Screen Sign In browse catalog ( create account ( ) user status msg navigate to ( display user not found msg ( ) sign in ( ) screen User Information input form sign In Form user name payments status msg password email navigate to ( display pending payment msg ( ) user name password submit ( ) o..1 compartment -Credit Card Info compartment Auction Informations type start date number expiry month expiry year name on card end date start time end time minimum bid category name title description street number unit number street city country postal code