Srs document for library management system?

Answer 1

Software Requirements Specification for Library Information System (LIS) Version 2.0 Prepared by Edgar Khachatryan American University of Armenia, CIS 1 April, 28, 2005 Table of Contents Table of Contents 1 Revision History 1 1. Introduction 2 1.1 Purpose 2 1.2 Project scope Error! Bookmark not defined. 1.3 Definitions, acronyms, abbreviation Error! Bookmark not defined. 2. Overall Description 2 2.1 Product Perspective 2 2.3 User Classes and Characteristics 3 2.4 Operating Environment 3 2.5 User Documentation 3 3. System Features 4 3.1 Searching 4 3.1 Clark 4 4. External Interface Requirements 4 4.1 User Interfaces 4 4.2 Software Interfaces 4 4.3 Communications Interfaces 4 5. Other Nonfunctional Requirements 5 5.1 Safety Requirements 5 5.2 Security Requirements 5 5.3 Software Quality Attributes 5 6. Use Cases 5 Appendix A: Glossary 10 Revision History Name Date Reason For Changes Version Edgar Khachatryan 28.March.2005 Draft version 1.0 Draft Edgar Khachatryan 28.April.2005 2.0 1. Introduction 1.1 Purpose The goal of this document is to give description of how to use the Library Information System (LIS) (release 1.0). It gives complete information about functional and nonfunctional requirements of system. This SRS document is done for developers of LIS as well as for Library clerk and staff. Document easy to read and understood, there are no particular typographical conventions. 1.2 Project Scope Purpose of LIS is to automat activities of Library informational system such as storing information about books, members and sponsors as well as penalties will be executed by computer. LIS will allow doing statistics for Library purposes (such as, sorting books or ordering new books). LIS can be fully independent system, but also can be part of other systems. In all cases data base will be only in the local SC. All menus will be standardized by KDE standard. Main programming language will be C++ and for interface Visual Java. 1.3 References CIS 260 Software Engineering - I http://developer.kde.org/documentation/standards/kde/style/basics/index.html 1.4 Definitions, Acronyms, and Abbreviations LIS - Library Information System SC - Server Computer UC - User Computer SUC - Staff User Computer M1 - Undergraduate student M2 - Postgraduate student M3 - Research scholar M4 - Faculty Member 2. Overall Description 2.1 Product Perspective Software Library Information System is aimed to automate required activities of Library. LIS will give possibility to provide high quality service to the Library members, also to have high planned and fast work. Do to friendly and multifunctional interface Library clerk will be able to easily insert, delete and update data, also append comments concern stuff, sponsors, books and members. Also BS will be able to search and get information about books and their availabilities. 2.2 User Classes and Characteristics Clerk - The Clerk is an organizer of all activities in the Library. Clerk has an all rights and accesses to all private information. Clerk has an opportunity to delete or to add member's, staff's, book's, sponsor's or other important information. Clerk is a user of SC, all databases and statistics visible only for Clerk. Library Staff - Part of library staffs which have an access to the SUC allow giving book and taking returned books. Library staff Member - Each Library member has an ID number. They have access to UC and allow searching book and borrowing or reserving it. Members must return book in time or pay penalties. M1 - Undergraduate student, can issue up to 2 books for 1 mount duration. M2 - Postgraduate student, can issue up to 4 books for 1 mount duration. M3 - Research scholar, can issue up to 6 books for 3 mount duration. M4 - Faculty Member, can issue up to 10 books for 6 mount duration. Books - The Library has at least 10 000 books. Each book has unique number (ISBN). B1 - This books can be borrowed B2 - These books can only be used inside of Library. 2.3 Operating Environment LIS based on DOS platform and minimum requirements for hardware are 100 MB available in HDD, 8mb RAM and 2x CD-ROM. LIS copyrighted by CIS 1 and fully maintained, it working in two languages (English and Armenian) but can be translated in any language. 2.4 User Documentation LIS sell give help when user pushing F1 in keyboard as well as by clicking into help button. Help includes guidelines about searching and borrowing the book. Also there is documentation where each member could get information about borrowing durations and Library policy. For the first time shell give tutorial in Macromedia Flash environment. 3. System Features 3.1 Searching Searching can be done in two ways by title and by author. If keyword true information about book will be executed with information is it available or not. If keyword wrong system will send massage with error condition. If keyword true but book not available system will return information about book with information about borrowing period. 3.2 Clerk Clerk putting ID number of member, if member has penalties system sending alarm with information about penalty, otherwise it continues work. Then clerk putting ISBN of book and if it is not reserved system asking about allowing to continue if answer OK it moving book from available into borrowed. 4. External Interface Requirements 4.1 User Interfaces LIS are very friendly it can be used by user without any explanation. 4.2 Software Interfaces LIS including two parts of system, one for member and second for user. In user part only search is available, in clerk part available all parts of system. 4.3 Communications Interfaces Communications realized by standard forms and massage windows. 5. Other Nonfunctional Requirements 5.1 Safety Requirements Product can be installed only if there are some kinds of operating system which are based on DOS or if available only DOS. Strongly requirement is to close LIS before shutting down computer. 5.2 Security Requirements Copying or using LIS not allowing without asking CIS 1. 5.3 Software Quality Attributes LIS very specific software for specific purpose, it is very easy and safe, with high productiveness. 6. Use Cases Use Case ID: 1 Use Case Name: Search of Material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader, Library Staff Description: A User accesses the LIS for searching a material. The process should be executed by LIS not more than 1 min. Preconditions: User is logged into LIS Postconditions: None Normal Flow: 1.0 Searching material 1. User asks to search material. 2. System opens appropriate place for choosing material. 3. User chooses appropriate material. 4. System opens appropriate place for searching. 5. User enters the key (keys) for searching the material. 6. System brings found records' list (records). 7. User chooses one record. Alternative Flows: None Exceptions: 1.0. E.1. Material to be searched does not exist. 1. System informs the user that the material does not exist in LIS data base. 2. User cancels the searching process. 3. System returns the user to the main window. Priority: Low Notes and Issues: Material is a book, CD, video, document, magazine, e-book. Use Case ID: 2 Use Case Name: Holding material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader Description: A User accesses the LIS for holding a material. The process should be executed by LIS not more than 1 min. Preconditions: User is logged into LIS. Postconditions: 1. The delete process is conformed. 2. System updates the holding list. Normal Flow: 1.0 Holding material 1. User asks to search material. 2. System opens appropriate place for choosing material. 3. User chooses appropriate material. 4. System opens appropriate place for searching. 5. User enters the key (keys) for searching the material. 6. System brings found records' list (records). 7. User chooses one record. 8. User holds material. Alternative Flows: None: Exceptions: 1.0. E.1. Material to be hold does not exist. 1. System informs the user that the material does not exist in LIS data base. 2. User cancels the holding process. 3. System returns the user to the main window. Priority: High Notes and Issues: User can hold maximum 5 materials. Use Case ID: 3 Use Case Name: Returning book Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 4 Use Case Name: Input Output member Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 5 Use Case Name: Statistics Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 6 Use Case Name: Input Output Material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 7 Use Case Name: Info about availableness Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 8 Use Case Name: Distant contact between reader and staff Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader and Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 9 Use Case Name: Penalty system Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: LIS Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 10 Use Case Name: Accountant system Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: LIS Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 11 Use Case Name: Print Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader, Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 12 Use Case Name: Reserve of material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Appendix A: Glossary Fig.2. Sequence Diagram of LIS Fig.2. Class Diagram of LIS Fig.1. Use case diagram of LIS Software Requirements Specification for Library Information System (LIS) Version 2.0 Prepared by Edgar Khachatryan American University of Armenia, CIS 1 April, 28, 2005 Table of Contents Table of Contents 1 Revision History 1 1. Introduction 2 1.1 Purpose 2 1.2 Project scope Error! Bookmark not defined. 1.3 Definitions, acronyms, abbreviation Error! Bookmark not defined. 2. Overall Description 2 2.1 Product Perspective 2 2.3 User Classes and Characteristics 3 2.4 Operating Environment 3 2.5 User Documentation 3 3. System Features 4 3.1 Searching 4 3.1 Clark 4 4. External Interface Requirements 4 4.1 User Interfaces 4 4.2 Software Interfaces 4 4.3 Communications Interfaces 4 5. Other Nonfunctional Requirements 5 5.1 Safety Requirements 5 5.2 Security Requirements 5 5.3 Software Quality Attributes 5 6. Use Cases 5 Appendix A: Glossary 10 Revision History Name Date Reason For Changes Version Edgar Khachatryan 28.March.2005 Draft version 1.0 Draft Edgar Khachatryan 28.April.2005 2.0 1. Introduction 1.1 Purpose The goal of this document is to give description of how to use the Library Information System (LIS) (release 1.0). It gives complete information about functional and nonfunctional requirements of system. This SRS document is done for developers of LIS as well as for Library clerk and staff. Document easy to read and understood, there are no particular typographical conventions. 1.2 Project Scope Purpose of LIS is to automat activities of Library informational system such as storing information about books, members and sponsors as well as penalties will be executed by computer. LIS will allow doing statistics for Library purposes (such as, sorting books or ordering new books). LIS can be fully independent system, but also can be part of other systems. In all cases data base will be only in the local SC. All menus will be standardized by KDE standard. Main programming language will be C++ and for interface Visual Java. 1.3 References CIS 260 Software Engineering - I http://developer.kde.org/documentation/standards/kde/style/basics/index.html 1.4 Definitions, Acronyms, and Abbreviations LIS - Library Information System SC - Server Computer UC - User Computer SUC - Staff User Computer M1 - Undergraduate student M2 - Postgraduate student M3 - Research scholar M4 - Faculty Member 2. Overall Description 2.1 Product Perspective Software Library Information System is aimed to automate required activities of Library. LIS will give possibility to provide high quality service to the Library members, also to have high planned and fast work. Do to friendly and multifunctional interface Library clerk will be able to easily insert, delete and update data, also append comments concern stuff, sponsors, books and members. Also BS will be able to search and get information about books and their availabilities. 2.2 User Classes and Characteristics Clerk - The Clerk is an organizer of all activities in the Library. Clerk has an all rights and accesses to all private information. Clerk has an opportunity to delete or to add member's, staff's, book's, sponsor's or other important information. Clerk is a user of SC, all databases and statistics visible only for Clerk. Library Staff - Part of library staffs which have an access to the SUC allow giving book and taking returned books. Library staff Member - Each Library member has an ID number. They have access to UC and allow searching book and borrowing or reserving it. Members must return book in time or pay penalties. M1 - Undergraduate student, can issue up to 2 books for 1 mount duration. M2 - Postgraduate student, can issue up to 4 books for 1 mount duration. M3 - Research scholar, can issue up to 6 books for 3 mount duration. M4 - Faculty Member, can issue up to 10 books for 6 mount duration. Books - The Library has at least 10 000 books. Each book has unique number (ISBN). B1 - This books can be borrowed B2 - These books can only be used inside of Library. 2.3 Operating Environment LIS based on DOS platform and minimum requirements for hardware are 100 MB available in HDD, 8mb RAM and 2x CD-ROM. LIS copyrighted by CIS 1 and fully maintained, it working in two languages (English and Armenian) but can be translated in any language. 2.4 User Documentation LIS sell give help when user pushing F1 in keyboard as well as by clicking into help button. Help includes guidelines about searching and borrowing the book. Also there is documentation where each member could get information about borrowing durations and Library policy. For the first time shell give tutorial in Macromedia Flash environment. 3. System Features 3.1 Searching Searching can be done in two ways by title and by author. If keyword true information about book will be executed with information is it available or not. If keyword wrong system will send massage with error condition. If keyword true but book not available system will return information about book with information about borrowing period. 3.2 Clerk Clerk putting ID number of member, if member has penalties system sending alarm with information about penalty, otherwise it continues work. Then clerk putting ISBN of book and if it is not reserved system asking about allowing to continue if answer OK it moving book from available into borrowed. 4. External Interface Requirements 4.1 User Interfaces LIS are very friendly it can be used by user without any explanation. 4.2 Software Interfaces LIS including two parts of system, one for member and second for user. In user part only search is available, in clerk part available all parts of system. 4.3 Communications Interfaces Communications realized by standard forms and massage windows. 5. Other Nonfunctional Requirements 5.1 Safety Requirements Product can be installed only if there are some kinds of operating system which are based on DOS or if available only DOS. Strongly requirement is to close LIS before shutting down computer. 5.2 Security Requirements Copying or using LIS not allowing without asking CIS 1. 5.3 Software Quality Attributes LIS very specific software for specific purpose, it is very easy and safe, with high productiveness. 6. Use Cases Use Case ID: 1 Use Case Name: Search of Material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader, Library Staff Description: A User accesses the LIS for searching a material. The process should be executed by LIS not more than 1 min. Preconditions: User is logged into LIS Postconditions: None Normal Flow: 1.0 Searching material 1. User asks to search material. 2. System opens appropriate place for choosing material. 3. User chooses appropriate material. 4. System opens appropriate place for searching. 5. User enters the key (keys) for searching the material. 6. System brings found records' list (records). 7. User chooses one record. Alternative Flows: None Exceptions: 1.0. E.1. Material to be searched does not exist. 1. System informs the user that the material does not exist in LIS data base. 2. User cancels the searching process. 3. System returns the user to the main window. Priority: Low Notes and Issues: Material is a book, CD, video, document, magazine, e-book. Use Case ID: 2 Use Case Name: Holding material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader Description: A User accesses the LIS for holding a material. The process should be executed by LIS not more than 1 min. Preconditions: User is logged into LIS. Postconditions: 1. The delete process is conformed. 2. System updates the holding list. Normal Flow: 1.0 Holding material 1. User asks to search material. 2. System opens appropriate place for choosing material. 3. User chooses appropriate material. 4. System opens appropriate place for searching. 5. User enters the key (keys) for searching the material. 6. System brings found records' list (records). 7. User chooses one record. 8. User holds material. Alternative Flows: None: Exceptions: 1.0. E.1. Material to be hold does not exist. 1. System informs the user that the material does not exist in LIS data base. 2. User cancels the holding process. 3. System returns the user to the main window. Priority: High Notes and Issues: User can hold maximum 5 materials. Use Case ID: 3 Use Case Name: Returning book Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 4 Use Case Name: Input Output member Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 5 Use Case Name: Statistics Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 6 Use Case Name: Input Output Material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 7 Use Case Name: Info about availableness Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 8 Use Case Name: Distant contact between reader and staff Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader and Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 9 Use Case Name: Penalty system Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: LIS Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 10 Use Case Name: Accountant system Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: LIS Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 11 Use Case Name: Print Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader, Library Staff Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Use Case ID: 12 Use Case Name: Reserve of material Created By: Edgar Khachatryan Last Updated by Edgar Khachatryan Date Created: April, 20, 2005 Date Last Updated Actors: Reader Description: Preconditions: Postconditions: Normal Flow: Alternative Flows: Exceptions: Priority: Notes and Issues: Appendix A: Glossary Fig.2. Sequence Diagram of LIS Fig.2. Class Diagram of LIS Fig.1. Use case diagram of LIS

Answer 2

it is a analysis for checking the status