Miniproject Simple Srs

7/26/2019 Miniproject Simple Srs

1/32

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 doesnt allow users to login from

dierent campuses.

1. As it is not available online every student calls up to nd out if the boo is

available or not. ! Too many calls to answer

". #very time a student calls for a boo you have to chec the racs for the

availability of the boo. ! Too much of physical wor.

$. %f some one reserves the boo& hes not sure if he denitely can get the

boo as the previous student may not return in time.

'. #ither the student has to call or come to the library to reserve the boo&

but cannot reserve online over the internet.

(. )ines have to be calculated manually.

*. +tudents have no idea to chec their account.

Project Scope

Project Title : Library Management System

Date :

Prepared By :

Project Justifcation:


2/32

This pro,ect is basically updating the manual library system into a

internet based application so that the users can now the details of

their account &availability of boos etc.&

Product Caracteristics and !e"uirements :

1. +ecured database.

". -ser tracing

$. +earch feature

'.alculating nes

(. hecing the availability of boos.

*.+tudents will get an #!mail before the due date in order to avoid

nes

Project Management Deli#erables:

Pro,ect plan& /esearch nding report& 0or breadown structure&

+cope statement& Pro,ect charter& Training manuals& lessons learned

report etc.&

Product$related deli#erables :

/esearch reports &design documents& software code& hardware

&test plan& pro,ect benet measurement plan etc.&

Project Success Criteria: ur main goal is to complete this pro,ect

within allotted dead line and also within the budget allotted. %t is

necessary to develop a method for capturing the benets while the

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


3/32

rolled out. %f the pro,ect taes a little longer to complete or costs a little

more than planned& the rm will still view it as a success if it has a

good paybac and helps promote the rms image as an e2cellent

management organi3ation

% +tatement of 0or

1. Scope of Work

The on!line Library 4anagement +ystem should manage dierent types of

library resources such as 5oos& 4aga3ines& 6ews Papers& 78797s& and any

other resources which the management feels in the future could form a

resource. A resource can be categori3ed to facilitate searching& sorting and

managing the resources. This can be e2emplied by dividing the boos as

being in %T or 5usiness category. +tudents and -niversity +ta 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. %f a stipulated return date has been specied and the resource

is not returned within this stipulated due date& a ne may be imposed on the

resource user. The basic ne amount should be updatable by the

management if a need to do so arises in the future. The +ystem should also

allow for a provision to bloc a resource& where by an individual can borrow

the bloced resource once it is returned by the current borrower.

2. Location of Work

The client for this pro,ect is the library which is inside the campus.

3. Period of Performance


4/32

The duration of the pro,ect is $ months. All the tass are e:ually distributed

among team members to accomplish the goal of completing the pro,ect.

4. Deliverables Schedule

Deli#erable Date Due

0ritten report part %;

+tatement of wor and Pro,ect Plan

0ee $

0ritten report part %%;

Pro,ect scope < problem statement8

re:uirements specication

0ee *

0ritten report part %%%;

Problem analysis and research report

0ee =

0ritten report part %9;

Prototype implementation or practical

e2perimental wor

0ee 11

0ritten report part 9;

/eview of results and statement of ndings

>including test reports?

0ee 1"

0ritten report part 9%;

+tatus reports and pro,ect diary

ngoing assessment at

supervisor meetings

5. pplicable Standards!


5/32

The pro,ect @Library 4anagement +ystem follows various

programming standards.

". cceptance #riteria!

The acceptance criteria for the users are

The website has to communicate with the database.

-sers can easily search the boo with in less time

4aintaining the account details of the user.

-sers can bloc the boo& view the boo through online etc.&.

$. dditional %e&uirements:

Bualied team members are very important for pro,ect.Team members have

to have a basic nowledge in the following areas;

A sound nowledge in programming languages such as A+P& Cava

and dot net and a nowledge of databases such as 4y+BL& +BL

server or Access.


6/32

So't(are Design Document

1. %ntroduction+oftware 7esign 7ocument is the design wor product that formallydocuments the design of the software components. +oftware 7esign7ocument gives us the detailed description about the Dow of the pro,ect.

1.1 Purpose+oftware 7esign 7ocument denes the modules& interfaces and the

interaction between modules and interfaces. %t also helps us in givinginformation about how the system will loo the appearance of user interfacesand the information about static and dynamic view of the system.The detailed design document is the developerEs blueprint. %t providesprecise directions to software programmers about how basic control and datastructures will be organi3ed. Typically& the 7etailed 7esign 7ocumentconsists of tables and diagrams that translate the functional specicationinto data structures& data Dows& and algorithms.The 7etailed 7esign 7ocument is written before programming starts. %t

describes how the software will be structured& and what functionality will beincluded. This document forms the basis for all future design and coding.

The designerEs goal is to develop a model that achieves the functionalre:uirements while operating within ey constraints& such as performancegoals and hardware. The main goal is create a design which is simple& easilyunderstood& easily communicated& and easily built and easily tested design.


7/32

1." +copeThe Library 4anagement +ystem is being developed for the college. Theimportant modules that are going to implement in the proposed system.

alculating the nes./eservation of boos.+earching facility depends upon i? 5oo name ii? Author.Log in& depends upon campus %d.Administrator has all the privileges to add& modify and delete the boos.4y account facility for the student so that he can view his account details.

1.$ %ntended Audience

This document is intended for use by technical developers. This documentalso includes sections relevant to the operational and maintenance group.

The intended audiences for this document are;

The team members of %nnovative library +olutions.The administrative sta of the college who is the client.The Pro,ect +upervisor

This document will be reviewed fre:uently by the above audiences to checif the dierent phases of the pro,ect are being completed by meeting thegiven re:uirements. %t is e2pected that the intended audience shall criticallyreview this document for functional accuracy and revert to team with theirfeedbac and comments within a less time.

1.' onstraints

The team has to follow the rules specied in the team contract. The team isproceeding to develop an appropriate systemF however the design mightslightly changed to meet the client re:uirements.

1.( 7enitions& Acronyms& and AbbreviationsThe acronyms that are constantly used in the document include the

following.+P4P G +oftware Pro,ect 4anagement Plan.+77 G +oftware 7esign 7ocument.+/+ G +oftware /e:uirements +pecication.-4L G -nied 4odelling Language/-P G /ational -nied Process4H G b,ect 4anagement Hroup


8/32

#/7 G #ntity /elationship 7iagram7)7 G 7ata )low 7iagramThe denitions that are constantly used in the document include thefollowing.

-nied modelling language ! The -nied 4odelling LanguageI ! -4L ! is4HEs most!used specication& and the way the world models not onlyapplication structure& behaviour& and architecture& but also business processand data structure.

/ational -nied process ! @/ational -nied Process 4odel is a softwareengineering process which provides a disciplined approach to assigning tassand responsibilities within a software development organi3ation for thesuccessful development of software.

".J +ystem verview

The Library 4anagement +ystem is a web!based application which is able tomanage dierent types of library resources such as 5oos& 4aga3ines& 6ewsPapers& 78797s& and any other resources which the management feels inthe future could form a resource

5asically& there are three views for the convenience of the user. %n thecatalogue view the user can nd the available boos in library& in 4y Accountview the user can now the details of boos he borrowed and inAdministrator view the user can have all the rights to add&delete&modify etc.&Advanced search &searches according to author &campus& boo name&category &%+56 number. Another button by name +earch which is used tosearch depending upon any one of the categories lie author& boo nameetc.& these are the main functions of the system.onte2t 7iagram summari3es all processing activity and also helps users toview highest level of system with system boundaries. The system overviewcan be shown in the form of conte2t diagram.


9/32

"." 7ata Dow 7iagram

7ataDow diagram is the graphical system model that shows all mainre:uirements for an %+ in one diagram


10/32

$. +ystem Architecture; The Three TierArchitecture;To develop software for Library management system the architecture that weare implementing is Three Tier Architecture. The -ser %nterface Layer&Application Logic Layer and 7ata +torage Layer together called as Three TierArchitecture.

$.1 -ser %nterface Layer

The -ser %nterface Layer will consist of everything shown directly to theclient. This Layer will communicate only with the Application Logic Layer.This Layer will also be responsible for initial validation of any user inputteddata. Any validation that re:uires communication to the 7ata +torage Layerwill however be completed at the Logic Layer.


11/32

$." Application Logic Layer

The 5usiness logic for our pro,ect is 9isual 5asic. %t will be responsible forproviding a secure connection to the 7ata +torage Layer and formattinginformation received from the +BL +erver for presentation to the -ser

%nterface Layer. +cripts that return user specic data& such as advisorystream selection will be run on the 7ata +torage Layer.

$.$ 7ata +torage Layer

The 7ata +torage Layer will record all information re:uired by the Logic and-ser %nterface Layer. This data will include +ub,ect details for the +treams&and general user and admin user information. All passwords stored in thedatabase will be encrypted to prevent unauthori3ed access. 0ithin the 7ata+torage Layer a collection of +BL Bueries will provide access to the data in a

meaningful way.

'.JArchitectural 7esign'.1Architectural 7escription

6ame; Library )irst PageType; A+P page7escription;)irst page contains the welcome message as well as the navigation buttonsto direct the user to other pages. )irst page consists of catalogue view& 4yAccount& Administration& Advanced +earch and search. Left panel iscontinuously changing depending upon the selection of buttonsperations;

