Pre-Semester Exam: Foundation Systems Assessment

Required Output Classification

Required output	Classification	Public/private guidance
Timed written answers, diagrams, code snippets, and design responses	Checkpoint evidence	Keep raw exam work private so it remains useful for assessment and retake calibration.
Post-exam review notes, missed-answer repairs, and Feynman explanations	Practice artifact	Use for spaced review; publish only rewritten explanations that no longer reveal exam solutions wholesale.
Capstone-defense or architecture-defense packets created from exam prompts	Portfolio candidate	Polish publicly only when they are original to your project, sanitized, and framed as engineering rationale rather than exam answers.

Duration: 2 hours
Format: Practical demonstration exam with hands-on tasks
Materials: Your configured development environment, access to your repositories
Assessment: Tests foundational competency through practical application rather than theoretical knowledge

Exam Philosophy

This exam tests practical foundation competency and workflow fluency, not memorization. Problems require demonstrating that your study systems, development environment, and Git workflow actually work effectively under time pressure.

---

Exam Structure

Section	Tasks	Time	Weight	Focus
Part A: Study System Application	3 tasks	30 min	25%	Learning and habit system effectiveness
Part B: Development Environment	4 tasks	45 min	35%	Command-line and tool proficiency
Part C: Git Workflow	4 tasks	30 min	25%	Version control and collaboration
Part D: Integration Challenge	1 task	15 min	15%	All systems working together

---

Part A: Study System Application (30 minutes)

Demonstrate your established study system working effectively under time pressure.

Task A1: Rapid Learning Challenge (15 minutes)

Scenario: You encounter a new CS concept (merge sort algorithm) that you need to understand quickly.

Requirements:

1. Use your study system to learn merge sort from provided resources (concept explanation, example code, complexity analysis)
2. Apply your learning techniques (note-taking, retrieval practice, or other methods from your system)
3. Demonstrate understanding by explaining the algorithm clearly and identifying key characteristics
4. Document process showing how your study habits supported efficient learning

Assessment:

• Study system supports rapid comprehension of new technical material
• Learning approach is systematic rather than haphazard
• Understanding demonstrated through clear explanation and application
• Process documentation shows effective use of established study habits

Task A2: Focus and Concentration Assessment (10 minutes)

Scenario: Complex technical problem requiring sustained focus with potential distractions.

Challenge: Trace through a recursive algorithm implementation manually while music plays and you receive simulated interruptions (instructor will provide controlled distractions).

Requirements:

1. Maintain focus on technical task despite distractions
2. Use concentration techniques from your study system
3. Complete task accurately with minimal errors due to distraction
4. Recover quickly from interruptions and return to productive work

Assessment:

• Concentration techniques effectively maintain focus on technical material
• Recovery from distractions is smooth and doesn't derail progress
• Technical accuracy maintained despite challenging focus conditions
• Sustainable approach that could handle regular academic pressures

Task A3: Learning Integration and Retention (5 minutes)

Scenario: Quick retention check of material from all three Pre-Semester modules.

Requirements:

1. Retrieve key concepts from memory (closed-book) across all three modules
2. Explain connections between different foundation areas
3. Apply spaced repetition principles to identify what needs review
4. Plan reinforcement for concepts that feel less solid

Assessment:

• Good retention of material from all three modules without heavy note dependence
• Clear understanding of how different foundation areas support each other
• Realistic self-assessment of strengths and areas needing reinforcement
• Systematic approach to maintaining and improving retention over time

---

Part B: Development Environment Proficiency (45 minutes)

Demonstrate command-line and development tool fluency through practical tasks.

Task B1: File System Navigation and Organization (10 minutes)

Scenario: Organize a messy project directory using only command-line tools.

Given: Directory with 30+ files of different types scattered without organization Requirements:

1. Create logical directory structure appropriate for CS coursework
2. Move and organize files using command-line tools efficiently
3. Apply consistent naming conventions and documentation
4. Complete within time limit demonstrating command-line fluency

Assessment:

• File operations completed faster via command line than GUI would allow
• Logical organization appropriate for academic and technical work
• Consistent naming and documentation practices
• Efficiency and confidence with command-line file management

Task B2: Text Processing and Data Extraction (15 minutes)

Scenario: Process algorithm performance data from log files to generate summary report.

Given: Multiple log files with performance timing data in different formats Requirements:

1. Extract timing data from multiple log files using command-line text processing tools
2. Calculate statistics (average, min, max, standard deviation) using shell tools
3. Generate summary report combining data from multiple sources
4. Automate process with script that could handle similar data in the future

Assessment:

• Effective use of grep, sed, awk, sort, and other text processing tools
• Mathematical calculations performed correctly using command-line tools
• Output formatting appropriate for technical communication
• Automation approach that demonstrates understanding of shell scripting principles

Task B3: Editor Proficiency Under Pressure (10 minutes)

Scenario: Make specific changes to code files using your configured editor.

Given: Python file with algorithm implementation containing specific issues to fix Requirements:

1. Navigate efficiently to specific code sections using editor features
2. Make precise edits including search/replace, block operations, and formatting
3. Use editor features (not just basic typing) to complete changes efficiently
4. Maintain code quality during rapid editing session

Assessment:

• Editor usage is fluent and efficient rather than hunting-and-pecking
• Complex editing operations completed using editor features rather than manual approaches
• Code quality maintained despite time pressure
• Workflow demonstrates editor mastery that supports rather than hinders development

Task B4: Environment Troubleshooting (10 minutes)

Scenario: Fix a broken development environment setup.

Given: Development environment with intentionally introduced configuration problems Requirements:

1. Diagnose issues systematically using command-line diagnostic tools
2. Fix configuration problems using knowledge of environment setup and tool interaction
3. Verify solutions and ensure environment works correctly for development tasks
4. Document fixes for future reference and learning

Assessment:

• Systematic troubleshooting approach rather than random trial-and-error
• Effective use of diagnostic tools and error message interpretation
• Solutions address root causes rather than just symptoms
• Documentation enables learning from troubleshooting experience

---

Part C: Git Workflow Competency (30 minutes)

Demonstrate version control and collaboration proficiency through realistic scenarios.

Task C1: Repository Setup and Organization (8 minutes)

Scenario: Initialize a new repository for a technical learning project.

Requirements:

1. Initialize repository with appropriate structure for academic technical work
2. Create documentation (README, project description, setup instructions)
3. Configure .gitignore appropriately for the project type
4. Make initial commits with professional commit messages and logical organization

Assessment:

• Repository structure appropriate for collaborative academic/technical work
• Documentation enables another person to understand and contribute to project
• .gitignore correctly excludes temporary files and system-specific content
• Commit history demonstrates professional practices from project start

Task C2: Branching and Feature Development (12 minutes)

Scenario: Implement a new feature using proper branching workflow.

Given: Existing repository with base implementation Requirements:

1. Create feature branch with appropriate naming and workflow
2. Implement changes with logical commit sequence and clear messages
3. Handle merge scenario (may include conflict resolution)
4. Complete integration with clean history and documentation

Assessment:

• Branching strategy appropriate for feature development and collaboration
• Commit sequence is logical and supports understanding of development process
• Merge conflicts (if any) resolved correctly without losing work or creating errors
• Final integration maintains clean repository history and professional standards

Task C3: Collaboration Simulation (10 minutes)

Scenario: Work with simulated collaborator changes and code review process.

Given: Repository with changes from simulated teammate, including some problematic commits Requirements:

1. Review collaborator work and provide constructive feedback
2. Integrate changes appropriately (merge, rebase, or other strategy)
3. Resolve any conflicts or issues arising from collaboration
4. Maintain project quality throughout collaboration process

Assessment:

• Code review feedback is constructive, technically accurate, and professionally communicated
• Integration strategy preserves both code quality and collaboration relationships
• Conflict resolution maintains technical accuracy without damaging team dynamics
• Professional communication and collaboration practices throughout

Task C4: Git Recovery Scenario (Bonus - if time allows)

Scenario: Recover from intentionally introduced Git problems.

Given: Repository with specific problems (bad commits, lost work, corrupted history) Requirements:

1. Diagnose Git issues using appropriate diagnostic commands and techniques
2. Apply recovery techniques to restore repository to working state
3. Preserve important work while fixing problems
4. Document solution for future reference

Assessment:

• Systematic diagnosis of Git problems rather than panic or random attempts
• Appropriate recovery techniques that solve problems without creating new ones
• Preservation of important work and project history during recovery
• Learning documentation that benefits future troubleshooting

---

Part D: Integration Challenge (15 minutes)

This task requires synthesis across all foundation areas under time pressure.

Task D1: Complete Foundation Workflow Demonstration

Scenario: New CS learning project setup integrating all foundation systems.

Challenge: You're assigned to learn and implement a new data structure (binary heap) with performance analysis.

Integration Requirements: Study System Integration:

