Problem Statement & Scope Statement

Problem statement

Problems that are facing by the users while using the current Library system

The current system of the university doesn’t allow users to login from
different campuses.

1. As it is not available online every student calls up to find out if the book is
available or not. - Too many calls to answer

2. Every time a student calls for a book you have to check the racks for the
availability of the book. - Too much of physical work.

3. If some one reserves the book, he’s not sure if he definitely can get the
book as the previous student may not return in time.

4. Either the student has to call or come to the library to reserve the book,
but cannot reserve online over the internet.

5. Fines have to be calculated manually.

6. Students have no idea to check their account.

Project Scope

Project Title : Library Management System

Date :
Prepared By :
Project Justification:
This project is basically updating the manual library system into a
internet based application so that the users can know the details of
their account ,availability of books etc.,
Product Characteristics and Requirements :

1. Secured database.

2. User tracking

3. Search feature

4.Calculating fines

5. Checking the availability of books.

6.Students will get an E-mail before the due date in order to avoid
fines
Project Management Deliverables:

Project plan, Research finding report, Work breakdown structure,

Scope statement, Project charter, Training manuals, lessons learned
report etc.,

Product-related deliverables :

Research reports ,design documents, software code, hardware

,test plan, project benefit measurement plan etc.,

Project Success Criteria: Our main goal is to complete this project

within allotted dead line and also within the budget allotted. It is

necessary to develop a method for capturing the benefits while the

Library management system is being developed, tested, and after it is

 rolled out. If the project takes a little longer to complete or costs a little

more than planned, the firm will still view it as a success if it has a

good payback and helps promote the firm’s image as an excellent

management organization

1. Statement of Work
1. Scope of Work

The on-line Library Management System should manage different types of

library resources such as Books, Magazines, News Papers, CD/DVDs, and any
other resources which the management feels in the future could form a
resource. A resource can be categorized to facilitate searching, sorting and
managing the resources. This can be exemplified by dividing the books as
being in IT or Business category. Students and University Staff can borrow
resources from the library. There need not be a stipulated return date for the
borrowed resource depending upon the individual to whom the resource has
been lent to. If a stipulated return date has been specified and the resource
is not returned within this stipulated due date, a fine may be imposed on the
resource user. The basic fine amount should be updatable by the
management if a need to do so arises in the future. The System should also
allow for a provision to block a resource, where by an individual can borrow
the blocked resource once it is returned by the current borrower.

2. Location of Work

The client for this project is the library which is inside the campus.

3. Period of Performance
The duration of the project is 3 months. All the tasks are equally distributed
among team members to accomplish the goal of completing the project.

4. Deliverables Schedule
Deliverable Date Due
Written report part I: Week 3

Statement of work and Project Plan

Written report part II:

Project scope & problem statement/ Week 6

requirements specification
Written report part III:

Problem analysis and research report Week 8

Written report part IV:

Prototype implementation or practical Week 11

experimental work
Written report part V:

Review of results and statement of findings Week 12

(including test reports)
Written report part VI: Ongoing assessment at
supervisor meetings
Status reports and project diary
5. Applicable Standards:

The project “Library Management System” follows various

programming standards.

6. Acceptance Criteria:

The acceptance criteria for the users are

 The website has to communicate with the database.

 Users can easily search the book with in less time

 Maintaining the account details of the user.

 Users can block the book, view the book through online etc.,.

7. Additional Requirements:

Qualified team members are very important for project.Team members have
to have a basic knowledge in the following areas:

 A sound knowledge in programming languages such as ASP, Java

and dot net and a knowledge of databases such as MySQL, SQL
server or Access.
 Software Design Document
1. Introduction
Software Design Document is the design work product that formally documents the design of
the software components. Software Design Document gives us the detailed description about
the flow of the project.

1.1 Purpose
Software Design Document defines the modules, interfaces and the interaction between
modules and interfaces. It also helps us in giving information about how the system will look the
appearance of user interfaces and the information about static and dynamic view of the system.

