CPN CPE Software Engineering study guide
CPN CPE Software Engineering · Work through your exam, one topic at a time.
The CPN CPE Software Engineering credential is a professional certification aimed at engineers who build software for nanotechnology-enabled systems, instruments, and analysis pipelines. It suits practitioners who already write code but need to demonstrate that they can do so under the discipline expected in a regulated, safety- and measurement-sensitive domain: traceable requirements, defensible architecture, verification evidence, and controlled change. The CPN CPE Software Engineering study guide has 9 sections and about 2,457 words.
01Software Requirements and Specification
This domain tests requirements engineering: elicitation, analysis, specification, validation, and management. Expect questions on functional versus non-functional requirements, specification quality characteristics, use cases, user stories with acceptance criteria, and bidirectional traceability.
276 words, about 1 min02Software Design and Architecture
This domain tests architectural structures, design principles, patterns, and quality-attribute tradeoffs. Expect questions on architectural styles, views, coupling and cohesion, SOLID and GRASP, design patterns, and architecture evaluation.
278 words, about 1 min03Software Construction and Implementation
This domain tests coding practices that turn designs into reliable software: standards, code review, defensive programming, error handling, concurrency, refactoring, static analysis, builds, and continuous integration. Prefer clear, consistent code over clever code; follow team standards for naming, formatting, and structure.
274 words, about 1 min04Software Testing and Verification
This domain tests test levels, techniques, coverage, and the distinction between verification and validation. Expect equivalence partitioning, boundary value analysis, decision tables, state transition testing, structural coverage, and regression testing.
274 words, about 1 min05Software Maintenance and Evolution
This domain tests maintenance categories, legacy-system evolution, impact analysis, refactoring, reengineering, and regression control. Expect questions on corrective, adaptive, perfective, and preventive maintenance, plus technical debt and Lehman’s laws.
260 words, about 1 min06Software Configuration and Quality Management
This domain tests configuration management, change control, baselines, audits, and quality management. Expect questions on configuration items, version control, change control boards, status accounting, and the distinction between quality assurance and quality control.
265 words, about 1 min07Software Project Management and Engineering Economics
This domain tests planning, estimation, scheduling, risk, and economic decisions. Expect work breakdown structures, critical path, PERT, COCOMO II, function points, earned value management, and make-or-buy or net present value reasoning.
291 words, about 1 min08Software Engineering Process and Lifecycle Models
This domain tests lifecycle models and process improvement. Expect waterfall, V-model, incremental, spiral, agile Scrum, Kanban, DevOps, and process maturity concepts.
264 words, about 1 min09Software Engineering Methods, Tools, and Security
This domain tests methods, tooling, and secure engineering. Expect model-driven and formal methods, prototyping, CI/CD, static and dynamic analysis, software composition analysis, threat modeling, and secure design principles.
275 words, about 1 min