Practical 4 Aim: Develop a Software Project Management Plan using Microsoft Project 2003/2007

Software Required: Microsoft Project Hardware Required: Computer Setup

Theory:
This document (Software Project Management Plan) describes the project management standards, procedures and various technical processes to be followed by 433-440 Team F throughout this project.These standards ensure management quality and consistency throughout the duration of the project. This document describes management processes and practices that the Team shall adopt throughout the duration of this project. These processes and management practices will be enforced in order for the Team to meet its four quality goals of Correctness, Completeness, Consistency and Reliability.

Software Project Management Planning

Online Techfest Managment System (TechFestO!)

1. Scope, Purpose and Objectives

This project is a Web Application that provides facility to conduct online management of the TechFest. This would be a dazzling change from the traditional way of managing the technical festival.

The purpose of this document is to present a detailed description of the Online TechFest Management System. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli.

This Web Application will be a TechFest management system for a college/university to organize and manage the technical festival. This system will be designed to maximize the organizing committees productivity by providing tools to assist in automating the selection process of events and their respective heads and the finance matters, which would otherwise have to be performed manually. By maximizing the committees work efficiency and production the system will meet the committees needs while remaining easy to understand and use. The application will facilitate communication between the organizing head, committee and the event managers via E-Mail.
2

2. Project estimation
2.1 Historical data used
Primarily we follow the manual systems documents that the HMS committee have been generated. The work done only on MS Excel and Ms Word. They created certain tables and done data entry in those excel sheets and take print outs. Then by analysing those prints they found conflicts manually. Then again change in those excel sheets. They place all these print out in store room for future reference.

2.2 Estimation techniques used

The purpose of the document is to specify the project plans and estimate the project. There may various estimation in size,cost,time and effort etc. We basically use the COCOMO model to estimate those area of project plans. 2.2.1 Size estimation For this we use size metric that is LOC(Line Of Code), which is very simple and most widely used size estimation technique. In this comments and blank lines should not be considered. Size estimation is mostly depend on which language the project is to be developed. For our project the estimated line of code will be approximately 3500 line. So it will be 3.5KLOC for whole project.

2.2.2 Effort estimation Effort = 2.4(KLOC)1.05 PM = 2.4(3.5)1.05 PM =8.94 9 PM

2.2.3 Time estimation Tdev is time to develop project is, Tdev = 2.5(Effort)0.38 Months = 2.5(9)0.38 Months = 5.76 6 Months

2.2.4 Cost Estimation Large systems are made up of smaller sub-systems so the cost can be affected depends on the behaviour, size, type and complexity of the project. Cost of each sub-system is estimated separately. Costs of the sub-systems are added to obtain total cost. It reduces the margin of error in the final estimate. It the schedule of the project is change then the cost can be affected relatively.

3. Risk management plan

3.1 Risk analysis
For our project there are several risks related with the system. As we done the primary analysis of those risks we found certain risks that might be occur. The reusabily of the software may low, or the lack of the technology found in our team etc. For our project we analyze risks and conclude that there may be more than 40% chance of occurance of those risks.

3.2 Risk identification and Estimation

For our project we idetified and estimate several risks defined in table below :

Risks
Size estimated may significantly low Large number of users than planned Less reuse than planned Delivery deadline will be tightened Funding will be lost Customer will change requirements Technology will not meet expectations Lack of training on tools Staff inexperienced Staff turnover will be high PS BU CU TE ST Project size risk Business risk Customer requirements risk Technological risk Staffing risk

Category
PS PS PS BU CU CU TE ST ST ST

Probability
70% 60% 50% 80% 10% 10% 50% 80% 60% 10%

Impact
2 3 2 2 1 2 1 3 2 2

Impact values : 1 2 Catastrophic Critical 3 Marginal

4 Negligible

4. Schedule
4.1Gantt chart representation:

Table-2 - Gantt Chart Task List

Figure 2 Gantt chart Representation

4.2 Network diagram representation:

Figure 2 Network Diagram Representation

5. Project resources
Human Resource:
Chintan Radia Chintan Pathak Chintan Ram Namra Saheba Shreyash Samani Keval Shah

Hardware and Software

To make the System we have included the Hardware Requirements like: 1. Processor : Intel core2 duo/core i3/core i5

2. Main Memory : 1-2 GB RAM 3. Display : Colour Monitor (800 * 600 or higher resolution)

4. Input Device : Mouse, Keyboard For the system to work properly Software Requirements are as follows: 1. Net Beans IDE 7.1 2. Microsoft Project 2010 3. Microsoft Word 2007 4. My SQL Server5.5

6. Staff organization
Team structure
Chintan Radia :: GUI Designing,Requirements gathering,Integration Chintan Pathak ::Coding,Integration,Database,Deployment Chintan Ram :: Analysis,Documentation,Testing,Scheduling

Namra Saheba ::Coding,Integration,Database,Deployment Shreyash Samani: GUI Designing,Requirements gathering,Intergration Keval Shah :: Analysis, Documentation,Testing,Scheduling

6.2 Management reporter

The updated SPMP will be circulated as mentioned in schedule. Each of preliminary versions of all the documents and updates and status reports will be sent and discussed with the advisor Ms. Kruti Khalpada and upon approval the approved document will be circulated to the project guide of our project. The report on the status of the project will be sent to the project guide at the end of the 6th semester of Charusat.

Conclusion:
Thus we studied and developed the SPMP document.

10

11