PROJECT PLAN FOR Community Web Site
INTRODUCTION:
This document is the Project Plan for the Template Based PHP Design..
DEFINITION:
Project Name Creating Community Web site
Project ID PHPF04
Project Sub ID IN
QMS ID B015
Customer Unknown
Project Type PHP Template web site
Project Model Offshore
OBJECTIVE AND SCOPE
OBJECTIVES
The objective of this project isdevelop a PHP based web site.
SCOPE
The Project will involve analysis, development, testing and documentation.
Special Terminology
Developer Programmer
CLT Centre for Latest Technologies
PMS Project Monitoring System
Excel Microsoft Excel
UTP Unit Test Plan
QMS Project Quality Management System
QC Quality Control
Word MS-Word
PL Project Leader
PM Project Manager
TM Team Leader
SCR Software Change Request
TPR Test Problem Report
BR Bug Report
System Boundaries and Assumptions
Responsibilities of the Customer
• The customer will set priorities for all work requested
• The customer will assign a Report Request number for each report requested, which will be used for all correspondence, as well as status monitoring of the specified task.
• The customer will provide all the data related to master entities
• Acceptance testing is responsibilities of the customer
• Test Problems Report (TPR) and Bug Report (BR) forms will be used to report problems with the software internally.
Expectations from the Customer
• Timely resolution of queries
• Time bound assimilation of functional requirements
• Approval of documents/ deliverables within a reasonable timeframe
• Providing all relevant documents
INITIAL STATUS OF THE SOFTWARE
The software is a New Dating/Community web site.
ORGANISATION
Team Composition
The project team shall consist of one Project Manager, one Project Leader and team members.
The exact numbers may vary from time to time and the current staffing shall be available in the latest team organization chart.
Name Qualification Experience Designation
Mr. Sandeep Joshi MSC (IT) 5 years Project Manager
Mr. Ravi Soni MCA 3 Year Project Leader
Mr. Jeevan Anjana BE 1 Year Team Member
Mr. Sanjay Jadham MCA 1 Year Team Member
Communication
Communication between project team and the client will be held as and when required by any of the following means:
Telephone
Office- Day Time Home- Night Time Alternate
+91-731-2460014 +91-9826220474 +91-9826352696
E-mail
Messenger
AOL MVPSandeeep
Yahoo Sandeepsnetid
Yahoo Sandeep56joshi
Organization and Technical Interface
The organization shall give the necessary support to the project and in case of additional software that are only project specific, the client will provide the licensed copy of the software for the project.
CLT Contacts
The names and addresses of all the contact persons are provided below for further communication.
CLT Office:
Mr. Anna Durai (Director)
35, Sapna Sangeeta Road, Indore(MP), India
Pin-452001
SCHEDULE
The Project duration is as follows
Project start Date: 5-Sep-2004
Project Estimated End Date: 15-Oct-2004
Time and Efforts
Phase Date of completion Total Man Hours
I 30 Sep 2004 200 Hr
II 15 Oct 2004 120 Hr
PROJECT PHASES
The project will be completed in two phases.
Phase 1:
1.) Analysis, Design and Template creation
2.) Coding and Unit Testing for Templates
Phase II:
1.) Integration of the Templates with the Existing System
2.) Deployment and Testing
Project Deliverables
For all the phases the deliverables will contain the corresponding web pages, the database script, and user documents. The buyer has to confirm the receipt of the deliverable within 2 days. If the buyer wants to change certain features then the request must be made within 3 days of receipt.
Project Delivery
Project delivery is scheduled on each Friday at 5 PM time. This will ensure us to work in a dedicated and concentrated way for the entire project.
Cost and Quality Measures
1. The overall cost for the product will be USD 1500.
2. For quality measure we will provide the following back log deductions
1. For late delivery [First 15 Days] - 2% deduction
2. For late delivery [after 15 Days] - 3% deduction
In order to quit from the deal the buyer has to intimate his/her reason after 3 days from start of a phase. Failing to do so will bound the buyer to pay the whole amount for that product.
Payment Schedule for Client
The client has following payment options:
1. Lump sum: The client can opt to pay full amount within 3 days of the project start.
2. Modular Payment
1. The client can pay the money in modules as follows
a. 30% at the beginning
b. 40% at the delivery of phase I
c. 30% at the delivery of phase II
The client can opt for any of the following payment services:
• Pay pal
• Wire to Wire Transfer [Bank]
Maintenance
The maintenance for the application will be provided free of cost for the first 60 days. This will cover all the programmatic errors and runtime application disabilities. For all Functional changes the buyer has to pay the change fee. To avoid this problem we recommend that the functionality should be clear in advance at both the sides.
WORK FLOW
1. Client will provide data required to develop the web pages and other relevant information.
2. The Functional Person will analyze those specifications and shall provide appropriate mappings in PHP Technology. The Project Leader will allocate the work/reports to appropriate Team Members and will designate the QC Person for that work. The Allocation will be done based on the following factors
• Familiarity with the functionality
• Current Stats of various Tasks
• Priority of Tasks
• Complexity of Tasks
• Availability of Resources
3. The TM will analyze the requirements and shall clarify the issues with PL/PM. The final requirements may be arrived after mutual discussions between the Functional Analyst and TM.
4. In case the task has to be completed on high priority, the user will convey the urgency to the PL.
5. The estimated End Date will be arrived at based on the estimated efforts and resource availability. These estimates are the reviewed [if required], and conveyed to the client.
6. The complexity of the task will be estimated based on following assumptions
For estimated efforts
• <=2 days. Task will be ‘Simple’
• <=4 days, task will be ‘Medium
• <=10 days, task will be ‘Complex’
7. The TM will create the detail report specification using the pre-defined templates and designated QC person will review this subsequently.
8. After QC Review all the defects will be resolved by the developer/TM and then QC person will carry out the rigorous testing and will fill the testing and UI checklist appropriately.
9. In case the specifications are revised or there is a delay in getting clarification for the queries, the end date will be negotiated. The task will then be re-estimated. The new date will be intimated to the client.
10. The PL will then inform the client that the task is ready for acceptance testing.
11. After the user formally accepted the task, it will be migrated to production.
RELEASE PROCEDURES
Delivery:
On Completion of task by TM, the designated QC Team will do iterative QC. Once cleared by QC team, the task will be given to client for Acceptance Testing. On receiving clearance from the client, the task will be migrated as deliverables.
Acceptance Criteria:
The client will convey the formal acceptance of the task via E-Mail.
If during acceptance testing, any enhancements or bugs re reported by the client, then a new Change Request Number documents the changes required.
Status Reporting and Progress Control
Client Reporting
RFD
The client will be sent a detailed status report every day. The report will list the project work log with the programmer and his efforts with tasks are assigned.
Status Reporting
Weekly Status Reports will be sent to the Project Manager every Friday.
The PM/PL shall review the progress of the project on weekly basis as per the QMS procedure.
Team Meeting
Team meetings will be conducted as and when required to update the status of Project to all TM and/or to resolve any issue pertaining to project.
Coding Standards
For all PHP stuff, the coding standards from PHP NUKE Framework will be used.
Commenting Standards
• Program Header
#================================================
# CLT IT Services
#
=================================================
# Owner : CLT
# Module : PHP
# File Name :
# Creation Date: 05/01/2004
# Last Update : 05/01/2004
# Description :
# Dependencies :
# Input Param :
# OutPut Param:
# Mdification History:
# Date By Comments
#================================================
Layout Standards
Font Type : Arial
Font Size : 14 (for Report Header)
Font Size : 12 (for Page Header of Report / general fields)
Font Size : 10 (for Report Body)
For all required fields the label Fore-color will be Red.
Quality Plan
Quality Objectives
Objectives of quality Plan are as under:
• To achieve maximum customer satisfaction by delivering code as per specification given by client
• To ensure all documentation and programs confirm to the standard agreed on.
• To facilitate early detection of defects /errors and subsequently correcting the defects, so as to deliver quality work.
• To focus on Defect Prevention through root cause analysis of defects.
Quantitative objectives are as follows:
• Schedule slippage – 0% for all major deliverables
• Work Product returns – below 5% of the deliverables
• Customer Satisfaction – 4 and above scores
Quality Activities
1. Work Product
Detail Report Specification
• Meets all specifications
• Reviewed
Reports
• Adherence to standards
• Consistent Layout
Executables /Reports
• No Bugs
Documentation
• No grammatical or typographical errors
2. Defect Detection
1. Review
• Peer Review
Task, for which efforts are greater than 7 days, would undergo a Peer Review. The review will be conducted as per QMS guidelines.
• Peer-to-Peer Review
A peer-to-peer review will be conducted for all the tasks that do not undergo a Peer review. The findings will be recorded in PMS accordingly.
2. Unit Test Plan
Unit Testing will be carried out for each unit of work assigned to a programmer. In this process, one standard checklist will be provided and all processes should adhere to it.
3. Other Test Plans
The nature of work is such that each module is related with each other. Under these circumstances there is a need of integration testing. Acceptance testing will be a responsibility of the customer.
3. Process Support
Mail Facility
Email facility will be used for communication.
Backup and recovery
For all development processes the MS Source safe will be used to maintain different version of code. Code Backup will be taken every Friday.
TESTING
Test Approach
Testing will be done in two stages. A checklist will be prepared to carry out testing of each report. Each report should adhere to the checklist and this will be verified in two stages. First, programmer will do a programmer level testing of work done and the QC person will test the same before releasing the project.
Test Design
Testing checklist will be created based on the design specifications by PL. and will be reviewed by QC person. Each test will clearly mention the test conditions.
Test Execution
During Testing, testing checklist will be checked against each process and the test results will be filled in the QC Entry Module of PMS, based on actual results obtained. If the actual results match with the expected results, the process will be accepted. Iterations of unit testing will be carried on the report till it is finally accepted. During a rejection, the testing team member will record the type and the number of errors found.
Unit Testing
Unit testing will be done for each process, by testing the performance of each process against the checklist, by developers along with the QC team. QC person may enhance testing checklist during QC cycle. Errors reported by QC person during the testing phases will be recorded in the QC entry module in PMS.
Acceptance Testing
Acceptance Testing is the responsibility of the client and will be conducted during the acceptance-testing phase of product immediately following the final delivery of the product.
Technical Details
Technology:
Front End – PHP
Middleware – XML
Database – MYSQL
Platform – Linux
Reasons for selecting PHP:
© Productivity
© GUI Quality
© Tools and Support
© Web Space Cost
© Time Frame availability.
Technical Documents
Technical documents will be sent after the analysis is over. The Technical documents will contain.
© Enterprise Data Model
© Software Requirement Specification
© Entity- Relationship Diagram
© Data Flow Diagram
© Physical Table Design
© Form Layouts
---------------------------------
---------------------------------