Product Line Engineering and Management

Question 1

Significance of Technical Management

Significance of Product Line Engineering

Answer 1

1. Technical Mgt provides Mgt support for a timely and proper deployment of PL in balance with pre-defined PL objectives such as resusability, cost, improving Q etc. as well as its planned cost, schedule and resources. Formulate a strategy for the successful implementation of a PL
2. Establish and manage Vy; reduce costs and Pd complexity; increase productivity and product Q through strategic, prescribed creation and use of Dn assets; shorten time to market; and increase customer satisfaction through mass-customization of Pds and more accurate estimation of schedules and costs

Note: (a) PL engg has to take explicitly into account multiple Pds and the variations within & b/n them.

(b) Most Vy needs should be based on the careful analysis of target markets, available technologies, offerings of competitors, and other factors

Question 2

Definitions:

1. Domain Engineering
2. Application Engineering
3. Application design

Answer 2

1. LC consisting of a set of processes for specifying and Mging the C&V of a PL
2. LC consisting of a set of processes in which the Appn assets and MPs of the PL are implemented and Mged by reusing Dn assets in conformance to the Dn Arx and by binding the Vy of the platform
3. Process of Appn engg where a single Appn Arx conforming to the Dn Arx is derived

Question 3

Definitions:

1. Domain asset
2. Application asset

Answer 3

1. O/p of Dn engg LC processes and can be reused in producing products during Appn engg.

Note: Dn assets may include Dn features, Dn models, Dn reqts specification, Dn Arx, Dn components, Dn test cases, Dn process description, and etc.

Note: Dn assets need to support mass-customization of multiple Apps within the PL

2. O/pof a specific Appn engg processes

Question 4

Definitions:

1. Product line
2. Product Line Platform

Answer 4

1. Set of Pds and/or services sharing explicitly defined and Mged common and variable features and relying on the same Dn Arx to meet the common and variable needs of specific markets
2. Consists of PL Arx, a configuration Mgt plan, and Dn assets enabling Appn engg to effectively reuse and produce a set of derivative Pds.

Note: Platforms are of strategic importance for PL orgzs. The introduction and elimination of entire platforms influence PL orgzs significantly.

Question 5

Definitions:

1. Product line scoping
2. Product scoping

Answer 5

1. Defines the MPs that will be produced within a PL and the major (externally visible) common and variable features among the Pds, analyzes the Pds from an economic point of view, and controls and schedules the development, production, and marketing of the PL and its Pds

Note: Pd Mgt is primarily responsible for PL scoping.

2. Subprocess of PL scoping that determines the Pd roadmap, that is
   1) the targeted markets;
   2) the Pd categories that the PL organization should be developing, producing, marketing, and selling;
   3) the common and variable features that the Pds should provide in order to reach the long and short term business objectives of the PL organization, and
   4) the schedule for introducing Pds to markets

Question 6

Definitions:

1. Domain scoping
2. Asset scoping
3. Asset Base

Answer 6

1. Identifies and bounds the functional Dns that are imp to an envisioned PL and provide sufficient reuse potential to justify the PL creation
2. Process of identifying the potential Dn assets and estimating the ROI in the assets
3. Stores reusable assets produced from both Dn and Appn engg

Question 7

Definitions:

1. Feature
2. Commonality
3. Variability

Answer 7

1. Abstract fnal characteristic of a system that end-users and other stakeholders can understand
2. Set of fnal and non-fnal characteristics that is shared by all Apps belonging to the PL
3. ‹PL› characteristics that may differ among members of the PL.

Note: The differences b/n members may be captured from multiple viewpts such as fnality, Q attributes. Vyes can be Mged orthogonally in order to avoid complexity of a PL. Therefore, the modeling and evolution of Vyes and their traceabilities with Dn/Appn assets must be enged systematically balancing with its cost, effectiveness, and supported over the PL cycle.

Vy must be defined, modeled, implemented, versioned, verified and validated.

Question 8

Definitions:

1. Variation Point
2. Variant

Answer 8

