Project Manager:PATS Project Manager Estimator:Peter Project Manager Start Date:1/1/2010 PATS Software PATS Project Team.

Slides:



Advertisements
Similar presentations
High level QA strategy for SQL Server enforcer
Advertisements

Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Project Management.
Estimation of Defects and Effort Requirements Engineering & Project Management Lecture.
Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics
Project Risks and Feasibility Assessment Advanced Systems Analysis and Design.
What is a project? Project Management Institute definition
The Systems Development Challenge “Challenges lead to opportunities”
Chapter 14 Systems Development. Agenda Reasons for Change System Development Life Cycle (SDLC) Prototyping Rapid Application Development (RAD) Object.
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
Nu Project Management Office A web based tool to Manage Projects.
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Lesson 10: IT Project and Program Management. Lesson 10 Objectives  Identify resources for technical data  Identify project management fundamentals.
Tim St. John Masters Computer Engineering Software Engineering Track.
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Using UML to report results of project management for information systems projects Donna M. Gavin MMIS 621 Information Systems Project Management Assignment.
Chapter 10.
COCOMO-SCORM: Cost Estimation for SCORM Course Development
Software Testing Lifecycle Practice
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Design Development Image credit:
Chapter 16 Structured Systems Analysis. Learning Objectives Know goals, plans, tasks, tools, & results of systems analysis Understand/appreciate costs.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Web Engineering and Technology Unit I. Categories/Types of Web-Based Systems CategoryExamples Document centricOnline newspapers, manuals InteractiveRegistration.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
Request for Proposal (RFP)
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Estimating Cost size difficulty effort productivity work rate cost LoC, fp mm (ideal) mm $ $/mm time.
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
Rating Very Very Extra Cost Drivers Low Low Nominal High High High Product Attributes Required software reliability Database size.
Project Management Why do projects fail? Technical Reasons
بشرا رجائی برآورد هزینه نرم افزار.
1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Introduction to Project Management Lecture 1 HNC/D Project Management.
Chapter 11 Project Management.
Project Cost Management
Stacy Kowalczyk WIC Technical Hour 3/30/2005
COCOMO III Workshop Summary
Productivity Data Analysis and Issues
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
Tutorial: Software Cost Estimation Tools – COCOMO II and COCOTS
Constructive Cost Model
Pongtip Aroonvatanaporn CSCI 577b Spring 2011 March 25, 2011
Software Systems Cost Estimation
COCOMO Models.
COCOMO 2 COCOMO 81 was developed with the assumption that a waterfall process would be used and that all software would be developed from scratch. Since.
PPT3: Project planning and management
Lesson 10: IT Project and Program Management
Software Testing Lifecycle Practice
Chapter 3 Managing the Information Systems Project
Chapter 2: Building a System
COCOMO MODEL.
Presentation transcript:

Project Manager:PATS Project Manager Estimator:Peter Project Manager Start Date:1/1/2010 PATS Software PATS Project Team

Project Description Project Type: Embedded, simple Lifecycle: RAD Standard: RAD Description:

Strategist$ Analyst$ Designer$ Programmer$ Labor Rates (per hour) Financial Information

Test / QA$ Copywriter$ Art & Media$ Management$ Labor Rates (per hour) continued Financial Information

1-Function Points207 pts Summary Project Volume

Scaling Factors Nominal Architecture/Risk Resolution Nominal Development Flexibility High Precedence High Process Maturity Nominal Team Cohesion

Environment Factors Personnel High Analyst Capability High Applications Experience High Language and Tool Experience High Management Capability High Management Experience High Personnel Continuity

Environment Factors Personnel (Continued) High Platform Experience High Programmer Capability

Environment Factors Platform Nominal Execution Time Constraint Nominal Main Storage Constraint Low Platform Volatility

Environment Factors Project High Effective Management Tools Very Low Multi-site Development Nominal Office Ergonomics High Use of S/W Tools

Environment Factors Product Nominal Database Size Nominal Documentation Match to Life- Cycle Nominal Internationalization Nominal Product Complexity Nominal Required Reusability

Environment Factors Product (Continued) Very High Required Software Reliability

Environment Factors Internet Nominal Graphics and multi-media Nominal Legacy Integration Nominal Site Security Nominal Text content Nominal Tool Selection Nominal Transaction loads

Environment Factors Internet (Continued) Nominal Web strategy

Environment Factors Task Assignment Nominal Concurrency Low Fragmentation High Intensity

Constraints 100 % Time-Cost Tradeoff 100 % Plans and Requirements 100 % Integration and Testing 0 % Overlap 100 % Customer Response Time

Constraints (Continued) 1 days Minimum Customer Response Time 0 % Cushion 0 Sigma Risk Tolerance 0 % Requirement Evolution

Likely Risks Error prone modules Excessive schedule pressure Inability to meet performance goals Inadequate cost estimating Inadequate exception testing

Additional Risks Canceled projects Error prone modules Excessive paperwork Excessive schedule pressure Inadequate configuration control Inadequate cost estimating

Results Staffing Profile

Results Gantt Chart Labor Activity Start Date1/1/2010 End Date8/6/2010 Total Schedule7.1 MTHS

Results Defects Reported Defects Total Defects: During Dev.1,344 Year 116 Year 26 Year 35 Year 45

Cost By Method Results Effort & Cost Summary Total Effort22.6PM Schedule7.1MTHS Sub-total$536, Wage Inflation$0.00 Integration$96, Final Cost$633,040.27

Results Maintenance Costs Cost Structure Maintenance Year 1$125, Year 2$113, Year 3$104, Year 4$94,139.95