Shortcut to Parametric Estimation via Web Trnsport Charles Engelke Info Tech, Inc.

Slides:



Advertisements
Similar presentations
Order Processing and Requisition Accelerator Wouldnt it be nice if … all of our service centers could be coordinated through one system. Services Supplies.
Advertisements

ITSF STORE BUSINESS SOLUTION PRESENTATION. STORE MODULE INCLUDES: Material Management Purchasing Components Handling Shipments Receiving of parts Store.
Database Planning, Design, and Administration
Enhanced XA Security CISTECH Security Solutions Belinda Daub, Senior Consultant Technical Services
An Internet-Based Cost Estimation Tool Charles Engelke November 4, 2005.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Imbalanced data David Kauchak CS 451 – Fall 2013.
Trnsport Test Suite Project Tony Compton, Texas DOT Charles Engelke, Info Tech.
Lena Bigelow Business 550 Presentation SCRUM. -A project management process - Embraces iterative and incremental practices -Concentrates on what is important:
Copyright  2002, Medical Present Value, Inc. All rights reserved. Copyright © 2010 Texas Education Agency. All rights reserved. TEA confidential and proprietary.
Todd Bergland Trnsport Systems Manager WebCES TRT Chair Randy Lawton Senior Analyst WebCES Development WebCES Interface.
Alternate Software Development Methodologies
BTS530: Major Project Planning and Design Iterative Development References: Agile & Iterative Development, by Craig Larman, 2004, Addison Wesley. Agile.
Agile development By Sam Chamberlain. First a bit of history..
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
Software Engineering.
Software Processes: Traditional CSCI102 - Systems ITCS905 - Systems MCS Systems.
Live dashboards for Progress built by anyone, available anywhere. Introducing DataPA OpenAnalytics Nick Finch CTO.
Order Processing and Requisition Accelerator Wouldn’t it be nice if … all of our service centers could be coordinated through one system. Services Supplies.
Next Generation Trnsport Presented by Paul Neumann, TTF Chair, Colorado DOT Ian Baldwin, Info Tech, Inc. November 2005.
LADOTD CONSTRUCTION COST ESTIMATING Charles Nickel, P.E. Cost Estimate & Value Engineering Director Office: (225)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Estimating Software Size Part I. This chapter first discuss the size estimating problem and then describes the PROBE estimating method used in this book.
IBM Proof of Technology Discovering the Value of SOA with WebSphere Process Integration © 2005 IBM Corporation SOA on your terms and our expertise WebSphere.
Next Generation Trnsport Trnsport Users Group Conference Field Management TAG November 7, 2005.
More U-Substitution February 17, Substitution Rule for Indefinite Integrals If u = g(x) is a differentiable function whose range is an interval.
Next Generation Trnsport Presented to the AASHTOWare Trnsport User Group October 14, 2004.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
COMP 410 Update. The Problems Story Time! Describe the Hurricane Problem Do this with pictures, lots of people, a hurricane, trucks, medicine all disconnected.
An Introduction to Designing and Executing Workflows with Taverna Katy Wolstencroft University of Manchester.
PROPOSING TO WRITE A PROPOSAL? BY PAPIA BAWA. What are Proposals? Long reports usually written in response to a specific request or in response to your.
| nectar.org.au NECTAR TRAINING Module 5 The Research Cloud Lifecycle.
1 FlexTraining in a Nutshell Welcome to a brief introduction of the FlexTraining Total e- Learning Solution. This short sample course will outline the.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
New Printing Options from RTF Charles Engelke Info Tech, Inc. Trnsport Users’ Group October 15, 2004.
FPGA-Based System Design: Chapter 6 Copyright  2004 Prentice Hall PTR Topics n Design methodologies.
MCTS Guide to Microsoft Windows Server 2008 Applications Infrastructure Configuration (Exam # ) Chapter Four Windows Server 2008 Remote Desktop Services,
13-January-2003cse LifeCycle © 2003 University of Washington1 Lifecycle CSE 403, Winter 2003 Software Engineering
Introduction to Systems Analysis and Design
An Introduction to Designing and Executing Workflows with Taverna Aleksandra Pawlik materials by: Katy Wolstencroft University of Manchester.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Cost Estimation System CES Implementation at NDOR TUG 2006.
Chapter 3 Agile Software Development (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.
Systems Analysis and Design in a Changing World, Fourth Edition
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Systems Development Life Cycle
Lecture 4 – XP and Agile 17/9/15. Plan-driven and agile development Plan-driven development A plan-driven approach to software engineering is based around.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Dr. Rob Hasker. What if every project used Scrum?  Why might Scrum not be perfect for every project? Hard to get the big picture Early choices may have.
CS451 Software Maintenance Yugi Lee STB #555 (816) Note: This lecture was designed based on Stephen Schach’s.
CS223: Software Engineering Lecture 4: Software Development Models.
SPI NIGHTLIES Alex Hodgkins. SPI nightlies  Build and test various software projects each night  Provide a nightlies summary page that displays all.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Dr. Rob Hasker. Should every project use Scrum?  When might Scrum not be an appropriate model?  What are some of its limitations? Hard to get the big.
Extreme Software Engineering A Hands-On Approach From Extreme Software Engineering: A Hands-On Approach Daniel H. Steinberg Daniel W. Palmer.
Chapter 5: Software effort estimation
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Progress Apama Fundamentals
Brad Bird System Center & VM Architect Cistel Technology Inc.
Fast Action Links extension A love letter to CiviCRM
Decomposition.
Chapter 5: Software effort estimation
Extreme Programming.
Project Behind Schedule! What are my options?
Presentation transcript:

Shortcut to Parametric Estimation via Web Trnsport Charles Engelke Info Tech, Inc.

The Parametric Paradox Parametric estimation is one of the most important and desired estimation techniques That very few people use

Why Don’t More People Use Parametric Estimation? Because it requires powerful software? –No, Trnsport CES is available

What Most CES Users See

The Real Obstacles Requires lots of resources and information –The scope and breadth of issues is very large –Methodology is complex, requires a lot of training and effort to master –A lot of fundamental data must be gathered and managed before the first estimate can be built These are the big issues for CES users

Parametric Estimation is More Varied than Detail Estimation The models for estimating an item price are the same regardless of the item Cost-based –Determine crew, productivity, materials consumption, overhead, margin –Plug in current costs and derive unit price Bid-based –Calculate weighted average prices or fit to standard formula via regression –Apply results to predict new item bid prices

Parametric Estimation Models Vary for Different Job Types Steps needed 1.Develop conceptual model 2.Define the model as a “template” for new jobs of that type 3.Define how bid items are related to cost drivers 4.Statistically analyze historical prices 5.Enter model parameters and calculate Only the last two steps apply to detailed estimation with CES or Estimator

The Real CES Challenges New CES users start with a blank screen for the parametric model templates Can’t develop estimates until all those preliminary definitions are done It’s hard to see how to specify the abstract model so it can be used for real jobs And there is always other, more urgent, work to be done

The Fundamental Dilemma CES is extremely flexible –Any parametric model that can be reduced to formulas of any kind can be defined in it But the first steps are extremely steep –And it’s hard to understand these steps without experience using other models The necessary flexibility and power in the system lead to barriers to entry

Simplify, simplify. Parametric estimation is very complex and difficult in general So forget the general problem for now –All of CES will still be there to handle it when we come back! Pick one type of problem, and create an “express lane” for it in CES –Make a shortcut to parametric estimation

The Shortcut(s) Choose specific types of estimates to support –Asphalt resurfacing, perhaps another Pick one estimation model per type –That is, determine what parameters will be considered, and how estimates will be derived from them Provide reasonable defaults for everything –So estimators can provide minimal data and get adequate results, or more data for better results –Use defaults to simplify installation, too

Example: Resurfacing Minimal parameters –Length, lanes, lane width, depth Optional parameters –Location, urban/rural, maintenance of traffic, mobilization, milling, drainage, earthwork Underlying data for calculations –Acquire cost data, and classify and analyze historical data

Shortcut Work Flow (for the user) User enters required parameters –An estimate total is provided User modifies defaulted parameters –The estimate is adjusted automatically User wants to change basic estimation model –Must leave the shortcut and continue work in full CES instead

Shortcut Work (for the agency) Install shortcut, accept default data –Get reasonable estimates, but not based on anything specific to your agency Classify basic historical data –Define a few item groups and conversions –Run analysis models to feed CES Develop your own models –Acquire cost driver data specific to your issues –Again, must leave shortcut for full CES at some point

Challenges for a Shortcut We don’t want to add it to today’s CES client –That’s already big enough –Trying to make something simple by adding to a complex product isn’t likely to succeed We don’t want to create a new application –Those are expensive to build and maintain –It might be the first of many specialized applications, which would be hard to manage What options are left?

Enter Web Trnsport An initiative to replace use of the Trnsport Windows clients for some functions –More ambitious than Trnsport Intranet –Not just a supplement to client-server Web functions are inherently very loosely coupled –So specialized functions can be developed independently of others –Within a single manageable framework

Web Trnsport is not a New Application Only the blue pieces are new

Strategic Direction to Web Lots of reasons for Web Trnsport –(I’ll gladly harangue anyone who’ll listen) –Part of strategic plan for several years So Info Tech proposed a project to create needed infrastructure –And the TTF said “what’s in it for the users?” –Every project should provide direct user value Project redirected to start Web Trnsport to solve important user problems –Starting with parametric estimation shortcuts

Project Goals Provide a useful function almost all licensees will want to deploy –Parametric estimation shortcuts Be easy for licensees to implement quickly –We don’t want to deliver “shelfware” Ready for people to use almost immediately –Without a lot of configuration, data management, or end-user training Create architectural foundation for Web Trnsport while delivering immediate value

Project in a Nutshell Performing this fiscal year –Late start due to redirection of goals Using “agile” methodologies –Replaces traditional lifecycle (with several review and approval stages) with constant communications –Product builds weekly or more frequently, available instantly to TRT Delivery Q3 2004

What We’re Shooting For

Issues Flexibility versus simplicity tradeoffs –Where do we draw the line? Integration with agency data –Can we make matching items to cost groups as simple as the rest? Authorized users –Same as for similar CES screens, or a broader group? –Allow “guest” estimators? Planners could create rough estimates, save in CES for estimators to develop more fully later.

What Can You Do? Communicate with the TRT –“Agile” methodologies mean more functional decisions happen during the project Discuss what you want –Chat about it on the TEA mailing list Get your system managers ready! –A successful project will result in something quick to install and deploy

Shortcut to Parametric Estimation via Web Trnsport Charles Engelke Info Tech, Inc.