PASC study guide
PASC · Work through your exam, one topic at a time.
The Professional Assessment of Software Competency (PASC) is an independent, multiple-choice examination intended to gauge whether a practitioner has the working knowledge expected of a mid-level software engineer across the full delivery lifecycle. It suits developers, testers, analysts, and technical leads who want an external check on breadth rather than a certificate in one language or framework. The PASC study guide has 8 sections and about 2,503 words.
01Software Requirements and Analysis
Requirements work is about discovering what a system must do, then expressing it so that everyone - users, developers, testers - reads the same thing. Know the vocabulary: functional requirements (behaviors), non-functional requirements (quality attributes such as performance, security, usability, each ideally measurable), constraints (imposed decisions like mandated platforms), and business rules .
330 words, about 2 min02Software Design and Architecture
Architecture is the set of significant decisions that are hard to change later: the major structures, their relationships, and the qualities they enable. Design fills in the details within that frame.
309 words, about 2 min03Software Construction and Implementation
Construction turns design into working code. The exam tests judgment about code quality, not syntax trivia.
315 words, about 2 min04Software Testing and Quality Assurance
Testing provides information about quality; QA is the broader process of building quality in. Know the test levels - unit, integration, system, acceptance - and their purposes: unit tests isolate logic, integration tests exercise interfaces, system tests validate end-to-end behavior, acceptance tests confirm fitness for use.
290 words, about 1 min05Software Configuration and Release Management
Configuration management (CM) keeps the evolving product under control. Know its four pillars: identification (what are the configuration items - code, docs, build scripts, environments), control (change management, baselines, approval), status accounting (what version is where, what changed), and audit/verification (does the delivered artifact match its specification and baseline).
291 words, about 1 min06Software Project Management and Process
Project management balances scope, schedule, cost, quality, and risk - change one and the others move. Know estimation techniques: expert judgment, analogy, and algorithmic models (e.g., function points, COCOMO), plus planning poker in agile settings.
313 words, about 2 min07Software Maintenance and Evolution
Most software cost lives after first release. Know the maintenance categories : corrective (fix defects), adaptive (respond to environment change - new OS, new regulation), perfective (improve performance or maintainability, add enhancements), and preventive (reduce future deterioration, e.g., refactoring, adding tests).
319 words, about 2 min08Software Engineering Ethics and Professional Practice
Professional ethics is not decoration - it is part of the job. Engineers hold specialized knowledge the public lacks, which creates duties of competence, honesty, and care.
336 words, about 2 min