New library management system slide
Download as PPTX, PDF1 like1,252 views
This document outlines the planning and analysis for a new library management system project at Norton University. It identifies key steps: 1) Prioritizing project requests and allocating resources like developers and a 3 month timeframe; 2) Analyzing the current manual system which is slow and inefficient, and determining user requirements like fast searching; 3) Recommending a new computerized system to allow students to quickly search and view book information, check book availability, and borrow books, improving the library experience.
New library management system slide
- 1. Norton University Educating Tomorrow’s Leaders College of Science Department of Computer Science Project: New Library Management System Year III Semester II Information System Analysis Lecturer: Lim Lyheng Prepared by Group M2 (Computer Science): Nov Panha ID: B20131122 Sok Seyha ID: B20122134 Phly Sary ID: B20133384 Pick Sak ID: B20131412 2015 - 2016
- 2. 1. Project Planning: a. Prioritize project requests (To do list) b. Allocate resources (Developers, Timeframe, Effort, IT related Tools) c. Identify project development team (Roles and Responsibilities)
- 3. a. Prioritize project requests Controlling all the book in Library Finding the book quickly Reading the content of each book Verifying the book (Borrowed or Returned)
- 4. b. Allocate resources (Developers, Timeframe, IT related Tools) This project has 4 developers to built: 1. System Analyst : 1200$ 2. Database Analyst: 1000$ 3. Design Analyst: 700$ 4. Program Analyst: 800$ + (Testing)
- 5. b. Allocate resources (Developers, Timeframe, IT related Tools) Duration: 3months to built this project System Analyst (1month) Database Analyst (2weeks) Design Analyst (2weeks) Program Analyst + Testing (1months)
- 6. b. Allocate resources (Developers, Timeframe, IT related Tools) Tools for each developers:
- 7. c. Identify project development team (Roles and Responsibilities) 1. System Analyst: Research more about system with User in Library Best understand with lifecycle of system Analysis/Design the plan of project “Library” Study the tool that related with system Work Closely with Database Analyst, Design Analyst and Programming
- 8. c. Identify project development team (Roles and Responsibilities) 2. Database Analyst: check physical database by studying project requirement, such as location, amount of space database, confirm new product in Library verify with System Analyst about database maintenance data in database
- 9. c. Identify project development team (Roles and Responsibilities) 3. Design Analyst: verify project requirement with analyst, database analyst and programmer design plan software, interface design the room of Library
- 10. c. Identify project development team (Roles and Responsibilities) 4. Program Analyst: verify project requirement with analyst, database analyst and designer write the software, testing maintenance training user
- 11. 2. Project Analysis a. Study current system (Process, Weakness and Strength) b. Determine user requirements (Requirement Definition, Mandatory and Constraints/Optional) c. Recommend solution (Propose new System, Process, Expected Result)
- 12. a. Study current system (Process, Weakness and Strength) Library is a building or room containing collections of books. At least 20% in Library that use the system by technology. Some libraries don’t prepare the book by standard. So it’s difficult to students that they find the book. There are a few points of disadvantage in library without system. Finding the book is slow (if the students rarely read the book, they find it too slow) Being tired when they stand or walk to find the book Do not know which book should they read, because some students is lazy to find the book by reading content Borrowing the book. when students want to borrow, they need to verify with librarian. Some libraries, just noted the name of student. So the students wants to borrow the book is difficult. And spend much time to wait the librarian checks the book
- 13. b. Determine user requirements (Requirement Definition, Mandatory and Constraints/Optional) This requirement of system is a little: touching on monitor by searching. (search the title, kinds of book…) spending a few time to read the content of each book
- 14. c. Recommend solution (Propose new System, Process, Expected Result) After the system built successful. So it makes the students easily to find the book. There are some benefit of using this system: Finding the book faster than before because student just search the book Searching the many books don’t use much time Viewing many contents of the book Checking the book (borrowed or returned) if the book borrowed, in monitor showed the book is unavailable
- 15. Thanks You for pay attention Any question?