1. Representation corresponding to particular variable characteristics of Pds, Dn assets, and Appn assets in the context of a PL

Note: Variation pts show what of the PL varies. Each variation pt should have at least one variant.

2. One alternative that may be used to realize particular variation pts.

Note: One or more variants must correspond to each variation pt. Each variant has to be associated with one or more variation pts. Selection and binding of variants for a specific product determine the characteristics of the particular Vy for the Pd.

Question 9

Definitions:

1. Variability constraint
2. Variability dependency

Answer 9

1. Constraint relationships b/n a variant and a variation pt, b/n two variants, and b/n two variation pts
2. Relationship b/n a variation pt and a set of variants, which indicates that the variation pt implies a decision about the variants

Note: Two kinds of Vy dependencies are possible:

(1) the optional Vy dependency states that the variant optionally dependent on a variation pt can be a part of a MP of a PL
(2) the mandatory Vy dependency defines that a variant dependent on a variation pt must be selected for a MP if the variation pt is selected for the MP.

Question 10

Definitions:

1. Variability model
2. Variability mechanism

Answer 10

1. Defines product line variability

Note: It introduces variation pts, types of variation for the variation pts, variants offered by the variation pts, and Vy dependencies and Vy constraints. Vy models may be orthogonal to or integrated in other models such as reqts or design models. There are two types of Vy models: Appn Vy models and Dn Vy models.

2. Handles variants in a PL for supporting assembly of Dn assets

Question 11

Variability management

Answer 11

It has two dimensions:Vy dimension and asset dimension.

Vy Mgt in the Vy dimension consists of tasks for overseeing Vy in the level of the entire PL, creating and maintaining Vy models, ensuring consistencies b/n Vy models, Mging all Vy and constraint dependencies across the PL, and Mging the traceability links b/n a Vy model and associated Dn and Appn assets (e.g., reqts models, design models).

Vy Mgt in the asset dimension consists of tasks for Mging the impacts of Vy within each Dn and Appn asset, that is, in which location of an asset a particular Vy occurs and which alternative shapes the asset can take in that location. The dimensions are complementary in nature, that is, both are needed for successful variability Mgt.

Question 12

Binding

Answer 12

Task to make a decision on relevant variants, which will be Appn assets, from Dn assets using the Dn Vy model and from Appn assets using the Appn Vy model.

Note: Performing the binding is a task to apply the binding definition to generate new Appn assets from Dn and Appn assets using the Dn and Appn Vy models.

Binding should be considered during Dn engg at a time when the variants are introduced as well as during and after Appn engg at the time when the variants are bound.

Static binding of Vy during Appn engg takes place before run time. Dynamic binding of Vy can be used during run time. It enables a system (1) to self-adapt their behaviors based on pre-specified rules and (2) to be adapted by their users (e.g., when they decide to bind additional variants to use enhanced features)

Question 13

Product Management Responsibilities:

Answer 13

It is responsible for the economic and business concerns of PL engg and Mgt and the resulting PL(s). It deals particularly with the market strategy and the competitive strategy.

PLs must evolve continuously in accordance with new innovative products and Appn assets that Pds within the PL can leverage, market changes, and new offerings from competitors.

Good practices for PL engg and Mgt include evolving a PL in iterative cycles, establishing clear objectives for each cycle, and reviewing performance after completing each cycle. Pd Mgt is responsible for these practices and for making appropriate adjustments to the Pd portfolio and the platform investments based on the review results.

Pd Mgt is needed in single-system engineering but it plays a more vital and powerful role in PL Engg.

Pd Mgt should have capability for defining and analyzing the measures that make it possible to evaluate designed reusability and productivity and thereafter coordinate a PL towards achieving its goals.

Question 14

Reusability

Answer 14

The reusability of Dn assets will be one of the critical success factors of PLs. Reusability requires strategic long-term focus on key Dns, so investments in developing Dn assets are feasible, and sound technological and Mgerial capabilities throughout the PL Engg and Mgt processes

Question 15

Steps in Domain Engineering Lifecycle