The detailed design document is the developer's blueprint. It provides precise directions to
software programmers about how basic control and data structures will be organized. Typically,
the Detailed Design Document consists of tables and diagrams that translate the functional
specification into data structures, data flows, and algorithms.

The Detailed Design Document is written before programming starts. It describes how the
software will be structured, and what functionality will be included. This document forms the
basis for all future design and coding.

The designer's goal is to develop a model that achieves the functional requirements while
operating within key constraints, such as performance goals and hardware. The main goal is
create a design which is simple, easily understood, easily communicated, and easily built and
easily tested design.

1.2 Scope
The Library Management System is being developed for the college. The important modules
that are going to implement in the proposed system.

Calculating the fines.

Reservation of books.
Searching facility depends upon i) Book name ii) Author.
Log in, depends upon campus Id.
Administrator has all the privileges to add, modify and delete the books.
My account facility for the student so that he can view his account details.
1.3 Intended Audience
This document is intended for use by technical developers. This document also includes sections
relevant to the operational and maintenance group.
The intended audiences for this document are:

The team members of Innovative library Solutions.

The administrative staff of the college who is the client.
The Project Supervisor

This document will be reviewed frequently by the above audiences to check if the different
phases of the project are being completed by meeting the given requirements. It is expected
that the intended audience shall critically review this document for functional accuracy and
revert to team with their feedback and comments within a less time.

1.4 Constraints
The team has to follow the rules specified in the team contract. The team is proceeding to
develop an appropriate system; however the design might slightly changed to meet the client
requirements.

1.5 Definitions, Acronyms, and Abbreviations

The acronyms that are constantly used in the document include the following.

SPMP – Software Project Management Plan.

SDD – Software Design Document.
SRS – Software Requirements Specification.
UML – Unified Modelling Language
RUP – Rational Unified Process
OMG – Object Management Group
ERD – Entity Relationship Diagram
DFD – Data Flow Diagram

The definitions that are constantly used in the document include the following.

Unified modelling language - The Unified Modelling Language™ - UML - is OMG's most-used
specification, and the way the world models not only application structure, behaviour, and
architecture, but also business process and data structure.

Rational Unified process - “Rational Unified Process Model is a software engineering process
which provides a disciplined approach to assigning tasks and responsibilities within a software
development organization for the successful development of software.”

2.0 System Overview

The Library Management System is a web-based application which is able to manage different
types of library resources such as Books, Magazines, News Papers, CD/DVDs, and any other
resources which the management feels in the future could form a resource

Basically, there are three views for the convenience of the user. In the catalogue view the user
can find the available books in library, in My Account view the user can know the details of
books he borrowed and in Administrator view the user can have all the rights to
add,delete,modify etc., Advanced search ,searches according to author ,campus, book name,
category ,ISBN number. Another button by name Search which is used to search depending
upon any one of the categories like author, book name etc., these are the main functions of the
system.

Context Diagram summarizes all processing activity and also helps users to view highest level of
system with system boundaries. The system overview can be shown in the form of context
diagram.
2.2 Data flow Diagram
Dataflow diagram is the graphical system model that shows all main requirements for an IS in
one diagram
3. System Architecture: The Three Tier Architecture:
To develop software for Library management system the architecture that we are implementing
is Three Tier Architecture. The User Interface Layer, Application Logic Layer and Data Storage
Layer together called as Three Tier Architecture.

3.1 User Interface Layer

The User Interface Layer will consist of everything shown directly to the client. This Layer will
communicate only with the Application Logic Layer. This Layer will also be responsible for initial
validation of any user inputted data. Any validation that requires communication to the Data
Storage Layer will however be completed at the Logic Layer.

3.2 Application Logic Layer

The Business logic for our project is Visual Basic. It will be responsible for providing a secure
connection to the Data Storage Layer and formatting information received from the SQL Server
for presentation to the User Interface Layer. Scripts that return user specific data, such as
advisory stream selection will be run on the Data Storage Layer.

3.3 Data Storage Layer

