Software Project Management Plan Version 1.

0 29/01/2012

ONLINE MOVIE TICKET RESERVATION SYSTEM.

Submitted to Department Of Information Technology Charotar University of Science & Technology CHANGA

Change History Major Field Achievement Test SPMP Version 1.0 Baseline Version Release date: 29/01/2012

Preface

The purpose of this document is to specify the project plan to develop the Online Movie Ticket Reservation System. The primary audience is the project advisor, Mr.Martin Parmar, and other members of the CE-IT department of the Charotar University. This document outlines a brief plan about how the project is to be shaped and also includes the milestones and deliverables. The SPMP document will serve as a guide for the students, faculty members, and other administrative persons. Updates of this document will serve to record the progress of the project.

Table of Contents
Table of Contents............................................................................................................................................................4

List of Figures 1. Figure.1 Schedule 2. Figure 2. Gantt chart

1.0. Overview 1.1. Project Summary 1.1.1. Scope, Purpose and Objectives

This project is aimed to provide the customers facility to book tickets for cinema halls online, through which they can book tickets anytime , anywhere. E-ticket system is basically made for providing the customer an anytime and anywhere service for booking the seat in the cinema hall and to gather information about the movies online. The user can easily be able to know about the movies released and then make the choice. In this project, we will illustrate our system by providing DFD on some functions. And we will also provide some process description and data dictionary. Admin can use the system to insert and delete data (e.g. film description, time table) which will update the webpage (webpage are dynamic page, changing according to the data in database). Also, admin can check the statistic information from the system.
5

OBJECTIVE OF THE PROJECT

The main purpose of our online ticket booking system is to provide another

way for the customer to buy cinema ticket. It is an automatic system. After inserting the data to database, staff need not to due with the order receive through the system. In fact, there is similar system on the internet, but there is no refund method found in the existing system. This system is basically aimed to provide the customer the complete information of the movie, according to which the customer can book the tickets and the refund facility provides more flexibility to the system. The goals of our system are: 1 To provide a anytime anyplace service for the customer 2 To minimize the number of staff at the ticket box 3 To promote the film on the internet 4 To increase the profit To obtain statistic information from the booking record

1.1.2. Assumptions and Constraints

The author of this document is expected to complete the project within two semesters. This project will use resources in the form of time and effort that will be spent developing the project deliverables and under the guidance of Mr.Martin Parmar sir who kindly agreed to be the advisor and a guide for this project. My advisor has said that a database of this whole system should be dynamic & should be accessible by the admin Of course, this databank can be modified and updated at any point of time in the future by the administrative person.

1.1.3. Project Deliverables

The list of project deliverables is: Project Management Plan Software Requirements Specification Software Design Description Working System with an Access Database Final Project Document Refer to section 1.1.4 for the expected delivery dates of the project deliverables.

1.1.4. Schedule and Budget Summary

Budget Summary: No budget required.

A tentative schedule is as shown below in table 1.

Figure 1: Schedule

1.2. Evolution of the Plan

The preliminary drafts of the SPMP will be submitted to my advisor and after approval, copies of the same will be distributed to the members of the committee on the date as referred to in section 1.1.4, figure 1. For configuration management, refer to section 7.1, configuration management plan.

2.0. References
This web application has been prepared on the basis of discussion with Team Members, faculty members and also taken information from following books & website
1)

IEEE Document Standards published in IEEE Standards Collection 2001 editions.

2) www.google.com 3) www.wikipedia.org 4) Fundamental of Software Engineering by Rajiv Mall 5) Software Engineering: A practitioners approach Ed. By Pressman, Roger 6) Software Engineering Seventh Edition Ian Somerville

3.0. Glossary

LAN- LOCAL AREA NETWORK GUI- GRAPHICAL USER INTERFACE SDD- SOFTWARE DESIGN DOCUMENT SCMP- SOFTWARE CONFIGURATION MANAGEMENT PLAN SRS- SOFTWARE REQUIREMENT SPECIFICATION

4.0. Project Organization 4.1. External Interfaces

The external interfaces for the project would be users who want to give online exams including the student and administrative persons related to that educational organization.

10

4.2. Internal Interfaces

None

4.3. Roles and Responsibilities

The software developer is responsible for all documentation to be developed and for all work to be done.

5.0 Managerial Process Plans 5.1. Work Plan 5.1.1. Work Activities
Refer to section 5.1.2 Gantt chart.

5.1.2. Schedule Allocation

Figure 2: Gantt chart Online Movie Ticket Reservation-Project Schedule Project Developers: 09IT056 09IT045 09IT052 09IT066 Status date: January 29th, 2012 Due Date: March 31st, 2012

11

