applications agenda (1 of 2)

33
10. Applications 1 Applications Agenda (1 of 2) 1. Introduction 2. Example 3. Simple products 4. Classical development 5. Incremental builds 6. Spiral development 7. Prototypes

Upload: pello

Post on 13-Feb-2016

21 views

Category:

Documents


0 download

DESCRIPTION

Applications Agenda (1 of 2). 1. Introduction 2. Example 3. Simple products 4. Classical development 5. Incremental builds 6. Spiral development 7. Prototypes. Applications Agenda (2 of 2). 8. Enterprise boundary 9. Less than optimum design 10. Less than optimum team - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Applications Agenda (1 of 2)

10. Applications 1

Applications Agenda (1 of 2)

1. Introduction 2. Example 3. Simple products 4. Classical development 5. Incremental builds 6. Spiral development 7. Prototypes

Page 2: Applications Agenda (1 of 2)

10. Applications 2

Applications Agenda (2 of 2)

8. Enterprise boundary 9. Less than optimum design 10. Less than optimum team 11. Common component 12. Algorithms 13. Reduction of hierarchy 14. State of mind

Page 3: Applications Agenda (1 of 2)

10. Applications 3

1. Introduction

Activities, applications, and products Management Objects Symbology

1. Introduction

Page 4: Applications Agenda (1 of 2)

10. Applications 4

Activities

Determine what customer wants

Decide what to do

Get what it takes to do it

Do it

Check it out

Convince customer it’s what he or she wanted

Make it happen

Page 5: Applications Agenda (1 of 2)

10. Applications 5

Application

Apply same set of activities to each task

Page 6: Applications Agenda (1 of 2)

10. Applications 6

A Product Composed of Products

Level 1 Product

Level 2 Product 1

Level 2 Product 2

Level 3 Product 1

Level 3 Product 2

Level 4 Product 2

Level 4 Product 1

Level 4 Product 3

Lower-level products

Page 7: Applications Agenda (1 of 2)

10. Applications 7

Symbology

1. Mange2. Understand3. Design4. Acquire5. Build6. Verify7. Sell off

1. Mange2. Understand3. Design4. Acquire5. --6. --7. --

1. Mange2. --3. --4. --5. Build6. Verify7. Sell off

These three symbols graphically indicate which set of activities apply

Page 8: Applications Agenda (1 of 2)

10. Applications 8

2. Example

Problem Requirements Suggestions

2. Example

Page 9: Applications Agenda (1 of 2)

10. Applications 9

Problem

An entrepreneur has identified a market for a device that can locate cattle.

The device needs to located all the cattle in a 100 square mile area.

The device can assume good weather The device must be capable of working when the

cattle are in rough terrain

Page 10: Applications Agenda (1 of 2)

10. Applications 10

Requirements

The device shall find 95 percent of all the cattle within a 100 square mile area within a continuous eight hour period assuming

The visibility is greater than 10 miles The humidity is less than 30 percent The terrain is that of Brewster County, Texas

The device shall display the location of each cow to the operator

Page 11: Applications Agenda (1 of 2)

10. Applications 11

Contractor Requirements

The contractor would like to make this device into a product line and sell to other customers, so the contractor imposes additional requirements

The device shall weigh less than 50 pounds. The device shall cost less than $10,000 in

production

Page 12: Applications Agenda (1 of 2)

10. Applications 12

Proposed Design

Cattle locating device

Cattle locator Cattle display

Camera Image processing hardware

Control computer

Control software

Display Display computer

Display software

Find and display cattle

Find cattle

Display cattle

Make image

Extract cattle

locations

Control hardware

Display cattle

Control display

Page 13: Applications Agenda (1 of 2)

10. Applications 13

Developing Products

Developing the cattle locating device employs 10 instantiations of the product-based development approach

1

2 3

4 6 7 8

9 10

5

Page 14: Applications Agenda (1 of 2)

10. Applications 14

Suggestions

Determining when to start Stabilizing the architecture Developing the staff and organization Understanding the customer Designing the product Developing the design concepts Looking at the big picture

Page 15: Applications Agenda (1 of 2)

10. Applications 15

Determining When to Start

Starting a product development depends upon Need of other products Available people Available money Schedule

Page 16: Applications Agenda (1 of 2)

10. Applications 16

Stabilizing the Architecture

It’s important to stabilize the architecture because the architecture influences

WBS Teams Staffing

A late change in fundamental architecture can cause rework

Page 17: Applications Agenda (1 of 2)

