Library Management System Project Plan

Our Team

Name	Role	Main Jobs
Aarya Patel	Team Leader	Makes most design choices, writes most code, helps everyone
Ruchi Tanwar	Data Manager	Handles storing and loading book information, works with files
Chesha Patel	Screen Designer	Creates menus and how things look to users
Khushwanth Solanki	Tester & Writer	Checks if everything works, writes guides and instructions

About Our Project

We are building a book tracking system that helps libraries keep track of their books. Users can:

• Add new books
• Find books by title, author, or type
• See book details
• Change book information
• Remove books
• Save all information in files

Our system will work with at least 5,000 books and will be easy for library staff to use.

Project Schedule (12 Weeks)

Weeks 1-2: Planning & Setup

• Week 1: Decide what we need to build and how it should work
• Week 2: Create basic files and start writing simple code

Weeks 3-6: Building Main Features

• Weeks 3-4: Create basic features (adding books, viewing books)
• Weeks 5-6: Add more advanced features (searching, updating, removing books)

Weeks 7-9: Putting Everything Together

• Connect all parts of the system
• Make sure everything works together
• Make the system faster and better

Weeks 10-12: Final Touches

• Test everything thoroughly
• Fix any problems we find
• Write instructions for users
• Finish the project

Who Does What

Aarya Patel (Team Leader)

Aarya is our main programmer and leads the team. Aarya will:

• Make big decisions about how the program works
• Write most of the code for managing books
• Help team members when they have problems
• Check everyone's work
• Make sure we finish on time

Aarya will spend about 40% of the total project time and handle the most complex parts.

Ruchi Tanwar (Data Manager)

Ruchi takes care of how we store and manage book information. Ruchi will:

• Design how book information is saved in files
• Write code to save and load books
• Make sure book data is correct
• Help make the system work with many books
• Check for problems with the data

Ruchi will spend about 20% of the total project time.

Chesha Patel (Screen Designer)

Chesha designs how users see and use our program. Chesha will:

• Create the menu system users see
• Design how book information is shown on screen
• Make the program easy to use
• Create helpful messages for users
• Make sure users can easily enter information

Chesha will spend about 20% of the total project time.

Khushwanth Solanki (Tester & Writer)

Khushwanth makes sure everything works and writes instructions. Khushwanth will:

• Test all parts of the program
• Find and report problems
• Write user guides and help information
• Create examples of how to use the program
• Make sure the program works as expected

Khushwanth will spend about 20% of the total project time.

Weekly Plan

Week 1: Planning

Day	What We'll Do	Who's Responsible	Helper
Monday	First team meeting, decide what we need	Aarya	Everyone
Tuesday	Plan how the program will work	Aarya	Ruchi
Wednesday	Plan how to store book information	Ruchi	Aarya
Thursday	Sketch how screens will look	Chesha	Everyone
Friday	Plan testing, review progress	Khushwanth	Everyone

Week 2: Starting to Build

Day	What We'll Do	Who's Responsible	Helper
Monday	Set up project files	Aarya	Everyone
Tuesday	Create basic book information structure	Aarya	Ruchi
Wednesday	Create file saving and loading	Ruchi	Aarya
Thursday	Create basic menu	Chesha	Khushwanth
Friday	Check progress, plan next week	Aarya	Everyone

Weeks 3-4: Basic Features

Aarya will:

• Create how book information is stored
• Write code to manage books
• Make adding and finding books work
• Plan memory use

Ruchi will:

• Make file reading and writing work
• Create data checking
• Make sure information is stored correctly
• Implement file saving

Chesha will:

• Build complete menu system
• Create screens for showing book information
• Make sure user typing is handled correctly
• Design helpful messages

Khushwanth will:

• Create test cases
• Test basic functions
• Document how things work
• Report problems

Weeks 5-6: Advanced Features

Aarya will:

• Make searching for books work
• Create updating and deleting books
• Make the program run faster
• Handle unusual cases

Ruchi will:

• Make file operations better for many books
• Implement faster data finding
• Create data recovery for errors
• Handle file problems

Chesha will:

• Improve user experience
• Create search results display
• Make advanced input handling
• Design error messages

Khushwanth will:

• Create advanced test cases
• Test unusual conditions
• Update instructions
• Test usability

Weeks 7-9: Integration

Aarya and Ruchi will:

• Connect core functions with data saving
• Improve memory use
• Make data operations more efficient
• Handle large amounts of books

Chesha and Khushwanth will:

• Connect screens to all system functions
• Create good error handling
• Test user workflows
• Document user processes

Everyone will:

• Test everything together
• Check performance
• Fix problems
• Complete features

Weeks 10-12: Finishing

Aarya will:

• Do final code review
• Fix important bugs
• Check all features work
• Make final system checks

Ruchi will:

• Check data is saved correctly
• Make final improvements to file operations
• Create maintenance guide
• Final storage improvements

Chesha will:

• Make final screen improvements
• Make user guide
• Create quick reference
• Final screen improvements

Khushwanth will:

• Do complete system testing
• Test on different computers
• Finalize all documentation
• Create installation guide

Everyone will:

• Show final system
• Discuss what we learned
• Share knowledge
• Finish the project

How We'll Work Together

Regular Meetings

• Daily Check-in: 15 minutes each morning to discuss progress
• Weekly Review: Friday afternoons to check progress and plan next week
• Technical Review: Twice a week to discuss coding problems

How We'll Communicate

• Code Storage: GitHub
• Task Tracking: Trello board
• Documents: Google Drive folder
• Chat: WhatsApp group and Discord

How We'll Handle Problems

Problem	How Likely	Impact	How We'll Handle It	Who's Responsible
Behind schedule	Medium	High	Clear deadlines, extra time in schedule	Aarya
Technical problems	Medium	Medium	Regular code reviews, research time	Aarya, Ruchi
Parts don't work together	Medium	High	Regular integration, clear interfaces	Aarya
Quality issues	Low	High	Thorough testing, code reviews	Khushwanth
Too many features requested	Medium	Medium	Clear requirements, change control	Aarya, Everyone

How We'll Know We're Successful

Our project will be successful when:

1. All features work correctly
2. The system can handle 5,000+ books without problems
3. All tests pass
4. Instructions are complete and easy to understand
5. We can show the system working perfectly

Team Skills and Learning Opportunities

Aarya Patel (Team Leader)

• Good at: C++ programming, system design, creating algorithms
• Will learn more about: Leading a team, managing a project, code optimization

Ruchi Tanwar (Data Manager)

• Good at: Data design, file operations, data checking
• Will learn more about: Advanced C++ techniques, database improvements, error handling

Chesha Patel (Screen Designer)

• Good at: User interface design, user experience, input handling
• Will learn more about: Console-based interface techniques, error messages, user workflow design

Khushwanth Solanki (Tester & Writer)

• Good at: Testing methods, documentation, finding problems
• Will learn more about: Test automation, technical writing, performance testing

---

Created by: Aarya Patel (Team Leader)
Date: April 25, 2023
Version: 1.0