Domain 8 Flashcards
SW-CMM
Software Capability Maturity Model
a 5 step model for measuring software development orgs
Level 1: Initial
No plan.
Level 2: Repeatable.
Basic lifecycle mgmt.
Level 3: Defined.
Formal, documented SW development processes.
Level 4: Managed.
Quantitative measures to gain detailed understanding.
Level 5: Optimizing. (CI/CD)
Continuous development process, w/ feedback loops.
CMMI
Capability Maturity Model Integration
5 steps Require peer reviews
Level 1: Initial
Unpredictable, poorly controlled, and REACTIVE
Level 2: Repeatable.
Characterized for PROJECTS and MANAGED
Level 3: Defined.
Characterized for ORGANIZATION and PROACTIVE
Level 4: Quantitatively Managed.
process QUANTITATIVELY measured and controlled
Level 5: Optimizing.
Focused on Continuous process improvement
IDEAL Model
Low to High maturity model for software model for software development which
implements many of the SW CMM attributes
Initiating. Business reasons outlined, support & infrastructure for initiative put in place.
Diagnosing. Engineers analyze current state of org & make recommendations for
Establishing. Org takes recommendations & develops plan to achieve those changes.
Acting. Plan put into action. Org develops solutions, tests, refines & implements
Learning. Org continuously analyzes efforts and results, proposes new actions to drive better results.
SDLC (steps)
Software Development Lifecycle
RDITE 5 steps
REQUIREMENTS ANALYSIS DESIGN IMPLEMENTATION TESTING EVOLUTION
Agile Model
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Waterfall Model
7-stage process that allows return
to previous stage for corrections
SYSTEM REQUIREMENTS SOFTWARE REQUIREMENTS PRELIMINARY DESIGN DETAILED DESIGN CODE AND DEBUG TESTING OPS & MAINTENANCE
Spiral model
lifecycle model that allows for multiple
iterations of a waterfall-style process.
known as a metamodel , or a “model of
models.”
each “loop” of the spiral results in the
development of a new system prototype
provides a solution to the major
criticism of the waterfall model:
it allows developers to return to the
planning stages as demands change