Intro to Software Development Curriculum

Public curriculum preview for visitors and enrolled students. Use this page to evaluate module scope, outcomes, and learning path.

Download PDFBack to Course
Curriculum

Intro to Software Development

Structured, hands-on learning path for Intro to Software Development with detailed weekly outcomes and practical delivery.

Duration: 12 Weeks
Level: Beginner
Study Time: 2 hours/week + labs
School: Hexadigitall Academy
12 WeeksBeginnerProject-Based

Welcome to Intro to Software Development! 🎓

This curriculum for Intro to Software Development follows a Bloom-aligned progression from foundational concepts to confident application, with weekly evidence, labs, and portfolio outputs matched to beginner expectations.

Each week advances from comprehension and application toward evaluation and creation, ensuring progressive learning and capstone readiness.

Your success is our priority. By the end, you will produce portfolio-ready artifacts and confidently explain your technical decisions. You will graduate with a professionally curated portfolio that demonstrates scope, depth, and delivery quality. You will graduate with a professionally curated portfolio that demonstrates scope, depth, and delivery quality. You will graduate with a professionally curated portfolio that demonstrates scope, depth, and delivery quality. You will graduate with a professionally curated portfolio that demonstrates scope, depth, and delivery quality.

Prerequisites

  • Programming language proficiency with solid grasp of data structures, algorithms, and design patterns
  • Version control mastery: Git workflows, code review, merge conflict resolution, and collaborative development
  • Testing fundamentals: unit testing, test-driven development, mocking, and test coverage analysis
  • Debugging and profiling skills: breakpoint debugging, performance flame graphs, and memory analysis

Essential Resources

  • Language-specific style guides, design patterns reference, and debugging tools inventory
  • Testing frameworks, mock libraries, and performance profiling instructions for your tech stack
  • Refactoring patterns, security best practices, and code quality tooling configurations

Complementary Courses

Web Development (Frontend/Backend)

Specialize in modern frameworks, API design, and full-stack architecture

System Design & Architecture

Master scalability patterns, distributed systems, and reliability engineering

DevOps & Quality Assurance

Learn CI/CD integration, automated testing, and production monitoring

Learning Roadmap

  • Early Weeks: Language fundamentals, testing basics, and design patterns
  • Middle Weeks: Advanced architectures, performance optimization, and debugging
  • Late Weeks: Production systems, scalability, and cross-platform deployment

Detailed Weekly Curriculum

Each week includes outcomes and practical lab work aligned to the curriculum structure.

Week 1

Intro to Software Development: Programming Foundations and Code Structure (Sprint 1)

