100+ Free PE Software Practice Questions

Pass your PE Software Engineering (Retired 2019) exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately

58-63% Pass Rate

100+ Questions

100% Free

1 / 10

Question 1

Score: 0/0

According to IEEE 830 / ISO/IEC/IEEE 29148, which characteristic of a 'good' software requirement means the requirement can be objectively evaluated against measurable criteria?

Unambiguous

Verifiable

Consistent

Traceable

to track

2026 Statistics

Key Facts: PE Software Exam

Retired

Status (April 2019)

NCEES

Historical Questions

NCEES

8 hrs

Historical Exam Time

NCEES

Knowledge Areas

SWEBOK-aligned

2013

First Administered

NCEES

58-63%

Historical Pass Rate

NCEES (first-time)

The PE Software Engineering exam was DISCONTINUED BY NCEES IN APRIL 2019 after roughly six years of availability (first administered in 2013) due to low candidate volume — fewer than 100 engineers took the exam each year toward the end of its run. No direct successor exam exists. Practice remains valuable because: (1) the content outline maps directly to SWEBOK v3, the canonical body of knowledge for software engineers; (2) a handful of state boards have historically explored reviving or accepting equivalent reviews for industrial exemption or software-track licensure; (3) the question set is excellent self-assessment for senior engineers and tech leads on requirements, design, testing, SCM, and engineering ethics. Candidates seeking current licensure should consult their state board about accepted alternatives such as the PE Electrical and Computer (Computer) or PE Industrial and Systems exams.

Sample PE Software Practice Questions

Try these sample questions to test your PE Software exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1According to IEEE 830 / ISO/IEC/IEEE 29148, which characteristic of a 'good' software requirement means the requirement can be objectively evaluated against measurable criteria?

A.Unambiguous

B.Verifiable

C.Consistent

D.Traceable

Explanation: A verifiable requirement has associated, objectively measurable acceptance criteria so that a tester, inspector, or analysis can determine whether the finished system satisfies it. IEEE 29148 lists verifiability as a core quality attribute of well-formed requirements.

2A team is eliciting requirements for a payroll system. Stakeholders include HR, finance, auditors, and end users. Which elicitation technique is MOST appropriate when the goal is to discover unstated assumptions by observing users in their natural work setting?

A.Structured interview

B.Ethnographic (contextual) observation

C.JAD (Joint Application Design) workshop

D.Requirements brainstorming

Explanation: Ethnographic or contextual observation places the analyst in the user's environment to capture tacit knowledge and workarounds that users rarely articulate in interviews or workshops. SWEBOK and the BABOK both list it as the primary technique for uncovering unstated assumptions.

3Which IEEE standard specifically addresses Software Requirements Specifications (SRS)?

A.IEEE 1012

B.IEEE 830 (superseded by ISO/IEC/IEEE 29148)

C.IEEE 828

D.IEEE 1028

Explanation: IEEE Std 830 — Recommended Practice for Software Requirements Specifications — was the canonical SRS standard. It was consolidated into ISO/IEC/IEEE 29148:2011/2018 (Requirements Engineering).

4A requirement states: 'The system shall respond quickly to user input.' What is the PRIMARY defect of this requirement?

A.It is not traceable

B.It is not verifiable because 'quickly' is not quantified

C.It is not consistent with other requirements

D.It duplicates another requirement

Explanation: The word 'quickly' has no measurable threshold, making the requirement unverifiable. A verifiable rewrite would state something like 'shall respond within 200 ms for 95% of user inputs under nominal load.'

5In requirements engineering, what is the PRIMARY purpose of a traceability matrix?

A.To list open defects

B.To link each requirement to its source and to downstream design, code, and test artifacts

C.To estimate project effort

D.To rank requirements by business value

Explanation: A requirements traceability matrix (RTM) maps each requirement backward to its source (stakeholder, regulation) and forward to design elements, code modules, and test cases. It supports impact analysis and verification coverage.

