Deliverable 5.2 System Requirements Document

1,097 views

Published on

  • Be the first to comment

  • Be the first to like this

Deliverable 5.2 System Requirements Document

  1. 1. Automated Media Asset Management System Software System Requirements Document Deliverable 5.2 Page 1 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  2. 2. 1 INTRODUCTION....................................................................................................................................... 4 2 FEASIBILITY STUDY AND RISK ANALYSIS..................................................................................... 4 2.1 FEASIBILITY STUDY.................................................................................................................................... 4 2.1.1 Structural Impact Assessment ..................................................................................................4 2.1.2 Materials Procurement.................................................................................................................. 5 2.1.3 Manpower Impact Assessment.......................................................................................................5 2.1.4 Cost Assessment.............................................................................................................................5 2.1.5 Benefits.......................................................................................................................................... 5 2.2 RISK ANALYSIS..........................................................................................................................................5 2.2.1 Project Risk....................................................................................................................................6 2.2.2 Product Risk...................................................................................................................................6 2.2.3 Business Risk................................................................................................................................. 7 2.2.4 Risk Profile ................................................................................................................................... 7 2.2.5 Risk Planning ...............................................................................................................................7 3 USER REQUIREMENTS...........................................................................................................................9 3.1 FUNCTIONAL REQUIREMENTS......................................................................................................................9 3.1.1 Search Catalog............................................................................................................................ 9 3.1.2 Check-out Asset........................................................................................................................... 9 3.1.3 Check-in Asset............................................................................................................................. 9 3.1.4 Overdue Notice............................................................................................................................ 9 3.1.5 Renew Check-out......................................................................................................................... 9 3.1.6 Hold Asset..................................................................................................................................... 9 3.1.7 Reserve Placement Request...................................................................................................... 10 3.1.8 Reports...................................................................................................................................... 10 3.1.9 Catalog Management................................................................................................................10 3.1.10 Maintain Patron........................................................................................................................10 3.2 NON-FUNCTIONAL REQUIREMENTS............................................................................................................10 3.2.1 User Friendly Interface............................................................................................................... 10 3.2.2 Speed............................................................................................................................................10 3.2.3 Volume....................................................................................................................................... 10 3.2.4 Accessibility............................................................................................................................... 10 4 ARCHITECTURE DESIGN.................................................................................................................... 11 5 SYSTEM REQUIREMENTS................................................................................................................... 12 5.1 USE CASE DIAGRAMS...............................................................................................................................12 5.1.1 Shared Use Cases........................................................................................................................ 12 5.1.2 Staff-only Use Cases.................................................................................................................... 13 5.2 USE CASE DESCRIPTIONS.......................................................................................................................... 13 5.2.1 Search Catalog............................................................................................................................ 13 5.2.2 Check-in Asset............................................................................................................................. 14 5.2.3 Check-out Asset........................................................................................................................... 14 5.2.4 Hold Asset.................................................................................................................................... 14 5.2.5 Reserve Asset Request..................................................................................................................15 5.2.6 Review Reserve Asset Request..................................................................................................... 15 5.2.7 Renew Check-out......................................................................................................................... 15 5.2.8 Staff Login....................................................................................................................................16 5.2.9 Staff Logout..................................................................................................................................16 5.2.10 Catalog New Asset..................................................................................................................... 16 5.2.11 Add Patron.................................................................................................................................16 5.2.12 Update Patron........................................................................................................................... 17 5.2.13 Delete Patron.............................................................................................................................17 5.2.14 Generate Reports....................................................................................................................... 17 Page 2 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  3. 3. 5.2.15 Overdue Notice.......................................................................................................................... 17 6 SYSTEM MODELS...................................................................................................................................19 6.1 SEMANTIC DATA MODEL.......................................................................................................................... 19 6.2 DATA FLOW MODELS...............................................................................................................................20 6.2.1 Catalog Search............................................................................................................................ 20 6.2.2 Asset Checkout.............................................................................................................................21 6.2.3 Asset Check-in............................................................................................................................. 21 6.2.4 Media Asset Overdue................................................................................................................... 23 6.2.5 Asset Check-in/Renewal...............................................................................................................24 6.2.6 Asset Hold.................................................................................................................................... 25 6.2.7 Asset Reserve Placement............................................................................................................. 26 6.2.8 Report Generation....................................................................................................................... 27 6.2.9 Catalog Management...................................................................................................................28 6.2.10 Catalog Update..........................................................................................................................29 6.2.11 Patron Add and Update............................................................................................................. 30 6.2.12 Patron Delete.............................................................................................................................31 7 GLOSSARY............................................................................................................................................... 32 Page 3 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  4. 4. 1 Introduction This document comprises Deliverable 5.2 for the AMAMS Development Project. It covers feasibility and risk analysis, user requirements, system architecture, and system models. 2 Feasibility Study and Risk Analysis This feasibility study was carried out by the project assessment department of the Alpha University in concert with the AMAMS project technical team. This report seeks to assess the practicability of the development of an Automated Media Asset Management System for the Alpha University. The University has determined that it requires such a system and seeks a study of the practicability and risk profile of such a project. The report is split into two sections 1. Feasibility study 2. Risk profile analysis. 2.1 Feasibility Study The principal requirements desired of the AMAMS by the University are: a) Comprehensive database management. b) Remote access from within the University campus . The feasibility of the project was examined in five broad areas 1. Structural impact assessment 2. Materials procurement 3. Manpower impact assessment 4. Cost assessment 5. Benefits 2.1.1 Structural Impact Assessment The AMAM system, due to its nature shall require the procurement of several high-tech devices. These devices by their nature will require specialized housing and support systems. The server and database shall require a) 225sq. feet of space b) 1000 feet of wiring c) 15 MW standby power system Installation of the system shall require the mounting and connection of transmission devices within the university campus. This will require a minimal amount of earth moving work. As the University structures are new, space for the hardware required is Page 4 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  5. 5. not at a premium. 2.1.2 Materials Procurement The materials requirements that have been identified are computers, servers, and database systems. All are readily available and shall be procured through the University’s procurements process. It is not expected that future hardware and software requirements for the project will be unavailable. 2.1.3 Manpower Impact Assessment The manpower that will be responsible for managing the AMAM system will have to be trained in operating the system. The available manpower currently has the pre-requisite training in handling automated technology systems. The project will necessitate the hiring of on-site maintenance personnel who shall be responsible for maintaining the system hardware after installation. 2.1.4 Cost Assessment The cost implication of the project can be split along two lines a) Hardware procurement cost. b) System development and installation cost estimates. Item Estimate of Costs Server Hardware (x1) $3,000 UPS Hardware (x1) $800 Staff Workstations (x4) $7,000 Bar Code Readers (x4) $1,800 Patron Workstations (x8) $10,000 LAN Hardware $1,500 LAN wiring labor $5,000 Software Licenses $7,500 System Development $55,000 Administration & Overhead $5,000 Total Estimated Costs: 2.1.5 Benefits The system when fully operational is expected to provide speedy, convenient and efficient media asset management to the university community. The system will encourage the use of the library and its media assets by its user friendliness. It is believed that the project will be of immense benefit to the university. 2.2 Risk Analysis The risk profile of the project has been analyzed along three broad lines Page 5 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  6. 6. 1. Project risk 2. Product risk 3. Business risk 2.2.1 Project Risk The possible risks taken into account are: 1 System Requirements alterations. 2 Project size under-estimation. 3 Staff change. 4 Management change. 5 Hardware unavailability. PROJECT RISK PROBABILITY S/NO RISK NAME OF OCCURRENCE EFFECTS 1 System requirements alteration Moderate Tolerable 2 Project size under-estimation Moderate Serious 3 Staff change Low Tolerable 4 Management change Low Insignificant 5 Hardware unavailability Very low Serious 6 Time requirement under-estimation Low Tolerable PROJECT RISK ASSESSMENT Low Tolerable 2.2.2 Product Risk The possible risks are 1 System Requirements alterations. 2 Product Specifications delay . 3 Under-performance of software development tools. PRODUCT RISK S/NO RISK NAME POSSIBILITY OF EFFECT OCCURENCE 1 System requirements alterations Moderate Tolerable 2 Product specification delay Low Tolerable Page 6 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  7. 7. PRODUCT RISK 3 Under-performance of CASE tools Low Serious 4 Under-performance of database Low Serious PRODUCT RISK ASSESSMENT Low Tolerable 2.2.3 Business Risk The possible risks are 1 Shut-down of the university technology services department. BUSINESS RISK S/NO RISK NAME POSSIBILTIY OF EFFECT OCCURENCE 1 Departmental Shut-down Very low Serious BUSINESS RISK ASSESSMENT Very low Serious 2.2.4 Risk Profile The project risk profile is shown diagrammatically . RISK PROFILE Business risk Product risk Project risk Very Low Moderate High Very Low High 2.2.5 Risk Planning All risks that are evaluated to have a greater than tolerable effect on the development of the AMAM system have had risk management plans developed. The risks and their management plans are: Page 7 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  8. 8. a. Project size under estimation: Evaluate possibility of increasing development team size or contracting out project segments. b. Hardware unavailability: Investigate possibility of custom developing required hardware components. c. Under-performance of CASE tools: Replace under-performing tools with more reliable tools. d. Database under-performance: Investigate the possibility of procuring a higher capability database. e. Departmental Shut-down: Attempt to the convince university management of importance of department and project to the university Page 8 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  9. 9. 3 User Requirements 3.1 Functional Requirements 3.1.1 Search Catalog 3.1.1.1 Search the various assets in the library catalog by author, title, keyword, author/title, subject or call number. The search result should return the title, author, location, loan type, call number and status 3.1.2 Check- out Asset 3.1.2.1 Valid patrons are a) Alpha University Students b) Alpha University Faculty Members c) Alpha University Staff 3.1.2.2 Books, CD-ROMs, DVDs, Microfilm and Videos can be checked out 3.1.2.3 Periodicals and journals are available only for use inside the library and are not allowed to be checked out. 3.1.2.4 The loan period for the assets vary among units. 3.1.2.5 The loan period for assets on reserve is specified by the faculty, while placing a reserve request. 3.1.2.6 Security should be enhanced by displaying the patron's picture while checking-out 3.1.3 Check- in Asset 3.1.3.1 When an asset is returned after the due date, a fine of $.50/day should be collected from the patron. 3.1.3.2 The status of the asset should be changed from 'checked-out' to 'In Library' 3.1.4 Overdue Notice 3.1.4.1 If an asset is not returned on the due date, a overdue notice should be sent to the patron 3.1.5 Renew Check- out 3.1.5.1 Assets can be renewed, provided the date is on or before the last day of the current semester. 3.1.5.2 Assets on reserve or on hold cannot be renewed and have to be returned on or before the return date. 3.1.6 Hold Asset 3.1.6.1 The patrons or library staff can recall an asset that is currently checked out. Once the asset is received, an email should be sent to the patron who requested the asset. Page 9 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  10. 10. 3.1.7 Reserve Placement Request 3.1.7.1 Assets can be placed on reserve by faculty. The faculty decides the number of days an asset can be kept by a student, depending upon the size of the class. 3.1.8 Reports 3.1.8.1 Library staff should be able to generate reports for the following purposes a) Assets borrowed today b) All Assets borrowed that are not returned c) Assets due today d) Assets overdue 3.1.9 Catalog Management 3.1.9.1 Add new asset such as books, videos, DVD's etc. 3.1.9.2 Update asset information 3.1.10 Maintain Patron 3.1.10.1 Add patron information 3.1.10.2 Delete patron information 3.1.10.3 Update patron information 3.2 Non- Functional Requirements 3.2.1 User Friendly Interface 3.2.1.1 The user interface must be easy to use and self-explanatory 3.2.2 Speed 3.2.2.1 The response time for finding an asset should be no more than 5 seconds. 3.2.3 Volume 3.2.3.1 The university has acquired 100,000 books, 1000 periodicals & journals, 300 CD's/Videos/DVD's and 1000 microfilms. The volume is expected to increase tremendously(about 10 times) in the next 5 years. The system should have the ability to hold this information. 3.2.4 Accessibility 3.2.4.1 To start with, only around 10-15 users will be accessing the system per minute, but as the university grows, more people will be accessing the system. The system should have the capacity to handle 100 users/min. Page 10 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  11. 11. 4 Architecture Design This section describes the envisioned system architecture at a high level of abstraction. It is not intended as an implementation system design, but rather to illustrate to the user community what the system will entail. Campus Network Tape Backup Asset Database Database Server Router Ethernet Barcode reader Barcode reader Patron Consoles Staff Workstation Staff Workstation Basic architecture of AMAMS. The essential components of the system will be: 1. A relational database management system; 2. A server capable of running the relational database management system and an application server capable of responding to client workstation requests; 3. Client workstations capable of using a barcode reader and running a client application; 4. Patron consoles capable of running a client application; 5. A network infrastructure capable of supporting communication between server, workstations, consoles, and the campus network. Page 11 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  12. 12. 5 System Requirements System requirements are described using a set of use case diagrams and descriptions. 5.1 Use Case Diagrams 5.1.1 Shared Use Cases Search Catalogue Check-out Ç uses È Ç uses È Asset Ç uses È Ç uses È Reserve Asset Ç uses È Ç uses È Request Staff Patron Ç uses È Ç uses È Ç uses È Hold Asset Ç uses È Renew Check- out Use cases shared between library staff and patrons. Page 12 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  13. 13. 5.1.2 Staff- only Use Cases Catalog New Asset Staff Login Ç uses È Ç uses È Staff Ç uses È Check-in Asset Staff Logout Ç uses È Maintain Patron Ç uses È Add Patron Update Patron Delete Patron Staff Ç uses È Ç uses È Generate Reports Ç uses È Overdue Notice Ç access È Email System Review Reserve Asset Request Use cases used only by library staff. 5.2 Use Case Descriptions Below are text descriptions of the use cases illustrated above. 5.2.1 Search Catalog Use Case Name Search Catalog Assumptions None Pre-conditions None Initiation Trigger Use case is triggered on demand Main Flow of 1. Patron enters search criteria Events 2. System responds with list of assets matching criteria Page 13 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  14. 14. 3. Patron selects assets of particular interest 4. System responds with location and availability of each asset Exceptions Flow 1. No assets match search criteria of Events 2. Patron returns to Step 1 of Main Flow Post-conditions None 5.2.2 Check- in Asset Use Case Name Check-in Asset Assumptions None Pre-conditions Staff member is logged into system Initiation Trigger Use case is triggered on demand Main Flow of 1. Patron deposits asset in the return bin Events 2. Staff person scans asset barcode 3. System updates the asset record to indicate that the asset is on site. Exceptions Flow None of Events Post-conditions None 5.2.3 Check- out Asset Use Case Name Check-out Asset Assumptions None Pre-conditions Staff member has logged onto the system Initiation Trigger Use case is triggered on demand Main Flow of 1. Patron takes asset to check-out station Events 2. Staff member enters patron ID 3. Staff member scans barcode 4. System records status and displays the due date 5. Staff member returns asset to patron Exceptions Flow 1. If Patron does not have a valid system id, the staff member of Events may create one with the Create Patron use case Post-conditions The asset is recorded in the asset database as being checked-out to the patron. 5.2.4 Hold Asset Use Case Name Hold Asset Assumptions Asset is not currently available Pre-conditions Staff member has logged onto the system Initiation Trigger Use case is triggered on demand Main Flow of 1. Patron sends a hold request message to the library Events 2. Staff member checks the database status of the asset 3. If available, staff member adds a hold record for the asset 4. System records status Page 14 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  15. 15. Exceptions Flow 1. If Patron does not have a valid system id, the staff member of Events may create one with the Create Patron use case 2. If the requested asset can not be held, the staff member requests the system to notify the patron Post-conditions The asset is recorded in the asset database as having a hold request. 5.2.5 Reserve Asset Request Use Case Name Reserve Asset Request Assumptions None Pre-conditions None Initiation Trigger Use case is triggered on demand Main Flow of 1. Patron uses use case Search Catalog Events 2. Patron submits the request to reserve the asset 3. System queues a notification for staff to review request Exceptions Flow None of Events Post-conditions None 5.2.6 Review Reserve Asset Request Use Case Name Review Reserve Asset Assumptions None Pre-conditions Staff member is logged in Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member calls up queue of reserve asset requests Events 2. Staff member reviews request and approves or disapproves 3. If approved, system updates the record to reflect reserve status 4. The system deletes the request from the queue Exceptions Flow 1. If the patron requesting the reserve is not faculty, the of Events request can not be approved 2. The system deletes the request from the queue. Post-conditions None 5.2.7 Renew Check- out Use Case Name Renew Checkout Assumptions Asset is currently checked-out to the requesting patron Pre-conditions Staff member has logged onto the system Initiation Trigger Use case is triggered on demand Main Flow of 1. Patron makes a renew asset request message to the library Events 2. Staff member checks the database status of the asset 3. If possible, staff member updates the asset checkout record 4. System records status Exceptions Flow 1. If Patron does not have a valid system id, the staff member of Events may create one with the Create Patron use case 2. If the requested asset can not be renewed, the staff member Page 15 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  16. 16. notifies the patron Post-conditions The asset record in the asset is updated with new due date 5.2.8 Staff Login Use Case Name Staff Login Assumptions None Pre-conditions None Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff members enters user id and password Events 2. System validates the user id and password Exceptions Flow 1. If the either the password or user id is invalid, the system of Events prompts the data to be input again Post-conditions The staff member is logged into the system 5.2.9 Staff Logout Use Case Name Staff Logout Assumptions Staff member is logged-in Pre-conditions None Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member selects the logout option Events 2. System invalidates the session Exceptions Flow None of Events Post-conditions The staff member is no longer logged into the system 5.2.10Catalog New Asset Use Case Name Catalog new asset Assumptions None Pre-conditions Staff member is logged into system Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member assigns new barcode to asset Events 2. Staff member scans new barcode 3. System adds asset to the database Exceptions Flow 1. If selected barcode is already assigned, the staff member of Events must select another barcode Post-conditions A new asset record is created in the database 5.2.11Add Patron Use Case Name Add patron Assumptions A patron record does not exist Pre-conditions Staff member is logged into system Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member selects the add patron option Events 2. Staff member enters new data 3. System adds a patron record to the database Page 16 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  17. 17. Exceptions Flow None of Events Post-conditions A new patron record is created in the database 5.2.12Update Patron Use Case Name Update patron Assumptions A patron record exists Pre-conditions Staff member is logged into system Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member selects the update patron option Events 2. Staff member enters new data 3. System updates the patron record in the database Exceptions Flow None of Events Post-conditions The patron record is updated in the database 5.2.13Delete Patron Use Case Name Delete patron Assumptions A patron record exists Pre-conditions Staff member is logged into system Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member selects the delete patron option Events 2. Staff member confirms delete 3. System removes the patron record from the database Exceptions Flow None of Events Post-conditions The patron record is removed from the database 5.2.14Generate Reports Use Case Name Generate reports Assumptions None Pre-conditions Staff member is logged into system Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member selects the generate reports option Events 2. System creates the reports Exceptions Flow None of Events Post-conditions None 5.2.15Overdue Notice Use Case Name Overdue notice Assumptions None Pre-conditions Staff member is logged into system Initiation Trigger Use case is triggered on demand Main Flow of 1. Staff member selects the generate overdue notices option Page 17 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  18. 18. Events 2. System generates email notices for all overdue assets Exceptions Flow None of Events Post-conditions None Page 18 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  19. 19. 6 System Models 6.1 Semantic Data Model Semantic Data Model of the AMAMS System Patron Student id 1 is a 1 degree first name major Faculty last name PT/FT address 1 is a 1 department phone depart phone picture 1 is a 1 Staff course 1 department course desc borrows depart phone 0,n Loan Asset Title asset no asset no title no 1 has a 1 out date n lend 1 title no title due date status author patron id asset type synopsis 1 is a 1 1 1 Book Multimedia Microfilm ISBN UPC Microfilm id edition format Page 19 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  20. 20. 6.2 Data Flow Models 6.2.1 Catalog Search CATALOG SEARCH DATA FLOW MODEL Input Search parameters Media Author, User Report Or Sort through media database Title, Search Results Subject Category, Media Type Search Parameters Relational Database Page 20 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  21. 21. 6.2.2 Asset Checkout ASSET CHECK-OUT MODEL User Report User Report Input Media Update Patron Media Details Update Media Details + Patron Details Database ID-Number Patron ID No. Media Identification Number Relational Relational Database Database 6.2.3 Asset Check- in Page 21 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  22. 22. ASSET CHECK-IN MODEL User Report Input Media Update Patron Media Details User Report Update Media Details + Patron Details Database ID-Number Patron ID No. Media ID Number Relational Relational Database Database Page 22 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  23. 23. 6.2.4 Media Asset Overdue MEDIA ASSET OVERDUE NOTICE MODEL Input Media Sort Media Past Media Obtain Patron Patron Dispatch Overdue Return Date Return Dates Return Dates Contact ID-No. + Details Emails Notice Details Return Date Media ID no. Relational Relational Database Database Page 23 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  24. 24. 6.2.5 Asset Check- in/Renewal ASSET CHECK-OUT RENEWAL MODEL User Report User Report Input Media Update Patron Media Check For Media Media Update Media User Report Details + Patron Details Details Status Changes e.g Holds Details Database ID-Number Media ID No. Patron ID No. Media ID No. Relational Relational Relational Database Database Database Page 24 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  25. 25. 6.2.6 Asset Hold ASSET HOLD DATA FLOW MODEL User Report Input Media Check Media Hold Update Media Patron Update Patron User Report Details + Patron Status Parameters Database Details Details ID-Number Media Media ID No. Patron Details ID No. Relational Relational Relational Database Database Database Page 25 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  26. 26. 6.2.7 Asset Reserve Placement ASSET RESERVE PLACEMENT MODEL User Report User Report Check Patron Input Media Patron Media Update Media User Report Status. Must Be Details + Patron Details Update Patron Details Details Database Faculty Member ID-Number Media ID Patron Number Patron ID. No. ID No. Relational Relational Relational Database Database Database Page 26 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  27. 27. 6.2.8 Report Generation REPORT GENERATION DATA MODEL User Report User Report User Report Sort For Sort For Input Current Sort For New Current Current Media Assets Current Sort For User Unreturned DayÕ Date s Check-outs Date Date Due On Date Overdue Media Report Assets Not Yet Due Current Date Current Current Current Current Date Date Date Date Relational Relational Relational Relational Database Database Database Database Page 27 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  28. 28. 6.2.9 Catalog Management CATALOG MANGEMENT DATA MODEL : NEW MEDIA ASSET ADDITION OPERATION User Report New Media Complete New Completed Update Media Media Allot Media (MIN) Attach (MIN) User Author, Title Media Details Form Database Details Identification To Media Report ISBN No. etc. Form Number (MIN) Media Media Details Details Relational Relational Database Database Page 28 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  29. 29. 6.2.10Catalog Update CATALOG MANAGEMENT DATA MODEL: MEDIA ASSET UPDATE OPERATION User Report Input Media Identification Sort For Media Media Complete Completed Update Media User Number Details Form Details Details Form Database Report Or Form Media Title, Author, ISBN No. Media ID No. Media Details Relational Relational Database Database Page 29 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  30. 30. 6.2.11Patron Add and Update LIBRARY PATRON MAINTAINANCE MODEL: NEW PATRON ADDITION OPERATION Input Patron Complete New Create New Completed Form User Report Allot New User Report + Details Patron Form Patron Account Patron ID No. Patron ID. No. Patron Details Patron Details Relational Relational Database Database PATRON DETAILS UPDATE OPERATION ------------------------------------------------------- User Report Input Patron Sort For Patron User ID-Number Patron Update Patron Updated Update Patron Details Form Report Or Details Details Form Form Details Patron Details e.g. Name, Patron Details Patron ID No. Department etc Or Details Relational Relational Database Database Page 30 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  31. 31. 6.2.12Patron Delete LIBRARY PATRON MAINTAINANCE MODEL: PATRON DELETION OPERATION User Report Input Patron Details Sort For Patron Delete Patron Or Patron User Report Patron Details Account Account ID-Number Form Patron ID No. Patron ID No. Or Details Or Details Relational Relational Database Database Page 31 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward
  32. 32. 7 Glossary This is a list of terms with special meaning within the Library domain. Patron Any person using Library services. Faculty A person with research or teaching responsibilities at the University. Staff Any person with assigned duties supporting the Library. Page 32 of 32 CMSI 641 Fall 2002 Ajay, Venugopal, Ward

×