Pre!condition; onnected to site Post!condition; presents another page #2ceptions; 6one6ame; 4y Account page

Type; A+P page7escription;%f the user wants to chec their account details& it can be done with the helpof 4yAccount.0hen ever 4y Account button is cliced it ass the user loginname and password& if the login name and password is valid the user isdirected to 4y account page. The left panel changes into 4y Account left


12/32

panel consists of %tems borrowed& %ssue history& %tems over due and /e:uestan item. The user can now his return date to avoid nes.%tems 5orrowed!+hows the current items holding by the user.%ssue Kistory!+hows the history of issue details of the user.%tems overdue!+hows the overdue items of the user.

/e:uest an item!+hows the information about the items where the userplaced re:uest.perations;

Pre!condition; onnected to site Post!condition; presents another page #2ceptions; 6one

6ame; Administration Page

Type; A+P page7escription;Administrator has all the rights of the complete system. To access theAdministration Page the user has to enter login name and password if theyare valid then the user can access Administration page. The left panel iscompleted dierent from other pages. %n the left panel there are Authors&ategories& %tems& 4edia Types& -sers& /eports& nal issue& /eturn %tem andTransfer.Authors!+hows the authors listategories!Hives the information about all the categories of boos in thedatabase

%tems!gives the information about boos& 7s etc.&4edia Types!+hows all media types lie 7s& 97s& boos etc.&)inal %ssue!This page contains the list of the people who re:uested the boo&the administrator checs the chec bo2 icon and nal issue button then theboos are nally issued to the student./eturn %tem!+earches the user and gets alist of all boos issued to thatparticular user and clics on the return button to return the boos.Transfer!%t shows a page where the administrator can have the boo list andlist of dierent campuses and he can transfer boos from one campus toother campus.perations;