2 hours + labs
Learning Outcomes
  • Identify the principles of Intro to Software Development: Programming Foundations and Code Structure (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Intro to Software Development: Programming Foundations and Code Structure (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Intro to Software Development: Programming Foundations and Code Structure (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: Programming Foundations and Code Structure (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Design and execute a concrete Intro to Software Development: Programming Foundations and Code Structure (Sprint 1) build in Intro to Software Development with a clear acceptance checklist.
  • Validate Intro to Software Development: Programming Foundations and Code Structure (Sprint 1) with objective tests and quality controls before review.
  • Deliver Intro to Software Development: Programming Foundations and Code Structure (Sprint 1) artifacts with reproducible steps and operational notes.
Week 2

Intro to Software Development: Data Structures and Problem Solving (Sprint 1)

2 hours + labs
Learning Outcomes
  • Identify the principles of Intro to Software Development: Data Structures and Problem Solving (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Intro to Software Development: Data Structures and Problem Solving (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Intro to Software Development: Data Structures and Problem Solving (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: Data Structures and Problem Solving (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Build a practical Intro to Software Development: Data Structures and Problem Solving (Sprint 1) workflow with source-to-output transformation steps.
  • Validate Intro to Software Development: Data Structures and Problem Solving (Sprint 1) quality and performance with objective checks and tuning updates.
  • Deliver reproducible Intro to Software Development: Data Structures and Problem Solving (Sprint 1) outputs (dashboard/report/notebook) with run instructions.
Week 3

Intro to Software Development: API Design and Integration (Sprint 1)

2 hours + labs
Learning Outcomes
  • Identify the principles of Intro to Software Development: API Design and Integration (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Intro to Software Development: API Design and Integration (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Intro to Software Development: API Design and Integration (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: API Design and Integration (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Produce a complete Intro to Software Development: API Design and Integration (Sprint 1) prototype from brief to high-fidelity handoff artifacts.
  • Run usability/visual QA for Intro to Software Development: API Design and Integration (Sprint 1) and apply iteration changes from feedback.
  • Deliver export-ready assets, source files, and implementation notes for Intro to Software Development: API Design and Integration (Sprint 1).
Week 4

Intro to Software Development: State and Application Architecture (Sprint 1)

2 hours + labs
Learning Outcomes
  • Identify the principles of Intro to Software Development: State and Application Architecture (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Intro to Software Development: State and Application Architecture (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Intro to Software Development: State and Application Architecture (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: State and Application Architecture (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Design and execute a concrete Intro to Software Development: State and Application Architecture (Sprint 1) build in Intro to Software Development with a clear acceptance checklist.
  • Validate Intro to Software Development: State and Application Architecture (Sprint 1) with objective tests and quality controls before review.
  • Deliver Intro to Software Development: State and Application Architecture (Sprint 1) artifacts with reproducible steps and operational notes.
Week 5

Intro to Software Development: Testing and Debugging Practices (Sprint 1)

2 hours + labs
Learning Outcomes
  • Apply the principles of Intro to Software Development: Testing and Debugging Practices (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Intro to Software Development: Testing and Debugging Practices (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Intro to Software Development: Testing and Debugging Practices (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: Testing and Debugging Practices (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Design and execute a concrete Intro to Software Development: Testing and Debugging Practices (Sprint 1) build in Intro to Software Development with a clear acceptance checklist.
  • Validate Intro to Software Development: Testing and Debugging Practices (Sprint 1) with objective tests and quality controls before review.
  • Deliver Intro to Software Development: Testing and Debugging Practices (Sprint 1) artifacts with reproducible steps and operational notes.
Week 6

Intro to Software Development: Performance and Optimization (Sprint 1)

2 hours + labs
Learning Outcomes
  • Apply the principles of Intro to Software Development: Performance and Optimization (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Intro to Software Development: Performance and Optimization (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Intro to Software Development: Performance and Optimization (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: Performance and Optimization (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Design and execute a concrete Intro to Software Development: Performance and Optimization (Sprint 1) build in Intro to Software Development with a clear acceptance checklist.
  • Validate Intro to Software Development: Performance and Optimization (Sprint 1) with objective tests and quality controls before review.
  • Deliver Intro to Software Development: Performance and Optimization (Sprint 1) artifacts with reproducible steps and operational notes.
Week 7

Intro to Software Development: Security and Reliability Basics (Sprint 1)

2 hours + labs
Learning Outcomes
  • Apply the principles of Intro to Software Development: Security and Reliability Basics (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Intro to Software Development: Security and Reliability Basics (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Intro to Software Development: Security and Reliability Basics (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: Security and Reliability Basics (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Implement baseline controls for Intro to Software Development: Security and Reliability Basics (Sprint 1) and verify enforcement on target systems.
  • Run assessment/scanning for Intro to Software Development: Security and Reliability Basics (Sprint 1) and prioritize findings by exploitability and impact.
  • Close critical findings for Intro to Software Development: Security and Reliability Basics (Sprint 1) and publish re-test evidence.
Week 8

Intro to Software Development: Deployment and Support Readiness (Sprint 1)

2 hours + labs
Learning Outcomes
  • Apply the principles of Intro to Software Development: Deployment and Support Readiness (Sprint 1) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Intro to Software Development: Deployment and Support Readiness (Sprint 1) in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Intro to Software Development: Deployment and Support Readiness (Sprint 1), then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Intro to Software Development: Deployment and Support Readiness (Sprint 1) with measurable success criteria and next actions.
Lab Exercise
  • Design and execute a concrete Intro to Software Development: Deployment and Support Readiness (Sprint 1) build in Intro to Software Development with a clear acceptance checklist.
  • Validate Intro to Software Development: Deployment and Support Readiness (Sprint 1) with objective tests and quality controls before review.
  • Deliver Intro to Software Development: Deployment and Support Readiness (Sprint 1) artifacts with reproducible steps and operational notes.
Week 9

Intro to Software Development: Programming Foundations and Code Structure (Sprint 2)

2 hours + labs
Learning Outcomes
  • Analyze the principles of Intro to Software Development: Programming Foundations and Code Structure (Sprint 2) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Intro to Software Development: Programming Foundations and Code Structure (Sprint 2) in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Intro to Software Development: Programming Foundations and Code Structure (Sprint 2), then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Intro to Software Development: Programming Foundations and Code Structure (Sprint 2) with measurable success criteria and next actions.
Lab Exercise
  • Design and execute a concrete Intro to Software Development: Programming Foundations and Code Structure (Sprint 2) build in Intro to Software Development with a clear acceptance checklist.
  • Validate Intro to Software Development: Programming Foundations and Code Structure (Sprint 2) with objective tests and quality controls before review.
  • Deliver Intro to Software Development: Programming Foundations and Code Structure (Sprint 2) artifacts with reproducible steps and operational notes.
Week 10

Intro to Software Development: Data Structures and Problem Solving (Sprint 2)

2 hours + labs
Learning Outcomes
  • Analyze the principles of Intro to Software Development: Data Structures and Problem Solving (Sprint 2) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Intro to Software Development: Data Structures and Problem Solving (Sprint 2) in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Intro to Software Development: Data Structures and Problem Solving (Sprint 2), then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Intro to Software Development: Data Structures and Problem Solving (Sprint 2) with measurable success criteria and next actions.
Lab Exercise
  • Build a practical Intro to Software Development: Data Structures and Problem Solving (Sprint 2) workflow with source-to-output transformation steps.
  • Validate Intro to Software Development: Data Structures and Problem Solving (Sprint 2) quality and performance with objective checks and tuning updates.
  • Deliver reproducible Intro to Software Development: Data Structures and Problem Solving (Sprint 2) outputs (dashboard/report/notebook) with run instructions.
Week 11

Intro to Software Development: API Design and Integration (Sprint 2)

2 hours + labs
Learning Outcomes
  • Analyze the principles of Intro to Software Development: API Design and Integration (Sprint 2) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Intro to Software Development: API Design and Integration (Sprint 2) in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Intro to Software Development: API Design and Integration (Sprint 2), then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Intro to Software Development: API Design and Integration (Sprint 2) with measurable success criteria and next actions.
Lab Exercise
  • Produce a complete Intro to Software Development: API Design and Integration (Sprint 2) prototype from brief to high-fidelity handoff artifacts.
  • Run usability/visual QA for Intro to Software Development: API Design and Integration (Sprint 2) and apply iteration changes from feedback.
  • Deliver export-ready assets, source files, and implementation notes for Intro to Software Development: API Design and Integration (Sprint 2).
Week 12

Intro to Software Development: State and Application Architecture (Sprint 2)

2 hours + labs
Learning Outcomes
  • Analyze the principles of Intro to Software Development: State and Application Architecture (Sprint 2) and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Intro to Software Development: State and Application Architecture (Sprint 2) in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Intro to Software Development: State and Application Architecture (Sprint 2), then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Intro to Software Development: State and Application Architecture (Sprint 2) with measurable success criteria and next actions.
Lab Exercise
  • Design and execute a concrete Intro to Software Development: State and Application Architecture (Sprint 2) build in Intro to Software Development with a clear acceptance checklist.
  • Validate Intro to Software Development: State and Application Architecture (Sprint 2) with objective tests and quality controls before review.
  • Deliver Intro to Software Development: State and Application Architecture (Sprint 2) artifacts with reproducible steps and operational notes.

Capstone Projects

Project 1: Intro to Software Development Foundation Build

Deliver a concrete foundation implementation covering the first phase of the curriculum.

  • Implement and validate Intro to Software Development: Programming Foundations and Code Structure (Sprint 1).
  • Integrate Intro to Software Development: Data Structures and Problem Solving (Sprint 1) with reusable workflow standards.
  • Publish evidence for Intro to Software Development: API Design and Integration (Sprint 1) with test and quality artifacts.

Project 2: Intro to Software Development Integrated Systems Build

Combine mid-program competencies into a production-style integrated workflow.

  • Build an end-to-end flow around Intro to Software Development: Testing and Debugging Practices (Sprint 1) and Intro to Software Development: Performance and Optimization (Sprint 1).
  • Add controls, observability, and rollback paths for reliability.
  • Document architecture decisions and trade-offs tied to Intro to Software Development: Security and Reliability Basics (Sprint 1).

Project 3: Intro to Software Development Capstone Delivery

Ship a portfolio-ready capstone with measurable outcomes and stakeholder-ready presentation.

  • Deliver a complete implementation centered on Intro to Software Development: Programming Foundations and Code Structure (Sprint 2).
  • Validate readiness for Intro to Software Development: Data Structures and Problem Solving (Sprint 2) using objective acceptance checks.
  • Present final defense and roadmap based on Intro to Software Development: API Design and Integration (Sprint 2) outcomes.