The Data Storage Layer will record all information required by the Logic and User Interface
Layer. This data will include Subject details for the Streams, and general user and admin user
information. All passwords stored in the database will be encrypted to prevent unauthorized
access. Within the Data Storage Layer a collection of SQL Queries will provide access to the data
in a meaningful way.

4.0Architectural Design
4.1Architectural Description
Name: Library First Page

Type: ASP page

Description:
First page contains the welcome message as well as the navigation buttons to direct the user to
other pages. First page consists of catalogue view, My Account, Administration, Advanced
Search and search. Left panel is continuously changing depending upon the selection of buttons
Operations:
Pre-condition: Connected to site
Post-condition: presents another page
Exceptions: None

Name: My Account page

Type: ASP page

Description:
If the user wants to check their account details, it can be done with the help of
MyAccount.When ever My Account button is clicked it asks the user login name and password,
if the login name and password is valid the user is directed to My account page. The left panel
changes into My Account left panel consists of Items borrowed, Issue history, Items over due
and Request an item. The user can know his return date to avoid fines.
Items Borrowed-Shows the current items holding by the user.
Issue History-Shows the history of issue details of the user.
Items overdue-Shows the overdue items of the user.
Request an item-Shows the information about the items where the user placed request.
Operations:

Pre-condition: Connected to site

Post-condition: presents another page
Exceptions: None

Name: Administration Page

Type: ASP page

Description:
Administrator has all the rights of the complete system. To access the Administration Page the
user has to enter login name and password if they are valid then the user can access
Administration page. The left panel is completed different from other pages. In the left panel
there are Authors, Categories, Items, Media Types, Users, Reports, final issue, Return Item and
Transfer.
Authors-Shows the authors list
Categories-Gives the information about all the categories of books in the database
Items-gives the information about books, CD’s etc.,
Media Types-Shows all media types like CD’s, VCD’s, books etc.,
Final Issue-This page contains the list of the people who requested the book, the administrator
checks the check box icon and final issue button then the books are finally issued to the
student.
Return Item-Searches the user and gets alist of all books issued to that particular user and clicks
on the return button to return the books.
Transfer-It shows a page where the administrator can have the book list and list of different
campuses and he can transfer books from one campus to other campus.
Operations:

Pre-condition: Connected to site

Post-condition: presents another page
Exceptions: None

5. Some screen shots of the library system

Login page for Administration page

6.0Database Description
The Database for Library Management System consists of sixteen tables. They are:
Authors
Campus
IssueDetails
Campus Item
Categories
ItemAuthors
ItemCategories
Usertype
Mediatype
RequestDetails
Reservation
Users
Items
CopyDetails
Payment
Preferences

6.1 Description of Each Table

Authors Table

The authors table stores all the details of the authors of the books. The author table consists of
three attributes which are AuthorId, AuthorName, Active. AuthorId is the primary key for this
table.

Campus Table

The Campus Table stores the details of the different campus of the university. It consists of two
attributes which are CampusId, CampusName and Active. CampusID is the primary key in this
table.

RequestDetails

The RequestDetails Table holds information of all the requests made by users for a book.the
attributes of this table are RequestDetailId, RequestedBy, CopydetailId, RequestDate,
RequestDeadlineDate, Status, Priority, SequenceNo.ThePrimary key in this table is
RequestDetailId..

Issue Details Table

The IssueDetails Table stores the details of the books issued. It will store information like
whom the book is issued to, on which date the book is issued, when the book is expected to
return ,the return date ,details of the copy with its ID.The attributes of this table are
IssueDetailsId, IssuedTo, IssuedDate, ExpectedDate, ReturnDate, CopyDetailId, IssueType,
RequestDate. IssueDetailsId is the primary key in this table.

CampusItem Table

The CampusItem table Stores the information about the different campuses for the
university.Each campus has a unique campus ID.The different attributes of this table are
CampusItemID, ItemID, CampusId. The CampusItemID acts as the primary key in this table.

Categories Table

