Please enable JavaScript.
Coggle requires JavaScript to display documents.
Fowler - Coggle Diagram
Fowler
-
Account
When people think about accounts, they usually think about monetary accounts. However accounts can be used for more than money. If I have twenty four bottles of Black Butte in my refridgerator, I can think about that as an account. When I take a couple of bottles out for Cindy and me to have with our Rogan Josh, I can think of that as an withdrawel of two bottles.
There are two essential qualities to the account pattern: keeping a collection of entries and providing summarizing information over those entries.
when to use
The first is where there is some value where I need current value, historical values, and to be able to keep a history of changes to that value. If I only need the current value I can just use a field. If I only need current and historic values I can use Temporal Property - although I'm not sure that Account is any more complicated than Temporal Property.
The second case is where I'm already using Accounting Entry (15) but I want to pull together all the entries for a common set of descriptions. This makes it easier to compare like entries with like.
It's not difficult to see the anlaogy between Account and the idea of version control systems. Indeed you can think of Account as applying the idea of verison control to money.
However I don't think that means that you can use Account for non quantitative situations. While I guess you can think of a code version control as balances, withdrawels, and deposits to text files; for me that's stretching the analogy a little too far.
The basic behavior for accounts is actually very straightforward, consisting of collecting together entries (Accounting Entry) and providing summary information.
-
BiModal IT
Bimodal IT is based on separation of IT systems by layer rather than the underlying business activity. Bimodal IT separates rapid-moving front-end systems of engagement from slow-but-reliable backend systems of record.
-
-