Answer 15

1. PL scoping:
   The major results of PL scoping are Pd roadmaps and asset proposals.

Each asset proposal includes a list of existing assets that could be used to derive Dn reqts and other Dn assets.

During the LC of the PL, PL scoping has to react to changes in customer needs, available technologies, competitors’ offerings, and in other market conditions. These changes necessitate adaptations of the Pd roadmaps and asset proposals such as the introduction of new features or the elimination of outdated MPs from the Pd portfolio.

PL scoping specifies which MPs should be derived in Appn reqts engg by prescribing which MP should possess which of the common and variable features.

2. Domain Requirements Engineering
3. Domain Design
4. Domain Realization
5. Domain Verification and Validation

Question 16

Explain sub-processes in “Product line Scoping

Answer 16

a. Product Scoping
b. Domain Scoping
c. Asset Scoping

Note: Refer to the above definitions

Question 17

Explain sub-processes in “Domain Requirements Engineering”

Answer 17

Purpose: Develops the common and variable reqts, produces its specifications and Dn Vy model, and provides feedback, if necessary, to the Pd Mgt about the changes required in the outcomes of PL scoping.

i. Domain Requirements Elicitation:
Reqts Elicitation of Single-System Engg, and Captures the scope and variations anticipated over the foreseeable lifetime of the PL explicitly through the use of appropriate techniques.

ii. Domain Requirements Analysis
Reqts analysis activities of single-system engg and to find commonalities and identify variations. Clarifies how a particular MP might achieve economic viability. A Dn Vy model is also structured.

iii. Domain Requirements Specification
Documents the analyzed PL reqts from which Appn reqts specification can select or adapt during Appn engg.

iv. Domain Requirements V&V

v. Domain Requirements Management
Plans, defines, and Mges the Dn reqts engg process and coordinates reqts engg activities PL-wide. Enacts a formal change Mgt mechanism for proposing changes in the base-lined Dn reqts. Traceability links maintained b/n Dn reqts and other assets.

Question 18

Explain sub-processes in “Domain Realization”

Answer 18

Purpose: It deals with the detailed design and implementation of common & variable domain assets

i. Identification, evaluation, selection, and integration of COTS components:
It can dramatically speed up Dn realization, lower the costs, and improve the Q of the platform as a whole.

ii.Interface realization:
Includes the internal design and coding of the interfaces of common and variable compts to ensure the interfaces expose appropriate info related to C&V. The level of interface details for the provided compts and required compts should be reviewed.

iii. Component realization:
Compts are the units used to compose whole MPs, as described by the ref Arx.

iv. V&V of domain realization

v. Domain realization management:
Systematically controls the changes and maintains the integrity and traceability of the compts and interfaces throughout the PL LC.

The diff b/n Dn realization and the realization of a single system is that the reusable compts of Dn realization are loosely coupled and configurable, and do not constitute an executable, testable artifact. In addition, Dn realization includes configuration mechanisms to realize the Vy.

Question 19

Explain sub-processes in “Domain Requirements Engineering”

Answer 19

Purpose: Develops the common and variable reqts, produces its specifications and Dn Vy model, and provides fb, if necessary, to the Pd Mgt about the changes required in the outcomes of PL scoping.

i. Domain Requirements Elicitation:
Reqts Elicitation of Single-System Engg, and Captures the scope and variations anticipated over the foreseeable lifetime of the PL explicitly through the use of appropriate techniques.

ii. Domain Requirements Analysis
Reqts analysis activities of single-system engg and to find commonalities and identify variations. Clarifies how a particular MP might achieve economic viability. A Dn Vy model is also structured.

iii. Domain Requirements Specification
Documents the analyzed PL reqts from which Appn reqts specification can select or adapt during Appn engg.

iv. Domain Requirements V&V

v. Domain Requirements Management
Plans, defines, and Mges the Dn reqts engg process and coordinates reqts engg activities PL-wide. Enacts a formal change Mgt mechanism for proposing changes in the base-lined Dn reqts. Traceability links maintained b/n Dn reqts and other assets.

