Software Product Lines - Revision history

Suhridk: /* What to build pattern */

2012-04-13T12:24:46Z

What to build pattern

2012-04-13T12:14:29Z

Product Line Patterns

2012-04-13T11:49:35Z

Org mgmt practice areas

2012-04-13T11:37:23Z

Technical Mgmt Practice Areas

2012-04-13T11:25:19Z

SE Practice Areas

2012-04-13T10:58:20Z

Activities KPA's

2012-04-13T10:40:31Z

Activities KPA's

2012-04-13T10:34:27Z

Management

2012-04-12T18:48:06Z

Product Development

2012-04-12T18:44:05Z

Core Asset Development

← Older revision		Revision as of 12:24, 13 April 2012
Line 170:		Line 170:

	[[File:WhatToBuildPattern.png]]		[[File:WhatToBuildPattern.png]]
		+
		+	== Factory Pattern ==
		+
		+	* Puts all the various patterns together.
		+
		+	[[File:PLFactoryPattern.png]]
		+
		+	* What to Build - determines products to be included in PL
		+	* Each Asset - provides individual core assets
		+	* Product Parts - provides the assets to form a product
		+	* Assembly Line - establishes product build capability
		+	* Product Builder - builds the products
		+	* Cold Start - prepares organisation for PL operation
		+	* In Motion - keeps PL organisation running
		+	* Monitor - keeps watch on the organisation

← Older revision		Revision as of 12:14, 13 April 2012
Line 161:		Line 161:
	* Problem - What part of a product line effort needs to be done ?		* Problem - What part of a product line effort needs to be done ?
	* Solution - Grouping of practice areas. Relations among these practice areas.		* Solution - Grouping of practice areas. Relations among these practice areas.
		+
		+	== What to build pattern ==
		+
		+	* Which KPA's help an org to decide on the products that need to be in the product line.
		+	* Context: An org has decided to field a sw product line and knows the general product area for the set of products.
		+	* Problem: To determine what products should be included in the product line.
		+	* Solution : Determining what to build requires information related to the product area, technology and market. The business justification and the process for describing the set of products to be included in the product line.
		+
		+	[[File:WhatToBuildPattern.png]]

← Older revision		Revision as of 11:49, 13 April 2012
Line 152:		Line 152:
	* Technology forecasting		* Technology forecasting
	* Training		* Training
		+
		+	= Product Line Patterns =
		+
		+	* They are process patterns rather than architectural or design.
		+	* Relate KPA's to specific activities.
		+
		+	* Context - Org Situation
		+	* Problem - What part of a product line effort needs to be done ?
		+	* Solution - Grouping of practice areas. Relations among these practice areas.

@@ Line 133: / Line 133: @@
 * Tool support
 * Config Mgmt
-* Make/buy/mine commission analysis
+* Make/buy/mine commission analysis.
-* Data collection, metrics and tracking
+** Buying COTS maybe more expensive - but is already generic.

@@ Line 113: / Line 113: @@
 * Requirements Engineering
 * Architecture Definition
 * Architecture Evaluation
 * Component Development
@@ Line 121: / Line 124: @@
 * Testing
 * Understanding relevant domains

← Older revision		Revision as of 10:58, 13 April 2012
Line 109:		Line 109:
	* SW Engg KPA's to support Core Asset development activities and product development activities.		* SW Engg KPA's to support Core Asset development activities and product development activities.
	* Technical Management KPA's and Org Mgmt KPA's to support management activities.		* Technical Management KPA's and Org Mgmt KPA's to support management activities.
		+
		+	== SE Practice Areas ==
		+
		+	* Requirements Engineering
		+	* Architecture Definition
		+	* Architecture Evaluation
		+	* Component Development
		+	* COTS Utilisation
		+	* Mining existing assets
		+	* System integration
		+	* Testing
		+	* Understanding relevant domains

← Older revision		Revision as of 10:40, 13 April 2012
Line 106:		Line 106:
	* Certain skills are required to support the three activity areas above.		* Certain skills are required to support the three activity areas above.
	* A practice area is a body of work or a collection of activities that an org. mast master to successfully carry out the essential work of a product line.		* A practice area is a body of work or a collection of activities that an org. mast master to successfully carry out the essential work of a product line.
		+
		+	* SW Engg KPA's to support Core Asset development activities and product development activities.
		+	* Technical Management KPA's and Org Mgmt KPA's to support management activities.

← Older revision		Revision as of 10:34, 13 April 2012
Line 101:		Line 101:
	* New relationships with customers and suppliers.		* New relationships with customers and suppliers.
	* Conformance to product line vision.		* Conformance to product line vision.
		+
		+	= Activities KPA's =
		+
		+	* Certain skills are required to support the three activity areas above.
		+	* A practice area is a body of work or a collection of activities that an org. mast master to successfully carry out the essential work of a product line.

← Older revision		Revision as of 18:48, 12 April 2012
Line 89:		Line 89:
	** New assets.		** New assets.
	** Product constraints.		** Product constraints.
		+
		+	== Management ==
		+
		+	* Commitment to effort essential.
		+	** Allocate sufficient resources.
		+	** Right allocation of resources/skills.
		+	** Funding may need higher level agreement as single product is unable to afford it.
		+	* Organisation of teams
		+	** Core asset developers
		+	** Product developers
		+	* New relationships with customers and suppliers.
		+	* Conformance to product line vision.

← Older revision		Revision as of 18:44, 12 April 2012
Line 65:		Line 65:

	== Core Asset Development ==		== Core Asset Development ==
		+
		+	* Inputs:
		+	** Product Constraints.
		+	** Styles, patterns and frameworks.
		+	** Production constraints.
		+	** Production strategy.
		+
		+	* Outputs:
		+	** Product line scope
		+	** Core assets
		+	** Production plan
		+
		+	== Product Development ==
		+
		+	* Inputs:
		+	** Product requirements
		+	** Product line scope - Does the product fit within the scope ?
		+	** Core assets
		+	** Production plan - How the core assets are to be used to build the product.
		+
		+	* Outputs:
		+	** Products.
		+	** New assets.
		+	** Product constraints.