Childrens Self-Checkout Library System Software Requirements Specification Kennesaw State University

Version 1.0

Revision History Date 09/15/08 09/16/08 Version Description 1.0 Specific requirements 1.1 Use-Case Diagram Author Group 4 Group 4

Table of Contents 1. 1.1 1.2 1.3 1.4 1.5 2. 3. 3.1 3.1.1 3.2 3.2.1 3.3 3.3.1 3.4 3.4.1 3.5 3.5.1 3.6 3.6.1 3.7 3.8 Introduction Purpose Scope Definitions, Acronyms and Abbreviations References Overview Overall Description Specific Requirements Functionality <Functional Requirement One> Usability <Usability Requirement One> Reliability <Reliability Requirement One> Performance <Performance Requirement One> Supportability <Supportability Requirement One> Design Constraints <Design Constraint One> Online User Documentation and Help System Requirements Purchased Components

3.9 3.9.1 3.9.2 3.9.3 3.9.4 3.10 3.11 3.12 4.

Interfaces User Interfaces Hardware Interfaces Software Interfaces Communications Interfaces Licensing Requirements Legal, Copyright and Other Notices Applicable Standards Supporting Information

Software Requirements Specification

1.

Introduction

1.1 Purpose
The purpose of the Software Requirements Specification (SRS) document is to provide a detailed preliminary analysis of all the requirements to design and implement the Childrens Self-Checkout Library System, CSCLS. This document discusses the human and systems interfaces and behaviors as it relates to using the CSCLS system.

1.2 Scope
The Childrens Self-Checkout Library System, CSCLS is a library system that enables children to checkout and return books to the Kennesaw State University library. Interactions and behaviors within the system are modeled in the Use-Case.

1.3 Definitions, Acronyms and Abbreviations

1.3.1 CLSCS: Childrens Library Self- Checkout System 1.3.2 KSU: Kennesaw State University

1.4 References
Appendix A: Check-out Diagram Appendix B: Check-in Diagram Appendix C: Maintain inventory Diagram

1.5 Overview
The SRS document starts by describing the overall description of the SRS which includes product perspectives, product functions, assumptions and dependencies and constraints. This document further describes the specific requirements of the SRS software which deals with functionality, usability, and reliability. This document also discusses SRS Performance; this performance describes response time, throughput, capacity, degradation and resource utilization. Moreover, this SRS document explains about maintainability and coding standards and also Design constraints, online user documentation and purchased components. This SRS document also discusses Interfaces, interfaces include user interfaces, Hardware

interfaces, and software interfaces. It also contains Communication interface, Licensing requirements, and copyright and other notices. Finally this SRS document includes the use-case diagram as the supporting information; the use-case diagram describes the basic functions of the system that means what the user can do and the responses of the system.

2. Overall Description
The following lists and describes some of the major mechanisms of the CSCLS in an effort to provide an overview of the system: 2.1 Product perspective 2.1.1 The CSCLS enables children and staff to check-in/checkout library materials 2.1.2 The CSCLS enables library staff to maintain the inventory the KSU library system 2.2 Product functions 2.2.1 The CSCLS accepts a unique user ID number from children and/or staff to checkin/checkout library materials 2.2.2 The CSCLS enables authenticated library staff to maintain the inventory the KSU library system 2.3 Assumption and dependencies: 2.3.1 User database is obtained from the university personal database system 2.3.2 Physical layout of the building is not known 2.3.3 Parental supervision and assistance of children is required 2.3.4 staff are KSU library employees 2.3.5 users are children of students/staff who possess library ID number 2.4 Constraints 2.4.1 Children of age 8 years and above will use this CLSCS and they need parent's assistance and supervision

3.

Specific Requirements

3.1 Functionality
Restricts patrons to a five item checkout maximum Enforces a one week checkout period with one time extension for another week Sends email notifications for overdue items Creates collections list Restricts the checkout of reserved items Calculates late fees Provides a manager section Authenticates for manager/library staff use only Enables inventory maintenance Enables printing capabilities

3.2 Usability
3.2.1 All users must be accompanied by an adult/parent.

3.3 Reliability
3.3.1 Availabilitythe system must be up and running 100% of the time during the library hours of operations. 3.3.2 Mean Time between Failures (MTBF) the system must not exceed more than 10 hours of failure per year. 3.3.3 Mean Time To Repair (MTTR) the system must not exceed more than 2 hours of down time between failures 3.3.4 Accuracycalculates late fees accurately 3.3.5 Maximum Bugs or Defect Rateno more than 10 for entire application. 3.3.6 Bugs or Defect Ratedatabase bugs are critical, user interface bugs are minor, and manager section interface bugs are critical.

3.4 Performance
3.4.1 Response time maximum is one minute per post-transaction 3.4.2 Throughput 100 mbs

3.4.3 Capacity only limited to the scalability of the database system 3.4.4 Degradation not acceptable as operations will be suspended in degradation mode 3.4.5 Resource utilization -- Predetermined by IT departmental resources.

3.5 Supportability
3.5.1 Maintainability - Documentation provided for upgrades and maintainability. Upgrade the application software and perform periodical maintenance on the system. 3.5.2 Coding Standard - JAVA standard guidelines used

3.6 Design Constraints

3.6.1
GUI design must be children-friendly and simple with detailed instructions for all components

3.7 On-line User Documentation and Help System Requirements

3.7.1 - Documentation provided for upgrades and maintainability

3.8 Purchased Components

3.8.1 Using all Open-source software

3.9 Interfaces
3.9.1 3.9.2 3.9.3 User Interfaces is colorful layout with images of cartoon characters Hardware Interfaces barcode reader Software Interfaces

Barcode reader driver

3.9.4

Communications Interfaces

Kennesaw State University Network used

3.10 Licensing Requirements

3.10.1 Free for personal and educational use only 3.10.2 No commercial use

3.11 Legal, Copyright, and Other Notices

Copyright @2008 Kenyatta Perkins, Keenan Carter, Jinyoung Choi, Ermias Kassa

4.

Supporting Information

Use Case 1:

Figure 1: Use Case 1