# Further Reading
# Team Resources
During the Reference Architecture planning work sessions, the Team made use of different resources to build and retain a record of discussions and to build the Use Case Models required to support all of the possible stakeholder requirements for the new architecture.
Please feel free to visit the Team’s resources using the links provided.
P.S. One resource that you might find particularly useful is Miro, where we keep a record of all of the Bounded Context Use Cases in use by the system.
Note: Please bear in mind that the Reference Architecture document is a living document, and as a result is updated from time to time for various reasons. This means that the resources that we have shared with you are still in use and will change occasionally.
| Resource | Purpose | Link/URL |
|---|---|---|
| Miro | Build Use Case flow diagrams | Miro - Mojaloop Reference Architecture (opens new window) |
| Google Docs | Session work notes for the team providing details of Reference Architecture for inclusion in the proposal and introductory documentation. | Mojaloop 2.0 Reference Architecture Work Sessions (opens new window) |
| Google Sheets | Record of Common Interfaces in use in the Switch architecture, along with various other bits and pieces. | Mojaloop 2.0 Reference Architecture (opens new window) |
# Reference Articles and Documents
The resources below were sourced to provide additional insight into the architecture models that have been implemented.
| Resource | Details |
|---|---|
| Domain-Driven Design, from Wikipedia, the free encyclopedia (opens new window) | Publisher: Wikipedia, the free encyclopedia; Author: Community; Date: non-specific; ±7mins to read |
| Domain, Subdomain, Bounded Context, Problem/Solution Space in DDD: Clearly Defined (opens new window) | Publisher: Medium.com; Author: Nick Tune; Date: 11/07/2020; ±7mins to read |
| Strategic Domain-Driven Design (opens new window) | Publisher: Vaadin.com; Author: Petter Holmstrom |
| Pattern: Decompose by Subdomain Context (opens new window) | Publisher: Microservices Architecture; Author: Chris Richardson |
| Rest API Tutorial (opens new window) | Publisher: Self-published; Author: Todd Fredrich; License: Creative Commons Attribution ShareAlike 4.0 International License (opens new window) |
| Use Case, from Wikipedia, the free encyclopedia (opens new window) | In brief, and quoting from the opening blurb of the Wikipedia article, a use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal. The actor can be a human or other external system. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements. |
# Project Iteration Convenings
The resources below are inclusions to the Mojaloop Technical Convenings by the Reference Architecture Team starting at the beginning of 2021. Resources include notes, slides, and video recordings.
| Project Iteration (PI) | Period | Description | Link/URL |
|---|---|---|---|
| PI-13 | January 2021 | Mojaloop Performance, Scalability and Architecture Update | PI-13 Slides & Recording (opens new window) |
| PI-14 | April 2021 | Opening and Mojaloop Reference Architecture and TigerBeetle | PI-14 Recording (YouTube) (opens new window) |
| PI-15 | July 2021 | Reference Architecture v1.0 | PI-15 Resources (opens new window) / PI-15 Video Library (YouTube) (opens new window) |
| PI-16 | October 2021 | Reference Architecture and V2 update | PI-16 Agenda (opens new window) / PI-16 Video Library (opens new window) |
| PI-17 | January 2022 | Reference Architecture: Documentation and v.Next Updates | PI-17 Reference Architecture Presentation (YouTube) (opens new window) |