The different attributes of the categories table are CategoryId, ParentId, CategoryName,
Description, and Active. The primary key in this table is CategoryId.

Items
The different Attributes of this table are ItemId, ItemName, Publisher,m AccessNumber, ISBN,
Description, Keywords, ItemEdition, ItemPrice isReference, Active, PreferenceId, MediaType.

ItemAuthors
The different attributes of this table are ItemId and AuthorId.

ItemCategories
This table has BookId and CategoryId as the attributes.Here BookId is the primar y
key.

Users
The users Table contains all the information of the users of the Library.The different attributes
of this table are UserId, LoginName, FirstName, MiddleName, LastName, CampusID, Password,
Email, Active, UsertypeId. UserId will be acting as the primary key in this table.

Usertype
The attributes of this table are UserTypeId and UserTypeName. The Primary Key in this table is
UserTypeId.

Mediatype
The attributes o f this Table are MediaTypeId, MediaTypeName and Active. MediaTypeId acts as
the Primary Key in this table.
Reservation

The Reservation tables hold the information of all the reservations made by users for a book in
the Library.The attributes of this table are ReservationId, ItemId, userId, ReservationDate and
Priority. The Primary Key in this table is ReservationId.

CopyDetails
This table stores the information of the different copies of books in the Library.The different
Attributes of this Table are CopyDetailsId, CampusItemId, Status, CopyPrice, Active and
isReference. The Primary Key in this table is CopyDetailId.

Payment
The payment table contains the information of the fines to be paid by users in case of late
return of issuedbooks.The attributes of this table are PaymentId, IssuDetailId, TotalAmount,
AmountPaid and isPaid.The primary key in this table is PaymentId.

Preferences
The different attributes of this table are PrferenceId, IssueDays and Blockdays
The primary key in this table is PreferenceId.
6.2 Relational Data Structures
Authors (AuthorId, AuthorName, Active)

Campus (CampusID, CampusName,Active)

RequestDetails (RequestDetailId, RequestedBy, CopydetailId, RequestDate,

RequestDeadlineDate, Status, Priority, SequenceNo)

Issue Details (IssueDetailsId, IssuedTo, IssuedDate, ExpectedDate, ReturnDate, CopyDetailId,

IssueType, RequestDate)

CampusItem (CampusItemID, ItemID, CampusId)

Categories (CategoryId, ParentId, CategoryName, Description, Active)

Items (ItemId, ItemName, Publisher,AccessNumber, ISBN, Description, Keywords, ItemEdition,

ItemPrice isReference, Active, PreferenceId, MediaType)

ItemAuthors (ItemId AuthorId.)

ItemCategories (BookId ,CategoryId)

Users (UserId, LoginName, FirstName, MiddleName, LastName, CampusID, Password, Email,
Active, UsertypeId)

Usertype (UserTypeId, UserTypeName)

Mediatype (MediaTypeId, MediaTypeName, Active)

Reservation (ReservationId, ItemId, UserId, ReservationDate, Priority)

CopyDetails (CopyDetailsId, CampusItemId, Status, CopyPrice, Active and isReference)

Payment (PaymentId, IssueDetailId, TotalAmount, AmountPaid, isPaid)

Preferences (PreferenceId, IssueDays, Blockdays)

6.3Entity Relationship Diagram

6.4 Relational Database Schema

Table Name Attributes Type Description

Authors AuthorId Number Primary Key
AuthorName Text
Active Text

Campus CampusID Number Primary Key

CampusName Text
Active Text

RequestDetails RequestDetailId Number Primary Key

RequestedBy Number
CopydetailId Number
RequestDate Text
RequestDeadline Text
Date Text
Status Number
SequenceNo Number
Priority Number

Issue Details IssueDetailsId Number Primary Key

IssuedTo Number
IssuedDate Text
ExpectedDate Text
ReturnDate Text
CopyDetailId Number
IssueType Number
RequestDate Text

CampusItem CampusItemID Number Primary Key

ItemID Number Foreign Key
CampusId Number Foreign Key

