Process Improvement Flashcards
**(13) **The 1990’s “Bootstrap project” (Haase, Kuvaja, et al.), which uses the SEI’s maturity levels, had the goal of addressing a particular shortcoming of the SEI process maturity model. What specific shortcoming did it attempt to address?
It had the goal of extending and adapting the SEI maturity model to make it applicable across a wider range of companies (i.e., more applicable to companies that are NOT US defense contractors).
(13-SC)What, according to Sommerville, “is likely to be the most cost-effective process improvement strategy” for small to medium-sized projects
Adopting agile development practices.
Other Wrong ones:
- Using the GQM approach.
- Validating requirements to ensure that the resulting product will perform as intended in the user’s environment, using multiple techniques as appropriate.
- Performing causal analysis of selected defects and other problems and proposing actions to address them.
- Establishing and maintaining an organizational policy for planning and performing the project planning process.
- Employing a process management and maturity-based approach.
- Adopting plan-driven development practices.
(13,11,10,09-T/F-CMMI) The CMMI “Defined” level of maturity focuses on organizational standardization and deployment of processes. Each project has a managed process that is adapted to the project requirements. Process assets and process measurements must be collected and used for future process improvements.
TRUE
**(13,11,10,09-T/F-CMMI) ****CMMI assessments involve directly examining the processes employed during one randomly selected on-going project and rating these on a six-point scale
FALSE
(13,11,10,09-T/F-CMMI) “Institutionalization of good practice” requires introducing process control using statistical and other quantitative techniques, regardless of maturity level
FALSE
**(13,11,10,09-T/F-CMMI) **In contrast to the continuous model, the staged CMMI permits discretion and flexibility in improving specific process areas, while still allowing companies to work within the CMMI improvement framework
FALSE
**(13,11,10,09-T/F-CMMI) **The staged CMMI model is used to assess the processes employed in specific software development stages, while the continuous model is used to measure the maturity of an organization’s software processes as a continuous whole
FALSE
**(13,11,10,09-T/F-CMMI) **The staged CMMI model allows an organization’s process capability to be assessed and assigned a maturity level from 1 to 5.
TRUE
**(13,11,10,09-T/F-CMMI) **The result of a staged CMMI assessment is a capability profile showing each process area and its associated capability assessment
FALSE
(13,11,10,09-T/F-CMMI) Predecessors of the CMMI process improvement framework include the SEI’s Software CMM, the People CMM, and the Systems Engineering CMM
TRUE
(13,11,10,09-T/F-CMMI) A CMMI assessment involves examining software processes in an organization and rating them on a six-point scale that assigns a level of maturity to each process area.
TRUE
(13,11,10,09-T/F-CMMI) The CMMI model identifies recommended practces within a process area that may be used, but these are not obligatory
TRUE
(13,11,10,09-T/F-CMMI) CMMI generic goals and practices are associated with the institutionalization of good practice rather than being technical in nature
TRUE
(13,11,10,09-T/F-CMMI) *CMMI generic goals and practices are NOT technical but are associated with the institutionalization of good practice.
TRUE
**(13,11,10,09-T/F-CMMI) **The result of a continuous CMMI model assessment is a capability profile showing each process area and its associated process capability assessment.
TRUE
(13,11,10,09-T/F-CMMI) The continuous CMMI rates each process area and assigns a capability assessment level from 1 to 6 to each
TRUE
(13,11,10,09-T/F-CMMI) The CMMI identifies specific recommended practices that are associated with each of 24 process areas relevant to software process capability and improvement.
TRUE
(13,11,10,09-T/F-CMMI) The CMMI identifies specific obligatory practices that are associated with each of 24 process areas relevant to software process capability and improvement
FALSE
(13,11,09-SC) **two common measures of software product reliability are “mean time to system failure” and “probability of no system failure in a specified time interval”. Based on Sommerville’s definition of process reliability, which one of the following would be the most appropriate measure of this process attribute?
Probability that a process error can be avoided or trapped before it results in a product error
Other Wrong:
- Probability that the process can continue in spite of a process error
- Mean development time to the discovery of a process error
- Mean time required for the process to evolve in order to reflect changing organizational requirements or identified process improvements
- Probability of no process error in a specified development time interval
(12-QA)for small projects, where there are only a few team members, sophisticated development tools are particularly important, but that paradoxically, such tools are less important in large projects. Briefly summarize his explanation for this.
In large projects, team members spend a smaller proportion of their time in development activities (supported by development tools) and more time communicating (with one another) and understanding other parts of the system. Development tools, Sommerville argues, make no difference to this
(12, QA)examples of “software process attributes” that may be targets for improvement (understandability, standardization, visibility, measurability, supportability, acceptability, reliability, robustness, maintainability, and rapidity), but notes that it is not possible to make process improvements that optimize all process attributes simultaneously. To illustrate this point, he cites three specific examples of “inverse relationships” that exist among the ten attributes listed. Briefly describe and explain TWO of the THREE specific examples he cites
- rapidity vs. visibility: making a process visible requires the people involved to produce info about the process itself; this may slow down software production because of the time it takes to produce these documents.
- maintainability, standardization vs. acceptability: To make a process more maintainable, you may have to adopt procedures and tools that reflect broader organizational practice and that are used in different parts of the company; such standardization may conflict with non-standard procedures and tools introduced to support locally preferred ways of working. The result can be a reduction in process acceptability.
Understandability
Is the process explicitly defined and easy to understand?
Standardization
Is the process based on a standard generic process? Is the same process used in all parts of a company?
Visibility
Do process activities culminate in clear results and is the progress being made visible externally?