6Which requirements prioritization technique classifies items as Must have, Should have, Could have, and Won't have this time?

A.Kano model

B.MoSCoW

C.Hundred-dollar test

D.AHP (Analytic Hierarchy Process)

Explanation: MoSCoW is an acronym for Must, Should, Could, Won't (this time). It is a lightweight, widely-used prioritization method for backlog grooming.

7A requirements document contains both functional and non-functional requirements. Which is a NON-functional requirement?

A.The system shall send a confirmation email after every purchase

B.The system shall support 10,000 concurrent users with 99.9% availability

C.The system shall allow users to reset their password via email

D.The system shall accept credit card payments via Stripe

Explanation: Non-functional requirements (quality attributes) specify how well the system performs its functions — availability, scalability, security, usability. The 99.9% availability and 10,000-user load are quality constraints, not features.

8In use-case modeling, what does the <<include>> relationship represent?

A.An optional behavior that may be invoked

B.A mandatory sub-behavior that is always executed as part of the including use case

C.A specialization/generalization between actors

D.A precondition on a use case

Explanation: <<include>> indicates a base use case always executes the included use case. Contrast with <<extend>>, which is optional/conditional. In UML, <<include>> promotes reuse of common sub-behavior.

9A stakeholder provides a user story: 'As a customer, I want to save my cart so I can return later.' Which of the following is the BEST acceptance criterion for this story?

A.The code passes all unit tests

B.When the customer adds items and logs out, the same items are present in the cart on next login within 7 days

C.The developer implements the feature using Redis

D.The feature is delivered in sprint 5

Explanation: Acceptance criteria describe externally observable, testable behavior tied to the user's goal. The Given-When-Then formulation with a specific retention window is verifiable.

10Which of the following BEST describes 'requirements creep' (scope creep)?

A.Removing requirements as the project matures

B.Gradual, uncontrolled addition of requirements during development

C.Documenting requirements in natural language

D.Merging duplicate requirements

Explanation: Scope creep is the uncontrolled growth of requirements during a project without corresponding adjustment to schedule, cost, or resources. It is mitigated by formal change control.

About the PE Software Exam

The NCEES PE Software Engineering exam was an 8-hour, 80-question computer-based test for professional licensure of software engineers. NCEES discontinued the exam in April 2019 after persistently low candidate volume. The historical content outline covered seven knowledge areas aligned with the IEEE Software Engineering Body of Knowledge (SWEBOK): software requirements, software design, software construction, software testing, software maintenance, software configuration management, and quality/professional practice (including engineering ethics). This practice set preserves the historical content outline for retake candidates in jurisdictions that still honor it, engineers preparing for state-specific licensure reviews, and software professionals who want a rigorous SWEBOK-based self-assessment.

Questions

80 scored questions

Time Limit

8 hours

Passing Score

Approximately 70% (scaled, historical)

Exam Fee

Retired — historical $350 (NCEES (discontinued April 2019))

PE Software Exam Content Outline

17.5%

Software Requirements

Elicitation techniques, requirements analysis, SRS per IEEE 830/29148, validation, traceability, and requirements management

17.5%

Software Design

Architectural styles, GoF design patterns, UML diagrams, detailed design, quality attributes, coupling/cohesion

17.5%

Software Construction

Coding standards, defensive programming, code reviews, inspections, pair programming, construction tools

17.5%

Software Testing

Unit/integration/system/acceptance testing, black-box and white-box techniques, coverage, regression, performance

10%

Software Maintenance

Corrective, adaptive, perfective, preventive maintenance; impact analysis; reverse engineering; evolution

10%

Software Configuration Management

Version control, branching, baselines, release management, change control, CI/CD, configuration audits

10%

Quality and Professional Practice

SQA, CMMI, ISO/IEC 12207, NSPE and IEEE/ACM codes of ethics, professional responsibility

How to Pass the PE Software Exam

What You Need to Know

Passing score: Approximately 70% (scaled, historical)
Exam length: 80 questions
Time limit: 8 hours
Exam fee: Retired — historical $350