10. Applications 17

Alternate Architecture

Cattle locating device

Cattle camera Cattle imager and display

Camera Image processing hardware

Display Display computer

Display software

Find and display cattle

Image cattle

Locate & display cattle

Make image

Extract cattle

locations

Display cattle

Control H/W & display

Page 18: Applications Agenda (1 of 2)

10. Applications 18

Management

A suggested priority for management objects is People, staffing, budget, and schedule Legal Risk, TPPs, and life cycle plan Facilities, tools, and capital Communication and library Systems for configuration, changes, issues,

problems, and action items Reviews

Page 19: Applications Agenda (1 of 2)

10. Applications 19

Developing the Staff and Organization

Cattle locating device

Cattle locator

Cattle display

Camera

Image processing hardware

Control computer

Control software

Display Display computer

Display software

System IPT

Subsystem 2 IPTSubsystem 1 IPT

Note: WBSs align with products

Page 20: Applications Agenda (1 of 2)

10. Applications 20

3. Simple Products

Some developments don’t require all seven activities

Study Concept Purchased product Service

3. Simple products

Page 21: Applications Agenda (1 of 2)

10. Applications 21

4. Classical Development

Three phases are used to visual some programs Phase 0 develops a concept Phase 1 confirms ready for development Phase 2 develops the system

Concept exploration(phase 0)

Program definition & risk

reduction(phase 1)

Engineering & manufacturing development

(phase 2)

concept prototype system

4. Classical development

Page 22: Applications Agenda (1 of 2)

10. Applications 22

Series of PBDs

Phase 0 Phase 1 Phase 2

Classical development is a series of PBDs Nature of products varies with program

4. Classical development

Page 23: Applications Agenda (1 of 2)

10. Applications 23

5. Incremental Builds

Incremental builds allow parallel design and build PBD for product becomes multiple PBDs for builds

Build 1

Build 2

Build 3

Single product Multiple products

5. Incremental builds

Page 24: Applications Agenda (1 of 2)

10. Applications 24

6. Spiral Development

Function Form

BuildCertify

final form

intermediate form 2

intermediate form 1

6. Spiral development

Page 25: Applications Agenda (1 of 2)

10. Applications 25

Spiral Development

Incremental builds allow parallel design and build PBD for product becomes multiple PBDs for spiral

Single product Multiple products

6. Spiral development

Page 26: Applications Agenda (1 of 2)

10. Applications 26

7. Prototypes

Prototypes are a separate set of PBDs Documentation may be less rigorous

Product

Prototype

7. Prototypes

Page 27: Applications Agenda (1 of 2)

10. Applications 27

8. Enterprise Boundary

Cattle locating device

Cattle camera Cattle imager and display

Camera Image processing hardware

Display Display computer

Display software

Company 1

Company 3Company 2

Splitting a product between companies may be a problem

8. Enterprise boundary

Page 28: Applications Agenda (1 of 2)

10. Applications 28

9. Less than Optimum Design

Cattle locating device

Cattle imager Cattle display

Camera Image processing hardware

Display Display computer

Display software

System IPT

Subsystem 6 IPT

Overcome by negotiation or mapping

9. Less than optimum design

Page 29: Applications Agenda (1 of 2)

10. Applications 29

10. Less Than Optimum Team

Cattle locating device

Cattle camera Cattle imager and display

Camera Image processing hardware

Display Display computer

Display software

System IPT

Subsystem 6 IPTSubsystem 5 IPT

Overcome by negotiation or mapping

10. Less than optimum team

Page 30: Applications Agenda (1 of 2)

10. Applications 30

11. Common Component

Common components can be treated as shared products

System

Unit Unit

Common CSCI

11. Common component

Page 31: Applications Agenda (1 of 2)

10. Applications 31

12. Algorithms

Algorithms can be treated as another product

System

Algorithms Unit

CSCI

12. Algorithms

Page 32: Applications Agenda (1 of 2)

10. Applications 32

13. Reduction of Hierarchy

Cattle locating device

Camera Image processing hardware

Control computer

Control software

Display Display computer

Display software

Find and display cattle

Make image

Extract cattle

locations

Control hardware

Display cattle

Control display

Reducing hierarchy reduces number of products

13. Reduction of hierarchy

Page 33: Applications Agenda (1 of 2)

10. Applications 33

14. State of Mind

The application of the PBD approach is a state of mind. It’s the ability to reduce clutter by treating a product as

a set of products and then being able to apply the PBD activities to each product.

14. State of mind