Pre!condition; onnected to site Post!condition; presents another page #2ceptions; 6one


13/32

(. +ome screen shots of the library systemLogin page for Administration page

*.J7atabase 7escriptionThe 7atabase for Library 4anagement +ystem consists of si2teen tables.They are;Authorsampus%ssue7etailsampus %temategories

%temAuthors%temategories-sertype4ediatype/e:uest7etails/eservation-sers%temsopy7etailsPaymentPreferences

*.1 7escription of #ach TableAuthors TableThe authors table stores all the details of the authors of the boos. Theauthor table consists of three attributes which are Author%d& Author6ame&Active. Author%d is the primary ey for this table.ampus TableThe ampus Table stores the details of the dierent campus of the university.%t consists of two attributes which are ampus%d& ampus6ame and Active.ampus%7 is the primary ey in this table./e:uest7etails


14/32

The /e:uest7etails Table holds information of all the re:uests made by usersfor a boo.the attributes of this table are /e:uest7etail%d& /e:uested5y&opydetail%d& /e:uest7ate& /e:uest7eadline7ate& +tatus& Priority&+e:uence6o.ThePrimary ey in this table is /e:uest7etail%d..

%ssue 7etails TableThe %ssue7etails Table stores the details of the boos issued. %t will storeinformation lie whom the boo is issued to& on which date the boo isissued& when the boo is e2pected to return &the return date &details of thecopy with its %7.The attributes of this table are %ssue7etails%d& %ssuedTo&%ssued7ate& #2pected7ate& /eturn7ate& opy7etail%d& %ssueType&/e:uest7ate. %ssue7etails%d is the primary ey in this table.ampus%tem Table

The ampus%tem table +tores the information about the dierent campusesfor the university.#ach campus has a uni:ue campus %7.The dierentattributes of this table are ampus%tem%7& %tem%7& ampus%d. Theampus%tem%7 acts as the primary ey in this table.ategories TableThe dierent attributes of the categories table are ategory%d& Parent%d&ategory6ame& 7escription& and Active. The primary ey in this table isategory%d.

%temsThe dierent Attributes of this table are %tem%d& %tem6ame& Publisher&mAccess6umber& %+56& 7escription& eywords& %tem#dition& %temPriceis/eference& Active& Preference%d& 4ediaType.%temAuthorsThe dierent attributes of this table are %tem%d and Author%d.%temategoriesThis table has 5oo%d and ategory%d as the attributes.Kere 5oo%d is theprimar y ey.

-sers The users Table contains all the information of the users of the Library.Thedierent attributes of this table are -ser%d& Login6ame& )irst6ame&4iddle6ame& Last6ame& ampus%7& Password& #mail& Active& -sertype%d.-ser%d will be acting as the primary ey in this table.-sertype


