<aside> 🛠 This project was a great way to put our knowledge of software engineering requirements to good use. This project expended my knowledge of GitHub, which was used to collaborate, and it introduced me to AsciiDoctor, with which I became proficient by the end. It also gave me more experience designing formal engineering diagrams, like use-case diagrams, activity diagrams, class diagrams, and more.
</aside>
<aside> 💡 During the project, I wondered how we could apply this to actually starting a project, which I will be doing in the near future with final capstone projects. I was curious what went into the planning when there was intent to design the system, how many features feasibly get cut out, and how a typical MVP could look.
</aside>
<aside> ⛔ Some roadblocks I hit included maintaining the Kanban board (including deciding the priority of issues and the designation of said issues between group members), and working with a Linux VM through WSL.
</aside>
<aside> 🚧 The main struggle for the group was figuring out the AsciiDoctor syntax as we went. We needed to make some in-depth tables, including our control tables, a RACI matrix, and many more. The syntax for hyperlinks in order to create a glossary and a bibliography were also odd to figure out with our initial limited AsciiDoctor knowledge.
</aside>