Written Report 1

ITECH 7602

Introduction
This purpose of this document is to to provide the plan and the statement of work for the Library Management System a Project to be developed by the team of 12 members under the guidance of Mr. Shreyash Patel. The team is to develop the library management system for ATMC, a well recognised educational institute affiliated to the University of Ballarat in Melbourne. The software must make the library system automated so that it is more efficient and easier to be used by both the users (students/staff) and admin (librarian).

Overview
1.1 Project Summary 1.1.1 Purpose: The purpose of this Library Management System project is to develop a software interface which provide access to two levels of the users- students/staff and admin. Students/staff should be able to use this system to Browse/search books Check status of books (available/borrowed) Request/hold a book Check books borrowed and their due dates Check fine due

Admin should be able to Add new books to the library

Written Report 1

ITECH 7602

Lend books to students/staff Set loan periods Check fines Add, delete, update and view books/students/staff records Generate reports about due books and fines etc.

Further, the system should be able to send auto-generated emails to remind about the due dates
1.1.2 Objectives: The objectives of this project are to

develop a system that can replace the current library management system with more efficient and easier to use by both the students/staff and admin

develop a database which stores user details & book details give reliable search facility for the users admin & users separate logins create an easy to understand and attractive user friendly environment develop the system documentation

1.1.3 Scope: This system is developed to be used on campus at ATMC, Melbourne. The

client may change the requirements to keep it online to be accessed by the users from anywhere especially the students to search and reserve the books along with checking

Written Report 1

ITECH 7602

their status of borrowed books, due dates and any fine charges. It can be further extended to the other campus of ATMC at Geelong in future. However, the system doesnt allow the students/staff to borrow the book directly without going through the librarian (admin).
1.1.4 Assumptions and Constraints: To develop the project it is assumed that

All team members will attend the scheduled meetings on time Each member will do the responsibilities assigned to them honestly and meet the dead lines.

The team members have the required skills to fulfil their parts and would learn the skills to complete their tasks otherwise

All team members will work together as a team and help the other member if required.

The system is open so that additional functionality may be added later.

Some of the constraints team may face during the project are: To meet the deadlines Not quite efficient in performing their roles and responsibilities as all team members are still students and learning Other commitments

Written Report 1

ITECH 7602

1.2 Problem Addressed: This project is to build/develop a new Library Management system

for ATMC which would make it easier and more efficient for the users of this system to use it. The current system doesnt provide the access to the students/staff to login or browse/search the book. Further, the naming of the books system is not very good due to which it is not easy for the student/staff to look the book on their own in the library. The new system would try to resolve these problems and provide a better naming system so that the books can be separated into the sections based on the subject which would provide make it easier for the students/staff to find the book and further, the new books can be put into the system without many problems. 2 Project Organization

2.1 External Organization: All the work is required to be done by all team members under

the supervision of Mr. Shreyash Patel while Ravi Kiran Singh Bondli will meet thrice or more times with client depending upon the need of the project to get the requirements, report the progress, discuss possible changes along with taking the final approval. The client in this case is ATMC where the main contact person is Mr. Ashwin Konero. However, the requirements are to be taken from either of the three project stakeholders: Name Ashish Jain Postion Technical Support Officer, ATMC Sung Kin Pun Chintan Shah VET Lecturer, ATMC Academic Student Support Officer, ATMC kin@atmc.vic.edu.au cshah@atmc.vic.edu.au Contact details asjain@atmc.vic.edu.au

Written Report 1

ITECH 7602

2.2 Internal Organization: The team is supervised by Mr. Shreyash Patel with Prit Pal Kaur

Lohat as the Project Manager. Further, the team members are divided into groups of Developers, Documenters, tester and Quality Assurer. The hierichal chart is as

Written Report 1

ITECH 7602

