Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
31 Cards in this Set
- Front
- Back
|
Categories of Process Improvement |
Increased budget and schedule predictability increased quality decreased cost of quality return on investment employee morale improved cycle time customer satisfaction productivity increase |
|
|
CMM? |
Reference model of mature practices in a specified discipline use to assess a group's capability to perform |
|
|
CMM Differences |
Discipline strict with software structure staged hota hay instead of continuous maturity is defined as process improvement path capaibility is defined as institutionalization |
|
|
CMM-SW? |
how to gain control on processes of development and maintenance Selection of process improvement strategies how to evolve towards culture of software engineering and management excellence |
|
|
8 slide do it now |
common sense |
|
|
software capability |
range of results that can be achieved using a software process |
|
|
software process performance |
results achieved by following a software process |
|
|
software process maturity |
extent to which software process is defined, managed, measured, controlled and is effective |
|
|
levels of software process |
Initial repeatable defined managed optimizing |
|
|
Initial? |
Unstable dev, lack of committment and reachable goals, complete success: complete projects over budget and schedule |
|
|
Repeatable? |
establishment of policies experience with projects comes in management practices and control tracking cost,schedule , functionality and requirements success can be repeated because planning and tracking of software project is stable |
|
|
defined |
standard processes are defined and documented accross the organization and integrated into standard of software process. Software capability are standard and consistent because both software engineering and management activities are stable and repeatable |
|
|
Managed |
Quantitative quality goals productivity and quality is measured projects achieve control by making narrowing variation in process performance |
|
|
Perfomance measures? |
unit with quanitity. number gives magintude and quanity meaning could be 1-D i.e time, errors, number of CPR certifications the can show variations in process or deviation from design |
|
|
example measures? |
frequency of defects -> defects per month cost per defect report defect report closure = NLD/ODR+NDR -> NLD is no. of lost days within specified time for all open and new defect reports ODR: no of opendefects reports within specified time NDR: no. of new defect reports within specified time |
|
|
Optimizing? |
continuous process improvement innovation effectiveness data of new technologies waste is unaceptable analyse defects to determine cause |
|
|
Effect of Maturity increase? |
difference between target results and actual results decreases accross projects Variability of actual results around targeted results decreases Targeted results improve |
|
|
optimizing key process areas |
Process change management technology change management defect prevention |
|
|
Managed key process areas |
Software Quality management Quantitative process management |
|
|
Defined key areas |
Peer reviews intergroup coordination integrated software management org process definition org process focus training program |
|
|
Repeatable key areas |
Software configuration managment quality assurance subcontract management requirement management software project planning software project tracking and oversight |
|
|
Common Features |
Comittment to perform (mgt sponsorship) Ability to perform Activities performed Measurement and Analysis Verifying Implementation |
|
|
CMMI Advantages |
Integrates systems and software disciplines into one process improvement provides a framework for introducing new disciplines as needs arise |
|
|
Advantages for CMMI in enterprise |
Provides improvement in multiple functional areas supports process integration and product improvement integrates multiple disciplines into one process improvement framework provides framework for introducing new disciplines as needs arise |
|
|
CMMI process areas? |
Process Management Project Management Engineering Support |
|
|
Relation between Capability and Organization maturity |
maturity-> staged representation capability-> continuous representation maturity pertains to set of process areas across an organization capability pertains to set of processes relating to a single process area or practice |
|
|
Advantages of staged and continuous? |
staged-> road map for implementing groups of process areas and sequencing of implementation continuous-> provides maximum flexibility for focusing on specific process areas according to business goals and objectives |
|
|
Conceptual differences ISO and CMMI |
CMMI is process model and ISO is an audit standard CMMI is et of related best practices derived from industry while ISO lays down standards and confirms if the process of businesses conform to those standards |
|
|
Scope differences ISO and CMMI |
CMMI -> software intensive ISO-> adaptable to all form of manufacturing CMMI -> engineering and project management ISO-> generic in nature CMMI mandates generic and specific practices in 22 developed process and orgs can choose ISO is same for all |
|
|
Difference in Approach |
CMMI requires ingraining processes in business needs while ISO specifies conformance and remains oblivious as to whether such conformances is of strategic business value or not |
|
|
Implementation |
CMMI is more focused complex with business objectives. ISO is flexible, wider in scope and not directly lined to business objectives |
