Houston 2015 COMFORTABLE SOFTWARE DEVELOPMENT FOR TEAMS FEATURE-DRIVEN DEVELOPMENT TM.

Slides:



Advertisements
Similar presentations
Welcome to the Montreal MIS Tutorial. MIS Tutorial What is an MIS What is the MIS role in JDF Introduction Gray Boxes MIS Requirements – Job Costing.
Advertisements

Coursework Origins It was developed as ‘Object Oriented Enterprise Engineering’ course for Dept. of Defense in Requirements were for OO language.
Eric Nickell.  History  What is Feature Driven Development?  What is a Feature?  Feature Driven Development Roles ◦ Class Ownership  Feature Driven.
Jon Grommes Feature Driven Development. Overview What is Feature Driven Development History of FDD Defining a Feature FDD Roles FDD Reporting FDD Process.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 Pittsburgh, PA Lecture 6: Team Planning.
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Feature Driven Development
CS 325: Software Engineering April 7, 2015 Software Configuration Management Task Scheduling & Prioritization Reporting Project Progress Configuration.
Chapter 19 Establishing Performance Standards
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Feature Driven Development Reid S. Carlberg SE470
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Design, Implementation and Maintenance
Design Reviews Peer Reviews. Agenda Peer Reviews Participants of Peer Review Preparation for a Peer Review Session The Peer Review Session Post-peer Review.
Chapter 9 Daily Food Cost
People © 2013 The Sleeter Group All rights reserved. Intuit, the Intuit logo and QuickBooks, among others, are registered trademarks of Intuit Inc. Other.
A PRODUCT COPYRIGHT © 2014 PATENT PENDING
CHAPTER 3 COST CONTROL What is revenue? (147) The income from sales before expenses.
VIRTUAL BUSINESS RETAILING Lesson 2 Purchasing. MAIN IDEA  Purchasing inventory for a store is an important & complicated job  To be successful, a store.
Roles Managers Technical Team Leaders Programmers Customers Database Administrators Instructors.
Sprint (1) Deliverables Capstone Courses. What are Sprint (1) Deliverables ? 1.Introductory Parts 2.High level planning and scheduling (with risk assessment)
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Insert: Introduction video. Insert: CMiC Job Cost Structure.
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
 It is especially important if you are starting a new business that you get a proper record keeping system in place from the beginning.  Good record.
