PROJECT PLAN
FIUSchool of Computing and Information Sciences
CEN 4021 Software Engineering II
Printshop Workflow Automation System
VERSION: 1.1 / REVISION DATE: 17 February 2010Approval of the Project Plan indicates an understanding of the purpose and content described in this deliverable. Approval of the Project Plan constitutes approval of the project planning results and hereby certifies the overall accuracy, viability, and defensibility of the content and estimates. By signing this deliverable, each individual agrees the project has been planned effectively as described herein.
ProfessorMasoud Sadjadi / / (305) 348-1835
Signature / Date
Project Manager
Mohammed Syed / / 786-371-8365
Signature / Date
FIU School of Computing & Information Sciences | CEN 4021 Software Engineering IIPROJECT Plan
Printshop Workflow Automation SystemVersion 1.1 | 17 February, 2010
Contents
Section 1.Project Overview
1.1Project Description
1.2Project Scope
1.3Assumptions
1.4Constraints
Section 2.Project Organization
2.1Project Structure
2.2External Stakeholders
2.3Roles and Responsibilities
Section 3.Project Start-Up
3.1Project Life Cycle
3.2Methods, Tools, and Techniques
3.3Estimation Methods and Estimates
3.4Work Activities
3.5Schedule Allocation
3.6Resource Allocation
3.7Budget Allocation
Section 4.Monitoring and Control
4.1Change Management
4.2Issue Management
4.3Status Reporting
Section 5.Quality Management
5.1Quality Management Approach
5.2Quality Objectives and Standards Identification
5.3Project Reviews and Assessments
5.4Deliverables Acceptance Criteria
5.5Process Improvement Activities
Section 6.Communication Management
6.1Communication Management Approach
6.2Communication Stakeholders and Information Identification
6.3Distribution Groups
Section 7.Configuration Management
7.1Configuration Management Approach
7.2Configuration Management Tools, Environment, and Infrastructure
7.3Configuration Identification
7.4Configuration Control
7.5Status Accounting and Reporting
7.6Audits and Reviews
7.7Interface Control
7.8Vendor Control
Section 8.Performance Management
8.1Performance Management Approach
8.2Performance Objectives and Standards Identification
Section 9.Risk Management
9.1Risk Management Approach
9.2Risk Assessment
9.3.Risk Monitoring and Control
Section 10. Project Transition
10.1Closeout Plan
10.2Phase Closeout
Section 11. References
Section 12. Glossary
Section 13. Revision History
Section 14. Appendices
DIR Document 20PP-T2-2Page 1
FIU School of Computing & Information Sciences | CEN 4021 Software Engineering IIPROJECT Plan
Printshop Workflow Automation SystemVersion 1.1 | 17 February, 2010
Section 1.Project Overview
1.1Project Description
Describe the approach the project will use to address the business problem, including summarizing how the project will deliver the expected business outcomes and performance objectives.
The purpose of this system is to facilitate and automate production for XYZ printing Co. To provide a uniform interface for customer order submission, employee workflow, and management activities - this will enhance productivity and efficiency.
The Objectives are to centralize and streamline order entry and processing. Success Scenario: Order entry is done solely by customers, without need to call the print company. No orders are lost due to human error during processing. Production times should be reduced from 3 to 1 business days.
1.2Project Scope
Describe the project scope by defining what the project will and will not accomplish. Provide a narrative or bulleted list of deliverables, services, and/or solutions expected as outcomes of the project.
Project IncludesWeb based front-end for customers place orders and track progress
Access-controlled back-end to allow managers and workers to receive, organize and schedule customer orders for production
Documentation on system operation
Project Excludes
Hardware
Hosting
Failover/Backup
Billing/Credit Card Processing
Support
1.3Assumptions
Describe any project assumptions related to business, technology, resources, scope, expectations, or schedules.
AssumptionsWeb-based system
Support for Firefox 3+, IE 7+
Development team expertise is in LAMP, thus project will be developed on LAMP platform
Customer, XYZ Printing, has 10 employees and averages 300 orders per month
A day consists of 8 working hours, a week consists of 5 working days
Weekends federal holidays are off. Religious holidays are off by request.
Development team is already in place
1.5Goals
The goals for the project.
GoalsA secure system - access to user, customer service, admin, and worker functions is controlled according to roles and permissions
Fast response times –pages must load within 5 seconds
High quality system – system will be delivered without any show-stop (high severity issues)
Delivered on time and within budget – the system will be delivered within the cost & timeline defined in this document
Fully functional – all use cases defined in the RAD will be delivered
1.6Constraints
Describe the limiting factors, or constraints, that restrict the project team’s options regarding scope, staffing, scheduling, and management of the project.
ConstraintsSection 2.Project Organization
2.1Project Structure
Specify the organizational structure of the project team and stakeholders by providing a graphical depiction as shown in the example project organization chart in the instructions.
2.2Project Personnel
Specify the personnel of the project team along with their roles
Team Member / Role(s)Dulcardo Arteaga / Technical Writer
Naveen Gowda / Designer
LarissaGuerrero / DBA, Sysadmin
ErikKessler / Programmer
Lenny Markus / Programmer
JavierMesa / Quality Assurance Engineer
RolandoVicaria / System Architect
Mohammed Syed / Project Manager
2.3Roles and Responsibilities
Describe roles and responsibilities for the project structure and external stakeholders as identified above. A Project Contact Register or its equivalent is developed as part of this section.
Role / ResponsibilityDesigner / Design layout for site, create necessary HTML, CSS, JS, required for website
System Architect / Designs the overall architecture of the system and makes the major technical decisions related to DB, server technology, application framework, etc. Delivers the Design Document.
DBA / Design DB and implement the database. Tune the DB for optimal performance.
Sysadmin / Set up, configure, secure and manage the development & production environment. Install any software required by the development team.
Programmer / Handles all the PHP coding required to implement Design Document.
Quality Assurance Engineer / Create & execute test plans, provide reports of test results, and perform regression testing.
Project Manager / Responsible for planning, organizing, monitoring, and adjusting project. Delivers the Project Plan and is responsible for the outcome of the project.
Technical Writer / Responsible for documenting system
Section 3.Project Start-Up
3.1Project Life Cycle
Specify and describe life cycle model(s) that will be used for the project. If formal standards have been established at the organization or agency level, refer to the agency and/or organizational practices. In the description, include tailoring of any practices to accommodate specific project needs if applicable.
The project will employ the waterfall model, using strict deliverables, milestones, and schedule.
3.2Methods, Tools, and Techniques
Identify the method(s), standards, policies, procedures, programming language(s), reusable code repositories, and other notations, tools, and techniques that may be used to develop and/or deploy the products and/or services for the project.
The system will be developed on the LAMP platform. LAMP is the development team’s area of expertise. The appropriate application development framework will be chosen during the design phase.
The additional benefits of using LAMP are the easy availability of human resources and low cost. The operating system, application server, and database licensing costs of LAMP are zero, giving it a major cost advantage over proprietary platforms.
3.3Estimation Methods and Estimates
Describe the methods used to estimate the project level of effort, schedule, and budget. Includetools and techniques used to obtain the estimates in the description.Provide estimates for the project dimensions (effort, schedule, and budget), and identify the source or basis of the estimates and the level of uncertainty and risk associated with the estimates.
Estimation Methods and EstimatesDescription /
- Met with the team members to estimate how much time each activity would take. Estimates are in table below
- WBS was created and individual tasks analyzed
- Activity estimates applied to each task
- Tasks were scheduled and overall estimate was generate.
Effort in person-months or person-hours / 555.72 hrs
Schedule in calendar months / 2 months
Budget in dollars
Source/Basis of Estimates / Requirements Analysis, WBS, Estimation of hours for each task
Level of Uncertainty
Activity / Estimate time
Designing screens / 2hr/screen
Testing out HTML screens / 10 screens/day
Test out integrated screens / 5 screens / day
Designing test cases / 5 test cases/day
Executing test cases / 5 test cases /day
Integration Tests / 10 screens/day
Unit Test Code / 8 functions / day
System decomposition / 5 use cases /day
Code use cases (functions) / 2 use cases (functions)/day
Database design / 2 tables / day
Design and implement security / 5 use cases / day
Project Management: Monitoring / 5% of the hours being managed
Project Management: Adjusting / 5% of the hours being managed
3.4Work Activities
Provide a reference to the location of the work breakdown structure (WBS) and work packages within the WBS.
WBS Location / initial-pwas-msproj-plan.mpp3.5Schedule Allocation
Provide a reference to the location of the project schedule.
Project Schedule Location / initial-pwas-msproj-plan.mppTo highlightmajor accomplishments as initially planned in the project schedule, identify major projectmilestones and planned completion dates for delivery. This list should reflect products and/or services delivered to the end user as well as the delivery of key project management or other project-related work products.
A 10% buffer has been added to the schedule to ensure the project to allow for slippage.
Project Initiation / 2/18/10
Deliver Design Document / 3/12/10
Complete Implementation / 4/26/2010
QA & Testing / 5/11/2010
Delivery of Documentation / 5/28/2010
3.6Budget Allocation
Provide a reference to the location of the budget schedule.
Budget Schedule Location / initial-pwas-msproj-plan.mppIdentify the budget amount allocated by key budget category (e.g., project milestone or standard cost categories such as personnel, travel), including the time period that may constrain use of the budget.
Key Budget Category / Budget AmountPersonnel / $30953.00
Risk Mitigation / $1773
Total / $32726
Section 4.Risk Management
4.1Risk Management Approach
Describe the overall, high-level approach to risk management for the project. Summarize how risk management activities will be accomplished collectively. If formal risk management policies and procedures have been established at the organization or agency level, refer to the agency and/or organizational practices. In the description, include tailoring of any practices to accommodate specific project needs if applicable.
The risks have been systematically identified and prioritized. These risks are managed by first identifying mitigation alternatives for each risk. The best alternative was determined by calculating the mitigation value cost for each alternative and picking the least expensive one.
4.2Risk Assessment
4.2.1Risk Identificationand Analysis
Based on project-specific methods, describe how risks are identified and organized in preparation for performing risk analysis, such as use of methods and techniques like brainstorming, interviews, and risk factor tables. A Risk Register or its equivalent is developed as part of this section.
The identification, probability of occurrence, and recover cost are based on historical statistical risk data from previous projects managed by our organization. The list was further refined in project planning meetings with the team.
Risk / Prob. Of Occurrence / Recovery Cost / Risk Value (RV)R1 / System Architect Leaves / 0.10 / $1188 / $118.8
R2 / Programmer lacks necessary skills to code system / 0.2 / $654.75 / $ 130.95
R3 / Overly optimistic assumptions about the availability of some technology / 0.1 / $8880 / $888
R4 / Hardware failure in development environment / 0.1 / $320 / $32
4.2.2Risk Mitigation
Based on project-specific methods, describe how risks will be continually tracked to ensure that effective risk management is performed, such as use of methods and techniques like risk checklists and watch lists.
For hiring replacements, we are estimating 20% cost of prorated the average annual salary of the resource being replaced. This is a typical fee charged by recruiters.
R1Risk / Recovery Cost / Probability of Failure / Mitigation Value Cost
Hire Replacement System Architect (1 month) / $2880 / 0.2 / $576
Hire Backup System Architect / $7920 / 0.1 / $ 792
R2
Risk / Recovery Cost / Probability of Failure / Mitigation Value Cost
Hire Replacement Programmer (1 month) / $1440 / 0.2 / $288
Employ System Architect as Programmer (100 hrs @ $90/hr minus $4500 already budgeted) / $4500 / 0.1 / $ 450
R3
Risk / Recovery Cost / Probability of Failure / Mitigation Value Cost
Re-analyze customer requirements / $8880 / 0.1 / $888
R4
Risk / Recovery Cost / Probability of Failure / Mitigation Value Cost
Rebuild development environment / $320 / 0.1 / $21
Section 5.References
Provide a list of all documents and other sources of information referenced in the Plan and utilized in the project. Include for each the document number, title, date, and author.
Document No. / Document Title / Date / AuthorSection 6.Glossary
Define all terms and acronyms required to interpret the Project Plan properly.
Abbreviation/Term / DefinitionPWAS / Printshop Workflow Automation System, the name of the proposed system.
LAMP / Technology Platform using Linux/Apache/MySQL/PHP
QA / Quality Assurance
PM / Project Manager
DB / Database
DBA / Database Administrator
Sysadmin / System Administrator
Designer / Human Interface Designer
WBS / Work Breakdown Structure
Section 7.Revision History
Identify changes to the Project Plan.
Version / Date / Name / Description1.1 / 17 February 2010 / initial-pwas-proj-plan.doc / Initital Project Plan
Section 8. Appendices
DIR Document 20PP-T2-2Page 1