3. Team Contract: There are 12 members working on this project. The names of the team members along with their roles are as: Team Member Name Prit Pal Kaur Lohat Pritpal.lohat@yahoo.com.au Project Manages project Contact details Role Responsibilities

Manager/Researcher resources and team activities. She is responsible for planning, initiating and closing of the project. Further, she is responsible to get all the deliverables made by the team member to be submitted on

Tajinder Singh

Dhillon_stud@yahoo.com

Assistant Project Manager/Team Cordinator/Minute taker

time. Coordinate the team meetings; help project manager to

Written Report 1

ITECH 7602

manage the work and team along with taking minutes (record) Raghu Veer Kosaraju Raghu.kosaraju@gmail.com Quality Control Manager of every meeting. Coordinates the activities required to meet the quality standards and come with the recommendations to meet the quality. He is also responsible to coordinate with Risk Manager and Kranthi Kumar Reddy Mora kranthicbz@gmail.com Lead Developer/Designer Tester. He is responsible for the design of the system and to design logo if any. Further, he is responsible to coordinate between all the

Written Report 1

ITECH 7602

people working on software development and data Pradeep Sagar Reddy Daggula Sandeep Reddy Udumala Reddy.sandy1@gmail.com Software Developer Sagarsunny124@gmail.com Data Administrator administrator. He is responsible for building database for the project. He needs to work under lead developer to develop the Anuj Kumar Goud Kodipaka anujkumargoud@gmail.com Risk Manager/ Developer system. His main responsibility is to assure everything is being done on time and has been saved properly. Along with this he needs to assist the developer Navin Kumar bnavinreddy@gmail.com Lead Documenter team. He is responsible to get the work

Written Report 1

ITECH 7602

Reddy

done by other documenters and compile the whole report and submit it on time. Further, he needs to handle all the queries of his group and do research work for

Prem Nath Dasari Kaustubh harish Nimbalkar Shiva Tejaswi

dasaripremnath@yahoo.co.in

Documenter

them. Writing documents Writing documents

Nimbalkar.kaustubh@gmail.com Documenter

Shivatejaswi007@gmail.com

Tester/ Documenter

Test the software on various platforms. Along with this he would also work as documenter till

Ravi Kiran Ravi_rks777@yahoo.com Singh Bondli

Client liaison

week 8. Take the requirements from the client and look over ut

10

Written Report 1

ITECH 7602

through out the project and fix meetings with client periodically to ensure the project is going in right direction.

Further, each team member has to devote about 20 hours every week on the project which is to be reported to Assistant Project Manager.

4 Project Plan
4.1 Work Breakdown Structure: Week Week 1-3 Week 4 Tasks to be accomplished Group forming, contacting team members Assigning roles/responsibilities Start working on documentation on written report I, research on SPMP, decision on the technologies to be used, enhance the skills required to develop the project especially the development and data Deliverables

11

Written Report 1

ITECH 7602

Week 5

administration team Finish the written report I by Friday and the developers must start thinking about the designing of the system to be

Written report I

Week 6

used Draft a rough design of the system and start working on the development of the system Documenters start working on the other documents Client liaison officer would hold client meeting to confirm the understanding of his requirements with the client and get the requirements from the client if there is a gap between his understanding and the

Week 7

clients requirements Development of the software and documentation continue

Week 8

Design the logo Prepare the oral presentation and the draft of the documentation by taking the

12

Written Report 1

ITECH 7602

requirements from the requirement liaison officer and proposed design from the designer along with continuity of the software development. The client liaison offer need to interact with the developers to find if they are developing the system according to the Week 9 requirements System development, document writing and testing. Second meeting with the client to check if the system developed so far is in accordance with his Week 10 Week 11 requirements. System development, document writing testing Final testing and approval from client, poster making Status reports, PM tool usage and project diary and Implementation of the Week 12 Presentation preparation software prototype Written Report II, III & IV Final demonstration of system with poster Oral Report: External documentation Review

13

Written Report 1

ITECH 7602

