Design for (Grape E)X(pectations) – Week #4

This week, the team continued work on improving our prototype and also learned about the expectations for the Final Design Review.

In terms of work this week, the members of Grape Expectations have been divided into specialized roles based on what still needs to be done for the project. A CS and BE team are working on the development of an API scraper to find and integrate new data sources for the original fire model and the new smoke model. One of our other CS members is working on the integration of our current fire model into a microservice for Terraview. Another CS member is working on improvements to the drought model. Finally, the other BE member is researching and documenting pest and disease threat sources to evaluate whether a pest/disease model would be a feasible endeavor given the time left with the project. Everyone is full steam ahead and working towards overall improvement of the project.

In class, we learned about the concept of “Design for X,” a model used to determine what we will be designing for and why. This helps us keep in mind the end goal of our project while working on it, so that we can optimize the outcome. We have determined that our team specifically will be designing for testing and integration.

Design for X (DFX) | 10 Approaches of DFX Explained | Fractory
Different modalities of “Design for X”

Leave a Reply

Your email address will not be published. Required fields are marked *