• Use your study approach to understand heap concepts and implementation strategies
• Apply focus and learning techniques to grasp both theory and practical considerations

Development Environment Integration:

• Set up project structure using command-line efficiency
• Implement and test heap operations using your configured development tools
• Use text processing tools to analyze performance data and generate reports

Git Workflow Integration:

• Track learning progress and implementation development with professional commit practices
• Organize project for potential collaboration and portfolio presentation
• Document learning process and technical decisions for future reference

Assessment Criteria:

• All foundation systems work together smoothly without friction or inefficiency
• Technical output demonstrates learning effectiveness supported by foundation competency
• Professional quality work suitable for portfolio presentation or collaborative development
• Time management and task completion show readiness for intensive academic schedule

Success Criteria for Integration Challenge

Excellent Integration (90-100%):

• All foundation systems support rather than compete with each other
• Technical learning and implementation proceed efficiently with high-quality results
• Professional workflow throughout with clear documentation and organization
• Demonstrates readiness for much more challenging technical coursework

Proficient Integration (80-89%):

• Foundation systems generally work well together with minor friction points
• Technical work completed successfully with good quality and reasonable efficiency
• Professional practices evident with minor areas for improvement
• Shows readiness for Semester 0 with continued foundation system development

Developing Integration (70-79%):

• Foundation systems work but may have some inefficiencies or conflicts
• Technical work completed but with more effort than should be necessary
• Basic professional practices with significant room for improvement
• May need additional Pre-Semester time for foundation consolidation

---

Overall Assessment

Exam Completion Requirements

To pass this exam and advance to Semester 0:

• 75%+ overall score with no section below 70%
• Demonstrated integration across all foundation areas
• Professional competency in tools and practices essential for collaborative technical work
• Sustainability evidence showing foundation systems can handle increasing academic demands

Next Steps Based on Performance

Ready for Semester 0 (75%+ with strong integration):

• Begin Semester 0 with confidence in foundation system support
• Continue developing foundation systems alongside CS coursework
• Apply professional practices to all Semester 0 projects and collaborations

Need Foundation Reinforcement (65-74%):

• Extend Pre-Semester by 1 week focusing on weakest foundation area
• Additional practice with integration exercises and workflow optimization
• Retake exam when foundation gaps are addressed

Need Foundation Rebuilding (Below 65%):

• Extend Pre-Semester by 2+ weeks with systematic foundation development
• Consider alternative study approaches or additional support resources
• Focus on building sustainable systems before attempting intensive technical coursework

---

Post-Exam Actions

Success Documentation

• Portfolio update: Include exam performance and foundation competency evidence in your learning portfolio
• System refinement: Make final adjustments to foundation systems based on exam experience
• Semester 0 preparation: Plan how foundation systems will support upcoming CS coursework intensity

Continuous Improvement

• Weekly check-ins: Monitor foundation system effectiveness throughout Semester 0
• Adaptation planning: How will you adjust foundation systems as academic demands increase?
• Support network: Establish connections with other learners and mentors for ongoing foundation development

This exam validates that your Pre-Semester foundation systems provide sustainable, efficient, and professional support for the intensive CS and systems engineering education ahead.

---

Mastery Rubric

Level	Evidence
Beginner pass	Can answer direct questions and complete familiar exercises with light notes.
Solid pass	Can solve new variants, explain choices, and connect the work to Basic computer literacy and willingness to work consistently..
Strong pass	Can defend tradeoffs, identify failure modes, and produce clean evidence in the portfolio artifact.
Not ready	Relies on copied solutions, cannot explain mistakes, or lacks durable artifacts.

Retake and Repair Rule

If a section is weak, do not only reread. Repair it by producing new evidence: a corrected solution, a fresh implementation, a rewritten proof, a benchmark, a diagram, a runbook, or a short teaching note.

---

Answer-Quality Examples

Use these examples when grading written answers or spoken explanations.

Quality	Example pattern
Weak	Names a concept but gives no example, constraint, or failure case.
Acceptable	Defines the concept and applies it to a familiar exercise.
Strong	Applies the concept to a new variant and explains why an alternative would fail.
Portfolio-ready	Connects the concept to Basic computer literacy and willingness to work consistently., current project evidence, and a future capstone decision.

Interleaving Prompt

For any missed answer, add one sentence starting with: This depends on an earlier skill because...

Calibration Materials

Use these learner-visible calibration materials before self-grading or requesting review:

• Answer key and solution outlines
• Rubric, passing standard, strong traits, and weak patterns