REQUEST FOR SYSTEM SERVICES

Date: August 13, 2023

Submitted by: Gerald Bandow

Department or Office Information Technology

Company Name: Central City Library

Stakeholders: Library management, staff, patrons, and suppliers

Business Product/Service: Library services, including book lending, cataloging, digital media access, etc.

Functional System Name: Library Management System (LMS)

Type of Request: ___ New System - no current computer support

__x_ Redesign current computer-based system

Problem Statement or Request Description:

The existing Library Management System (LMS) lacks efficiency in managing inventory, user registrations, digital media access, and reporting functionalities. Specific issues include:

What is or is not happening? Delays in updating inventory, difficulties in tracking overdue books, inefficient user registration process.

When and how often does this happen? Daily, impacting staff workflow and patron satisfaction.

Who or what departments are affected? Library staff, management, patrons, and suppliers.

When this situation occurs what is the result? Late reports, unhappy patrons, increased labor time, potential loss of revenue.

The System Development Life Cycle I will use the Agile model for this project because of its flexibility, adaptability, and emphasis on customer collaboration. This approach will allow for ongoing feedback and iterative development, ensuring that the new system aligns with the library's evolving needs.

The above is what I did in week one that I somehow need to go off of for Week Three. below here I need to use the information from above to set up a plan.

Central City Library

Office information Technology

Project Plan

Version: 1.0

Prepared by:

Gerald Bandow

August 27, 2023

Table of Contents

Table of Contents................................................................................................................................................................................2

Executive Summary.............................................................................................................................................................................3

Introduction............................................................................................................................................................................................4

Purpose of this document........................................................................................................................................................................4

Background..................................................................................................................................................................................................4

Project Purpose...........................................................................................................................................................................................4

Project Assumptions and Constraints...............................................................................................................................................4

Assumptions:...............................................................................................................................................................................................4

Constraints:................................................................................................................................................................................................4

Scope Management..............................................................................................................................................................................4

Project Scope Statement.........................................................................................................................................................................4

Hardware/software requirments........................................................................................................................................5

Interface Considerations............................................................................................................................................................5

Network Diagram.................................................................................................................................................................................6

Team Management................................................................................................................................................................................6

Team Directory...........................................................................................................................................................................................6

Executive Summary

Introduction

Purpose of this document

The purpose of the Project Plan is to define the hardware and software requirements. In addition, it will include interface considerations, a network diagram and the scope of the project.

Background

Project Purpose

.

Project Assumptions and Constraints

Assumptions:

Constraints:

Scope Management

Scope Management involves the identification of all the work required, and only the work required, to complete the project successfully.

Project Scope Statement

.

Hardware/software requirEments

• Symantec Antivirus

Interface Considerations

Network Diagram

Team Management

.

Issues

Teamwork

The project team is only as strong as the weakest link. Creating a chained approach to solving issues will help build communications to the stakeholders. Ultimately, communication will help the project succeed or lack of communication will end up making the project struggle.

Relationships among projectteammembers are critical to project success. You don't have to be friends, but you do have to be coworkers andteamplayers. If sound working relationships are not present among the projectteamor stakeholders, there will be problems.

• The project manager can schedule team building activities outside of the office like going to a sports event, attending a comedian show, or a viewing of an art gallery. These outside events can build relationships and help members relate to each other. It will also build the communication especially with a team that may not be as familiar with each other.

Team Directory

The following is a list of all team members on the project.

Role	Name	Department	Phone Number	Email Address