1 / 33

Applications Agenda (1 of 2)

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

pello
Download Presentation

Applications Agenda (1 of 2)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  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

  3. 1. Introduction • Activities, applications, and products • Management Objects • Symbology 1. Introduction

  4. Activities Determine what customer wants Make it happen 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

  5. Application • Apply same set of activities to each task

  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 1 Level 4 Product 2 Level 4 Product 3 Lower-level products

  7. Symbology 1. Mange 2. Understand 3. Design 4. Acquire 5. Build 6. Verify 7. Sell off 1. Mange 2. Understand 3. Design 4. Acquire 5. -- 6. -- 7. -- 1. Mange 2. -- 3. -- 4. -- 5. Build 6. Verify 7. Sell off These three symbols graphically indicate which set of activities apply

  8. 2. Example • Problem • Requirements • Suggestions 2. Example

  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

  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

  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

  12. Proposed Design Cattle locating device Find and display cattle Find cattle Display cattle Cattle locator Cattle display Image processing hardware Camera Control computer Display computer Display Make image Extract cattle locations Display cattle Control software Display software Control hardware Control display

  13. Developing Products 1 2 3 5 4 8 6 7 10 9 Developing the cattle locating device employs 10 instantiations of the product-based development approach

  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

  15. Determining When to Start • Starting a product development depends upon • Need of other products • Available people • Available money • Schedule

  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

  17. Alternate Architecture Cattle locating device Find and display cattle Locate & display cattle Image cattle Cattle camera Cattle imager and display Image processing hardware Camera Display computer Display Make image Display cattle Extract cattle locations Display software Control H/W & display

  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

  19. Developing the Staff and Organization System IPT Cattle locating device Cattle locator Cattle display Image processing hardware Camera Control computer Display computer Display Control software Display software Subsystem 1 IPT Subsystem 2 IPT Note: WBSs align with products

  20. 3. Simple Products • Some developments don’t require all seven activities • Study • Concept • Purchased product • Service 3. Simple products

  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 system concept prototype Concept exploration (phase 0) Program definition & risk reduction (phase 1) Engineering & manufacturing development (phase 2) 4. Classical development

  22. Series of PBDs • Classical development is a series of PBDs • Nature of products varies with program Phase 0 Phase 1 Phase 2 4. Classical development

  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 Multiple products Single product 5. Incremental builds

  24. 6. Spiral Development final form Function Form intermediate form 2 intermediate form 1 Build Certify 6. Spiral development

  25. Spiral Development • Incremental builds allow parallel design and build • PBD for product becomes multiple PBDs for spiral Multiple products Single product 6. Spiral development

  26. 7. Prototypes • Prototypes are a separate set of PBDs • Documentation may be less rigorous Product Prototype 7. Prototypes

  27. 8. Enterprise Boundary Company 1 Cattle locating device • Splitting a product between companies may be a problem Cattle camera Cattle imager and display Image processing hardware Camera Display computer Display Display software Company 2 Company 3 8. Enterprise boundary

  28. 9. Less than Optimum Design System IPT Cattle locating device • Overcome by negotiation or mapping Cattle imager Cattle display Image processing hardware Camera Display computer Display Subsystem 6 IPT Display software 9. Less than optimum design

  29. 10. Less Than Optimum Team System IPT Cattle locating device • Overcome by negotiation or mapping Cattle camera Cattle imager and display Image processing hardware Camera Display computer Display Subsystem 6 IPT Display software Subsystem 5 IPT 10. Less than optimum team

  30. 11. Common Component • Common components can be treated as shared products System Unit Unit Common CSCI 11. Common component

  31. 12. Algorithms • Algorithms can be treated as another product System Algorithms Unit CSCI 12. Algorithms

  32. 13. Reduction of Hierarchy • Reducing hierarchy reduces number of products Cattle locating device Find and display cattle Image processing hardware Camera Control computer Display computer Display Make image Extract cattle locations Display cattle Control software Display software Control hardware Control display 13. Reduction of hierarchy

  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

More Related