Reuse of Know-how and the Quality Improvement Paradigm

Question 1

Reuse of know-how

Answer 1

• Software models (products, processes, …) are build for different ways of reuse
• Context[model] ≠ Context[application]
• Software reuse
  
  • Use of existing software components to construct new
  • Applicable to all the intermediate work products in life-cycle
• Assumptions for reuse
  
  • Any kind of information, knowledge and experience can be reused
  • Reuse typically requires modification
  • Reuse requires careful planning and organization
  • Reuse typically requires up-front investment
  • Evaluation and measurement is required to decide about reuse
  • Reuse always has to be discussed in the context of the real processes and environment

Question 2

QIP

Answer 2

Quality Improvement Paradigm

• Is based on the fundamental ideas of:
  
  • Evolution based on learning feedback
  • Systematic reuse of know-how
  • Goal-orientation
• Can be applied to different tasks within software process improvement.

Question 3

1. Characterize

Answer 3

• Collect the information available about the project as a basis for the subsequent planning steps.
• Characterize the overall goals, products, processes, resources, qualities, time restrictions, etc.
• Identify objects that can be reused in the project.

Question 4

**2. Set Goals **

Answer 4

• On the basis of the initial characterization and of the overall goals, set quantifiable goals for successful project performance and project analysis
• The reasonable expectations are defined based upon the baseline provided by the characterization step.

Question 5

3. Choose Models

Answer 5

• On the basis of the characterization of the environment and of the goals that have been set, choose the appropriate processes for the project performance and supporting methods and tools, making sure that they are consistent with teh goals that have been set.

Question 6

4. Execute

Answer 6

• Perform the processes constructing the products and providing project feedback based upon the data on goal achievement that are being collected.

Question 7

5. Analyze

Answer 7

• At the end of the project, analyze the data and the information gathered to evaluate the current practices, determine problems, record findings, and make recommendations for future project improvements.

Question 8

6. Package

Answer 8

• Consolidate the experience gained in the form of new, or updated and refined models and other forms of structured knowledge gained from this and prior projects and store it in an experience base so it is available for future projects.

Question 9

Project-internal feedback loop

Answer 9

Feedback provided to the project during the execution phase in order to:

• Prevent and solve problems as they occur.
• Monitor and control the project.
• Realign chosen processes with defined goals.
• Change goals when they appear unrealistic.

Question 10

Organizational feedback loop

Answer 10

Feedback provided to the organization after completion of the project in order to:

• Analyze the conformance of the newly collected project data with the expected data
• Interpred deviations
• Capture experience, lessons learned
• Model and accumulate experience in a reusable form: software artifacts and process/product/quality models applicable to future projects.

Question 11

Strategic Level QIP

Answer 11

Characterize - Characterize organization and identify future trends

Set goals - Set-up improvement goals and hypotheses in measurable terms

Choose models - identify projects or pilots for investigating the hypotheses

Execute - Perform projects or pilots and collect data

Analyze - Analyze projects and pilots and evaluate hypotheses

Package - Package experiences for use in future projects.