The section that I choose to focus on is Thea’s Pantry Workflow. The workflow is an important part of this application because the workflow facilitates the flow of information, tasks, and events. A workflow is a blueprint for developers to follow on how to use git. Everyone on the team has access to the information that’s needed to complete the required actions. In Thea’s Pantry, the blueprint is easily readable and understandable on how to use git for this application. Any developer looking at the workflow or any new developers added to the team will be able to follow this process easily. The workflow also lets developers know if any push/commits that failed is explained as to why when using commitlint.

From the blog CS@Worcester – The Dive by gonzalezwsu22 and used with permission of the author. All other rights reserved by the author.

After reading  the items from Thea’s pantry, user stories is the item that I find interesting because it provides me sufficient information that I need to know about the project. The user stories of this project has a total of five stories which are used to describe how the software will interact with the end users through access management, guest visiting, (food) inventory, and the monthly reporting. In other words, the user stories tell me that what inputs should be received and what output should be generated for each interaction between the software and the end users.

On the other hand, I find the user stories useful because it helps me better understand the project’s goals, and also understand the architectural parts more easily. Based on that, I can also figure out what I have to do in my capstone’s project.

From the blog CS@Worcester – T's CSblog by tyahhhh and used with permission of the author. All other rights reserved by the author.

What is Thea’s Pantry?

Thea’s Pantry is a food bank for Worcester State University community. It helps students, staff, and faculty who require food and other necessities. This service runs out of the Student Center on campus, offers a confidential service to people in need. There are a lot of positive things about Thea’s Pantry. The Thea’s Pantry client solution is described in full in the Documentation project, which includes User Stories, Architecture, Technology, Workflow, Release Process. Since I came from a retail background, architecture is a very interesting component for me because it helps layout the foundation of the business in general. For example, in this project, the architecture gives info about GuestInfoSystem, InventorySystem, ReportingSystem, IAMSystem (Third-party), EventSystem (Third-party). The Architecture allows the users to interact with the frontend and backend, where the guests will be able to interact with the frontend.

From the blog CS@Worcester – Site Title by proctech21 and used with permission of the author. All other rights reserved by the author.

I wanted to reread and write more about the architecture of Theas Pantry because it gave a detailed layout of multiple components, some of which are projects being worked on by some teams in the class. The main components shown are the standalone integration tests for GuestInfoSystem, InventorySystem, and ReportingSystem, and then a full integration test for Thea’s Pantry. I liked how it was divided into the standalone tests for the different components that will be worked on and used as a reference for the developers, and it is helpful to also show how they all come together in Thea’s Pantry with the added components such as IAMSystem and DirectorySystem for the full integration.

From the blog Jeffery Neal's Blog by jneal44 and used with permission of the author. All other rights reserved by the author.

I took a look at the user stories documentation to familiarize myself with the process of how everything works. The user stories are organized in a way that I can understand the step by step flow of the processes. I believe that this document will be pretty useful to refer to when working on the project. That being said, I noticed the pantry log entry form has been modified with all of the donation options crossed off. It would make sense to have separate forms for guests and donors. One thing I am curious about though is how they transfer the information from the google forms to the database, I will probably have to look into it some more.
Link: https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/documentation/-/blob/main/UserStories.md

From the blog CS@Worcester – Null Pointer by vrotimmy and used with permission of the author. All other rights reserved by the author.

Another aspect of preparation for my Software Development Capstone project is to become familiar with Thea’s Pantry. Thea’s Pantry is a section of LibreFoodPantry that is being worked on by the staff and students of Worcester State University.

One important takeaway from this pantry’s data is that most, if not all, of the pantry’s technology is familiar to me; from OpenAPI and VUE to MongoDB and Docker, these technological tools have all been used by me in a previous class at Worcester State. I chose to write this down due to the fact that I find it nice that the flow of knowledge seems to be “continuous” as opposed to “discrete”. By this, I mean that aspects of one class are used in others, instead of being dropped entirely once the semester ends.

From the blog CS@Worcester – mpekim.code by Mike Morley (mpekim) and used with permission of the author. All other rights reserved by the author.

I found the architecture used in Thea’s Pantry interesting. It was nice to see the UML diagrams as they help tremendously with understanding how the architecture works. It is also nice seeing the individual pieces of the system, and then seeing them all together at the end, seeing the entire system come together. I also found the workflow interesting as well, having a new branch for every feature/fix/refractor, each being associated with a merge request when the branch is created. Then, using conventional commits, and commit merging. It is good to see this level of organization in the workflow process.

From the blog CS@Worcester – Erockwood Blog by erockwood and used with permission of the author. All other rights reserved by the author.

One of the things that I found surprising while going through the Thea’s pantry project was in the UserStories.md file, it includes a .PDF file of the form that the staff would fill out for each visit. What surprised was not that the form was already made or that it was included in the Markdown file but rather it had a copy of the form with strikethroughs. I found this both surprising and interesting because the form looks mostly finished so I would normally assume the version of the form on GitLab would be a polished version without any markups or strikethroughs. I chose to write about this because it made me wonder if there was more that needed to be added or fixed on the form. But seeing the strikethrough also helps me see their thought process as to which they removed or moved certain things in the document.

From the blog CS@Worcester – Just a Guy Passing By by Eric Nguyen and used with permission of the author. All other rights reserved by the author.