Computer Science Software Engineering Slide 1

LMS

Response to requirements• “We gave them what they asked for, so we are not to

blame if the system is not being used”

Clients may leave out requirements that are “obvious”

Computer Science Software Engineering Slide 2

LMS Requirements questions Interface? GUI. Online search? Library number required? Unique id? Expiration? Electronic interlibrary loans? Patron’s use of research databases

• Limits?

• Cost tracking?

• Does patron status determine which resources can be used?

Computer Science Software Engineering Slide 3

LMS Requirements questions Should the system advise staff on potential books

to retire? Criteria? How do we notify staff? How long is a requested resource held before it is

returned to circulation? Are overdue fees the same for all types of

resources? What indexes and databases are provided to

library patrons? …

Computer Science Software Engineering Slide 4

Supported activity list

• Allow library staff to perform administrative tasks• Change status of book• Check if patron has valid library id number

• Validating that a patron has an up-to-date library number, no resources > 2 weeks, not too many resources checked out

Computer Science Software Engineering Slide 5

Supported activities Giving library number to patrons Deleting expired library numbers and patrons. A

library number is valid until a student graduates. A library number is valid until faculty/staff terminate employment at college

Checking out books for various loan periods.• Students – 4 weeks, faculty – 3 months, staff – 1 year

Checking out other resources. 1 week only. References cannot be checked out

Computer Science Software Engineering Slide 6

Supported activities Checking in resources Change status of resource from “reshelve” to

“available” Putting a resource owned by the library on

reserve. Faculty and library staff. Reserved resources cannot be checked out

Putting an item not owned by library on reserve. These items cannot be checked out

Computer Science Software Engineering Slide 7

Supported activities Requesting a resource for a patron. Requested

resource will be held for two weeks for a patron. If not checked out within two weeks, returned to circulation

Searching online catalog by author, subject, keyword, resource title, or Dewey call number

Interacting with online research resources such as Infotrac, Wilson’s Guide to Periodicals, and First Search

Computer Science Software Engineering Slide 8

Supported activities Adding a resource to the online catalog Deleting a resource from the online catalog Generating lists of overdue resources Generating form letters for patrons with resources

more than two week overdue Determining the fee amount for each overdue

resource. $0.25/day for each resource to a maximum of $5.00 per resource

Computer Science Software Engineering Slide 9

Supported activities Linking to the online catalogs of other libraries

for searching Generating interlibrary loan requests

Computer Science Software Engineering Slide 10

HCI Two modes

• Public• Search catalog, databases, indices

• Private (Staff) – password protected• View library record of any patron

• Add/Delete resources

• Work productivity information

• Request lists of overdue items

• Check in /Check out resources

Computer Science Software Engineering Slide 11

Solved Problems List No information

Computer Science Software Engineering Slide 12

Information Source List Other libraries

• Need to query UNLV’s collections

Online research resources• InfoTrac, Wilson’s guide to Periodicals, and First Search

Existing online catalog• Convert (one-time) existing catalog to new format

Existing patron database• Convert (one-time) existing database to LMS format

Computer Science Software Engineering Slide 13

Information Source List Student records Database

• Admissions, graduations, … Affect patron addition/deletion

Employee Database• Employ, retire, dismiss, … Affect patron addition/deletion

Computer Science Software Engineering Slide 14

Information requesting entities Other libraries …

Computer Science Software Engineering Slide 15

Automated Checks and Balances All dates must be checked for validity (Feb 31,

2001) should not be allowed Publishing dates for resources cannot be in the

future Only students/employees of College can be

patrons

Computer Science Software Engineering Slide 16

Security/Fault tolerance Passwords for staff What happens if system goes down?

• Paper/pencil records until system comes up again

Computer Science Software Engineering Slide 17

Interoperating systems list ?

Computer Science Software Engineering Slide 18

Present Info capacity and growth How many resources, how much memory? How fast is the library growing?

Computer Science Software Engineering Slide 19

Projected time frame Ready for Fall 2002

Computer Science Software Engineering Slide 20

Prioritization of Requirements Which requirements will be done first? What SDP will you follow?

Computer Science Software Engineering Slide 21

Ethical Concerns System keeps track of past check-outs of patrons

• If subpoena, who has access to this history?

• What if patron is a minor?

• …

Does our system use internet search engines?• Should we allow unrestricted access?