CSC - Software engineering 1. Consider the following use cases for the business processes of the Department of Communication at the College that rents camera kits to student borrowers:

Use Case Name:	1. Register borrower
Description:
Student wishes to be registered at the department, and works with a secretary administrator to get the registration done.
Stakeholders:
Preconditions:
The administrator must be known to the department. The borrower must not have an account with the department.
Workflow:
The administrator provides the Clerk with his/her id and password. The Clerk verifies the identification information by looking up the administrators id information in the administrators page in the worker ledger and informs the administrator. The Clerk asks the administrator what kind of transaction he/she desires. The administrator informs the Clerk of his/her intention to register a new student borrower. The Clerk provides the administrator with a form on which to enter the following information about the student borrower: Banner ID, First name, Last name, Address, City, State, Zip, Phone number, E-mail address The administrator completes this form and hands it over to the Clerk. The Clerk fails to look up a page with this Banner ID in the borrower ledger using the Banner ID on this form. The Clerk creates a new borrower page and fills it with the information on this form. The Clerk files the borrower page into the borrower ledger. The Clerk informs the administrator of the successful registration of the borrower.
Results:
1. The student is registered with the department
Alternates:
The Clerk could not verify the identification information presented by the administrator. The administrator does not have all the information needed by the Clerk for the student.

Write a sequence diagram for this use case in the space below, taking care to ensure that the user (administrator) walks away happy and the data maintained by the business (i.e., the Borrower ledger) is also updated properly. NOTE: You can figure out the contents of a single Borrower page by carefully reading through the above use case. Note that the primary key of the Borrower ledger is the Banner ID field.

2. Here is another use case for a borrower renting a camera kit

Use Case Name:	2. Borrow a camera kit
Description:
The registered borrower rents a camera kit from the department
Stakeholders:
Preconditions:
The borrower knows his/her Banner id The worker knows his/her Banner id
Workflow:
The worker walks up to the Clerk and provides his/her id and password. The Clerk verifies the identification information by looking up the worker id information in the workers page in the worker ledger and ensuring that the password provided on this page matches the one provided by the worker. The Clerk asks the worker what kind of transaction he/she desires. The worker informs the Clerk of his/her intention to rent a camera kit to a borrower. The Clerk asks the worker for the borrowers Banner Id. The worker supplies the Clerk with the borrowers Banner Id. The Clerk uses the supplied Banner Id and retrieves the page of the borrower who has this Banner Id from the borrower ledger. The Clerk asks the worker for the barcode of the camera the borrower wishes to borrow. The worker provides the barcode of the camera to the clerk. The Clerk uses the supplied barcode and retrieves the page of the camera that has this barcode from the Item ledger. The Clerk computes a due date for the camera kit. The Clerk creates a new Rental page and writes the following information on it: Borrowers Banner Id, barcode of the camera, current date, due date, Banner Id of worker. The Clerk asks the worker for the barcode of a battery associated with this camera kit. The worker provides the barcode of the battery to the clerk. The Clerk uses the supplied barcode and retrieves the page of the battery that has this barcode from the Item ledger. The Clerk creates a new Rental page and writes the following information on it: Borrowers Banner Id, barcode of the battery, current date, due date, Banner Id of worker. The Clerk asks the worker for the barcode of a case associated with this camera kit. The worker provides the barcode of the case to the clerk. The Clerk uses the supplied barcode and retrieves the page of the case that has this barcode from the Item ledger. The Clerk creates a new Rental page and writes the following information on it: Borrowers Banner Id, barcode of the case, current date, due date, Banner Id of worker. The Clerk informs the worker of the due date for all these three items and asks for an OK. The worker conveys the OK message to the Clerk. The Clerk files the Rental pages corresponding to the three items above into the Rental ledger. The Clerk creates a receipt containing the Banner Id of the borrower, the barcodes of the 3 items borrowed, the current date and the due date and hands that to the worker.
Results:
The borrower has received a camera kit. Three new Rental pages are inserted into the Rental ledger
Alternates:
The Clerk could not verify the worker. The Banner Id of the borrower is not found in the Borrower ledger. The borrower does not agree to the due date and says so to the worker The borrower does not bring at least one of the three required items to the worker

Write a sequence diagram for this use case in the space below, taking care to ensure that the user (administrator) walks away happy and the data maintained by the business (i.e., in this use case, the Rental ledger) is also updated properly. NOTE: You can figure out the contents of a single Rental page from STEP 16 of the above use case. This ledger has an auto-generated primary key. Similarly, an Item page in the Item ledger has the item barcode as the primary key, and an item description to go with it.

3. Here is another use case for the borrower returning a camera kit

Use Case Name:	3. Return a camera kit
Description:
Return a camera kit borrowed previously
Stakeholders:
Preconditions:
The worker knows his/her banner id The borrower knows his/her banner id
Workflow:
The worker walks up to the Clerk and provides his/her id and password. The Clerk verifies the identification information by looking up the worker id information in the workers page in the worker ledger and ensuring that the password provided on this page matches the one provided by the worker. The Clerk asks the worker what kind of transaction he/she desires. The worker informs the Clerk of his/her intention to return a camera kit from a borrower. The Clerk asks the worker for the borrowers Banner Id. The worker supplies the Clerk with the borrowers Banner Id. The Clerk uses the Banner Id to retrieve all pages from the Rental ledger where the borrower id field matches this Banner Id and the DateReturned field on that page is NULL/empty. For all barcodes of the items in the kit the borrower wishes to return: The Clerk asks the worker for the barcode of one of the items of the kit to be returned. The worker provides the Clerk with the barcode of one of the items in the kit. The Clerk accesses the Rental that has the barcode provided in Step 8(b) in the Item id field in one of the Rental pages retrieved in Step 7 above. The Clerk writes the current date (todays date) into the DateReturned field on the Rental page identified for this barcode. For each Rental page in the collection created in step (7) above: The Clerk re-files the Rental page in the Rental ledger. The Clerk creates a receipt containing the Banner Id of the borrower, the barcodes of the 3 items borrowed, the date rented, the due date and the current date and hands that to the worker.
Results:
The borrowers kit has been returned. The Rental pages associated with the latest rental of this kit by the borrower have all been updated with a value for the DateReturned field.
Alternates:
The Clerk could not verify the worker. There were no Rental pages with NULL/empty DateReturned field found for the specified Banner Id of the borrower. The supplied barcode does not match the Item id field in any of the Rental pages retrieved for the borrower.

Write a sequence diagram for this use case in the space below, taking care to ensure that the user (administrator) walks away happy and the data maintained by the business (i.e., the Rental ledger) is also updated properly. NOTE: Step 10 above implies a loop yet another loop, maybe in the sequence diagram.