Scribd
Upload
105 views11 pages

Library Management System For Stanford

The document proposes a library management system for Stanford University to automate their library activities and accommodate over 4 million books. Some key points: - The current manual system is time-consuming and inefficient. The proposed online system will allow users to search for and check out/return books via a web portal or kiosks, generating automated emails and reducing staff needs. - The system scope includes searching for books, checking books in/out, and accessing e-resources. It will have features like acquisition management, circulation tracking, and reporting. - Entity relationship and data flow diagrams, use cases, wireframes, and requirements are presented as part of the analysis for the new system. Functional requirements include user authentication

Uploaded by

sampathsamns.2000
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
105 views11 pages

Library Management System For Stanford

The document proposes a library management system for Stanford University to automate their library activities and accommodate over 4 million books. Some key points: - The current manual system is time-consuming and inefficient. The proposed online system will allow users to search for and check out/return books via a web portal or kiosks, generating automated emails and reducing staff needs. - The system scope includes searching for books, checking books in/out, and accessing e-resources. It will have features like acquisition management, circulation tracking, and reporting. - Entity relationship and data flow diagrams, use cases, wireframes, and requirements are presented as part of the analysis for the new system. Functional requirements include user authentication

Uploaded by

sampathsamns.2000
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

Library Management System

for Stanford

Submitted By:
SAMPATH NEERUBAVI SATHEESHA
INDEX:

• Identifying stakeholders – Create a list of stakeholders (as taught in


Business Analysis Planning and Monitoring Knowledge Area)
• Identify the problem statement in this system
• Identify advantages of the new Library Management System
• Create as-is and future process map (using flowcharts). You can use any of
the popular tools in the market like Microsoft Visio, Lucid Chart, Creately,
Pidoco, or Balsamiq
• As a Business Analyst working on this project, find out the scope of the
Library Management System. To find the scope you can use Use Case
diagram (UML) or Context diagram
• Write down the main features that need to be developed
• Write the in-scope and out-of-scope items for this software
• Draw a data flow diagram for the system
• Draw an ER diagram of the system
• Write out the Business Requirements, both Functional and Nonfunctional
Requirements
• Draw wireframes or mock screens for any 2 of the features namely book
record creation and any other feature as deemed fit by the student. (Use
the technique prototyping or wireframing that is taught in the training).
You can use any of the wireframing tools like Microsoft PowerPoint,
Microsoft Word, Balsamiq, Sketch, Adobe XD, Adobe Illustrator, Figma,
UXPin, InVision Studio, InVision Freehand, or Moqups
Identifying Stakeholders

Identify the problem statement

• A lot of time is wasted managing the manual library.


• The number of employees needed to manage the library is high.
• Fine calculation is a tedious and time-consuming affair.
• No reports could be generated on books issued due to the manual
system.
• It is difficult to manage 4 million books present in the library.
• Students could deposit the books only in the library timings.

Advantages of Library Management System


• Reduce overheads and increase productivity of library staff
• Cost reduction
• Up-to-date records of all books, research papers, magazines, and other
materials available in the library
• Improve student engagement in the library
• It will generate dynamic reports for better decision-making

Existing and Future System Process Map

Existing System
• There is no existing software system as the library is manual.
• Manual-based systems are dependent on humans being correct with
details and more space is needed for documents.
• The manual-based system is more time consuming and need many
numbers of employees to manage 4 million books present in the library.
• It takes lot of time to enter data manually.
• Paperwork can take up a significant amount of space, and the need of
space will increase as the number of the document increases in growth
of the business.

Proposed system
• User friendly interface. Students could deposit the books only in the
library timings.
• The proposed online library system should keep records of different
categories of materials available in the library like books, magazines,
research papers, journals, and newspapers.
• Fast access to the database
• Search facility
• Automated emails sent to students before few days
• 24/7 book dropping mechanism
Flowchart for Library Management System
Scope using Context Diagram

In and Out of Scope


In Scope:
• Stanford University is in the view of automating their library activities to
accommodate its
• With just few clicks one can find books of any subject/author
issue/reissue books through
• Physical "Kiosk" access points on location will be used by students and
staff to locate and
• The library shall have books subject wise, magazines, research papers,
journals, and
• Students can search for books on the LMS by search criteria like name of
the book or author.
• Access will be given to free e-journals and e-books through the software.
• Students can return books at any time in the RFID enabled book
drop box station
Out of Scope:
• The access to Online library is only for the students, readers of Stanford
University and not for others or general public
• Student to have a unique identification number and are required to get
registered with the University.
• Every reading material available shall have a RFID tag on it and incase
not found, librarian to do proper checks and ensure to have the tags on
every book displayed in the web portal.
• System shall receive automated emails to the students 3 days before the
return date to avoid late return of books and there is no further extension
of due dates. Student is obliged to pay fine from the date is expiry of
return date till the return date as per the system. calculations.
• A student shall notify on the books lost if any after receiving to the
management immediately through email or in person. The loss to be
borne by the student.

Data Flow Diagram


ER Diagram for the system

Business Requirements:
Functional Requirements
• User id will be provided when students register with the online library
system
• The system must allow only one user id a password to enter the system
• The system must process the authorization as to who can access to the
library
• The user must be able to logout from the system after ordering books
• Acquisition Management
• Books Circulation Tracking
• Rapid and Powerful Searches
• Import and export the books and ensure the AvalonBay User-friendly
User Interface and manage the whole system
• High-end Reporting

Non-Functional Requirements
• Performance Requirements
• Safety Requirements
• Security Requirements
System Requirement:
• Data should be stored in cloud and in java script
• The data should be secure and reliable.
• The system should have good network connection to access
• LMS can be used on any Windows and MacOS run computers
• It will be RFID ready (NCIP 2.0 HTTP server available)
• Auto scheduled tasks like emails and database maintenance.
Usability:
• The developed screens should be self-explanatory and user friendly
• Users to have internet access to access the portal.
Environments:
• Coding scheduled tasks like emails and database maintenance.
• Coding in Java as it need less maintenance and it will not
change much over time.
Wireframe or Mock Screens:
Create sample wireframes for the system. Capture what screen will be show to
the library employees to create records for each book and at what stage in the
system.
Thank you

You might also like