Question 20

Explain sub-processes in “Domain Verification and Validation”

Answer 20

Purpose: Ensure the right Dn assets have been modeled, specified, designed, built, verified, and tested in the right way as prescribed in previous Dn LC processes.

a. Domain test planning:
Documents the scope, strategy, resources, and schedule of Dn V&V activities.

b. Domain test design:
Specifies Dn test procedures, test cases, test data, and test environments considering Vy involved in Dn assets.

c. Domain test execution

d. Domain test closure and report:
The tests not covered by Dn test execution are the responsibility of Appn V&V. Test cases performed in Dn V&V typically have to be repeated in Appn V&V

e. Domain test management:
keeps track of Dn V&V assets

Question 21

Definitions:

1. Domain architecture
2. Application Architecture

Answer 21

Reference Arx including the Arxal structure and texture (e.g. common rules and constraints) that constrains all MPs within a PL.

2. Arx including the Arxal structure and rules (e.g. common rules and constraints) that constrains a specific MP within a PL.The Appn Arx captures the high-level design of a specific MP of a PL

Question 22

Steps in Application Engineering Lifecycle

Answer 22

Appn engg develops Appn assets and individual systems on top of a platform. Appn engg is effective and efficient in comparison to single-system engg because, depending on the scope and maturity of the platform, much or even most of the PL engg effort and complexity have been allocated to Dn engg, reducing Appn complexity and shortening Appn development times. Appn engg typically involves customers and thus needs to deal with evolving market needs.

Steps:

1. Application Requirements Engineering
2. Application Design
3. Application Realization
4. Application Verification and Validation

Question 23

Explain sub-processes in “Application Requirements Engineering”

Answer 23

Purpose: Develops Appn-specific reqts reusing common and variable reqts defined during Dn reqs engg. It also has an imp role in providing insights and fb to Dn reqts engg in order to guide platform development especially in the early phases of the PL creation. It typically involves trade-off decisions with regard to the reqts posed by customers. Reqts deltas such as performance reqts that are tighter than anticipated by the PL engineers may involve significant modifications of the Dn Arx and the reusable coms. Modifications affect the Appn development costs and it is necessary to decide whether to accept higher prices and/or longer schedules or to abstain from costly reqts.

(i) Application requirements elicitation:
Elicits initial reqts, uses the variation pts and variants to communicate to the stakeholders, lets the stakeholders select the variants that best meet their needs, and binds the appropriate Dn reqs of the PL based on the selections.

(ii) Application requirements analysis:
Ensures that all initial reqs of the Appn stakeholders are understood and scrutinized for incorrectness, omissions, and inconsistencies through abstracting, modeling, prototyping, simulation, and etc. The gap b/n Dn and Appn reqts, are then analyzed and negotiated.

(iii) Application requirements specification Documents the analyzed Appn reqts by adding the Appn-specific reqts to the specification of the selected, possibly adapted, and bound Dn reqts.

(iv) Application requirements V&V:
Confirm that the Appn-specific reqts are complete, correct, consistent, and unambiguous and that the bound variants are relevant to the specific Pd reqts.

(v) Application requirements managemen:
Plans, defines, Mges, and coordinates the Appn reqts engg process and baselines the Appn reqts.

Question 24

Explain sub-processes in “Application Design”

Answer 24

Purpose: Appn design derives an Appn Arx from the ref Arx in order to meet Appn reqts. Pd specific adaptations shall be done to satisfy pdspecific reqts. The Appn Arx should adhere to the structure and texture of the ref Arx.

(i) Binding variants of the domain architecture:
Responsibility of the Appn architect to establish a baseline for the Appn Arx. Variants for the variation pts of the Dn Arx must be bound according to the Appn Vy model and the binding results from Appn reqts engg.

(ii) Application specific architecture design:
Appn Arx is a combination of the Appn design assets and the bound ref Arx.

