The last week was spent diving into our documentation. We adjusted our main outline to include a background of the project and site, what ideas worked both last year and this year, and what ideas have not worked. Per Latifah’s recommendation, we aim to provide next year’s team as thorough a body of information as possible. Below are a few of the aspects we have focused on to ease the project familiarity process for the 2021 team.
By providing an overview of the tools and materials available at Chavin, Huaraz, and Lima, we’ll hopefully leave next year’s team better prepared to accurately plan how and where they will source all their materials. Additionally, both the 2019 and 2020 teams have come up with an extensive list of technical requirements. Aware that many of these specifications include project-specific terms, we define key terms such as “modularity,” “water permeability,” and “reversibility,” which define the overarching goals of our project. Defining these terms was important in terms of creating specific technical specifications that a team can test against through experimentation. Another relevant section we have created covers things one might think would work but actually wouldn’t. These were ideas, such as ordering various large parts online, we had spent some time discussing before ultimately realizing they weren’t feasible. We hope these explanations will save the 2021 team time and allow them to get started revising requirements and prototyping as quickly as possible. Our next steps for this week are to continue synthesizing information from previous documents, compile a video summarizing the entire document and especially our prototypes, and further sharpen the document to be concise and easy-to-read.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2020
Categories |