Determining scope of the AWD-concept, a product owners view (Part 1)
December 4, 2014. admin.
Earlier this week Bricknode announced the release of the Account Worlds & Dimensions concept, AWD in short. During the development of a complete financial platform, like Bricknode Financial Systems (BFS), there is a constant battle going on with regards to how far the scope of the platform should stretch.
As the product owner of BFS this is one of my main issues to manage. Now, what do I mean by scope? Well, its not how many functions our platform should have but rather how far the platform should look into external accounts and how should it be used in terms of accounting. Before we go further into this topic I will start describing the main roles within BFS.
The House within BFS is the operator/owner of a BFS-instance. This is the company that owns the customers within the BFS-instance and who is responsible for everything that goes on. The House is the entity that exports accounting data files from BFS in order to import into its own accounting system and who is responsible for all client assets, settlement and reconciliation.
A House member is someone who is using an instance of BFS and has a relationship with the House of the instance. For example, an Advisor managing customers and creating orders within the BFS-instance. A House member is also a company or a private individual who is a customer of the House. The assets of a House member that is keep within the BFS-instance is managed by the House but the House member might want to be able to extract their own accounting files for only their own account within the BFS-instance.
A provider of a BFS-instance could be a fund marketplace offering fund trading to the customers of the House, it could be a quote feed provider which the House has contracted with among other things.
These concepts are the pilars of BFS.
Please watch the following short clip about the AWD-concept before you continue to read more articles of this series.
More Developer posts
How to connect to the BFS API using Visual Studio and our NuGet package - October 12, 2021
How to handle acquisition values for internal transfers via API - February 26, 2021
New API release including AutoGiro Orders - February 1, 2021
We are speeding up the release rate of new API functionality - January 24, 2021
Use JSON to work with complex data in custom fields - June 27, 2020
The great new feature called KycDate - February 16, 2020
Our API progress in release 2.23 of BFS - January 3, 2020
The difference between cash assets and currencies - December 12, 2019
Customize Bricknode Financial Systems and make it your own - December 5, 2019