Categories CategoryId Number Primary Key

ParentId Number
CategoryName Text
Description Text
Active Text

Items ItemId Number Primary Key

ItemName Text
Publisher Text
AccessNumber Text
ISBN Text
 Description Text
Keywords Text
ItemPrice Number
isReference Text
PreferenceId Text Foreign Key
Active Number
MediaType Number

ItemAuthors ItemId Number Primary Key

AuthorId. Number Foreign Key

ItemCategories BookId Number Primary Key

CategoryId Number Foreign Key

Users UserId Number Primary Key

LoginName Text
FirstName Text
MiddleName Text
LastName Text
CampusID Number Foreign Key
Password Text
Email Text
Active Text
UsertypeId Number Foreign Key

Usertype UserTypeId Number

UserTypeName Text

Mediatype MediaTypeId Number Primary Key

MediaTypeName Text
Active Text

Reservation ReservationId Number Primary Key

ItemId Number Foreign Key
UserId Number Foreign Key
ReservationDate Text
Priority Number

CopyDetails CopyDetailsId Number Primary Key

CampusItemId Number Foreign Key
Status Number
CopyPrice Number
Active Text
isReference Text

Payment PaymentId Number Primary Key

 IssueetailId Number Foreign Key
TotalAmount Number
AmountPaid Number
isPaid Text

Preferences PreferenceId Number Primary Key

IssueDays Number
Blockdays Number

6.5Data Dictionary
Name Used in the Description
System
Authors Table name which contains the information of the
Authors of different books
AuthorId Each author is given a unique AuthorID
AuthorName Name of the Author
Active
Campus Name given to table which stores different
campus details
CampusID Each campus is given a unique number
CampusName Name of the Campus
RequestDetails Table name which stores the information of
requests made by students
RequestDetailId Unique number given to each request made
RequestedBy Name of the person who made a request
CopydetailId Details of the copy where each copy has a unique
ID
RequestDate Date on which the request is made
RequestDeadline Date for the deadline of the request
Status Status of the book availableor not
SequenceNo This store the sequence numbers
IssueDetails IssueDetails tables stores the details of the book s
which are issued
IssueDetailsId Primary key in Issue details Table
IssuedTo To whom the book is issued
IssuedDate Date when the issue is done
ExpectedDate When the book will be expected to returned
ReturnDate When the book will is returned
CopyDetailId Details of the Copy of the book
IssueType What is type os issue
RequestDate Date when the request is made
CampusItemID Number for each Campus
ItemID Id given to each Item
CampusId Id given to each Campus
CategoryId Number given to each category
ParentId Number given to each parent Book
CategoryName Name of the Category to which the book belongs
to
Description Description of the book
Active Status whether active or not
ItemName Name of the Item
Publisher Nameof th epublisher
AccessNumber Number for access
ISBN ISBN number of the book
Description Description of the book
Keywords Any keywords for the book
ItemPrice Price of the book
isReference If it is a reference book thisis true
PreferenceId Number given for preference
Active Satus given
MediaType Type of Media for the Item
AuthorId. Number given to each author
BookId Number given to each book
UserId Number given to each user
LoginName User Login name
FirstName First Name of the user
MiddleName Middle Name of the User
LastName Last Name of the user
CampusID ID given to each campus
Password Password given to the User
Email Email id of the user
Active Satus whether true or false
UsertypeId Type of user each user has an ID
UserTypeName Name of the UserType
ReservationId Each Reservation has a unique ID
ItemId Each Item has a Unique ID
ReservationDate Date when the reservation is made
Priority If staff priority is given first to them
CopyPrice Price of the Copy
PaymentId Each payment is given a unique payment Id
TotalAmount Total Amount to be paid
AmountPaid Amount paid till now
isPaid Whether paymentis paid
IssueDays For how may days the book is issued
Blockdays For how many days the book is blocked

End Users of This Database

The end users of this database are:

The main client who will be using Library Management System is University of Ballarat
Students of university of Ballarat
Staff of University of Ballarat

