Example use case create a user account on hospital

This preview shows page 27 - 30 out of 44 pages.

Example : Use Case: Create a User Account on Hospital Web Portal Actor: Patient Scenario: 1. Navigate to Web Portal 2. Click the register link
01.04.2019 CS 2401 - AY2019-T3: Week 3 Discussion Question 28/44 3. Enter username (email) a. Returns error if email is not valid 4. Enter password a. Returns error is length is not 8 digits or more. b. Returns error if it does not contain both upper and lower case. c. Returns error if it does not contain a number or special character. 5. Enter password again a. Returns error if password does not match. 6. Clicks Register Button a. Returns Success Page if account does not exist. b. Returns Failure Page if the account already exists. i. Prompted to reset password. 7. Client can log into account. References: 1. Ivan Marsic (2012). Software Engineering: Why Software Engineering is Di´cult . Retrieved from: - SE_marsic.pdf 294 words Permalink | Show parent | Reply Re: Week 3 Discussion Question by Alex David - Wednesday, 20 February 2019, 8:57 AM You have done well with your post and I am able to grab a new idea from it, thanks for sharing. 21 words Permalink | Show parent | Reply Re: Week 3 Discussion Question by Mohammad Maysam - Wednesday, 20 February 2019, 6:06 PM
01.04.2019 CS 2401 - AY2019-T3: Week 3 Discussion Question 29/44 Hi Dwayne, I like your post. It is concise, precise and well cited. Thank you for your contribution to this week's discussion forum. Thank You, MM 26 words Permalink | Show parent | Reply Re: Week 3 Discussion Question by Timothy Frank - Tuesday, 19 February 2019, 5:51 PM A single use case can consist of a few di±erent de³nitions which can get confusing depending on context. but it usually signi³es a single change in either the semantics of a system (usually a change in the way a system would normally operate under normal use) or a di±erent implementation of the same system such that the 'logic' behind how it works di±ers from the original design (such as a motion sensor activating a door instead of a switch or remote control). A scenario may consist of the same system being used in another environment (a garage door for a house compared with a retailer's loading dock door) and may have di±erent expectation for operation from the customer, such as assuming that the driver does not have a remote control to the door and therefore must be opened from an employee working inside of the facility. A scenario may also be the same system working in the same (or di±erent) environment with a di±erent combination of use cases. For example, for security and accessibility reasons you obviously wouldn't want to use a garage door for every door in your house, you would probably want your front door to lock with a key and be opened by hand. By that same standard, someone with a handicap may have di´culty opening the door and would rather prefer a door that would open at the press of a remote control. Examining a di±erent scenario may reveal di±erent use cases that would not have been possible with one system design or implementation

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture