CPN CPE Computer Engineering study materials
CPN CPE Computer Engineering study resources

CPN CPE Computer Engineering study plan

CPN CPE Computer Engineering · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Computer Architecture and Organization & Digital Logic and Circuit Design

  • Derive CPI, MIPS, and speedup for at least five pipelined and non-pipelined CPU examples by hand

  • Draw and label the stages of a classic 5-stage RISC pipeline and identify data, control, and structural hazards in worked traces

  • Convert between number bases and two's complement representations, then compute overflow and sign-extension cases without error

  • Minimize three Boolean functions using Karnaugh maps and verify each result with a truth table

Your checkpoint

A 10-problem self-test on architecture and logic, scored, with every wrong answer rewritten as a corrected worked solution

Week 2

Computer Architecture and Organization & Digital Logic and Circuit Design

  • Explain cache mapping (direct, set-associative, fully associative) and compute hit/miss rates for at least four memory access traces

  • Compare RISC and CISC tradeoffs and justify a design choice in a short written argument

  • Design a synchronous finite-state machine from a word description, including state diagram, state table, and excitation logic

  • Analyze setup and hold timing for a simple register-to-register path and state whether the design closes timing

Your checkpoint

A complete FSM design packet (state diagram, encoded state table, flip-flop input equations, timing check) for one traffic-light or vending-machine controller

Week 3

Operating Systems & Data Structures and Algorithms

  • Trace process state transitions and compute average waiting and turnaround times for FCFS, SJF, round-robin, and priority scheduling on the same workload

  • Detect deadlock using a resource-allocation graph and apply Banker's algorithm to a small claim matrix

  • Implement and compare insertion, merge, and quicksort on the same input, recording operation counts and complexity

  • Implement a hash table with collision resolution and measure load-factor impact on probe counts

Your checkpoint

A runnable code repository with three sorting implementations plus a hash table, a benchmark table of measured runtimes and operation counts, and a one-page complexity analysis

Week 4

Software Engineering and Programming & Data Structures and Algorithms

  • Apply at least four design patterns (strategy, observer, factory, adapter) to a single small problem and justify each choice

  • Write unit tests covering normal, boundary, and error paths for one module and report achieved coverage

  • Implement graph traversal (BFS and DFS) and a shortest-path algorithm, then verify against hand-computed expected results

  • Refactor a duplicated code sample into a cleaner structure without changing behavior, proving equivalence with tests

Your checkpoint

A tested mini-application with a README documenting design decisions, test coverage percentage, and before/after refactoring evidence

Week 5

Computer Networks & Security and Cryptography

  • Subnet a given address block into at least four sized subnets and verify host ranges and broadcast addresses

  • Trace a packet across a small multi-router topology, listing source and destination MAC and IP at each hop

  • Explain TCP handshake, flow control, and congestion control with a labeled sequence diagram

  • Compare symmetric and asymmetric cryptography and select appropriate primitives for confidentiality, integrity, and authentication in a scenario

  • Identify and mitigate at least five common web or network vulnerabilities mapped to their underlying cause

Your checkpoint

A network design and security review document containing a subnetting table, an annotated packet-walk diagram, and a threat-to-control mapping table

Week 6

Database Systems & Operating Systems

  • Normalize a messy relation to third normal form and justify each decomposition step

  • Write SQL queries using joins, aggregation, and subqueries, then validate results against expected output sets

  • Explain transaction isolation levels and demonstrate a lost-update or dirty-read scenario

  • Compare paging and segmentation and compute effective access time with a TLB and page faults

  • Explain virtual memory, thrashing, and page-replacement behavior using a reference-string trace

Your checkpoint

A database workbook with a normalized schema, ten validated SQL queries, a transaction anomaly write-up, and a page-replacement trace table

Week 7

Embedded and Real-Time Systems & Computer Engineering Practice, Ethics, and Professionalism

  • Compute worst-case execution time and response time for a fixed-priority task set and determine schedulability with rate-monotonic analysis

  • Explain priority inversion and describe how priority inheritance resolves it

  • Describe interrupt latency, watchdog, and memory-constrained design considerations for an embedded target

  • Apply a professional code of ethics to at least three realistic engineering scenarios and articulate the conflicting obligations

  • Distinguish negligence, incompetence, and misconduct in engineering practice and state appropriate responses

Your checkpoint

An embedded schedulability analysis for a five-task system plus a written ethics case brief covering three scenarios with reasoned recommendations

Week 8

Computer Architecture and Organization & Software Engineering and Programming & Computer Engineering Practice, Ethics, and Professionalism

  • Complete two full-length timed practice exams and record per-domain accuracy

  • Re-derive the five weakest concepts from scratch without notes and confirm correctness

  • Build a one-page formula and reference sheet covering architecture, logic, OS, and networking essentials

  • Review professional-responsibility topics and resolve any remaining uncertain items

Your checkpoint

A scored practice-exam report with per-domain accuracy, a prioritized remediation list, and a completed one-page reference sheet

Milestones

Week 2: Score at least 70% on a self-made 20-question architecture and logic test, and correctly complete one FSM design without reference material

Week 4: All code in the repository runs, tests pass with at least 80% coverage on the tested module, and sorting benchmarks match expected complexity trends

Week 6: Subnetting table and packet walk are error-free, SQL queries return expected result sets, and the schema is in third normal form with written justification

Week 8: Average at least 75% across two timed practice exams with no domain below 60%, and every remaining weak item has a written remediation note