Library report
-
Upload
saurabh-kumar-gupta -
Category
Technology
-
view
2.150 -
download
2
description
Transcript of Library report
REPORT
Library Management System
Submitted By: Submitted To
Kamesh (1120565) Mr. Vikram Singh
Saurabh (1120739)
CO - 4
1
Index
Contents Page Number
System Requirement and specifications 3
Data Flow Diagram 6
Entity Relationship Diagram 11
Coupling 12
Cohesion 16
Testing (Flow Charts) 17
Unit Testing (Test Cases) 22
System Testing 24
Lab Objectives 25
2
Software Requirement Specification
1. Introduction: This document aims at defining the overall software requirement for ‘Library Management System’. The final product will be having features /functionalities mentioned in this document and may have some additional features as per the need.
1.1 Purpose: The SRS typically contains the brief description of the project. The purpose of the requirement document is to specify all the information required to design, develop and test the software. The purpose of this project is to provide a friendly environment to maintain the details of books and library members and to maintain easy circulation system using computers and to provide different reports.
1.2 Scope: The document only covers the requirements specifications for the Library Management System. This document does not provide any references to the other component of the Library Management System. All the external interfaces and the dependencies are also identified in this document.
Feasibility study: The overall scope of the feasibility study was to provide sufficient information to allow a decision to be made as to whether the Library Management System project should proceed and if so, its relative priority in the context of other existing Library Management Technology. The feasibility study phase of this project had undergone through various steps which as describe as under:
1. Identity the origin the information at different level.2. Identity the expectation of user from computerized system.3. Analyze the drawback of existing system(manual system)
1.3 Definition, Acronyms, Abbreviation:
C : platform independence
DFD : Data Flow Diagram
ERD : Entity Relationship Diagram
Dev C++ : compiler
3
SRS : Software Requirement Specification
1.4 References:
Let Us C:- Yashwant Kanetkar
1.5 Overview: The implementation of Library Management starts with entering the admin password and then updating master records like book details, library information (registering new users, if any). Any further transaction like book issue, book return will automatically update the current books.
2. Overall Description:The ‘Library Management System’ will have capability to maintain database of books in the library for future reference. The system will fulfill this purpose by registering users, issuing books, returning books and updating them.
2.1 Product Perspective: The proposed Library Management System will take care of the current book detail at any point of time. The book issue, book return will update the current book details automatically so that user will get the update current book details. The application will be window based.
2.1.1 System Interfaces: None
2.1.2 User Interface: The software will have a user-friendly and menu based interface. Following screens will be provided:
1. As the system will start there will be a screen containing two options – admin and exit.
2. After logging in, a screen will have the main library operations like book detail, student details, manage books, feedback and logout. The user will now be prompted to input a choice for the desired operation.
3. Each screen will have a back choice to go back to the main menu.
2.1.3 Hardware Interface: Screen resolution of at least 800x600 is required for proper and complete viewing. Higher resolution will not be a problem.
4
2.1.4 Software Interface:1. Any window-based operating system (Windows 7/8). 2. Dev-c++ for coding/developing the software.3. File system (DAT file) for storing the information in the program.
2.1.5 Communication Interfaces: None.
2.1.6 Memory Constraints: At least 64MB RAM and 100MB space on hard disk will be required for running of the application.
2.2 Product function: 1. The main purpose of this project is to reduce the manual work.2. This software is capable of managing book issues, returns book details. Generating
various reports for record-keeping according to end user requirements.
2.3 Assumption and dependencies: All the data entered will be correct and up to date. This software package is developed using C language as front end which is supported by Dev C++ compiler. 2.4 Product Description:The system is accessed by all users and no user can change the information and data base of the system. Any information regarding the change in the database should be made separately by a person who will do the specific changes in the database as per the requirement of the system.
2.5 User characteristics: Educational level: He should be comfortable with the English language. Technical Expertise: Should be comfortable in using the general purpose
application in the computer.
2.6 Constraints: As the system is purely based on C language so less user friendly interface and the low graphics will be there (if any). All the inputs will be taken from the keyboard and the system will run on the command line.
Data Flow Diagram
5
DFD Level == 0
User registerView book
` Book request/Return
Library Database
6
Administrator User/Student0 Library
Management System
detailRead/Write operation
DFD Level == 1
Admin
User name Password
Book .dat Issue.dat Student.dat Feedback.dat
7
1.1 Login
1.2 Get Choice
List 1.7 Logout
1.6 Feedback
1.5 Student Details
1.4 Issuing Section
1.3 Manage
Book
DFD Level == 2 (manage_book)
Bo
o k. d a t
8
1.3.1 Manage
Book
1.3.4 Search Book
1.3.5 Edit Book
1.3.6 Back to main menu
1.3.3 Display Records
1.3.2 Add Book
Book information
Show
Book Information
Book Information
DFD Level == 2 (issuing_section)
Is
Show sue.dat
DFD Level == 2 (student_details)
9
1.4.1 Manage
Book
1.4.5 Go back to
main menu
1.4.4 Return Book
1.4.3 Display
Issued Book
1.4.2 Issue Book
Student idISBN no.
Student idISBN no.
1.5.2 Add
Student
Student.dat
Entity Relationship Diagram
10
1.5.1 Student Details
1.5.6 Delete Student Detail
1.5.7 Go back to
main menu
1.5.5 Edit Student Detail
1.5.4 Search Student
1.5.3 Display Students
Show
Student information
Student ID
Student information
Student ID
Address
11
BOOK
AUTHOR NAME
NAME
ISBN NUMBER
PRICE
BRANCH
RACK NUMBER
Borrowed By
STUDENT
NAME
STUDENT ID
Issued By
ADMIN
USER NAME
PASSWORD
NAME
Return Date
Due Date
Issue
Published By
No of Copies
PUBLISHER
Pub-Id Name
Design of System
Coupling:
12
main( )
issue_book( )
student_edit_ record( )
edit_book( )
issuing_section( )
student_details( )
manage_book
feedback( )
return_book( )
Control Coupling
Control CouplingControl Coupling
Control Coupling
Data Coupling
Data Coupling
Data Coupling
Data Coupling
External, data coupling
Basically in our library management system there are nine modules -
(1) main(2) manage_book(3) issuing_section(4) student_details(5) feedback(6) student_edit_record(7) edit_book(8) return_book(9) issue_book
Coupling Values Calculation :
Di: number of input data parameters
ci : number of input control parameters
do: number of output data parameters
co : number of output control parameters
gd : number of global variables used as data
gc : number of global variables used as control
w : number of modules called (fan-out)
r : number of modules calling the module under consideration (fan-in)
13
Coupling Values
14
Module name Coupling Values
main( ) 0.83
manage_book( ) 0.80
issuing_section( ) 0.67
student_details( ) 0.85
feedback( ) 0.80
student_edit_record( ) 0.67
edit_book( ) 0.80
return_book( ) 0.83
issue_book( ) 0.67
15
Cohesion
16
Module name Cohesion Type
main( ) Co-incidental Cohesion
manage_book( ) Functional Cohesion
issuing_section( ) Functional Cohesion
student_details( ) Functional Cohesion
feedback( ) Sequential Cohesion
student_edit_record( ) Functional Cohesion
edit_book( ) Logical Cohesion
return_book( ) Sequential Cohesion
issue_book( ) Functional Cohesion
Testing
17
Enterpassword
Match
BookDetail
FeedbackStudentDetail
ManageBook
Logout
Choice
Take choice
AdminLogin
choice
start
Flow Chart of Manage_book ( ):
18
StartPrint Title and list
Of choices
Take choice
Choice1
AddBook
Back toMain menu
DeleteBook
EditBook
SearchBook
DisplayRecord
Open fileBook.DAT
Take choice
Exit
Flow Chart of issuing_section( ):
19
Print Title and list Of choices
IssueBook
Back toMain menu
Search issuedBook
Display issuedBook
Open fileBook.DAT
Flow Chart of Student_details ( ):
20
Print Title and list Of choices
Take choice
Choice3
AddStudent
Back toMain menu
DeleteStudent
EditStudent
SearchStudent
DisplayRecord
Open filestudent.DAT
Take choice
Choice2
Flow Chart of feedback( ):
21
Print Title and list Of choices
GiveFeedback
Back toMain menu
Search Feedback
Display Feedback
Open filefeedback.DAT
Unit Testing Test Cases (Book Detail):-
Input Expected Output Output
1 Take Book information from admin to add add book info
2 Display Book Records Book Records
3,java Display java’s book Detail Java book detail
4,101 Edit book info having Isbn(101) Edit 101 isbn Book Info
5,101 Delete book record having Isbn(102) delete
6 Go to main menu Main menu
Test Cases (Issue Book Detail):-
Input Expected Output Output
1 Take Id,Isbn to issue book Issue Book
2 Display issued Book record Display issued book
3(1,102) Return Book isbn(101) by id(1) Return Book
4 Go to main menu Main menu
22
Take choice
Choice4
Test Cases (Student Detail):- Input Expected Output Output
1 Take student information from admin to add Add student info
2 Display Student Records Student Records
3(1) Display Student Detail of Id(1) Student id(1) detail
4(1) Edit student info having Id(1) Edit 1 id student Info
5(1) Delete student record having Id(1) deleted
6 Go to main menu Main menu
Test Cases (Feedback Detail):-
Input Expected Output Output
1 Take book isbn, name& feedback Insert feedback
2 Display Feedback Records Display Feedbacks
3(101) Display feedback of book’s isbn(101) Feedback of book 101 isbn
4 Go to main menu Main menu
23
System Testing:
Test Cases:
Sr. no. Input Desired Output System Output
1. 1 Login page Login page
2. 1 1 Add book Add book
3. 1 2 Display book record Display book record
4. 1 5 Delete book Delete book
5. 2 1 Issue book Issue book
6. 2 2 Display issued Bookrecord
Display issued book record
7. 2 3 Return book Return book
8. 3 1 Add student information Add student information
9. 3 3 Search student info Search student info
10. 3 4 Edit student info Edit student info
11. 3 5 Delete specific student record
Delete specific student record
12. 1 3 1 Search book by isbn Search book by isbn
13. 1 3 2 Search book by name Search book by name
14. 4 1 Give feedback Give feedback
15. 4 3 Search feedback Search feedback
16. 4 3 4 main menu main menu
24
LAB OBJECTIVES
1 – Calculate Halsted’s equation for a given program/software/system where,
N1=No. of distinct operators
N2=No. of distinct operands
N3=Total no. of operators
N4=Total no. of operands
Evaluate –
a) Program vocabulary (M) = N1+N2 = 205
b) Program length (N) = N3+N4 = 1742
c) Calculated program length = N1log2N1+N2log2N2 = 615.00
d) Volume (V) = Nlog2M = 13377.6543
e) Difficulty (D) = N1/2 * N3/N2 = 3.8985
f) Effort (E) = D*V = 52152.4798
g) Time required (T) = E/18 = 2897.3600
h) No. of delivered bugs (B) = V/3000 or ((E)2/3)/3000 = 4.46
2 – Compute average no. of live variables per statement in a program.
Avg. no. of live variables = (Total no. of live variables)/ (Total lines of code) = 0.466176
3 – Compute average life of variables in a program/shell
Avg. life of variables = (Sum of life instances of all variable)/(Total lines in program) = 0.636
25
4-Calculate the cyclomatic complexity of a system.
26
27