Purpose:
 To make the existing system more efficient.
 To make a user friendly environment.
 To make functionality of library faster.
Our Project’s Aims And Objectives
To eliminate the paper work in library.
To record every transaction in computerized
system.
To provide a user friendly interface which suit the
user’s requirement.
To save cost and time.
System Requirments :
Functional:
Admin Login:
Admin should login to the system account before main screen
using its username and password.
Sign-up for new admin account:
There will be an option to sign-up for new user account if a new
person becomes an admin for this system.
Add book :
If new books are added in the library, the system will allow the
admin user to add new books in the system records.
Searching:
While issuing a book to a student, the system will provide
the facility to the admin user to search for book that the
book is available or not. It should also maintain its record.
Return book:
The system will provide the facility to the admin user to
maintain record while the student returns the book.
Statistics:
Students and books details will be shown in a separate
page.
Non-Functional :
Security Requirements:
our system will be
scure and error free.
Software Quality Attributes:
The software will not
crash.
System Planing :
Planning document.
Overview
What the motivation for this project is (e.g. to fill a gap in the product
portfolio)
The motivation of this project is to learn how to engineer a software.
Who the customer is
Riphah International University
What the project will deliver. Is it a new product or an extension of an
existing one?
The product will facilitate Library’s Management/Librarian to manage
their overall library’s records.
Planning document.
What it will cost
This product will cost Rs0.
How long it will take
It will take about two months.
Which organizations are involved
There are no other organizations involved in this project.
Which other projects depend on the project result
There are no other projects depend on this project result.
Which other projects contribute with their results
There are no other projects which will contribute in this
project.
System Analysis:
FLOW CHART
System Design
WIRE-FRAME:
System Implementation:
Codeing :
In our system, admin can login to the system.
New admin can sign up for new account.
Admin can add books.
The system can keep record of the books which
are added.
Admin can issue and return books.
The Software can keep record of all the system in
a database.
TESTING :
Test Data:
username:
• Username==Admin (valid)
• Username == admin (invalid)
• Username == Admin12 (invalid)
Password:
• Password==Admin$123 (valid)
• Password==admin$123 invalid)
• Password==admin123 (invalid)
Username Test Cases:
Test Case Input P. tested Expected output
1 Admin Username
==Admin
ok
2 admin Username ==
Admin
Error
3 Admin12 Username ==
Admin
Error
Password Test Cases:
Test Case Input P. tested Expected output
1 Admin$123 Password==Adm
in$123
ok
2 admin$123 Password==admi
n$123
Error
3 admin123 Password==admi
n123
Error
Library Management System -Software Engineering
Library Management System -Software Engineering

Library Management System -Software Engineering

  • 3.
    Purpose:  To makethe existing system more efficient.  To make a user friendly environment.  To make functionality of library faster.
  • 4.
    Our Project’s AimsAnd Objectives To eliminate the paper work in library. To record every transaction in computerized system. To provide a user friendly interface which suit the user’s requirement. To save cost and time.
  • 5.
  • 6.
    Functional: Admin Login: Admin shouldlogin to the system account before main screen using its username and password. Sign-up for new admin account: There will be an option to sign-up for new user account if a new person becomes an admin for this system. Add book : If new books are added in the library, the system will allow the admin user to add new books in the system records.
  • 7.
    Searching: While issuing abook to a student, the system will provide the facility to the admin user to search for book that the book is available or not. It should also maintain its record. Return book: The system will provide the facility to the admin user to maintain record while the student returns the book. Statistics: Students and books details will be shown in a separate page.
  • 8.
    Non-Functional : Security Requirements: oursystem will be scure and error free. Software Quality Attributes: The software will not crash.
  • 9.
  • 10.
    Planning document. Overview What themotivation for this project is (e.g. to fill a gap in the product portfolio) The motivation of this project is to learn how to engineer a software. Who the customer is Riphah International University What the project will deliver. Is it a new product or an extension of an existing one? The product will facilitate Library’s Management/Librarian to manage their overall library’s records.
  • 11.
    Planning document. What itwill cost This product will cost Rs0. How long it will take It will take about two months. Which organizations are involved There are no other organizations involved in this project. Which other projects depend on the project result There are no other projects depend on this project result. Which other projects contribute with their results There are no other projects which will contribute in this project.
  • 12.
  • 13.
  • 14.
  • 15.
  • 22.
  • 23.
    Codeing : In oursystem, admin can login to the system. New admin can sign up for new account. Admin can add books. The system can keep record of the books which are added. Admin can issue and return books. The Software can keep record of all the system in a database.
  • 24.
  • 25.
    Test Data: username: • Username==Admin(valid) • Username == admin (invalid) • Username == Admin12 (invalid) Password: • Password==Admin$123 (valid) • Password==admin$123 invalid) • Password==admin123 (invalid)
  • 26.
    Username Test Cases: TestCase Input P. tested Expected output 1 Admin Username ==Admin ok 2 admin Username == Admin Error 3 Admin12 Username == Admin Error
  • 27.
    Password Test Cases: TestCase Input P. tested Expected output 1 Admin$123 Password==Adm in$123 ok 2 admin$123 Password==admi n$123 Error 3 admin123 Password==admi n123 Error