(iii) Application architecture V&V:
Check that the Vy introduced during Appn design is feasible, appropriately documented in the Appn Vy model, and can be bound correctly. The Appn Arx is also evaluated from the viewpts of Appn-specific Q attributes.

(iv) Application architecture management:
Mges and maintains the Appn Arx and the associated Appn assets throughout theLC of the MP. The major tasks for Mging the Appn Arx can be divided into 3 groups: configuration Mgtt, change Mgt, and traceability Mgt.

Question 25

Explain sub-processes in “Application realization”

Answer 25

Purpose: Implements the Pd by drawing upon the Appn reqts and Arx; reusing and configuring Dn compts and interfaces

(i) Binding component-level variability:
Internal variation pts of Dn compts are bound. Interfaces realized in Dn realization should be reused without changes. Otherwise, the texture of the Dn Arx is likely to be broken and the strategic reuse of Dn assets is hampered.

(ii) Identification, evaluation, selection, and integration of COTS components

(iii) Application specific interface realization:
Includes the internal design and coding of the interfaces of Appn-specific components.

(iv) The V&V of application realization assets:
Review both Dn realization assets associated with the bound variants and Appn compts and interfaces to see whether the bound variants and implemented compts and interfaces conform to the App Arx and obey the confgn mechanism(s) and Arxal texture.

(v) Application realization management:
Defines, schedules, and coordinates the Appn realization process and systematically controls changes and maintains the integrity and traceability of Appn compts and interfaces throughout the Appn life cycle

Question 26

Explain sub-processes in “Application Verification & Validation”

Answer 26

Purpose: Appn V&V ensure the right MP and the right Appn assets have been modeled, specified, designed, built, verified, and validated right. They draw upon Dn V&V assets and create Appn V&V assets to ensure sufficient quality of the MP.

(i) Application test planning
(ii) Application test design
(iii) Application test execution
(iv) Application test closure and reporting
(v) Application test Mgt

Question 27

Organizational management process group

Answer 27

Orgzal Mgt processes are necessary for the orchestration of the PL organization. Introduction and institutionalization of the PL strategy in an organization requires ongoing preparation, planning, execution, and improvement efforts.

It has following subprocesses:

1. Organizational-level PL planning
2. Organizational PL-enabling Mgt
3. Organizational PL Mgt

Question 28

Explain “Organizational-level product line planning”

Answer 28

Purpose: Pertains to strategic orgznal-level planning. It involves various types of plans such as PL adoption plans, sourcing plans, and domain asset investment plans.

Note: One of its most important responsibilities is to make the go/no-go decision regarding the adoption of the PL strategy by analyzing the benefits to be gained and the efforts and investments required.

Based on the previous info, orgznal business Mgt should establish business value targets to achieve by introducing the PL approach. Thereafter it should check whether the business value targets have been measurably achieved. If they have not been achieved, the orgzn must take necessary corrective actions.

Activities involved:
(A) Business opportunity analysis
(B) Customer relationship management
(C) Developing a sourcing strategy
(D) Organizational transition planning
(E) Organizational PL evolution planning
(F) Value management planning

Question 29

Activities involved in “Organizational-level product line planning” - Part 1.

Answer 29

(A) Business opportunity analysis:
Serves as decision aids to determine 1) whether to initiate a PL approach, and 2) whether to include a particular Pd as a member of an existing PL. This includes the cost/benefit estimation and business value analysis.

Key Point: For successful business opportunity analysis, establishing a collaborative atmosphere among representatives from top Mgt, marketing, Pd Mgt, engg, and the customer relationship Mgt and user groups is essential. Markets have to be analyzed to make the initial adoption decision and to guide the evolution of the PL and the introduction of new Pds into the PL on an ongoing basis. Business opportunity analysis also needs to determine the magnitude of investments required to establish and operate the Dn asset base.

Question 30

Activities involved in “Organizational-level product line planning” - Part 2

Answer 30

(B) Customer relationship management:
Refers to the exchange of info and other resources b/n designated representatives of the PL orgzn (e.g., marketing, a Pd Mger, domain experts, a user group coordinator) and one or more particular interest groups of the customer (e.g., legal, financial or technical entities, operations, training)

