Beruflich Dokumente
Kultur Dokumente
0
Software Requirements Specification 27-02-2011
itchamps
itchamps
Version 1.0
EMail: abhishekbhardwaj241@gmail.com
Revision History
Table Of Contents
Description Page No.
1.0 Introduction………………………………………………………05
1.1 Purpose..................................................................................05
1.2 Scope.....................................................................................05
1.3 Definition, Acronyms, and Abbreviations ............................06
1.4 References.............................................................................07
1.5 Technologies to be used........................................................07
1.6 Overview...............................................................................07
2.7 Constraints……………………….……….………………..10
Apache HTTP Server- Apache HTTP Server is an server that runs business
applications and supports the PHP and web services standards.
HTTP- Hypertext Transfer Protocol is a transaction oriented client/server
protocol between web browser & a Web Server.
XML (Extensible Markup Language):-It is a markup language that was
designed to transport and store data.
1.4 References:
IEEE SRS format
Problem Definition(Provided by IBM)
1.6 Overview
The web pages (XHTML/PHP) are present to provide the user interface
on client side. Communication between client and server is provided
through HTTP/HTTPS protocols.
The Client Software is to provide the user interface on system user
client side and for this TCP/IP protocols are used.
On the server side web server is for PHP and database server is for
storing the information.
Server Side –
Processor RAM Disk Space
Apache HTTP Pentium IV at 512MB 100MB
1.3 GHz
Server V2.2.17
2.7 Constraints –
GUI is only in English.
Login and password is used for identification of customer and there is no
facility for guest.
1. Librarian- Responsible for activities such as adding book records, deleting book
records, updating book status such as if book is issued & etc.
2. Library Database- Responsible for keeping records of all present & requested
books in library.
3. Guest- Registers for a new account for becoming a library member.
4. User- Already registered member who can access library services such as
searching books, registering books, requesting for new books and etc.
2.9 Database Design-
ER Diagram-
1 Database library
id int(5) No
name varchar(100) No
author varchar(100) No
publisher varchar(100) No
subject varchar(50) No
type varchar(20) No
days int(3) No
fine_per_day int(3) No
copies int(3) No
id int(5) No
name varchar(100) No
author varchar(100) No
publisher varchar(100) No
subject varchar(50) No
type varchar(20) No
days int(3) No
fine_per_day int(3) No
copies int(3) No
id int(2) No
name varchar(20) No
max_books int(2) No 0
id int(2) No
name varchar(20) No
max_books int(2) No 0
uname varchar(25) No
fname varchar(20) No
lname varchar(20) No
email varchar(25) No
pass varchar(50) No
reg char(15) No
department varchar(25) No
photo varchar(35) No
activated int(1) No
uname varchar(25) No
fname varchar(20) No
lname varchar(20) No
email varchar(25) No
pass varchar(50) No
reg char(15) No
department varchar(25) No
photo varchar(35) No
activated int(1) No
uname varchar(30) No
status varchar(500) No
uname varchar(30) No
status varchar(500) No
bookid int(3) No
uname varchar(30) No
last_rep_date varchar(10) No
bookid int(3) No
uname varchar(30) No
last_rep_date varchar(10) No
bookid int(5) No
uname varchar(30) No
return_dd int(2) No
return_mm int(2) No
return_yyyy int(4) No
type varchar(15) No
bookid int(5) No
uname varchar(30) No
return_dd int(2) No
return_mm int(2) No
return_yyyy int(4) No
type varchar(15) No
id int(2) No
uname varchar(25) No
pass char(50) No
id int(2) No
uname varchar(25) No
pass char(50) No
res_id int(10) No
bookid int(3) No 0
uname varchar(30) No
type varchar(20) No
dd int(2) No
mm int(2) No
yyyy int(4) No
res_id int(10) No
bookid int(3) No 0
uname varchar(30) No
type varchar(20) No
dd int(2) No
mm int(2) No
yyyy int(4) No
uname varchar(25) No
fname varchar(20) No
lname varchar(20) No
email varchar(25) No
pass varchar(50) No
reg char(15) No
course varchar(25) No
photo varchar(35) No
activated int(1) No
uname varchar(25) No
fname varchar(20) No
lname varchar(20) No
email varchar(25) No
pass varchar(50) No
reg char(15) No
course varchar(25) No
photo varchar(35) No
activated int(1) No
The end user should have a basic knowledge of English and computer usage.
Administrator is created in the system already.
Roles and tasks are predefined.
3. Specific Requirements
3.1 State Diagrams As System Use Reports
3.1.1 State diagram of whole system
Totally 12 windows.
All states except "Display Exit Info"
can go back to Main Menu.
Help
Get Help Content
Enter Book Info Add a book Main Menu
14
1 Add a student
do/ Insert a student into DB
Enter Student Info
7
Reset Search students do/ Insert student into DB
Search books
Exit
View Mylist
Enter Search Info
Enter Search Info
11
2 Update/Delete
Search
Display
Back
Exit Info
Display MyList
5 Display Results
New Search 12
exit/ Send from List message Check In/Out
entry/ Search students in DB
Search
Add to list View Detail / UpdateDelete
Update,Delete
Add to list Display Book Detail
4 Check In/Out
Back Update Detail
do/ Update, Delete 60
do/ Update,Delete
View Detail
Display Results
3
Check In/Out
entry/ Search books in DB
Check In/Out
Student class
[ not exist s ]
[ exists ]
return Resultset
[ empty ]
Return false
Book class
no
return success
message
yes
return exist
message
return
resultset
update record in
database
return success
message
check
existence
no
exist?
yes
delete the
record return fail
message
return success
message
Transaction class
SQL Statement
(Update.....)
Exception? Yes
Print "error
message"
No
SQL Statement
(Update.....)
Exception? Yes
Print "error
message"
No
MyList class
SQL Statement
(Insert.....)
Exception? Yes
Print "error
message"
No
SQL Statement
(Delete.....)
Exception? Yes
Print "error
message"
No
SQL Statement
(Select....)
Exception? Yes
Print "error
message"
No
24 x 7 Availability - If the base is now the entire world, staying open 24 hours a day
becomes critical. Because system can be an automated Process, so it can stay open for 24
hours a day. So UPS support must be on server site for at least 8 hours in case of power
failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup and
maintenance purpose.
Dynamic Website - Many early Web implementations consisted of static HTML pages.
This becomes very difficult to manage if the number of pages gets too large. An effective
system should be largely dynamic taking advantage of technology that automates this
process rather than relying on manual processes. Application should serve dynamic user
based customized web pages to its clients from server.
Integration with existing enterprise systems – Any existing Web site that relies on the
manual duplication of data from another system is one that can be improved. Most of the
business data in the world today exists in enterprise servers that can be connected to the Web
servers to make this process far more effective.
Provide good performance and the ability to scale the server – The Web application
Server should provide good performance and the ability to manage performance with
techniques, such as support for caching, clustering, and load balancing.
Providing session management capability - Web application developers should not spend
valuable time worrying about how to maintain sessions within the application. The Web
Application Server should provide these services.