Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Library Management System

No description
by

Anshul Garg

on 8 April 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Library Management System

Library currently uses traditional system wherein user registration and modifications are done manually.
Updating book's status upon issue and return is done manually.
Retrieving book and user information is difficult and tedious.
Issues with generating redundant or wrong information
No access to real-time information.
LMS : Problem Statement
Automate the user registration process.
Provide an easy way to authorize the users.
Book search, request, reservation and renewal can be done 24*7.
User authorization can be done easily with the biometric validation system.
Book can be added, updated and the database can be maintained more seamlessly.
Facilitates real-time updation and retrieval of user and book information.
With system generated emails, user is more aware of due dates and fine notification.
Eliminates long and manual processing.
Overall improved effectiveness and efficiency in administration and management.
LMS : Our Solution
LMS : Use Case Diagram
Functional Requirements
LMS : Requirement Analysis
Library Management System
Group 1
Software Engineering
Spring 2014

LMS : Project Plan and Schedule
LMS : System Architecture
LMS : Activity Diagram
LMS : Use Case Details
LMS : Sequence Diagram
LMS : Collaboration Diagram
LMS : Class Diagram
LMS : Database Design
LMS : Component Diagram
LMS : Security Component & Design
LMS : Visual Prototypes
Entry Criteria
LMS : Test Plan
Key areas of Risk occurence
LMS : Risk Management
Prerequisite
Basic knowledge of computer and internet browsing.
Know-how of Network Systems and Management.
Know-how of Database Management.

LMS : Training Plan
Gathering requirements accurately is the foundation for a better implementation of SDLC.
Understood the concepts of Verification and Validation in the real world scenario.
Implementing the LMS concepts to UML diagrams such as Gantt Chart, Class Diagram and Activity Diagram using tools like MS Project and Gliffy gave us better understanding of Software engineering concepts.
Understanding the concepts of generalization, specialization, association, dependency and multiplicity.
The use of biometric validation technology helped us understand the concepts and implementation techniques.
Designing the system and creating the test plans helped us understand the system from a designer’s and tester’s perspective respectively.
Test cases should be designed in a manner that they uncover errors.
The weekly meetings gave us a chance to exchange ideas and skills.
It is important to understand team dynamics, strengths and weakness of each team member and circulate the tasks accordingly.

LMS : Lessons Learnt
LMS : Questions ?
User
Create and update profile
Search Books
Reserve Books
Request Books
Renew Books

Librarian
Add, Modify and Delete Books from the Database
Update the database on book return
Generate RFID and map it to the user
Deactivate User

System Requirements
Generate Fine Notifications
Generate Due Date Notifications
Non-Functional Requirements
Error Handling
Safety & Security
Usability
Performance
Software & Hardware Constraints
Maintainability & Portability
Derived Requirements
LMS : Requirement Analysis
Organizational Requirements
All the users should be a part of the organization.
Requires basic computer knowledge.
More economical means for tracking information.
Improved efficiency and effectiveness.
Improved customer service.
Reduces errors.
Eliminates manual processing.
More reliable security for sensitive and confidential information.
Greater accountability and transparency in operations.
RFIDs should be generated and mapped correctly.
System should be able to track reserve, request and due dates accurately.
Librarian should be able to update book and user records seamlessly.
System should be able to track issue and renewals for all the books and users.
System should be able to track the user data on books and fines accurately.
LMS is based on Model-View-Controller Architecture.
Ideal for web-based applications
Minimizes coupling between business logic and data presentation to the web user.
Architecture
Deployment
Initial version of the software will be deployed IE 11.0, Chrome and Firefox.
Implementation
Software will be implemented in Object-Oriented Design.

Evaluation
Constant feedback and evaluation mechanism to ensure effectiveness of the training procedure.
Resources
Overhead Projector, screen, visual aids, workstations, view graphics and slides
Training Highlights
Need to train the librarian on the following "How to":
Use finger print scanner to generate RFIDs
Map RFIDs against the user.
Modify and delete book and its details from the system.
Deactivate user from the system
System Evaluation, Management and Support.
The librarian need to train the users on the following:
Register on the online portal
Complete the registration process.
Request, reserve, return and renew policies.
Fine payment in case of overdue.
Outlines how risk management activities will be performed and monitored throughout the lifecycle.
Provides templates for recording and prioritizing tasks.
Earlier identification of risk minimizes the impact.
Essential to do qualitative and quantitative risk analysis.
Risks can be categorized into the following depending on the impact and probability:
- High - Medium -Low


For each risk, one of the approaches can be taken:
- Avoid - Mitigate - Accept -Transfer
Timely delivery of the project deliverables.
Work breakdown structure.
Cost and Effort estimates.
Resource planning.
Other constraints and assumptions.
Risk Management highlights
Handling Defects
























Team Members:
Nidhi Mehta
Anshul Garg
Poonam Gupta
Jayalakshmi Ramachandran
Kalyan Cherukuru
Mallik Chowdary

Instructor:
Dr. Richard Riehle
Full transcript