Keys to Passing

Complete 500+ practice questions
Score 80%+ consistently before scheduling
Focus on highest-weighted sections
Use our AI tutor for tough concepts

PE Software Study Tips from Top Performers

1Study the IEEE SWEBOK Guide v3 cover-to-cover — the historical content outline maps to its 15 knowledge areas

2Master design patterns (Gang of Four) and know when to apply creational, structural, and behavioral patterns

3Practice UML diagram interpretation: class, sequence, state, activity, and component diagrams

4Review IEEE standards: 830/29148 (SRS), 1012 (V&V), 828 (SCM plans), 829 (test documentation), 1028 (reviews)

5Memorize the NSPE Code of Ethics and the IEEE/ACM Software Engineering Code — professional-practice questions expect citation-level recall

Frequently Asked Questions

Is the PE Software Engineering exam still offered?

No. NCEES discontinued the PE Software Engineering exam in April 2019 due to persistently low candidate volume (fewer than 100 examinees per year at the end of its run). The exam was first administered in April 2013 and offered only six times. Engineers who already hold PE Software licensure retain it per their state board's rules, but no new candidates can sit for the exam through NCEES.

What replaced the PE Software exam?

Nothing officially replaced it. NCEES has not announced a successor exam. Software engineers seeking PE licensure today typically pursue adjacent NCEES exams such as the PE Electrical and Computer Engineering — Computer option, or the PE Industrial and Systems Engineering exam, depending on their work and state board acceptance. Some candidates also pursue non-NCEES credentials (IEEE CSDP/CSDA, ISTQB, PMI-ACP) for professional recognition.

Why did NCEES discontinue the PE Software exam?

NCEES cited insufficient examinee volume — the exam averaged fewer than 100 candidates per administration at the end. State boards did not require PE licensure for most software engineering roles, and software industry practice historically did not tie compensation or authority to a PE license. Without enough examinees to maintain item-development and psychometric standards, NCEES retired the exam in April 2019.

Is it worth practicing PE Software questions if the exam is retired?

Yes, for three reasons. First, the content outline maps directly to the IEEE Software Engineering Body of Knowledge (SWEBOK), which remains the canonical reference for software engineering fundamentals. Second, a small number of state boards have explored reviving software-track licensure or accepting equivalent reviews. Third, the question set is an excellent self-assessment tool for senior engineers, tech leads, and software architects on requirements, design, testing, SCM, and engineering ethics.

What topics did the PE Software exam cover?

The exam covered seven SWEBOK-aligned knowledge areas: Software Requirements (17.5%), Software Design (17.5%), Software Construction (17.5%), Software Testing (17.5%), Software Maintenance (10%), Software Configuration Management (10%), and Quality/Professional Practice (10%). Professional Practice included the NSPE Code of Ethics and IEEE/ACM Software Engineering Code of Ethics. Expect questions on SRS quality, UML, design patterns, coverage metrics, branching strategies, and CMMI.

What reference materials did candidates use for the PE Software exam?

NCEES provided the PE Software Engineering Reference Handbook as a searchable PDF during the exam. Candidates typically studied the IEEE SWEBOK Guide, IEEE standards (830 for SRS, 1012 for V&V, 828 for SCM, 829 for test documentation), ISO/IEC 12207 (software life cycle processes), CMMI process areas, the NSPE Code of Ethics, and the IEEE/ACM Software Engineering Code of Ethics. These remain useful references for this practice set.

How can I still become a licensed software engineer in 2026?

Consult your state engineering board. The most common paths today are: (1) PE Electrical and Computer — Computer option (NCEES, active) for engineers with electrical/computer engineering degrees; (2) PE Industrial and Systems Engineering (NCEES, active) for systems-oriented software roles; (3) state-specific industrial exemptions for software work at licensed firms; (4) international engineering credentials (Chartered Engineer, P.Eng. Canada) for cross-border recognition. Each state sets its own rules for accepted exams and experience.