Consider the following scenario from a library Information system and consider the associated SSD and domain model that will follow.

Actor Actions	System Response
1. This use case begins when an online registered user selected to a movie to rent online. 2. Patron arrives at a checkout with library resources (e.g. books, videos, tapes,) to borrow. Some of the resources can be borrowed for free, while others will have a borrowing fee.
3. The library patrons present their membership identification to the library staff, who enters it into the system.	4. Presents membership information, and status of loans (usually nothing on loan, and no outstanding fines).
5. For each library resource, the library staff records the item identification into the system.	6. Presents accumulating list of resources titles, due dates. The standard due date is 3 weeks from today.
7. Library staff informs library patrons of total borrowing fee, and asks for payment.
8. Library patron pays cash to library staff.
9. Library staff records payment into system.	10. Generates receipt and loan report.
11. Library staff gives receipt and loan report to library patron, who then leaves with the rental resources.

(1) Bounded by the above scenario and the domain model, write the operation contracts for the two operations:

- confirmMembership(ID)

- recordResourceBorrowing(ID)

(2) Using the confirmMembership operation contract as a starting hint, draw the UML sequence diagram. Annotate every message with the GRASP (Expert, Creator, and so on) and/or other pattern that justifies it.

(3) Using the recordResourceBorrowing operation contract as a starting hint, draw the UML sequence diagram. Annotate every message with the GRASP (Expert, Creator, and so on) and/or other pattern that justifies it.