Close
AlgoliaLogoLight
Close full mode
logo

Revenue Expense App Modelling Diagram

Git RepositoryEdit on Github

Revenue/Expense App modelling diagram

Table per hierarchy (TPH)

  • Transaction table represent table per hierarchy which contains two types: Transaction and CalculatedAmountTransaction which derives from Transaction

ER diagram

TransactionintIdvarcharDiscriminatornvarcharTypeintCategoryIdDateTimeCreatedUtcDatenvarcharUnitNamedecimalNumberOfUnitdecimalPricePerUnitdecimalAmountintTagIdAttachedFileintIdintTransactionIdstringUrlCategoryintIdstringNameTagintIdstringNamecontainshashas

Class diagram

Transaction+int Id+TransactionType Type+TransactionCategory Category+DateTime CreatedUtcDate+decimal Amount+string NoteCalculatedAmountTransaction+UnitName UnitName+decimal NumberOfUnit+decimal PricePerUnit+decimal Amount« enumeration »TransactionTypeRevenueExpense« enumeration »UnitNameKilogramTransactionCategory+int Id+string NameTag+int Id+string Name110..11

Questions

  • Should I rename Tag to LogicalGroup?
  • Is it okay to create TransactionType and TransactionCategory to enumeration?
Loading comments...