presentation

4.2 Project Deliverables: Along with the development of the project the team need to

provide the following deliverables on the scheduled time: Statement of Work and Project Plan in week 5 Oral Presentation and Draft Documentation: Project Requirements and Proposed design in week 8 Oral Report: External documentation review in week 9 Implementation of the software prototype & draft of final document in week 11 Process, teamwork and participation: Status reports, PM tool usage and project diary in week 11 Final documents of requirements, design & testing in week 12 Final demonstration of system with poster presentation in week 12

4.3 Scheduled Meetings: Throughout the project span two meetings (team meetings and

supervisor meetings) are scheduled every week. The detailed description is as follows: Week Week 4 Week 5 Week 6 Week 7 Supervisor Meeting Tuesday 12:00 pm- 12: 30 pm Tuesday 1:00 pm- 1:30 pm Tuesday 1:30 pm- 2:00 pm Tuesday 1:00 pm- 1:30 pm Team Meeting Monday through the day (building first contact) Monday 12:00 pm 1:00 pm Monday 12:30 pm 1:30 pm Tuesday 12:00 pm- 1:00
14

Written Report 1

ITECH 7602

Week 8 Week 9 Week 10 Week 11 Week 12

Tuesday 1:00 pm- 1:30 pm Tuesday 1:00 pm- 1:30 pm Tuesday 1:00 pm- 1:30 pm Tuesday 1:00 pm- 1:30 pm Tuesday 1:00 pm- 1:30 pm

pm Tuesday 12:00 pm- 1:00 pm Tuesday 12:00 pm- 1:00 pm Tuesday 12:00 pm- 1:00 pm Tuesday 12:00 pm- 1:00 pm Tuesday 12:00 pm- 1:00 pm

15

Written Report 1

ITECH 7602

4.4 Team Communication Plan: On the first team meeting the members shared the

contact details which include the contact numbers and email ids. On every team meeting the tasks would be reallocated to the team members after analysing the earlier work done by the Project Manager and team members are required to send their work via email to all members on the scheduled date and time. The inability to do work or attend the meeting or any other concern is also to be communicated to the team through group email. All issues would be resolved in the team meetings as scheduled above.
5. Quality Assurance statement: Quality Assurance manager would check all the

major deliverables before the due date to ensure the quality of the project is met. However, he may ask for the work to be checked for quality at the end of each week. 6 Risk Management Plan: Developing a project is a big task and the team must take care of all the risks which might erode the whole project. In the development of this project the team members found various risk factors which can create a problem as given. The contingency plan is further made to handle these risk if ever come into picture Risk: Unpredictable power failure or system shut down during work may result in loss of data. Contingency Plan: Team members are advised to save the work periodically may be after every 10- 15 minutes. Risk: Conflicts in the group.

16

Written Report 1

ITECH 7602

Contingency Plan: Try to resolve the conflict by listening to others and putting forward your concern between themselves. In case, it cant be resolved within the team members the assistance of project manager or supervisor can be taken. Risk: Inability to attend the meeting or do the assigned work due to uncertain reasons. Contingency Plan: Each major task has been provided to more than one member. The team member with the problems need to talk to the members within their subgroup and request to do their part while other members are expected to consider the request. Risk: Unpredicable system failure Contingency: Make the back up of each deliverable on the secondary device. References: Schach, S.R. (n.d.) Example IEEE software project management plan (SPMP) Retrieved August 15, 2011 www.intellisphere.org/index.php?option=com_docman...doc... Software Project Management Plan (SPMP) for Nirvana National Bank ATM Software Project (2004) Retrieved August 15, 2011 from http://www.buckleygolder.com/papers/mbg_SPMP_ProjectManagement.pdf Examples of SPMP from James (n.d.) Retrieved August 15, 2011 http://www.cmpe.boun.edu.tr/courses/cmpe450/fall2007/downloads/spmp.htm

17