PE Computer Engineering study plan
PE Computer Engineering · Give each week a clear focus.
8 weeks · About 6 hours per week
Computer Systems & Digital Systems
Map the Computer Systems blueprint into a one-page checklist of subtopics, marking each as known, shaky, or unknown
Derive cache hit/miss behavior by hand for a direct-mapped and a 2-way set-associative cache given an address trace
Compute average memory access time for three cache configurations and state which parameter dominates
Convert between binary, hex, and two's-complement representations for 8-, 16-, and 32-bit signed values
Sketch the datapath stages of a simple pipelined CPU and label where each hazard type arises
Your checkpoint
A hand-worked cache and number-representation problem set (at least 15 solved problems) with a written error log listing each mistake and its cause
Computer Systems & Digital Systems
Explain virtual memory translation from virtual address to physical address including TLB, page table walk, and page fault path
Compare interrupt-driven I/O, DMA, and programmed I/O for a given throughput requirement and justify a choice
Minimize a 4-variable Boolean function using Karnaugh maps and verify the result algebraically
Design a combinational circuit from a truth table and express it in sum-of-products and product-of-sums form
Analyze a synchronous sequential circuit by deriving its state table and state diagram from a schematic description
Your checkpoint
A timed 90-minute mock set of 20 mixed Computer Systems and Digital Systems questions, scored, with every wrong answer rewritten as a correct explanation
Digital Systems & Hardware and Embedded Systems
Trace instruction execution through a 5-stage pipeline and quantify stall cycles for data, control, and structural hazards
Compute speedup and efficiency for a pipeline versus a non-pipelined datapath at several instruction mixes
Distinguish setup time, hold time, and propagation delay and check a given timing path against a clock constraint
Classify memory types (SRAM, DRAM, flash, EEPROM) by volatility, endurance, and typical embedded use
Select an appropriate communication bus (I2C, SPI, UART, CAN) for three stated embedded scenarios and defend each choice
Your checkpoint
A written timing and bus-selection analysis for three embedded scenarios, each with a labeled timing diagram and a justified component choice
Software Engineering & Hardware and Embedded Systems
Implement a bounded-buffer producer-consumer in a language of your choice using a mutex and condition variable, then remove the lock and demonstrate a race
Identify deadlock conditions in a supplied resource-allocation description and propose two distinct fixes
Write unit tests that achieve branch coverage on a function with nested conditionals and report the coverage number
Explain the difference between a process and a thread and predict output ordering for a given concurrent program
Describe the embedded firmware boot sequence from reset vector through initialization to main loop
Your checkpoint
A small concurrent program with tests, a coverage report, and a short write-up proving the race condition exists without synchronization
Software Engineering
Apply each SOLID principle to refactor a poorly structured class and document the before/after design
Compare waterfall, iterative, and agile lifecycle models and match each to a stated project constraint
Produce a requirements specification for a small feature with testable acceptance criteria
Construct a control-flow graph for a function and compute cyclomatic complexity by two methods
Perform a code review of a supplied snippet and log at least six defects classified by severity
Your checkpoint
A refactoring portfolio: one class refactored against SOLID, its control-flow graph, computed complexity, and a defect log with severity ratings
Networks and Communications
Work through the TCP three-way handshake and connection teardown, labeling every flag and state transition
Compare TCP and UDP for four application profiles and justify the transport choice for each
Subnet a given IPv4 address space to satisfy stated host-count requirements and verify no overlap
Trace a packet across a routed network hop by hop, stating what changes in the headers at each device
Explain ARP, DNS resolution, and DHCP lease acquisition as ordered message sequences
Your checkpoint
A subnetting and protocol-trace workbook: five subnetting problems fully solved plus three annotated message-sequence diagrams
Networks and Communications & Hardware and Embedded Systems
Compute link budget or throughput for a given channel specification and identify the limiting factor
Describe the OSI and TCP/IP layer models and map five protocols to their layers with justification
Analyze an embedded networked device for security weaknesses at each layer and propose mitigations
Compare wired and wireless embedded networking options for latency, power, and range
Diagnose a described network failure using a structured layer-by-layer troubleshooting method
Your checkpoint
A structured troubleshooting case study: one simulated fault, the layer-by-layer diagnostic path, and the confirmed root cause with fix
Computer Systems & Digital Systems & Software Engineering & Networks and Communications & Hardware and Embedded Systems
Take two full-length timed practice exams under exam conditions and record per-domain scores
Rank your five domains by accuracy and re-drill the two weakest with targeted problem sets
Rebuild your one-page checklist from week 1 and confirm every item is now marked known
Memorize and rehearse the standard formulas (AMAT, speedup, subnetting, complexity, link budget) from a single formula sheet
Simulate exam pacing by allocating time per question and reviewing flagged items
Your checkpoint
Two scored full-length practice exams with a per-domain accuracy table and a one-page formula sheet you can reproduce from memory
Milestones
Week 2: Score at least 70% on the 20-question mixed Computer Systems and Digital Systems mock, and correctly derive a cache AMAT and a Karnaugh-map minimization without notes
Week 4: Demonstrate a reproducible race condition, then fix it with a mutex, and state the coverage percentage achieved on the tested module
Week 6: Solve all five subnetting problems with zero arithmetic errors and correctly label every state in the TCP handshake and teardown
Week 8: Reach at least 75% overall on both full-length practice exams with no single domain below 60%, and reproduce the formula sheet from memory