Product families

984 views

Published on

How to manage requirements of a set of products, using commonalities and variabilities and specialties among the products

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
984
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • 09/08/11 10:18
  • Product families

    1. 1. Product Lines (Product Families) <ul><li>How to manage requirements for different variants of a product </li></ul><ul><ul><li>Introduction </li></ul></ul><ul><ul><li>Open Discussion </li></ul></ul><ul><li>Yaron Zelichover </li></ul><ul><li>February 2009 </li></ul><ul><li>www.manageware.co.il </li></ul>
    2. 2. <ul><li>Purpose </li></ul><ul><li>How to manage requirements of a set of products, using commonalities and variabilities and specialties among the products </li></ul><ul><li>Benefits </li></ul><ul><li>Reuse of common requirements </li></ul><ul><li>Central control of commonalities </li></ul><ul><li>Shorter Time-To-Market </li></ul><ul><li>Central Updates for requirements changes between product lines. </li></ul>Product Families
    3. 3. <ul><li>Concept </li></ul><ul><li>Splitting the requirements base into infrastructure and products </li></ul><ul><li>Managing commonalities, variabilities, and product specific requirements </li></ul><ul><li>Tractability between instances of same requirements in different product lines (rather than just “clone and own”) </li></ul><ul><li>Terminology: Product, Product-line, Common, Variant, Specialty. </li></ul>Product Families
    4. 4. <ul><li>Possible Solutions in DOORS </li></ul><ul><li>Common and Variant in a single module using Filters. </li></ul><ul><li>Central module for Common requirements and a separate module for variant requirements </li></ul><ul><li>Base infrastructure module for common requirements and a module per product line with copy of common requirements and additional variant requirements </li></ul>Product Families
    5. 5. <ul><li>Solution 1: “One Module” - concept </li></ul><ul><li>One module contains both common and Variant requirements </li></ul><ul><li>Use Objects hierarchy to structure module </li></ul><ul><li>Use Object Attributes to differentiate variants </li></ul><ul><li>Use Filters and Views to display required variant requirements </li></ul><ul><li>Use Views to switch between complete list or a product line </li></ul>Product Families
    6. 6. <ul><li>“ One Module” solution </li></ul>Product Families Heading Heading Common Requirement Variant Requirement Specific Requirement Heading Common Requirement Variant Requirement Specific Requirement Product Requirements module
    7. 7. <ul><li>Solution 1: “One Module” – Pros. </li></ul><ul><li>Complete view of all requirements for all product lines </li></ul><ul><li>Simplicity – basic DOORS operations (filters, etc…) </li></ul><ul><li>Solution 1: “One Module” – Cons. </li></ul><ul><li>Large modules – </li></ul><ul><ul><li>Lower performance </li></ul></ul><ul><ul><li>Navigation in the module is less convenient </li></ul></ul><ul><li>No real separation between product lines – error prone. </li></ul><ul><li>Document Structure (i.e. Headings) must remain the same. </li></ul><ul><li>Baselines are for the entire module – not per product line </li></ul><ul><li>Requires multi users work on the same module </li></ul>Product Families
    8. 8. <ul><li>Solution 2: “Variant Modules” - concept </li></ul><ul><li>Central module for common requirements </li></ul><ul><li>Separate module for each product-line that contains only the variant requirements (Delta) </li></ul><ul><li>No duplication of Common requirements in different modules </li></ul><ul><li>The “big picture” is represented by a set of modules </li></ul><ul><li>Links represent &quot;Derived From&quot; relationship </li></ul>Product Families
    9. 9. <ul><li>“ Variant Modules” solution </li></ul>Product Families Heading Heading Common Requirement Common Requirement Common Requirement Heading Common Requirement Common Requirement Common Requirement Heading Heading Variant Requirement Specific Requirement Heading Variant Requirement Specific Requirement Common Requirements module Product Line 1 module Heading Heading Variant Requirement Specific Requirement Heading Variant Requirement Specific Requirement Product Line 2 module
    10. 10. <ul><li>Solution 2: “Variant Modules” – Pros. </li></ul><ul><li>Smaller modules </li></ul><ul><ul><li>Better performance </li></ul></ul><ul><ul><li>Easier to navigate in the module </li></ul></ul><ul><li>Simplicity – basic DOORS operations </li></ul><ul><li>Central view a of an original requirements and all it variants. </li></ul><ul><li>Solution 2: “Variant Modules” – Cons. </li></ul><ul><li>No complete view with “out-of-the-box” functionality </li></ul><ul><li>No dynamic updates between product lines </li></ul>Product Families
    11. 11. <ul><li>Solution 3: “Base and Variant” - concept </li></ul><ul><li>One &quot;Base module&quot; which holds the a product &quot;reference&quot; requirements </li></ul><ul><li>Each Product Line module is a copied module of the &quot;Base module&quot; (or only relevant sections are copied) </li></ul><ul><li>Links between each copied requirement in the Variant module to its source in the Base module </li></ul><ul><li>In the Variant modules requirements can modified and specific requirements added </li></ul><ul><li>Base module manager is responsible to check for modification in the variant modules (‘Suspect Links’) and update the Base and other Variants </li></ul>Product Families
    12. 12. <ul><li>“ Base and Variant” solution </li></ul>Product Families Heading Heading Common Requirement Variant Requirement Specific Requirement Heading Variant Requirement Specific Requirement Heading Heading Variant Requirement Specific Requirement Heading Common Requirement Variant Requirement Specific Requirement Heading Heading Common Requirement Common Requirement Common Requirement Heading Common Requirement Common Requirement Common Requirement Common Requirements Product Line 1 module Product Line 2 module
    13. 13. <ul><li>Solution 3: “Base and Variant” – Pros. </li></ul><ul><li>Complete view of all requirements per product line </li></ul><ul><li>Dynamic updates between different product lines </li></ul><ul><li>Efficient reuse of requirements between different product lines </li></ul><ul><li>Solution 3: “Base and Variant” – Cons. </li></ul><ul><li>Relatively complex setup and management </li></ul><ul><li>Requires management of Base module </li></ul>Product Families
    14. 14. <ul><li>Open Discussion </li></ul><ul><li>How do you do it in your organization? </li></ul>Product Families

    ×