Project Status Symbols S Schedule A Satisfactory C Caution F Critical

Planning / Progress Symbols

B S A X Work before Schedule Time Scheduled Activity Time Work after Scheduled Time Scheduled But Not Worked

12

5.1.3. Resource Allocation

This project will use resources in the form of time and effort that I shall spend developing the project deliverables as mentioned in section 1.1.3.

5.1.4. Budget Allocation

None

5.2. Control Plan 5.2.1. Requirements Control Plan

When changes are to be made in the requirements after the SRS has been released, the changes shall be brought to the attention of our group and discussed. Any changes that are to be made will be with the prior approval of the group and only if feasible and permissible within the constraints of the project mentioned in section 1.1.2, and resources in terms of knowledge and skill of the developer required. Once the changes have been made to the SRS document, an updated version of the SRS shall be released and circulated to the committee. However, no changes shall be made to the requirements once the SDD is completed.

5.2.2. Schedule Control Plan

If the work scheduled in section 1.1.4 is gets behind, the developer is ready to spend extra time on the project in between and after the schedules to make up for the lost time and deliver the final project on time.

5.2.3. Budget Control Plan

None
13

5.2.4. Reporting Plan

The updated SPMP will be circulated as mentioned in schedule of section 1.1.4. Each of preliminary versions of all the documents and updates and status reports will be sent and discussed with the advisor and upon approval the approved document will be circulated to the other members of the group. The report on the status of the project will be sent to the members of the group at the second module of this project.

5.3. Risk Management Plan

Risk # 1 Deficiency in the knowledge and understanding of the problem and its Solution indicates that the developer does not have the complete understanding of the problem. This will affect the quality of the project in terms of requirements of the product and their fulfillment, which is not desirable. Building a prototype for the project model and doing an extensive literature search can overcome this. This will help the developer in delivering an efficient and quality product. Risk # 2 Lack of Skills and knowledge of tools needed for statistical analysis, which means that the developer does not have knowledge about the tools and knowledge of working on statistical analysis. In this case, the developer is expected to update his / her knowledge of tools available for this purpose and decide the one that will be used in the project and master it. The developer may consult the faculty and other members of the group especially.

5.4. Closeout Plan

All the details about the post-mortem debriefings, report on the lessons learnt, project objectives and the milestones achieved would be mentioned as part of the final project paper at the end of the first module of the project component. At the end of the second module of project the developer will provide the group with electronic version of the project code and documentation for future reference and maintenance purposes.
14

6.0 Technical Process 6.1. Process Model

The ONLINE MOVIE TICKET RESERVATION SYSTEM will be implemented and executed using the WATERFALL MODEL.

6.2. Methods, Tools, and Techniques

Refer to section 6.1 (process model) for a description of the process. This process is described in [Braude] Software Engineering: An Object Oriented Perspective. This project adapts the system for use on a Personal Computer using PHP and MY SQL as its database management system. The tool for the statistical analysis is undecided at this point of time and would be mentioned in the updated version of this document.

6.3. Infrastructure Plan

The hardware resources are two Pentium III computers running Windows Xp/vista/7 Operating System. Each of these computers should have at least 256 MB RAM and a minimum of 10 GB of hard disk space.

6.4. Product Acceptance Plan

The committee will test the final product / application for acceptance.

15

7.0 Support Process Plans 7.1. Configuration Management Plan

All the project deliverables are to be considered as configuration items. The Configuration item as well as its file would be named after the document like SRS, SDD and followed by the version number. For example, all the preliminary versions that are submitted to the advisor for review would be named with the abbreviation followed by 0.1, 0.2. After the advisor approves the basic SPMP, this baseline document will be version 1.0 and is distributed to the group members and stakeholders. Informal updates with the advisor will be numbered with 1.1, 1.2, etc. and the next full distribution to the group would be version 2.0, etc.

7.2. Documentation Plan

The IEEE standards would be followed for all documentation purposes. All the documents would be discussed and reviewed with advisor before their baseline versions are issued and distributed to the members of the committee on the due dates mentioned in section 1.1.4 for delivery dates.

7.3. Quality Assurance Plan

A Software Quality Assurance Plan will be developed following recommended departmental standards. See section 1.1.4 for its delivery date.

16

7.4. Review and Audits

Review and Audits would be addressed as a part of the Software Quality Assurance and Verification & Validation Plan that would be developed following recommended departmental standards. See section 1.1.4 for its delivery date.

7.5. Problem Resolution Plan

None, problems would be resolved informally between the developer, the advisor and the studio committee.

7.6. Subcontractor Management Plan

None

7.7. Process Improvement Plan

None, this is a single software development experience and the lessons learned will be included in the final project document.

17