Reference
|
|
k,c,a
|
E,D
|
Hours
|
PRO
|
Software process
|
|
|
33
|
PRO.con
|
Process concepts
|
|
|
3
|
PRO.con.1
|
Themes and terminology
|
k
|
E
|
|
PRO.con.2
|
Software engineering process infrastructure (e.g., personnel, tools, and training)
|
k
|
E
|
|
PRO.con.3
|
Modeling and specification of software processes
|
c
|
E
|
|
PRO.con.4
|
Measurement and analysis of software processes
|
c
|
E
|
|
PRO.con.5
|
Software engineering process improvement (individual, team, and organization)
|
c
|
E
|
|
PRO.con.6
|
Quality analysis and control (e.g., defect prevention, review processes, quality metrics, and root cause analysis of critical defects to improve processes and practices)
|
c
|
E
|
|
PRO.con.7
|
Systems engineering life-cycle models
|
|
D
|
|
PRO.imp
|
Process implementation
|
|
|
8
|
PRO.imp.1
|
Levels of process definition (e.g., organization, project, team, and individual)
|
k
|
E
|
|
PRO.imp.2
|
Life-cycle model characteristics (e.g., plan-based, incremental, iterative, and agile)
|
c
|
E
|
|
PRO.imp.3
|
Individual software process (model, definition, measurement, analysis, and improvement)
|
a
|
E
|
|
PRO.imp.4
|
Team process (model, definition, organization, measurement, analysis, and improvement)
|
a
|
E
|
|
PRO.imp.5
|
Software process implementation in the context of systems engineering
|
k
|
E
|
|
PRO.imp.6
|
Process tailoring
|
k
|
E
|
|
PRO.imp.7
|
Effect of external factors (e.g., contract and legal requirements, standards, and acquisition practices) on software process
|
k
|
E
|
|
PRO.pp
|
Project planning and tracking
|
|
|
8
|
PRO.pp.1
|
Requirements management (e.g., product backlog, priorities, dependencies, and changes)
|
a
|
E
|
|
PRO.pp.2
|
Effort estimation (e.g., use of historical data and consensus-based estimation techniques)
|
a
|
E
|
|
PRO.pp.3
|
Work breakdown and task scheduling
|
a
|
E
|
|
PRO.pp.4
|
Resource allocation
|
c
|
E
|
|
PRO.pp.5
|
Risk management (e.g., identification, mitigation, remediation, and status tracking)
|
a
|
E
|
|
PRO.pp.6
|
Project tracking metrics and techniques (e.g., earned value, velocity, burndown charts, defect tracking, and management of technical debt)
|
a
|
E
|
|
PRO.pp.7
|
Team self-management (e.g., progress tracking, dynamic workload allocation, and response to emergent issues)
|
a
|
E
|
|
PRO.cm
|
Software configuration management
|
|
|
6
|
PRO.cm.1
|
Revision control
|
a
|
E
|
|
PRO.cm.2
|
Release management
|
c
|
E
|
|
PRO.cm.3
|
Configuration management tools
|
c
|
E
|
|
PRO.cm.4
|
Build processes and tools, including automated testing and continuous integration
|
a
|
E
|
|
PRO.cm.5
|
Software configuration management processes
|
k
|
E
|
|
PRO.cm.6
|
Maintenance issues
|
k
|
E
|
|
PRO.cm.7
|
Distribution and backup
|
|
D
|
|
PRO.evo
|
Evolution processes and activities
|
|
|
8
|
PRO.evo.1
|
Basic concepts of evolution and maintenance
|
k
|
E
|
|
PRO.evo.2
|
Working with legacy systems
|
k
|
E
|
|
PRO.evo.3
|
Refactoring
|
c
|
E
|
|