Databases
StackOverflow2013
Postsdbo
POBusiness Rule Split among two classes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBusiness Rule Split among two classes
    primarykey
    data
    text
    <p>I have a project allocation domain with the following business rules</p> <ol> <li>When a new employee is getting allocated to a project the total expenditure should not exceed the Budget Amount.</li> <li>For an employee the total allocation percentage should not exceed 100%</li> </ol> <p>I have created entities as shown below created in <code>C#</code>. </p> <p><strong>QUESTION</strong></p> <p>The <code>Allocate</code> logic is split across two classes – Project and Employee..The <code>List&lt;Allocation&gt;</code> is passed as a parameter to the Allocate method rather than adding as property of the class... Is it correct approach or do I need to add <code>List&lt;Allocation&gt;</code> as property in these two classes?</p> <p>Note: </p> <p><strong>Database</strong></p> <p><img src="https://i.stack.imgur.com/c27VX.png" alt="enter image description here"></p> <p><strong>Entitles</strong></p> <p><img src="https://i.stack.imgur.com/2cEyL.png" alt="enter image description here"></p> <p><strong>Code</strong></p> <p><em>Project</em></p> <pre><code> public class Project { public int ProjectID { get; set; } public int BudgetAmount { get; set; } public string ProjectName { get; set; } public void Allocate(Role newRole, int newPercentage, Employee newEmployee, List&lt;Allocation&gt; existingAllocationsInProject) { int currentTotalExpenditure = 0; if (existingAllocationsInProject != null) { foreach (Allocation alloc in existingAllocationsInProject) { int allocationExpenditure = alloc.Role.BillRate * alloc.PercentageAllocation / 100; currentTotalExpenditure = currentTotalExpenditure + allocationExpenditure; } } int newAllocationExpenditure = newRole.BillRate * newPercentage / 100; if (currentTotalExpenditure + newAllocationExpenditure &lt;= BudgetAmount) { List&lt;Allocation&gt; existingAllocationsOfEmployee = GetAllocationsForEmployee(newEmployee.EmployeeID); bool isValidAllocation= newEmployee.Allocate(newRole, newPercentage, existingAllocationsOfEmployee); if (isValidAllocation) { //Do allocation } else { throw new Exception("Employee is not avaiable for allocation"); } } else { throw new Exception("Budget Exceeded"); } } } </code></pre> <p><em>Employee</em></p> <pre><code>public class Employee { public int EmployeeID { get; set; } public string EmployeeName { get; set; } public bool Allocate(Role newRole, int newPercentage, List&lt;Allocation&gt; existingAllocationsOfEmployee) { int currentTotalAllocation = 0; if (existingAllocationsOfEmployee != null) { foreach (Allocation alloc in existingAllocationsOfEmployee) { currentTotalAllocation = currentTotalAllocation + alloc.PercentageAllocation; } } if (currentTotalAllocation + newPercentage &lt;= 100) { return true; } return false; } } </code></pre> <p><strong>References</strong></p> <p>Following is from <a href="https://stackoverflow.com/questions/5017969/repository-pattern-without-an-orm">Repository Pattern without an ORM</a></p> <blockquote> <p>What behaviour is there that requires the customer to have a list of orders? When you give more thought to the behaviour of your domain (i.e. what data is required at what point) you can model your aggregates based around use cases and things become much clearer and much easier as you are only change tracking for a small set of objects in the aggregate boundary.</p> <p>I suspect that Customer should be a separate aggregate without a list of orders, and Order should be an aggregate with a list of order lines. If you need to perform operations on each order for a customer then use orderRepository.GetOrdersForCustomer(customerID); make your changes then use orderRespository.Save(order);</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USLijo
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBusiness Rule Split among two classes
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBusiness Rule Split among two classes
      1. USLijo
      1. VTBountyStart
    1. COReferences 1. http://stackoverflow.com/questions/16426112/how-to-choose-ddd-aggregate/16426701#16426701 2. http://stackoverflow.com/questions/5694241/ddd-the-rule-that-entities-cant-access-repositories-directly 3. [Services in Domain-Driven Design (DDD)](http://gorodinski.com/blog/2012/04/14/services-in-domain-driven-design-ddd/)
      singulars
      1. POBusiness Rule Split among two classes
      1. USLijo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload