Do not misinterpret ModuleNames for RouteNames. If you take a look inside module.config.php you'll see an array in the following syntax:
'router' => array(
'routes' => array(
'$routeName' => array(
// $routeParams
)
)
)
In this case $routeName of course always will be a string that defines the NAME of a route. To know which URL is attached to that route, you got to look at the $routeParams. This usually looks like the following:
'type' => '$routeType',
'options' => array(
'route' => '$theRoute'
)
The $routeType always is a string, too. Here people usually add one of the shortnames for the routetype that are defined here (scroll up a little). Alternatively the full classname to the specific route could be given, too.
Inside the options array you'd define the options that a route needs. One will always be route, as this is the matching criteria for a route. Following example:
'route' => '/test'
Matching URL: http://myproject.dev/test
There's one catch however and that is child-routes. When there are child-routes, the route option gets attached to it's parent routes. So for example:
'route' => '/test' // <- This is the PARENT Route
'route' => '/foobar' // -< This is the CHILD Route
Matching URL: http://myproject.dev/test/foobar
Hope this helps you out a little with understanding the framework routing. More information can always be gathered from the official Documentation of Zend\Mvc\Router