PE Software study guide
PE Software · Work through your exam, one topic at a time.
The Principles and Practice of Engineering (PE) exam is NCEES's competency examination for a specific engineering discipline, and the Software exam is one of the more than 20 PE exams NCEES offers. It is designed for engineers who have gained a minimum of four years post-college work experience in their chosen engineering discipline, so it tests judgment built on practice rather than classroom recall alone. The PE Software study guide has 6 sections and about 2,611 words.
01Requirements Engineering
The exam probes whether you can tell a requirement from a design decision, and whether you can spot a statement that no test could ever pass or fail. Expect elicitation technique selection, requirement classification, specification quality attributes, traceability, and change control.
419 words, about 2 min02Software Design
Design questions ask whether you can decompose a system into modules that are cheap to change and test, and whether you can justify a structure against quality attributes rather than fashion. Expect architectural styles, modularity metrics, interface contracts, and information hiding.
415 words, about 2 min03Software Construction
Construction covers detailed design, coding, unit testing, integration, and the mechanics that turn a design into working, maintainable code. Expect defensive programming, complexity metrics, review effectiveness, refactoring discipline, and integration strategy.
464 words, about 2 min04Software Testing
Testing questions reward precision about levels, techniques, and coverage criteria, and punish the belief that testing can prove absence of defects. Expect black-box design methods, white-box coverage relationships, regression strategy, and defect clustering.
421 words, about 2 min05Configuration Management and Maintenance
This domain checks whether you can keep a changing product under control: identifying configuration items, controlling change, proving what shipped, and classifying maintenance work correctly. Expect baseline discipline, version control workflow, and the maintenance taxonomy.
442 words, about 2 min06Software Engineering Management, Process, and Quality
Management questions test estimation, scheduling, risk, earned value interpretation, and the distinction between process quality assurance and product-level testing. You are expected to compute performance indices and read them correctly.
450 words, about 2 min