15/32

The attributes of this table are -serType%d and -serType6ame. The Primaryey in this table is -serType%d.4ediatypeThe attributes o f this Table are 4ediaType%d& 4ediaType6ame and Active.

4ediaType%d acts as the Primary ey in this table.


16/32

/eservationThe /eservation tables hold the information of all the reservations made byusers for a boo in the Library.The attributes of this table are /eservation%d&%tem%d& user%d& /eservation7ate and Priority. The Primary ey in this table is

/eservation%d.opy7etailsThis table stores the information of the dierent copies of boos in theLibrary.The dierent Attributes of this Table are opy7etails%d&ampus%tem%d& +tatus& opyPrice& Active and is/eference. The Primary ey inthis table is opy7etail%d.PaymentThe payment table contains the information of the nes to be paid by usersin case of late return of issuedboos.The attributes of this table are

Payment%d& %ssu7etail%d& TotalAmount& AmountPaid and isPaid.The primaryey in this table is Payment%d.PreferencesThe dierent attributes of this table are Prference%d& %ssue7ays and5locdaysThe primary ey in this table is Preference%d.

*." /elational 7ata +tructuresAuthors >Author%d& Author6ame& Active?ampus >ampus%7& ampus6ame&Active?/e:uest7etails >/e:uest7etail%d& /e:uested5y& opydetail%d& /e:uest7ate&/e:uest7eadline7ate& +tatus& Priority& +e:uence6o?%ssue 7etails >%ssue7etails%d& %ssuedTo& %ssued7ate& #2pected7ate&/eturn7ate& opy7etail%d& %ssueType& /e:uest7ate?ampus%tem >ampus%tem%7& %tem%7& ampus%d?ategories >ategory%d& Parent%d& ategory6ame& 7escription& Active?%tems >%tem%d& %tem6ame& Publisher&Access6umber& %+56& 7escription&eywords& %tem#dition& %temPrice is/eference& Active& PreferenceId&4ediaType?%temAuthors >%tem%d AuthorId.?


17/32

%temategories >5oo%d &CategoryId?-sers >-ser%d& Login6ame& )irst6ame& 4iddle6ame& Last6ame& CampusID&Password& #mail& Active& UsertypeId?

-sertype >-serType%d& -serType6ame?4ediatype >4ediaType%d& 4ediaType6ame& Active?/eservation >/eservation%d& ItemId& -ser%d& /eservation7ate& Priority?opy7etails >opy7etails%d& CampusItemId& +tatus& opyPrice& Active andis/eference?Payment >Payment%d& IssueDetailId& TotalAmount& AmountPaid& isPaid?

Preferences >Preference%d& %ssue7ays& 5locdays?

*.$#ntity /elationship 7iagram


18/32


19/32

6.4 Relational Database Schema

'able (ame ttributes ')pe Description

uthors uthor*d (umber Primar) +e)

uthor(ame 'e,t

ctive 'e,t

#ampus #ampus*D (umber Primar) +e) #ampus(ame 'e,t

ctive 'e,t

%e&uestDetails %e&uestDetail*d (umber Primar) +e) %e&uested-) (umber

#op)detail*d (umber

%e&uestDate 'e,t%e&uestDeadline 'e,t

Date 'e,tStatus (umberSe&uence(o (umber

Priorit) (umber

*ssue Details *ssueDetails*d (umber Primar) +e) *ssued'o (umber

