Spring 2027 transfer applications are open.Priority review: November 20Find your next step

School of Computing & Data

Software Engineering.

Build and maintain software through requirements, architecture, testing and team delivery.

Two software students review an application and a paper acceptance checklist.
AwardBachelor of Science
Degree credits120
Typical durationFour years · full time
Learning formatIn person · projects & practice

A discipline you can put to work.

Useful software has a life beyond the first successful demonstration. Someone has to understand its requirements, change its behavior and investigate it when a user encounters a problem. Software Engineering treats those responsibilities as part of building the application.

Programming, data structures, databases and systems provide a shared foundation. Later courses connect requirements, architecture, server-side work, testing and collaborative delivery. Students learn to give a reason for a boundary in the code as well as a reason for a feature on the screen.

Define the behavior

Turn a user problem into explicit requirements and useful acceptance criteria.

Structure the application

Create interfaces and data boundaries that support maintainable changes.

Deliver as a team

Use reviews, tests and a release record to make individual contributions visible.

A project with a useful question.

A workshop-booking application requires more than an available-time display. Students model roles and data, decide how a request changes state and test failure paths. A small, tested vertical slice provides evidence before the team expands the application.

See student project records for methods, advisers and the evidence each team prepares.

The places behind the pathway.

Vector classrooms support version-controlled team work, ordinary workstation testing and discussion around an explicit application model. Projects use prepared or approved teaching information rather than real private records.

Explore the teaching setting

2026–27 catalog / sample sequence

Your four-year course map.

The 120-credit degree combines 30 general-education credits, 30 foundation credits, 24 required major credits, 18 concentration electives and 18 free electives.

The sample concentration selection is published below as actual courses. Free electives are adviser-approved, unduplicated college-level work with prerequisites met. Transfer review and actual class availability can change an individual sequence.

Year 130 credits

Fall semester

Semester credits15

Spring semester

Semester credits15
Year 230 credits

Fall semester

ADVISER-APPROVED SELECTIONFree elective 13
Semester credits15

Spring semester

ADVISER-APPROVED SELECTIONFree elective 23
Semester credits15
Year 330 credits

Fall semester

ADVISER-APPROVED SELECTIONFree elective 33
Semester credits15

Spring semester

ADVISER-APPROVED SELECTIONFree elective 43
Semester credits15
Year 430 credits

Fall semester

ADVISER-APPROVED SELECTIONFree elective 53
Semester credits15

Spring semester

ADVISER-APPROVED SELECTIONFree elective 63
Semester credits15

Eight courses that define the major.

Each course builds on documented prerequisites. The proposal and implementation capstones sit in the final fall and spring terms.

SWE210 · Web Interfaces

Build semantic, responsive browser interfaces with accessible interactions. Students test behavior across screen sizes and document interface decisions.

Read the catalog entry

SWE220 · Software Requirements and Modeling

Translate a user problem into requirements, use cases and system models. Students review ambiguity, scope and acceptance criteria.

Read the catalog entry

SWE310 · Application Architecture

Organize an application into components with explicit data and service boundaries. Projects examine maintainability, interfaces and deployment assumptions.

Read the catalog entry

SWE320 · Software Testing and Quality

Design tests for expected behavior, boundary conditions and failure paths. Students use review, automation and defect reports to improve a codebase.

Read the catalog entry

SWE330 · Server-Side Application Development

Implement application routes, data operations and service interfaces. Coursework addresses validation, authentication concepts and error handling.

Read the catalog entry

SWE340 · Collaborative Software Delivery

Work in a version-controlled team with reviews, issue tracking and release planning. Students assess the quality of both software and collaboration.

Read the catalog entry

SWE401 · Software Capstone I

Scope a software product and build a tested vertical slice. Teams document architecture, user feedback and a realistic delivery plan.

Read the catalog entry

SWE402 · Software Capstone II

Complete and evaluate the capstone application. Teams present user evidence, test results, operational notes and a maintainable handover package.

Read the catalog entry

Prepare for the next step.

Algebra, clear writing and experience explaining how a project works. Calculus readiness is reviewed for engineering and data pathways.

Required courses need a grade of C or better and graduation requires a 2.0 cumulative GPA. At least 30 of the final 45 credits and both capstones are completed at Larkmere. An adviser can explain the distinction between a transferable course and one that satisfies a particular requirement.

Possible directions include Software developer, application engineer, software quality analyst. These are study-to-work directions, not guaranteed placements. Career Development helps students select portfolio evidence and explain their individual contribution.

See where an idea can take you.

Start with a conversation. Come see the work.

Find your next page.

Open the full search page