PROJECT COSTING ZETA ERP. FLOW PANEL.
CENTURY 21 ACCOUNTING © Thomson/South-Western LESSON 6-1 The Nature of Merchandise Inventory.
Common Activities Activities and Tasks in the WBS.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Equipment Module Usage Tracking, Repairs & Maintenance.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
Copyright © 2012 by John Wiley & Sons, Inc. All Rights Reserved. HOUSEKEEPING MANAGEMENT SECOND EDITION ︳ MATT A. CASADO.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 3 1 Software Size Estimation I Material adapted from: Disciplined.
McGraw-Hill/Irwin Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. MRP (Material Requirement Planning) (Method under Dependent.
Chapter 19 Establishing Performance Standards Principles of Food, Beverage, and Labour Cost Controls, Second Canadian Edition Principles of Food, Beverage,
Chapter 3: Software Project Management Metrics
Manufacturing Plant maintenance Materials management Quality management.
Compare Delivery Invoice and Purchase Order Product Quantity (weight or count) Purchase Unit Price Confirm Product Quality Sign Delivery Invoice Issue.
As Partial fulfilment of Master of Computer Application [M.C.A. sem-6] Submitted by: – Suman M chauhan Project Guide: Mrs Vaishali Kaneriya.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Inventory Terms  Inventory – an amount of goods stored, including raw materials, purchased components, manufactured sub-assemblies, works in process,
Problem solving Chapter 3
Feature-Driven Development
SQA project process standards IEEE software engineering standards
Master Production Scheduling (MPS)
3. SYSTEMS DESIGN: JOB-ORDER COSTING
Scrum.
Feature Driven Development
Enterprise Processes and Systems
SQA project process standards IEEE software engineering standards
ERP = Enterprise Resource Planning
Supply Chain Logistics: management of the flow of things between the point of origin and the point of consumption to meet requirements of customers or.
Description of Revision
Production Record Keeping
Ready, Set, GoTransactions
Summarizing Our Models to Date
Production Record Keeping
Create, Collaborate, Construct - A Guide to Projects
NetSuite’s Value Propositions
Chapter 11 The Accounting Information System
Stock Handling /Inventory Control
Clinic Management System(CMS)
Principles of Cost Accounting 15th edition
Scrum in Action.
{Project Name} Organizational Chart, Roles and Responsibilities
Material Requirements Planning and Enterprise Resource Planning.
Presentation transcript:

Houston 2015 COMFORTABLE SOFTWARE DEVELOPMENT FOR TEAMS FEATURE-DRIVEN DEVELOPMENT TM

Three reasons why FDD may not be for you…

Do you do that voodoo that you do, so well? Copyright 1974 by Warner Brothers, Inc.

Are you small? Hi, I’m Larry. This is my brother, Darryl. And this is my other brother, Darryl. And, our nephew, Steve Jobs.

You cannot champion change …nothing more difficult… …nor more doubtful of success… …nor more dangerous to handle… …has enemies in…the old order… …lukewarm defenders… …nothing more difficult… …nor more doubtful of success… …nor more dangerous to handle… …has enemies in…the old order… …lukewarm defenders…

i am curtis schlak

How to participate how i present

Comfort The premises and conclusions by which I entrust myself to FDD

Axiom software is about people 1

Axiom all methodologies provide an illusion of control 2

Corollary participants’ belief in a process enable the success of a process 1

Corollary participants’ belief in a process enables accurate reporting 2

What we need believability familiarity simplicity

FDD: Who/How High-Level Review of Feature-Driven Development

The roles in FDD project manager chief architect development manager chief programmers class owners* domain experts

Develop an Overall Model Build a Feature List Plan by Feature 213 BUFD! Phases 1 - 3

Design by Feature Build by Feature 54 Phases 4 and 5

The anatomy of a phase entry criteria tasks verification exit criteria

Example Requirements People join the club to become members and get invoiced monthly a flat fee and participation fees for classes Participation fees for classes consist of a prorated amount of the instructor’s hourly rate and a percentage of the cost of the equipment used by participants in the class Record member purchases of food and beverages from the club for rewards For every ten dollars spent on food and beverages from the club, the member receives a one dollar credit on their next invoice Members RSVP for classes and their arrival is recorded Instructors schedule rooms and equipment for classes

Develop an Overall Model Phase I

Model Building Mechanics tasks learn the domain develop the model verification by team output diagrams and notes

Four Categories of Domain Objects problem domain systems integration data management user interface

Problem Domain Advice problem domain modeling in color

Systems Integration and Data Management Advice systems integration data management traditional design enterprise patterns blah blah blah

User Interface Advice user interface hand waving and unicorns

A Note on Modeling domain-neutral component moment-interval moment-interval details role thing description

Example Model

Build a Features List Phase II

Features List Mechanics tasks build a features list verification by domain experts output a categorized list of features by business activity and feature type

Syntax of a Feature feature: «action» «result» «object» «calculate» the «total amount» of a «sale» «determine» the «total quantity sold by a retail outlet» for an «item description»

Syntax of a Business Activity business activity: «action» «object» «completing» a «sale» «forecasting» «inventory»

Syntax of a Subject Area subject area: «object» management «sales» management «inventory» management

Member Management Rewarding a Member «create» a «$1 credit» for a «member purchase» «create» an «invoice line item» for «every credit»

Plan by Feature Phase III

Features List Mechanics tasks determine development sequence assign business activities owners assign class owners Output development order completion dates owners

intermezzo fixed-cost estimates

Design by Feature Phase IV

Features List Mechanics tasks form the team review features and domain in-depth design verification through inspection output the “design package”

Task Percentages of Time walkthrough1% design40% inspection3%

Build by Feature Phase V

Build Mechanics tasks code verification through code inspections and unit tests output promote to main

Task Percentages of Time code45% inspection10% promote1%

Tracking and Reporting

All Percentages of Tasks walkthrough1% design40% design inspection3% code45% code inspection10% promote1%

Tracking by Feature

Burn-Up

Report Board Member Management Billing a Member (18) 77% March 2016 Rewarding a Member (4) April 2016 Invoicing a Member (7) 50% January 2016

Houston 2015 fin