Administrators of This Database

The Librarian will be the administrators of this database.

The management staff who are appointed as administrators for the Library.
5.3 Some screen shots of the library system
Login page for Administration page
2.1Context Diagram for Library Management System

Software Requirements Specification

1. Introduction

1.1. Purpose

The main objective of this document is to illustrate the requirements of the project Library
Management system. The document gives the detailed description of the both functional and
non functional requirements proposed by the client. The document is developed after a number
of consultations with the client and considering the complete requirement specifications of the
given Project. The final product of the team will be meeting the requirements of this document.

1.2. Document Conventions

The following are the list of conventions and acronyms used in this document and the project as
well:
 Administrator: A login id representing a user with user administration privileges to the
software
 User: A general login id assigned to most users
 Client: Intended users for the software
 SQL: Structured Query Language; used to retrieve information from a database
 SQL Server: A server used to store data in an organized format
 ASP: Active Server Pages: A Web Page formatted on the server and delivered to the
browser.
 Layer: Represents a section of the project
 User Interface Layer: The section of the assignment referring to what the user interacts
with directly.
 Application Logic Layer: The section of the assignment referring to the Web Server. This
is where all computations are completed.
 Data Storage Layer: The section of the assignment referring to where all data is recorded
 Data flow diagram:It shows the dataflow between the entities.
 Use Case: A broad level diagram of the project showing a basic overview
 Boolean: A true/false notation
 Interface: Something used to communicate across different mediums
 Unique Key: Used to differentiate entries in a database

1.3. Intended Audience and Reading Suggestions

The intended audiences for this document are:
 The team members of Innovative library Solutions.
 The librarian of the college who is the client.
 The Project Supervisor and Project Coordinator.

This document will be reviewed frequently by the above audiences to check if the different
phases of the project are being completed by meeting the given requirements.

2. Overall Description
2.1 Product Perspective

The proposed Library Management System which is being developed by Innovative Library
Management Solutions team is an on-line Library Management System. This System will provide
a search functionality to facilitate the search of resources. This search will be based on various
categories viz. book name or the ISBN. Also Advanced Search feature is provided in order to
search various categories simultaneously. Further the library staff personnel can
add/update/remove the resources and the resource users from the system.

2.2 Product Features

There are two different users who will be using this product:

 Librarian who will be acting as the administrator

 Student of the University who will be accessing the Library online.

The features that are available to the Librarian are:

 A librarian can issue a book to the student

 Can view The different categories of books available in the Library
 Can view the List of books available in each category
 Can take the book returned from students
 Add books and their information of the books to the database
 Edit the information of the existing books.
 Can check the report of the issued Books.
 Can access all the accounts of the students.

The features available to the Students are:

 Can view The different categories of books available in the Library

 Can view the List of books available in each category
 Can own an account in the library
 Can view the books issued to him
 Can put a request for a new book
 Can view the history of books issued to him previously
 Can search for a particular book

2.3 User Classes and Characteristics

There are various kinds of users for the product. Usually web products are visited by various
users for different reasons.

The users include :

Students who will be using the above features by accessing the Library online.
 Librarian who will be acting as the controller and he will have all the privileges of an
administrator.

2.4 Operating Environment

The product will be operating in windows environment. Also it will be compatible with the IE
6.0. Most of the features will be compatible with the Mozilla firefox & Opera 7.0 or higher
version. The only requirement to use this online product would be the internet connection.

2.5 Design and Implementation Constraints

The Product is developed using ASP. The backend database for this MySQL Server. The product is
accomplished with login facility so that specific function is available to specific student.

2.6 User Documentation

The product will include user manual. The user manual will include product overview, complete
configuration of the used software (such as SQL server), technical details, backup procedure and
contact information which will include email address. There will be no online help for the
product at this moment. The product will be compatible with the Internet Explorer 6.0 or
higher. The databases will be created in the MySQL.

2.7 Assumptions and Dependencies

The product needs following third party product.

 MySQL server to store the database.

 ASP to develop the Product