Mging the customer relationship also requires that a PL organization coordinates customer reqts with those of the PL and realizes the changes required by the customers as necessary. Especially in business to business settings PL orgzns and their customers should aim at establishing and maintaining mutually beneficial long-term relationships.

Question 31

Activities involved in “Organizational-level product line planning” - Part 3

Answer 31

(C) Developing a sourcing strategy:
Serves to establish an actionable plan for achieving specific PL goals and outcomes through contracting for Pds and services. Sourcing helps obtain new Dn assets and incorporate new Pds in the PL.

Question 32

Activities involved in “Organizational-level product line planning” - Part 4,5,6

Answer 32

(D) Organizational transition planning:
Establishes an orgznal capability to populate and nurture a PL. It plans for the initiation of the PL and specifies resources and schedules such as the orgzn, the people, and the budget needed to establish and Mg the PL. It also defines target goals to be achieved by adopting a PL approach.

(E) Organizational product line evolution planning: Defines how the Dn and Appn engg processes will be continuously evolved to leverage the effectiveness and efficiency of the PL.

(F) Value management planning:
Provides integrated measurement schemes for the effectiveness of transition plans and operation plans. The target business values defined in the business opportunities and their goals that should be achieved are planned.

Question 33

Explain “Organizational product line-enabling management”

Answer 33

Purpose: It plans for the initiation and evolution of the PL and designs the orgznal processes, the structure of authority and responsibilities, and the infrastructure needed to establish and Mg the PL.

(A) Structuring the PL orgzn
(B) Training and human resource gt
(C) Orgznal quality management

Question 34

Explain “Organizational product line management”

Answer 34

Purpose: It initiates the orgznal transitioning toward PL engg. It is concerned with the systematic evolution of both the PL organization and the PL from the as-is state toward the desired state.

(A) PL evolution Mgt
(B) Deployment and innovation Mgt
(C) Operations Mgt
(D) Orgznal risk Mgt
(E) Orgzn-level monitoring and control

Question 35

Activities involved in “Organizational product line management” - Part 1,2.

Answer 35

(A) PL evolution Mgt:
Periodically analyzes the status and changing trends of customer needs, key competitors, technology, and other market environments. PLs should be evolved to cope with these changes through evolving PL platform and/or aligning MPs.

(B) Deployment and innovation Mgt:
Facilitate the successful implementation of the PL approach through effective assessment, improvement, and activation of the PL plans. Pilot projects may be conducted to evaluate the capability and readiness of a PL orgizn before the PL approach is broadly deployed. The orgzn should V&V whether it can achieve its objectives through the PL strategy.

Question 36

Activities involved in “Organizational product line management” - Part 3

Answer 36

(C) Operations Mgt:
Typically designs, measures, and monitors how particular orgzal units produce and evolve Dn assets, define and evolve the production plans, and use the Dn assets and the production plans to establish Pds. The key measures should help to track the progress and deliverables of PL efforts and take corrective actions as necessary to achieve orgznal business value targets.

Question 37

Activities involved in “Organizational product line management” - Part 4,5

Answer 37

(D) Organizational risk management

(E) Organization-level monitoring and control:
Measures the actual progresses and results accomplished by introducing and evolving the PL approach. The key measures for the PL orgzn should be focused on the defined business values and their measurable goals.

Question 38

Technical Management

Answer 38

Technical Mgt is necessary for the creation and evolution of PL processes, Dn assets, and Pds. It consists of:
(A) Process Mgt
(B) Vy Mgt
(C) Asset Mgt, and 
(D) Support Mgt.

Monitors and control whether the desired level of reusability is achieved in a PL.

Question 39

Explain “Variability management”

Answer 39

PL Vy defines how MPs are differentiated from each other. Vy Mgt requires explicit documentation of Vy through Dn and Appn Vy modeling.

(i) Vy model Mgt
(ii) Vy binding Mgt
(iii) Vy documentation Mgt
(iv) Vy tracing
(v) Vy control and evolution

