|
|
| (19 intermediate revisions by the same user not shown) |
| Line 3: |
Line 3: |
| <blockquote><br> | | <blockquote><br> |
| {{TOCleft}} | | {{TOCleft}} |
| | = Purpose = |
| | |
| | The primary purpose of the <b>Redvant</b> moniker is to name the separation of some product lines from their domain space aspects. Products developed under its rubric can be compiled for operation strictly on the basis of the FOSS or COTS software upon which they are based without any integration with DS though in some cases this can gut the app if presentation of a DS feature was its purpose. A non-DS application can then supply a new purpose. My <b>tl;dr</b> line and other apps sold on stores may thus have core function repurposed to such new apps without committing to DS ops. |
| | |
| | However this separation is only in evidence at the time of it's application in such non DS development activity. Redvant exposition is largely or entirely in terms of its use in domain space and does not further comment on this separability . |
| | |
| = Précis = | | = Précis = |
| <span class=plainlinks> | | <span class=plainlinks> |
| Line 13: |
Line 19: |
| and "vant" is just from haskell-servant. | | and "vant" is just from haskell-servant. |
| </div><br><span class=plainlinks> | | </div><br><span class=plainlinks> |
| Use of Apache [https://isis.apache.org <font color=lime>ISIS</font>] or other fat DDD pkg is intended later in the development our overall DDD product line engineering (i.e. a 'redvantis'). Some enterprise users may prefer the java basing of ISIS or an ERP core and these future developments are anticipated after the foundational elements are established. | | Use of Apache [https://isis.apache.org <font color=lime>ISIS</font>] or other fat DDD pkg is intended later in our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer the java basing of ISIS or an ERP core and this is anticipated for later development. |
| </span> | | </span> |
|
| |
|
| Line 21: |
Line 27: |
|
| |
|
| For pragmatic reasons, it is accounting oriented and doesn't address the full actual scope of use as implied by § 2.2 below, which could be confusing. | | For pragmatic reasons, it is accounting oriented and doesn't address the full actual scope of use as implied by § 2.2 below, which could be confusing. |
| | |
| | Later, there will coverage in the Docs DCMS volume. |
|
| |
|
| == Scope == | | == Scope == |
| Line 34: |
Line 42: |
|
| |
|
| == Transacting == | | == Transacting == |
| ==== django-oscar ====
| | § deleted see history. |
| | |
| <blockquote class=plainlinks>
| |
| I chose this back end pkg because of its claim of being domain driven. That claim, as it turns out is based on dynamic class loading. So without quibbling and as its sole focus on txing is convenient it turns out to be an early anchor in my DDD praxis.
| |
| | |
| Provides front end for tx'ing objects. We introduce the notion of an ephemeral tx ledger, oriented to a single, possibly complex tx which is connected to the others (§ 2.4.1.1). Like 'ledger', transaction 'tx' is defined to be an abstract change to a ledger. The process of application of a real instance of such change to persistent ledgers is called settlement.
| |
| | |
| Consequently, any transaction requirements are realized as constraints on the [https://django-oscar.readthedocs.io/en/3.1/ref/apps/index.html 16 Oscar Apps] or new classes in its framework.
| |
| </blockquote>
| |
| | |
| == Accounting == | | == Accounting == |
| <blockquote>
| | § deleted see history. |
| === Design Principles ===
| |
| <blockquote>
| |
| | |
| ==== Abstraction and Unity ====
| |
| <blockquote>
| |
| Ledgers are abstract entities realized differently in different packages but from the perspective of a single accounting ontology.
| |
| | |
| Unless qualified, 'ledger' means double entry accounting ledger, a fundamental concept conserved across all ledger implementations, the basis of their unification.
| |
| </blockquote>
| |
| ==== Security and Transparency ====
| |
| <blockquote>
| |
| This is a requirement that requires a balancing of interests as transparency can conflict with security. Users. i.e. individuals and groups (including firms) may opt
| |
| for near complete opacity of their accounts which has been the general norm. The System, domain space, however is required to have open books and line items
| |
| against its books are why it's not complete opacity.
| |
| </blockquote>
| |
| </blockquote>
| |
| | |
| === Back End Packages ===
| |
| <blockquote>
| |
| ==== hledger ====
| |
| | |
| The users personal ledger. It may be convenient for the group administrators personal ledger to be used as the group ledger and this is the assumed default. hledger-web is not duplicated, nonetheless because of its accounting function and system integration, it is deemed a part of 'redvant'.
| |
| | |
| ==== ledger ====
| |
| | |
| Basis of the System Journal, how the system views all ledgers. AKA ledgercli, ledger c++, the original that was ported to hledger.
| |
| | |
| ==== SQL-Ledger / LedgerSMB ====
| |
| | |
| The enterprise Chart of Accounts (COA), typical of a ERP type ledger. Individuals don't normally view this package and its interface is mod perl based.
| |
| Every O class user has its own COA.
| |
| The System COA is visible to all AKPERSONs.
| |
| | |
| </blockquote>
| |
| | |
| </blockquote>
| |
|
| |
|
| = Sonstiges = | | = Sonstiges = |
