Making a Use Case, please help! i would really appreciate it, and would be of great help.?

an example it at the top. ^

how do i Create a set of use cases for an online university

registration system. The system should enable the

staff of each academic department to examine the

courses offered by their department, add and

remove courses, and change the information about

them (e.g., the maximum number of students permitted).

It should permit students to examine currently

available courses, add and drop courses to

and from their schedules, and examine the courses

for which they are enrolled. Department staff

should be able to print a variety of reports about the

courses and the students enrolled in them. The system

should ensure that no student takes too many

courses and that students who have any unpaid fees

are not permitted to register. (Assume that a fees

data store is maintained by the university’s financial

office, which the registration system accesses but

does not change).

or

Create a set of use cases for the following system: A

Video Store (AVS) runs a series of fairly standard

video stores. Before a video can be put on the shelf,

it must be catalogued and entered into the video

database. Every customer must have a valid AVS

customer card in order to rent a video. Customers

rent videos for three days at a time. Every time a

customer rents a video, the system must ensure that

this customer does not have any overdue videos. If

so, the overdue videos must be returned and an overdue

fee paid before the customer can rent more

videos. Likewise, if the customer has returned overdue

videos, but has not paid the overdue fee, the fee

must be paid before new videos can be rented. Every

morning, the store manager prints a report that lists

overdue videos; if a video is two or more days overdue,

the manager calls the customer to remind him

or her to return the video. If a video is returned in

damaged condition, the manager removes it from the

video database and may sometimes charge the customer

or

Create a set of use cases for a university library borrowing

system. (Do not worry about catalogue

searching, etc.) The system will record the books

owned by the library and will record who has borrowed

what books. Before someone can borrow a

book, he or she must show a valid ID card that is

checked to ensure that it is still valid against the

student database maintained by the registrar’s office

(for student borrowers), the faculty/staff database

maintained by the personnel office (for faculty/staff

borrowers), or against the library’s own guest database

(for individuals issued a “guest” card by the

library). The system must also check to ensure that

the borrower does not have any overdue books or

unpaid fines before he or she can borrow another

book. Every Monday, the library prints and mails

postcards to those people with overdue books. If a

book is overdue by more than two weeks, a fine will

be imposed and a librarian will telephone the borrower

to remind him or her to return the book(s).

Sometimes books are lost or are returned in damaged

condition. The manager must then remove

them from the database and will sometimes impose

a fine on the borrower.