Separating entities in the business logic layer

Question

I am going to start a project, which in the BLL would have something like:

I need to keep track of all those, so I will make probably classes which hold them, e.g.:

First of all, is that a good practice to hold all the objects and is it good if I separate them like:

BLL.Entity for the Jumper, Map, Record and BLL.List for JumperList, MapList, RecordList

Okay, I may have written it in a confusing way. What I meant was, is it good to make it like that:

BLL.Entity
 - Jumper
 - Map
 - Record
BLL.List
 - JumperList
 - MapList
 - RecordList

I don't really think you have enough entities to get any advantage from separating them. I don't even think you can think of sensible way to separate them. — Euphoric
– Euphoric, Commented Jan 16, 2014 at 21:40
@Euphoric I have more than 10 classes, those 3 I have given are just an example. My point was to separate the entity classes and entityList classes — Nikola
– Nikola, Commented Jan 16, 2014 at 21:51
@LynHeadley, they are in the BLL.. just basic objects which I will generate from XML — Nikola
– Nikola, Commented Jan 16, 2014 at 23:41

Zafua · Accepted Answer · 2014-01-16 22:05:02Z

-1

Separating is often good practise. But i prefer Repository, not List. And also look at this separation:

Bll.Jumper
    +JumperEntity
    +JumperRepository
Bll.Map
    +MapEntity
    +MapRepository
Bll.Record
    +RecordEntity
    +RecordRepository

answered Jan 16, 2014 at 21:34

Zafua

11 bronze badge

1 Answer 1