From cb6864355a1ad4f68d1da47df63fc57b312c311c Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Mon, 28 Nov 2022 14:30:25 +1300 Subject: [PATCH] vault backup: 2022-11-28 14:30:25 --- ...lockchain Through a Case Study of Insolar.md | 2 +- ...erature review on blockchain governance.md | 13 ++ content/notes/blockchain-project.md | 15 +-- content/notes/media.md | 6 +- content/notes/review-i201.md | 120 ------------------ 5 files changed, 19 insertions(+), 137 deletions(-) delete mode 100644 content/notes/review-i201.md diff --git a/content/notes/Permissionless and Permissioned, Technology-Focused and Business Needs-Driven — Understanding the Hybrid Opportunity in Blockchain Through a Case Study of Insolar.md b/content/notes/Permissionless and Permissioned, Technology-Focused and Business Needs-Driven — Understanding the Hybrid Opportunity in Blockchain Through a Case Study of Insolar.md index feaacc6eb..e570fd784 100644 --- a/content/notes/Permissionless and Permissioned, Technology-Focused and Business Needs-Driven — Understanding the Hybrid Opportunity in Blockchain Through a Case Study of Insolar.md +++ b/content/notes/Permissionless and Permissioned, Technology-Focused and Business Needs-Driven — Understanding the Hybrid Opportunity in Blockchain Through a Case Study of Insolar.md @@ -3,7 +3,7 @@ title: "Permissionless and Permissioned, Technology-Focused and Business Needs-D tags: link: doi: 10.1109/TEM.2020.3003565 date: -authors: H. M. Kim, H. Turesson, M. Laskowski, A. F. Bahreini +authors: --- # Summary diff --git a/content/notes/a systematic literature review on blockchain governance.md b/content/notes/a systematic literature review on blockchain governance.md index 2795983ab..91183e408 100644 --- a/content/notes/a systematic literature review on blockchain governance.md +++ b/content/notes/a systematic literature review on blockchain governance.md @@ -7,6 +7,7 @@ authors: --- # Summary +As the title states, this paper is a systematic literature review on blockchain governance. # Extracts @@ -56,4 +57,16 @@ p14 "process mechanisms describe the steps of blockchain development via the gov - How is it implemented - Process Mechanisms - steps of development via governance meta-rules - Product Mechanisms - features of a blockchain, as outcomes of the development process + # Related +- J. Werner, S. Frost, and R. Zarnekow, “Towards a taxonomy for governance mechanisms of blockchain-based platforms,” 2020. +- Z. Bao, K. Wang, and W. Zhang, “An auditable and secure model for permissioned blockchain.” New York, NY, USA: Association for Computing Machinery, 2019. +- Governance in the Blockchain Economy: A Framework and Research Agenda +- The invisible politics of bitcoin: governance crisis of a decentralized infrastructure +- Regulatory issues in blockchain technology +- The internal and external governance of blockchain-based organizations: Evidence from cryptocurrencies +- M. Finck, Blockchain regulation and governance in Europe. Cambridge University Press, 2018 +- S. Azouvi, M. Maller, and S. Meiklejohn, “Egalitarian society or benevolent dictatorship: The state of cryptocurrency governance,” in Financial Cryptography and Data Security, A. Zohar, I. Eyal, V. Teague, J. Clark, A. Bracciali, F. Pintore, and M. Sala, Eds. Berlin, Heidelberg: Springer Berlin Heidelberg, 2019, pp. 127–143. +- W. Reijers, I. Wuisman, M. Mannan, P. De Filippi, C. Wray, V. Rae-Looi, A. C. Velez, and L. Orgad, “Now the ´ code runs itself: On-chain and off-chain governance of blockchain technologies,” Topoi, pp. 1–11, 2018. +- B. D. Trump, M. Florin, H. S. Matthews, D. Sicker, and I. Linkov, “Governing the use of blockchain and distributed ledger technologies: Not one-size-fits-all,” IEEE Engineering Management Review, vol. 46, no. 3, pp. 56–62, 2018. +- T. John and M. Pam, “Complex adaptive blockchain governance,” in MATEC Web of Conferences, vol. 223. EDP Sciences, 2018, p. 01010. \ No newline at end of file diff --git a/content/notes/blockchain-project.md b/content/notes/blockchain-project.md index bd30f6101..d92ff14e0 100644 --- a/content/notes/blockchain-project.md +++ b/content/notes/blockchain-project.md @@ -88,20 +88,7 @@ Blockchain technology falls into two distinct classes: open (permissionless) blo - https://www.ndss-symposium.org/wp-content/uploads/2019/02/ndss2019_02A-2_Zhang_paper.pdf A Treasury System for Cryptocurrencies: Enabling Better Collaborative Intelligence - Quadratic voting - https://ieeexplore.ieee.org/document/8818409 # A Full-Spectrum Blockchain-as-a-Service for Business Collaboration -- J. Werner, S. Frost, and R. Zarnekow, “Towards a taxonomy for governance mechanisms of blockchain-based platforms,” 2020. -- Z. Bao, K. Wang, and W. Zhang, “An auditable and secure model for permissioned blockchain.” New York, NY, USA: Association for Computing Machinery, 2019. -- Governance in the Blockchain Economy: A Framework and Research Agenda -- The invisible politics of bitcoin: governance crisis of a decentralized infrastructure -- Regulatory issues in blockchain technology -- The internal and external governance of blockchain-based organizations: Evidence from cryptocurrencies -- M. Finck, Blockchain regulation and governance in Europe. Cambridge University Press, 2018 -- S. Azouvi, M. Maller, and S. Meiklejohn, “Egalitarian society or benevolent dictatorship: The state of cryptocurrency governance,” in Financial Cryptography and Data Security, A. Zohar, I. Eyal, V. Teague, J. Clark, A. Bracciali, F. Pintore, and M. Sala, Eds. Berlin, Heidelberg: Springer Berlin Heidelberg, 2019, pp. 127–143. -- W. Reijers, I. Wuisman, M. Mannan, P. De Filippi, C. Wray, V. Rae-Looi, A. C. Velez, and L. Orgad, “Now the ´ code runs itself: On-chain and off-chain governance of blockchain technologies,” Topoi, pp. 1–11, 2018. -- B. D. Trump, M. Florin, H. S. Matthews, D. Sicker, and I. Linkov, “Governing the use of blockchain and distributed ledger technologies: Not one-size-fits-all,” IEEE Engineering Management Review, vol. 46, no. 3, pp. 56–62, 2018. -- T. John and M. Pam, “Complex adaptive blockchain governance,” in MATEC Web of Conferences, vol. 223. EDP Sciences, 2018, p. 01010. - - - +- [systematic review Related papers](notes/a%20systematic%20literature%20review%20on%20blockchain%20governance.md#Related) **Other maybe relevant Papers** diff --git a/content/notes/media.md b/content/notes/media.md index 84aad48cd..2d796b28f 100644 --- a/content/notes/media.md +++ b/content/notes/media.md @@ -6,9 +6,9 @@ tags: --- # Albums -- https://open.spotify.com/album/63EL3UcZwzgO8rLyCnvNj6?si=TBa8bX_sRZ28oPDsfJjUNw +- https://open.spotify.com/album/63EL3UcZwzgO8rLyCnvNj6 - plantation lullabies -- +- the way through, deca # Books - 2022 @@ -28,6 +28,8 @@ tags: - Jane Eyre - a midsummer nights dream - the second sex + - cryptonicon + - the amazing maurice and his educated rodents - future - actual air david berman - woman in the dunes diff --git a/content/notes/review-i201.md b/content/notes/review-i201.md deleted file mode 100644 index 0cf792aad..000000000 --- a/content/notes/review-i201.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: "review-i201" -aliases: -tags: - ---- - -# soft. dev. methods -- [SDLC](notes/systems-development-life-cycle.md) -- [1 traditional](notes/approaches-to-systems-development.md#1%20traditional) (predictive) vs [1 object oriented](notes/approaches-to-systems-development.md#1%20object%20oriented) (flexible) -- [UP](notes/unified-processes.md) (OO) -- [scrum](notes/scrum.md) -- [xp](notes/extreme-programming.md) - -# requirements engineering -- [business-process](notes/business-process.md) re engineering -- [requirements](notes/requirements.md) - - properties of good ones [requirements-guidelines](notes/requirements-guidelines.md) - - functional vs not [furps](notes/furps.md) - - importance (moscow) -- elicitation [requirements-elicitation](notes/requirements-elicitation.md) - - stakeholders techniques [stakeholders](notes/stakeholders.md) [Stakeholders](notes/requirements-elicitation.md#Stakeholders) - - outcome validation [Validation of Requirements](notes/requirements-elicitation.md#Validation%20of%20Requirements) - -# business functions and use cases -- business functions - how to identify [1 Id business functions](notes/business-functions.md#1%20Id%20business%20functions) -- use cases - how to model [2 Use case](notes/business-functions.md#2%20Use%20case) -- uml use case diagrams [use-case-diagrams](notes/use-case-diagrams.md) - - actors usecases [2 1 Actor](notes/use-case-diagrams.md#2%201%20Actor) [2 2 Use case](notes/use-case-diagrams.md#2%202%20Use%20case) - - associations, dependencies [2 3 Association](notes/use-case-diagrams.md#2%203%20Association) [2 5 Dependency](notes/use-case-diagrams.md#2%205%20Dependency) - -# BPM -- business processes and how the are modelled [business-process](notes/business-process.md) [[bsin]] -- BPMN vs (high level) UML activity [business-process-model-and-notation](notes/business-process-model-and-notation.md) [activity-diagrams](notes/activity-diagrams.md) - -# Data modelling - - erd concepts [ERD](notes/entity-relationship-diagrams.md) - - subtypes [subtypes](notes/entity-relationship-diagrams.md#subtypes) - - parrallel and reursive relationships [parallel relationship](notes/entity-relationship-diagrams.md#parallel%20relationship) [recursive relationship](notes/entity-relationship-diagrams.md#recursive%20relationship) - - historical data [dealing with data history](notes/entity-relationship-diagrams.md#dealing%20with%20data%20history) - - normalisation [normalisation](notes/normalisation.md) - - redundancy and anomalies [redundancy-and-anomalies](notes/redundancy-and-anomalies.md) - - function and multivaly dependencies [dependencies](notes/dependencies.md) - - normal forms [2 Normal forms](notes/normalisation.md#2%20Normal%20forms) - -# Modelling object structure -- oop concepts [10-oop-concepts-and-uml](notes/10-oop-concepts-and-uml.md) - - state behaviiour encapsilation - - class vs instance, object reference -- uml diagrams [what-are-uml-diagrams](notes/what-are-uml-diagrams.md) - - steriotypes, visibility, multiplicity [1 Stereotypes](notes/class-diagrams.md#1%20Stereotypes) [3 1 multuplicity](notes/class-diagrams.md#3%201%20multuplicity) - - specialsation/generalisation, navigability [3 8 Specialisation generalisation](notes/class-diagrams.md#3%208%20Specialisation%20generalisation) [3 4 Navigability](notes/class-diagrams.md#3%204%20Navigability) - - erd vs class diagram [4 Domain class model](notes/class-diagrams.md#4%20Domain%20class%20model) vs [5 System class model](notes/class-diagrams.md#5%20System%20class%20model) -# object behaviour -- inheritance [1 Inheritance](notes/modelling-behaviour.md#1%20Inheritance) - - specialisation vs implementing an interface [1 1 Via Specialisation](notes/modelling-behaviour.md#1%201%20Via%20Specialisation) vs [1 2 Via Interface](notes/modelling-behaviour.md#1%202%20Via%20Interface) - - separation of public private API (programming to interface) [1 3 Public vs Private](notes/modelling-behaviour.md#1%203%20Public%20vs%20Private) -- rich vs anaemic domaini models "processor objects" [2 Behaviour](notes/modelling-behaviour.md#2%20Behaviour) -- modelling behaviour with uml [modelling-behaviour](notes/modelling-behaviour.md) - - sequnce diagrams [sequence-diagrams](notes/sequence-diagrams.md) - - low level activity and state diagrams [activity-diagrams](notes/activity-diagrams.md) - -# round trip engineering -- foward engineering [UML to Java Foward Engineering](notes/uml-java-forward-engineering.md) - - erd -> SQL - - uml class diagram -> e.g., java - - correspondenc with use cases -- reverse engineering (code <- diagrams) [reverse engineering](notes/uml-java-reverse-engineering.md) - -# Data access -- data persistence file vs database [Data Access](notes/data-access.md) -- database APIs (JDBC etc) [JDBC](notes/java-database-connectibity.md) -- DAOs [DAO](notes/data-access-object.md) - - oner per use case (not just per domain class) - - often programming via DAO interface - -# Database transactions -- ACID [ACID](notes/18-advanced-sql-1.md#ACID) -- what and why [Transactions](notes/18-advanced-sql-1.md#Transactions) -- commit vs rollback [commit and rollback](notes/18-advanced-sql-1.md#commit%20and%20rollback) - -# SQL select -- select from where [Select](notes/19-advanced-sql-2.md#Select) -- sorting grouping aggregation [Aggregation and grouping](notes/19-advanced-sql-2.md#Aggregation%20and%20grouping) -- view, inner and outer joins, subqueries [Inline views](notes/19-advanced-sql-2.md#Inline%20views) [Joins](notes/19-advanced-sql-2.md#Joins), [Subqueries](notes/19-advanced-sql-2.md#Subqueries) - -# data integrity -[20-data-integrity](notes/20-data-integrity.md) -- nulls and their issues -- business rules, databas contrainsts, veification, validation [Validation](notes/20-data-integrity.md#Validation) [Verification](notes/20-data-integrity.md#Verification) [Check constrainsts](notes/20-data-integrity.md#Check%20constrainsts) [Primary and foreign key constraints](notes/20-data-integrity.md#Primary%20and%20foreign%20key%20constraints) -- in-database vs outside database -- in data base automation: sequence, triggers, stored procedures [Automation](notes/20-data-integrity.md#Automation) - -# softare architectures, patterns, and templates -[08-business-patterns](notes/08-business-patterns.md) -- monolithic vs client/server vs distributed (services) [Monolithic architecture](notes/software-architectures.md#Monolithic%20architecture) -- separation of reponsilbilities [Separation of reponsibilities](notes/software-architectures.md#Separation%20of%20reponsibilities) -- "standard patters" of design (recognise) [Generic old info sys architecture](notes/software-architectures.md#Generic%20old%20info%20sys%20architecture) -- sysstem templates [system-templates](notes/system-templates.md) - -# performance and security -- performance requirements [Performance requirements](notes/22-performance-and-security.md#Performance%20requirements) - - how to quantify and measure - - response time, workload, scalability - - caching pooling - - system reliability -- security and integrity requirements [Integity and securuty controls](notes/22-performance-and-security.md#Integity%20and%20securuty%20controls) - - consider throughout development - - authentication and authorisation - - principle of least privilege - - hat a user should only have access to what they absolutely need in order to perform their responsibilities, and no more. - -# cost benefit analysis - - project feasbility [justifying a project](notes/25-cost-benefit-analysis.md#justifying%20a%20project) - - need, funding, strong will - - duration, priority, rick, uncertainty - - should we, can we, is it worth it? - - economic feasibility: [costs and benefits](notes/25-cost-benefit-analysis.md#costs%20and%20benefits) - - costs vs benefits (tangigble/intangible) - - payback time (break even), NPV, ROI \ No newline at end of file