*ssuedDate 'e,t

,pectedDate 'e,t%eturnDate 'e,t

#op)Detail*d (umber*ssue')pe (umber

%e&uestDate 'e,t

#ampus*tem #ampus*tem*D (umber Primar) +e)

*tem*D (umber /orei0n +e) #ampus*d (umber /orei0n +e)

#ate0ories #ate0or)*d (umber Primar) +e) Parent*d (umber

#ate0or)(ame 'e,t

Description 'e,t

ctive 'e,t

*tems *tem*d (umber Primar) +e)

*tem(ame 'e,tPublisher 'e,t

ccess(umber 'e,t

*S-( 'e,t


20/32

Description 'e,t

+e)ords 'e,t

*temPrice (umberis%eference 'e,t

Preference*d 'e,t /orei0n +e)

ctive (umberedia')pe (umber

*temuthors *tem*d (umber Primar) +e) uthor*d. (umber /orei0n +e)

*tem#ate0ories -ook*d (umber Primar) +e)

#ate0or)*d (umber /orei0n +e)

sers ser*d (umber Primar) +e)

Lo0in(ame 'e,t

/irst(ame 'e,tiddle(ame 'e,t

Last(ame 'e,t#ampus*D (umber /orei0n +e)

Passord 'e,t

mail 'e,t

ctive 'e,tsert)pe*d (umber /orei0n +e)

sert)pe ser')pe*d (umberser')pe(ame 'e,t

ediat)pe edia')pe*d (umber Primar) +e) edia')pe(ame 'e,t

ctive 'e,t

%eservation %eservation*d (umber Primar) +e)

*tem*d (umber /orei0n +e)

ser*d (umber /orei0n +e)

%eservationDate 'e,tPriorit) (umber

#op)Details #op)Details*d (umber Primar) +e) #ampus*tem*d (umber /orei0n +e)

Status (umber

#op)Price (umberctive 'e,t

is%eference 'e,t

Pa)ment Pa)ment*d (umber Primar) +e)


21/32

*ssueetail*d (umber /orei0n +e)

'otalmount (umber

