-
Class Diagrams and documentation of design patterns and SOLID principles
-
Let's take a step back and have a call to brainstorm and document the design decisions we want to stick to here. This will also capture wider interoperability issues (related: #6 and https://github.co…
-
# Information Architecture
These tasks represents creation of our information architecture for the UI/UX
- [ ] Create a requirements specification document
- [x] Create a mind map
- [x] Create a user…
-
-
Create [Game Design Document](https://docs.google.com/document/d/13fX321W-eeNtgqgCcP057t_KMlanBf3pnOwanqHygks/edit?usp=drive_link) with folowing sections:
- [ ] Title
- [ ] Game overview
- [ ] ● Gene…
-
Section 2 of NEA, due on 16th October 2024
-
Create ARDS:
Adding design decision rationale to your project on GitHub is essential for maintaining clarity and providing context for future contributors. Here's how you can effectively document d…
-
## Description
Project maintainers have decided to maintain the current and future architecture and design documents of the various OpenEBS engines/features in a single location in the curr…
-
**Problem description**
We have over time added several rules, naming conventions etc. in the design guideline document that are "must" for Camara subprojects to follow and incorporate in their spec …
-
This will be live-updated with minimal formatting until it's time for it to be turned in. Any internal code documentation goes here