Question 40

Activities involved in “Variability management” - Part 1.

Answer 40

(i) Variability model management:
Supports the development of detailed Vy models using Vy related info from Dn and Appn engg. It supports Vy modeling using consistent notations. Dn engg typically provides most of the Vy info necessary for structuring the Dn Vy model. The model is refined and Mged throughout the Dn Engg LC. However, Appn Engg provides Vy info as well because each MP may offer plenty of Vy. This info is documented in an Appn Vy model. This model is also refined throughout the Appn engg LC.

Note: The levels of detail of Vy info differ depending on the process (e.g., Appn reqts engg) where the info is produced.

Question 41

Activities involved in “Variability management” - Part 2.

Answer 41

(ii) Variability binding management:
Supports the consistent exploitation of Vy during Appn Engg, facilitating proactive and correct reuse of Dn assets. It maintains info that Dn and Appn engineers as well as automated tools need to resolve Vy appropriately; Vy binding helps maintain MPs as it documents precisely which Vy has been bound and how in a particular MP.

Question 42

Activities involved in “Variability management” - Part 3.

Answer 42

(iii) Variability documentation management:
Supports stakeholders to document Vy models in detail with annotations. Annotations may provide justifications for providing certain Vy while omitting some other Vy from the Dn assets, supporting the reuse of Dn assets across the MPs of a PL. The annotations for the Dn Vy model should help make binding decisions. The annotations for the Appn Vy model are expected to provide the rationale of the binding results and newly added variation points, variants, dependencies, and constraints for the specific MP.

Question 43

Activities involved in “Variability management” - Part 4,5.

Answer 43

(iv) Variability tracing:
Enables the establishment and maintenance of traceability links b/n elements of the Vy models and the associated Dn and Appn assets. An economic analysis of the costs and benefits from traceability links should be conducted to decide on the appropriate level of detail for traceability Mgt.

Note: Having too much or too little traceability is costly.

(v) Variability control and evolution:
Manages the different versions of Vy models and associated traceability links stored in the asset base. It also deals with the change requests related to Vy models, so the PL Vy can be Mged as a strategic orgznal resource.

Question 44

Explain “Asset Management”

Answer 44

Asset Mgt is responsible for storing, mining, and Mging Dn assets and Appn assets. It controls the platform and other assets, including the the annotations necessary to reuse Dn assets (e.g., glues, processes, and their descriptions that are attached to Dn assets and prescribe how to use the assets), change requests and fb, traceability links, and the versions of Dn and Appn assets after they have been baselined.

(i) Asset identification
(ii) Asset base implementation
(iii) Asset verification
(iv) Asset evolution

Question 45

Explain “Support Management”

Answer 45

(i)Technical Q management:
Ensure that work Pds and processes comply with the predefined provisions and plans.

(ii) Configuration management

(iii) Decision management:
Helps to choose the most beneficial option(s) among business or technical decision alternatives. The strengths and weaknesses implied by each alternative should be considered during decision making to choose the best option(s).

(iv) Technical risk management:
Addresses technical risk issues that could endanger the achievement of targeted business values and other PL objectives. Severe technical risks (e.g., lack of domain knowledge, uncertain or volatile Dn reqts, lack of historical data for effort estimation, etc.) are likely to materialize without adequate technical risk Mgt, so PL orgzns must develop mitigation and/or contingency plans to cope with those risks.

(iv) Tool Mgt

Question 46

What are the System-level assets

Answer 46

Mission and stakeholder needs and reqts
Use cases
Environmental descriptions
Context descriptions
Architectural data
Behavioral partitioning & allocation
Design justifications
System-level simulations

Question 47

Define “Product Roadmap”

Answer 47

Defines Pds that will be included within a PL and their major assets (e.g., high-level common and variable features) with their quantified costs and estimated benefits. A product roadmap may define a schedule for delivering specific MPs to customers or for bringing them to market. The schedule is the result of strategic reasoning and effort estimation performed jointly by the PL and/or Pd Mgers.