Product life cycle @ ppt doms


Published on

Product life cycle @ ppt doms

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Product life cycle @ ppt doms

  1. 1. PSU CS 106 Computing Fundamentals II Product Life Cycle & SW Product Life Cycle HM 9/3/2007
  2. 2. Agenda <ul><li>Definition: Product Life Cycle </li></ul><ul><li>Generic PLC Phases (4) </li></ul><ul><li>SW PLC Phases (6) </li></ul><ul><li>Time Line of PLC </li></ul><ul><li>Summary of PLC Phases </li></ul>
  3. 3. Definition: Product Life Cycle <ul><li>The Product life cycle (PLC) describes a framework by which an organization manages the development of its products from inception to EOL </li></ul>
  4. 4. Generic PLC Phases (4) <ul><li>Exploration </li></ul><ul><li>Planning </li></ul><ul><li>Development </li></ul><ul><li>Refresh (or Deployment 1 st time) </li></ul>PLC phases progress sequentially. Due to feedback from learning in some later phases, earlier phases experience corrections or completions; also, for relatively short periods, some phases overlap. The 4 phases of the generic PLC are:
  5. 5. SW PLC Phases (6) <ul><li>Requirements Gathering </li></ul><ul><li>Requirements Specification </li></ul><ul><li>Architecture Design </li></ul><ul><li>Detailed Design </li></ul><ul><li>Implementation </li></ul><ul><li>Validation and Verification </li></ul>The more specific PLC for SW products refines the Exploration into a more elaborate requirements gathering and specification effort. Similarly, the Planning phase is broken into a High-level (architectural) and Detailed Design phase. The 6 phases of the generic PLC are:
  6. 6. Time Line of PLC Exploration Planning Refresh Development Product Production Candidate (PPC) Product Qualified (PLQ) Product Post Mortem Product Architecture Document (PAD) Product Deployment Opportunity Assessment (OA) Opportunity To Product Map (OPM) Product Qual Approval (PQA) Product Launch Approval (PLA) Opportunity Feasibility Approval Opportunity Scope Approval Opportunity Commit Approval Product Commit Approval (PCA) Product Feasibility Approval (PFA) Product Scope Approval (PSA) Product Integration Exit Product Integration Ready Product Design Complete Opportunity Identification Approval
  7. 7. Summary of PLC Phases Exploration Phase analyzes market, business and technology trends & opportunities which identify product solutions, that are implementable and of evident added value. Planning Phase formalizes next level of detail including market requirements, decision times, product scope, usage, features, technology integration, and results in an approved, documented POR . Development Phase implements requirements defined in Planning Phase; its Milestones are synchronization points to quantify progress toward goal. Refresh Phase constitutes further product revisions (or EOL) after initial product launch; may include updates to software, hardware, and other technologies. Exploration Planning Refresh Development
  8. 8. Requirements <ul><li>During Exploration phase of PLC, the customer’s requirements are gathered </li></ul><ul><li>Requirements define what needs to be done, not how it can be implemented </li></ul><ul><li>Takes ~ 20% of total time, calendar time </li></ul><ul><li>Error-prone, when not communicating with real customer </li></ul><ul><ul><li>Experts need to contribute </li></ul></ul><ul><ul><li>Not just pointy-haired managers </li></ul></ul><ul><li>Requirements must be specified in written documents </li></ul><ul><li>Documented requirements are signed off </li></ul><ul><ul><li>Iterations of refinement </li></ul></ul><ul><ul><li>Forming an agreement </li></ul></ul><ul><li>Change Control process defines, whether how requirements can be changed before EOL </li></ul>
  9. 9. Design <ul><li>During Planning phase of PLC, the product is designed </li></ul><ul><li>Solution to requirements are designed in 2 phases </li></ul><ul><li>Takes ~ 25% of total time, calendar time </li></ul><ul><li>High-level (AKA architectural) design selects general, high-level methods </li></ul><ul><ul><li>Including top-down approach </li></ul></ul><ul><ul><li>Or bottom-up approach selection </li></ul></ul><ul><li>Detailed design breaks architecture into small, implementable modules </li></ul><ul><ul><li>With inputs, outputs, globals, parameters </li></ul></ul><ul><ul><li>Dependencies between modules </li></ul></ul><ul><ul><li>Ideal to have few dependencies </li></ul></ul><ul><li>Detailed design results in actual plans, with milestones, measurable goals, bottle-necks, and recovery plans </li></ul><ul><li>Result is an agreed Plan of Record (POR) </li></ul>
  10. 10. Implementation <ul><li>During Development phase of PLC, the detailed design documented in the POR is implemented </li></ul><ul><li>I.e. the steps of the detailed design are actually executed </li></ul><ul><ul><li>Sequentially to use experience of programmer </li></ul></ul><ul><ul><li>In parallel, to meet milestones on time </li></ul></ul><ul><li>Takes ~ 35% of total time, calendar time </li></ul><ul><li>Can create large work force, progressing in parallel </li></ul><ul><li>Milestones needs to be tracked, met, and if missed, a backup plan needs to be selected to meet final goal </li></ul>
  11. 11. V&V and Refresh <ul><li>During Refresh phase of PLC, the implemented product is tested </li></ul><ul><ul><li>If first release, run all Validation and Verification steps </li></ul></ul><ul><ul><li>If subsequent release, focus on new features </li></ul></ul><ul><li>Important to schedule some of V&V steps from day 1 </li></ul><ul><ul><li>Possible to test modules via Unit Testing </li></ul></ul><ul><ul><li>Other parts tested via simulation </li></ul></ul><ul><ul><li>Rest desk-tested, or inspected </li></ul></ul><ul><li>Takes ~ 25% of total time, calendar time </li></ul><ul><ul><li>Total of all phases not = 100% </li></ul></ul><ul><li>Critical to have devised automated tools for testing </li></ul>