For the web application (ASP.NET MVC) I\'m currently developing, we have the following architecture in place:
Data Access Layer
: Logic for persisting
From a high level, I'd describe it as layered architecture. Describing it as domain-driven design would also look at smaller patterns like aggregate, repository, bounded contexts, etc. I can't tell just from your description.
If the domain layer resides in an assembly/package that doesn't reference any of the others, then it has the core of the Onion Architecture principles, which are:
A concrete thing to look for is if your DataAccess references Domain.