mountPaid (umberisPaid 'e,t

Preferences Preference*d (umber Primar) +e) *ssueDa)s (umber

-lockda)s (umber

6.5Data Dictionary

(ame sed in theS)stem

Description

uthors 'able name hich contains the information of the

uthors of different books

uthor*d ach author is 0iven a uni&ue uthor*D

uthor(ame (ame of the uthor ctive

#ampus (ame 0iven to table hich stores different

campus details#ampus*D ach campus is 0iven a uni&ue number

#ampus(ame (ame of the #ampus%e&uestDetails 'able name hich stores the information of

re&uests made b) students

%e&uestDetail*d ni&ue number 0iven to each re&uest made

%e&uested-) (ame of the person ho made a re&uest#op)detail*d Details of the cop) here each cop) has a uni&ue

*D

%e&uestDate Date on hich the re&uest is made%e&uestDeadline Date for the deadline of the re&uest

Status Status of the book availableor not

Se&uence(o 'his store the se&uence numbers*ssueDetails *ssueDetails tables stores the details of the book s

hich are issued

*ssueDetails*d Primar) ke) in *ssue details 'able*ssued'o 'o hom the book is issued

*ssuedDate Date hen the issue is done

,pectedDate When the book ill be e,pected to returned


22/32

%eturnDate When the book ill is returned

#op)Detail*d Details of the #op) of the book

*ssue')pe What is t)pe os issue%e&uestDate Date hen the re&uest is made

#ampus*tem*D (umber for each #ampus

*tem*D *d 0iven to each *tem#ampus*d *d 0iven to each #ampus

#ate0or)*d (umber 0iven to each cate0or)

Parent*d (umber 0iven to each parent -ook #ate0or)(ame (ame of the #ate0or) to hich the book belon0s

to

Description Description of the book ctive Status hether active or not

*tem(ame (ame of the *tem

Publisher (ameof th epublisher

ccess(umber (umber for access

*S-( *S-( number of the book Description Description of the book

+e)ords n) ke)ords for the book *temPrice Price of the book

is%eference *f it is a reference book thisis true

Preference*d (umber 0iven for preferencective Satus 0iven

edia')pe ')pe of edia for the *tem

uthor*d. (umber 0iven to each author -ook*d (umber 0iven to each book

ser*d (umber 0iven to each user

Lo0in(ame ser Lo0in name/irst(ame /irst (ame of the useriddle(ame iddle (ame of the ser

Last(ame Last (ame of the user

#ampus*D *D 0iven to each campusPassord Passord 0iven to the ser

mail mail id of the user

ctive Satus hether true or falsesert)pe*d ')pe of user each user has an *D

ser')pe(ame (ame of the ser')pe

%eservation*d ach %eservation has a uni&ue *D

*tem*d ach *tem has a ni&ue *D%eservationDate Date hen the reservation is made

Priorit) *f staff priorit) is 0iven first to them

#op)Price Price of the #op)Pa)ment*d ach pa)ment is 0iven a uni&ue pa)ment *d

'otalmount 'otal mount to be paid

mountPaid mount paid till noisPaid Whether pa)mentis paid


23/32

*ssueDa)s /or ho ma) da)s the book is issued

-lockda)s /or ho man) da)s the book is blocked

#nd -sers of This 7atabase

The end users of this database are;

The main client who will be using Library 4anagement +ystem is -niversity of5allarat+tudents of university of 5allarat+ta of -niversity of 5allarat

Administrators of This 7atabase

The Librarian will be the administrators of this database.The management sta who are appointed as administrators for the Library.


24/32

(.$ +ome screen shots of the library system

Login page for Administration page


25/32

2.1Context Diagram for Library Management System

+oftware /e:uirements +pecication1. Introduction1.1. Purpose

The main ob,ective of this document is to illustrate the re:uirements of thepro,ect Library 4anagement system. The document gives the detaileddescription of the both functional and non functional re:uirements proposedby the client. The document is developed after a number of consultations

with the client and considering the complete re:uirement specications ofthe given Pro,ect. The nal product of the team will be meeting there:uirements of this document.

1.2. Document Conventions

The following are the list of conventions and acronyms used in this documentand the pro,ect as well;

Administrator; A login id representing a user with user administrationprivileges to the software

-ser; A general login id assigned to most users

lient; %ntended users for the software +BL; +tructured Buery LanguageF used to retrieve information from a

database

+BL +erver; A server used to store data in an organi3ed format

A+P; Active +erver Pages; A 0eb Page formatted on the server and

delivered to the browser.

Layer; /epresents a section of the pro,ect

-ser %nterface 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

0eb +erver. This is where all computations are completed. 7ata +torage Layer; The section of the assignment referring to where

all data is recorded

7ata Dow diagram;%t shows the dataDow between the entities.

-se ase; A broad level diagram of the pro,ect showing a basic

overview

5oolean; A true8false notation


26/32

%nterface; +omething used to communicate across dierent mediums

-ni:ue ey; -sed to dierentiate entries in a database

1.3. Intended Audience and Reading Suggestions

The intended audiences for this document are; The team members of %nnovative library +olutions.

The librarian of the college who is the client.

The Pro,ect +upervisor and Pro,ect oordinator.

This document will be reviewed fre:uently by the above audiences to checif the dierent phases of the pro,ect are being completed by meeting thegiven re:uirements.

2. Overall Description2.1 Product PerspectiveThe proposed Library 4anagement +ystem which is being developed by%nnovative Library 4anagement +olutions team is an on!line Library4anagement +ystem. This +ystem will provide a search functionality tofacilitate the search of resources. This search will be based on variouscategories vi3. boo name or the %+56. Also Advanced +earch feature isprovided in order to search various categories simultaneously. )urther thelibrary sta personnel can add8update8remove the resources and theresource users from the system.

2.2 Product FeaturesThere are two dierent users who will be using this product;

Librarian who will be acting as the administrator

+tudent of the -niversity who will be accessing the Library online.

The features that are available to the Librarian are; A librarian can issue a boo to the student

an view The dierent categories of boos available in the Library

an view the List of boos available in each category

an tae the boo returned from students

Add boos and their information of the boos to the database

#dit the information of the e2isting boos.

an chec the report of the issued 5oos.

an access all the accounts of the students.


27/32

The features available to the +tudents are;

an view The dierent categories of boos available in the Library

an view the List of boos available in each category

an own an account in the library an view the boos issued to him

an put a re:uest for a new boo

an view the history of boos issued to him previously

an search for a particular boo

2.3 User Classes and Caracteristics

There are various inds of users for the product. -sually web products arevisited by various users for dierent reasons.

The users include ; +tudents 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.! Operating "nvironmentThe product will be operating in windows environment. Also it will becompatible with the %# *.J. 4ost of the features will be compatible with the4o3illa refo2 < pera M.J or higher version. The only re:uirement to usethis online product would be the internet connection.

2.# Design and Implementation Constraints

The Product is developed using A+P. The bacend database for this 4y+BL+erver. The product is accomplished with login facility so that specicfunction is available to specic student.

2.$ User Documentation

The product will include user manual. The user manual will include productoverview& complete conguration of the used software >such as +BL server?&technical details& bacup procedure and contact information which willinclude email address. There will be no online help for the product at thismoment. The product will be compatible with the %nternet #2plorer *.J orhigher. The databases will be created in the 4y+BL.


28/32


29/32

3.2.1.1UserInter+aces

7escribes how this product interfaces with the user.

H-% ! 7escribes the graphical user interface if present. This section shouldinclude a set of screen dumps or mocups to illustrate user interfacefeatures.

7escription ! The user interface must be customi3able by the administrator

riticality! This issue is essential to the overall system. All the modulesprovided with the software must t into this graphical user interface andaccomplish to the standard dened.Technical issues ! %n order to satisfy this re:uirement the design should besimple and all the dierent interfaces should follow a standard template.

There will be the possibility of changing colors and images& plus switchingbetween interfaces with the minimum impact for the users.

/iss ! To reduce the circumstances under which this re:uirement might notable to be satised& all the designers must have been developed web sitespreviously and they must be aware of html restriction and cross browsersimplementations before starting the designing. %n order to reduce theprobability of this occurrence the entire design team will be trained in basichtml development and macromedia rewors& this tool will be used insteadof Photoshop.

7ependencies with other re:uirements ! All user interfaces should be able tointeract with the user management module and a part of the interface mustbe dedicated to the login8logout module

!. ,on Functional Re*uirements

4.2. Hardware Interfaces

Ser#er Side:

perating +ystem; 0indows N282p &0indows 4#

Processor; Pentium $.J HK3 or higher


30/32

/A4; "(* 4b or more

Kard 7rive; 1J H5 or more

Client side:

perating +ystem; 0indows N2 or above& 4A or -6%O.

Processor; Pentium %%% or ".J HK3 or higher.

/A4; "(* 4b or more

4.3. Software Interfaces

Database:+BL +erver.

)pplication:A+P >Active +erver Pages?

*eb Ser#er: %%+ >%nternet %nformation +ervices >%%+? is a

powerful 0eb server that provides a highly reliable& manageable& and

scalable 0eb application infrastructure?

4.4. Communications Interfaces


31/32

The ustomer must connect to the %nternet to access the

0ebsite;

7ialup 4odem of (" bps

5roadband %nternet

7ialup or 5roadband onnection with a %nternet Provider.

#. Oter ,on+unctional Re*uirements

5.1. Performance Requirements

The proposed system that we are going to develop will be used as the

hief performance system within the dierent campuses of the

university which interact with the university sta and students.

Therefore& it is e2pected that the database would perform functionally

all the re:uirements that are specied 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 re:uired to tae the

database bacup.

5.3. Security Requirements

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

are dierent categories of users namely teaching sta& administrator&

library sta& students etc.& 7epending upon the category of user the

access rights are decided. %t means if the user is an administrator

then he can be able to modify the data& delete& append etc.& All other


32/32

users other than library sta only have the rights to retrieve the

information about database.

5.4. Software Quality ttri!utes

The Buality 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 re:uires a database in order to store persistent data. The

database should have bacup capabilities.

5." Software Constraints

The development of the system will be constrained by the availability

of re:uired software such as web servers& database and development

tools.

The availability of these tools will be governed by the -niversity.

The most recent versions of software development tools may not beinstalled at the -niversity.

5.# $esi%n 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.

Date post:	02-Mar-2018
Category:	Documents
Upload:	rasa-govindasmay
View:	218 times
Download:	0 times

Miniproject Simple Srs

Documents