c# - Object Architecture Design Question -

I'm trying to explain how best to do this. I tell you what I have now, but I am thinking that there is a better way to do this.

I have a class section in which the basic properties are: name, description, AL. I use a list of streams to select users. I can add streams several times because they want a parent object and any number of sections.

When they add a section to parents, tell them which group it belongs to (group 1, group 2, group 3 says) and in what order it will be displayed . This group's property is not in the table, when a user lists sections to choose from, then no group is required, this does not mean. Think of this section they are adding as extra clans to a clone.

I have another table which has a foreign key for parents and stream, 1 parent can be added to many classes.

So when I create a parent object and ask for a collection of its sections, this link includes a grouping and display order column (along with some other) on the table. Try the same section class. Want to do and use it and want to add group properties?

  section 1 section 2 section 3 generator 1 section 1 - group = g1, display order = 1 section 1 - group = g2, displayOrder = 2 section 2 - group = g2, display Order = 3 Section 3 - Group = G3, Display Order = 4 Generator 2 Section 4 - Group = G3, Display Order = 1 Section 1 - Group = G2, Display Order = 2 Section 2 - Group = G3, DisplayApp = 3  

Let me know what I do not know and I will try to understand it better ... or I will remove it and I never would have asked = P

It seems that the group is not an internal property of a section . Given this, it is only meaningful when parents are related to classes, I will not add group property, maybe create a section container square which exposes the group:

  Interface IGroupedSection { ISection section {get; } String group {get; }}  

Or create parent's property group, e.g.

  interface importer {void AddSection (string group, example section); IEnumerable & LT; ISection & gt; GetSectionsInGroup (string group); }  

You may need more than one section grouping strategy, after all, it is not best to include your section design in some type of collection type.