[PoC to v0.1 Migrations] - UML Key Services/Objects/Functionalities to more easily manage migrations from

[idiom-bytes]

Problem:

As we migrate PoC systems over to backend services & products, it would benefit us from having these objects documented from a very simple UML-Like fashion, where we can identify their main functions/interfaces/parameters, and more easily follow along in terms of tasks + implementation + verify they are migrated correctly.

Example: DAOBot

• What are all the systems in here?
• What are their functions and objects?
• What are their parameters?
• Now that these are laid out, can I map them to the new systems we're building?

DoD:

• [ ] Write out existing services/objects/functionality in an UML diagram.
• [ ] I should be able to understand DAOBot, it's objects/functionalities/parametrs
• [ ] I should be able to understand where those functionalities are moving into the new infrastructure
• [ ] I should be able to map from UML to new infrastructure, and verify that all functionlity is in place and is verifiable