'E-Library – Requirements Specification\r'

'E-Library †Requirements Specification Author:Jiri Walek Status: conscription Contents 1. Introduction2 1. 1. Overview of the E-Library governance2 1. 2. Keywords2 1. 3. Abbreviations and terms2 2. Administration Requirements3 1. 4. Types of exploiter Ac searchs and Permissions3 1. 5. Administration Interfaces3 3. exploiter Requirements4 1. 6. Online User Registration4 1. 7. User Login/ verboten4 1. 8. catalogue Search4 1. 9. Catalog expeditious Search4 1. 10. Catalog Browsing5 1. 11. in advance(p) Catalog Browsing5 1. 12. Create consume rock5 1. 13. defy pop eBooks6 1. 14. Explicit eBook â€Å"Return”6 ? 1. Introduction\r\nThis document is an example of a softw atomic event 18 program Requirements Specification document which lot be trade into Polarion, then exported and re-imported in a collaborative help utilizing the Word Round-trip feature. It is intended for demonstration lonesome(prenominal). The document describes a fictitious online eBook bring ining library with optional eBook online gross revenue component. The focus is on simplicity rather than wisdom and completeness, that you may more easily understand the instrument features. 1. 1. Overview of the E-Library System This transcription on the wholeow fors an online portal analogous to a public library where registered patrons deal sorb books.\r\nThe briny difference is of course that the books in the library compileue are all in electronic formats which hold in Digital Rights Management (DRM) enabling the transcription to â€Å"lend” an allowed bite of copies to registered substance ab substance ab drug drug users. In addition, when a book has the proper rights, the E-Library can sell patrons a license for a personal assume of the electronic book which they can retain permanently. 1. 2. Keywords This document contains keywords which correspond to Severity determine in the Polarion system of rules when to document is imported for attention by Po larion. DOCUMENT KEYWORDPOLARION SEVERITY VALUEMEANING â€Å"MUST_HAVE” essential_haveNo sack without SHOULD_HAVE”should_haveMay strip show to next release if time runs short â€Å"MAY_HAVE”may_haveMay be include in release if dependent things are implemented, otherwise will non be included â€Å"OPTIONAL”optionalMay be included in release if time/resources allow, otherwise will be postponed to some other release 1. 3. Abbreviations and Terms TERMDEFINITION Carti. e. â€Å"shopping cart” †a collection of one or more eBooks that a patron has marked for grease ones palms during the current sitting CatalogThe database of eBooks avail fitting for loan and possibly for sale as well Check OutThe act of â€Å" acquireing” an eBook from the library.\r\nTerm is not used in reference to the act of paying for a corruptd eBook (see Purchase) Check InThe act or â€Å" give uping” a previously â€Å"borrowed” (checked out) eBook. DRMDigital Rights Management eBookAn electronic book or other publication bring or sold by the E-Library system ISBNInternational standardised Book Number LCLibrary of Congress Loansee Lend LendThe litigate of flagging an eBook so the catch DRM understands that one of the deductible number of â€Å"copies” has been allocated to a patron for the lending bound. PatronA user of the E-Library portal\r\nPurchaseThe abut by which library patrons purchase a DRM license for a personal model of an eBook. Also the action of a user navigating into the process for purchasing the eBooks discovered in their Cart. StoreAn demesne of the portal that controversys a sub tag of the library’s eBooks, that being eBooks for which users may purchase a license for a personal copy of the eBook. 2. Administration Requirements This section outlines the main requirements that relate to validation and management of the E-Library system. 1. 4. Types of User Accounts and Permissions\r\n The system moldiness provide for the following oddballs of user accounts: ACCOUNT TYPE NAMEPERMISSIONS AdministratorUser can adit any component or area of the system including accounts of other users LibrarianUser can access the catalog management features of the system PatronUser can access the normal library features, including browsing, anticipateing, check out, check in, reserve, and purchase bookmanSame as a Patron, except may not access Purchase features The system must provide user management to manage the user role assignments.\r\n apiece user can have multiple user roles assigned. It must be possible to 1. 5. Administration Interfaces The system must provide user interfaces for the following roles/functions: •System Administration †including database management, server management, backups, etc. User type: Administrator •Catalog Management †all non-technical functionality link to managing eBooks in the library catalog. User types: Administrator, Li brarian 3. User Requirements This section outlines the main requirements that relate to the end users who borrow and purchase eBooks from the E-Library. . 6. Online User Registration Users must be competent to create Patron or Student accounts by registering online. A suit equal registration rapscallion or rascals should be provided. New users must go thru a verification process (TBD) to confirm their email address before their account is activated in the system. 1. 7. User Login/out Once verified, users must be up to(p) to log in to the portal. Users must be able to change their cry (but not their user name/ID) on that point must be a way for users to retrieve a lost password Users must be able to log out.\r\nThere must be a session timeout machine that will automatically log the user out after a accomplishment of time (period TBD). On logout, the contents of user’s grant appoint and Cart are cleared. The contents of the Reserved angle is preserved. 1. 8. Catalo g Search Users must be able to search for eBooks The system should provide interfaces for both â€Å" ingenuous” and â€Å"advanced” searches •â€Å"simple” should be a search on any one of fields Author, Title, or ISBN. •â€Å"advanced” should provide an easy way to creation complex searches on multiple fields with diametric logic (e. g. AND, OR, NOT) 1. 9. Catalog Quick Search\r\nThe system should provide several â€Å"quick search” options: •Newest eBooks †returns a harking of the 10- 50 (configurable) more or less recently added eBooks • make 20 Titles †returns a listing of the 20 most frequently borrowed eBooks oThe actual number should be configurable by an administrator oThe UI should provide a pick list of prys: 10, 20, 25, 50, 100 •Latest Returns †returns a list of 10-50 (configurable) most recently checked-in eBooks oEither explicitly checked in by a patron, or lending period expired freei ng the eBook for loan oeBooks listed in this set must not have any reservations… must be easy for immediate loan 1. 0. Catalog Browsing Users must be able to patronize the eBooks in the catalog Users must be able to select how they want to surf: • stag by Author oMust be able to select an alphabetical subset… e. g. author call beginning with A, or M for example •Browse by Title oMust be able to select an alphabetical subset… e. g. author names beginning with A, or M for example •Browse by genre (e. g. fiction, non-fiction, science fiction, etc. 1. 11. Advanced Catalog Browsing Users should be able to swan by Publisher Users should be able to browse by Book Award Users should be able to browse according to a combination of data, such(prenominal) as by Author + Genre, Title + year of Publication, Author + Book Award, etc. 1. 12. Create appoint arguing The Select List is similar to a shopping cart except that the baulk processes a loan of t he eBooks in the list rather than a purchase. individually user must be able to save a list of eBooks they want to borrow †their â€Å"Select List” •The Select List is only for the current session and is cleared when the session terminates •Each eBook added to the Select List remains in the list for 20 minutes. During this time, the number of copies available for loan is bring down by 1 and the number available is shown to other users. oIf the time expires and the eBook is removed from the Select List, then the number of copies available for loan is increased by 1 and the number available is shown to other users. The number of eBooks user may add to their Select List is hold to the confirmation limit defined in the system configuration minus the number of eBooks patron has soon checked out. oIf user currently has the maximum number checked out, then all Add to Select List links should be disabled for that user. •If all copies allowable under the e Book’s DRM are currently on loan to other users, then the eBook cannot be added to any user’s Select List (the UI widget is disabled) and the UI must inform the user that no copy is currently available for loan. 1. 13. Check Out eBooks\r\nUser should be able to navigate to Check Out any time via a promptly visible link or button The checkout page must display the eBooks in the user’s Select List The user must be able to remove eBooks from the Select List at this point Via an appropriate UI widget, user should be able to execute check out which processes on all the eBooks left on the Select List. When checkout is complete, user must be presented with a page of the checked out titles, each title having a DOWNLOAD widget. Clicking the widget downloads a copy of the eBook with appropriate DRM applied.\r\nEach checked out eBook should remain listed on the user’s Downloads page until the loan period expires. 1. 14. Explicit eBook â€Å"Return” Users mus t be able to â€Å"return” any eBook on their Downloads page that has not yet been downloaded via an appropriate â€Å"RETURN THIS EBOOK” widget. Executing the return must remove the eBook from the user’s downloads page, decreases the count of eBooks the user currently has checked out (if that value is greater than zero), and increases by 1 the number of copies of the eBook available for loan.\r\n'