I'm creating an application using MVP: Passive View and EF (model first). As of know, I have a presenter getting data directly from the DataContext created through EF. It looks something like this:

```
        private void UpdateOrderTableControl()
    {
        IList<Order> orders = dataContext.Orders.ToList();
        IList<OrderViewModel> viewOrders = new List<OrderViewModel>();
        foreach (var o in orders)
        {
            viewOrders.Add(new OrderViewModel()
            {
                OrderId = o.Id,
                CustomerId = o.CustomerId,
                LastName = o.Address.LastName,
                FirstName = o.Address.FirstName,
                Company = o.Address.Company,
                Weight = o.Weight,
                Sum = o.Sum,
                Date = o.Date
            });
        }

        view.GetOrderDataGridView().DataSource = viewOrders;
    }

```

So the presenter gets a list of all orders, creates a list of order view models (combining data from different tables, i.e address above) and then sends the view model list to the view.

It's pretty much the same thing the other way around, when retrieving data from the view in order to edit or add to the db:

```
        private void SaveOrder()
    {
        GetOrderDataFromView();

        if (isNewOrder)
        {
            dataContext.Orders.Add(selectedOrder);
        }
        else
        {
            dataContext.Entry(selectedOrder).State = EntityState.Modified;
        }

        dataContext.SaveChanges();
        isSaved = true;

        UpdateOrderTableControl();
    }

```

1) Can EF (the entities created through EF, the DataContext etc) be considered as the DAL? Should it be in a project of its own?

2) I guess the presenter should not have access to the DataContext like that, but rather to another layer in between the two, right? Would that be a service layer, a business layer or both? 

3) Is what I refer to as a view model in fact a view model or is it something else? I just want to get my terminology right.

EDIT:

4) I read some suggestions about adding business logic to the entities generated by EF, but that doesn't sound quite right to me. Should I create business objects in a separate business layer on top of EF? Meaning I would have Order (generated by EF), OrderBO (the business object) and OrderViewModel (the order to be displayed). I would have to do more mapping, since I'd add another layer, but it would make the presenter lighter.

Thanks in advance!