3. System Features
3.1. Database – Storage

3.1.1. Description and Priority

Proposed Database is intended to store, retrieve, update, and manipulate information related to
university which include

 Books availability
 Staff information
 Student details
 My Account
 Calculation of fines

3.1.2. Stimulus / Response Sequences

Responses for Administrator: The administrator can Login and Logout. When the Administrator
Logs into the Library system. The system will check for validity of login .If the Login and
password are valid, the response to this action is the administrator will be able to modify, view,
add, deleting and all other functions that can be performed on the database.

3.2. Functional Requirements

This section gives the list of Functional and non functional requirements which are applicable to
the Library Management System.

3.2.1 Interface Requirements

This section describes how the software interfaces with other software products or users for
input or output.

3.2.1.1UserInterfaces

Describes how this product interfaces with the user.

GUI - Describes the graphical user interface if present. This section should include a set of
screen dumps or mockups to illustrate user interface features.

Description - The user interface must be customizable by the administrator

Criticality- This issue is essential to the overall system. All the modules provided with the
software must fit into this graphical user interface and accomplish to the standard defined.
Technical issues - In order to satisfy this requirement the design should be simple and all the
different interfaces should follow a standard template. There will be the possibility of changing
colors and images, plus switching between interfaces with the minimum impact for the users.

Risks - To reduce the circumstances under which this requirement might not able to be satisfied,
all the designers must have been developed web sites previously and they must be aware of
html restriction and cross browsers implementations before starting the designing. In order to
reduce the probability of this occurrence the entire design team will be trained in basic html
development and macromedia fireworks, this tool will be used instead of Photoshop.

Dependencies with other requirements - All user interfaces should be able to interact with the
user management module and a part of the interface must be dedicated to the login/logout
module

4. Non Functional Requirements

4.2. Hardware Interfaces

Server Side:

 Operating System: Windows 9x/xp ,Windows ME

 Processor: Pentium 3.0 GHz or higher

 RAM: 256 Mb or more

 Hard Drive: 10 GB or more

Client side:

 Operating System: Windows 9x or above, MAC or UNIX.

  Processor: Pentium III or 2.0 GHz or higher.

 RAM: 256 Mb or more

4.3. Software Interfaces

 Database: SQL Server.

 Application: ASP (Active Server Pages)

 Web Server: IIS (Internet Information Services (IIS) is a

powerful Web server that provides a highly reliable, manageable, and
scalable Web application infrastructure)

4.4. Communications Interfaces

The Customer must connect to the Internet to access the

Website:

 Dialup Modem of 52 kbps

 Broadband Internet

 Dialup or Broadband Connection with a Internet Provider.

5. Other Nonfunctional Requirements

5.1. Performance Requirements

The proposed system that we are going to develop will be used as the
Chief performance system within the different campuses of the
university which interact with the university staff and students.
Therefore, it is expected that the database would perform functionally
all the requirements that are specified by the university.

5.2. Safety Requirements

The database may get crashed at any certain time due to virus or
operating system failure. Therefore, it is required to take the
database backup.

5.3. Security Requirements

We are going to develop a secured database for the university .There

are different categories of users namely teaching staff, administrator,
library staff, students etc., Depending upon the category of user the
access rights are decided. It means if the user is an administrator
then he can be able to modify the data, delete, append etc., All other
users other than library staff only have the rights to retrieve the
information about database.

5.4. Software Quality Attributes

The Quality of the database is maintained in such a way so that it

can be very user friendly to all the users of the database.

5.5 Hardware Constraints

The system requires a database in order to store persistent data. The

database should have backup capabilities.

5.6 Software Constraints

 The development of the system will be constrained by the availability
of required software such as web servers, database and development
tools.

The availability of these tools will be governed by the University.

The most recent versions of software development tools may not be

installed at the University.

5.7 Design Constraints

The system must be designed to allow web usability. That is, the
system must

be designed in such a way that will be easy to use and visible on

most of the browsers.