Jan 13, 2021
Cassie animorphs is very loveable
seen from United Kingdom
seen from United States
seen from China
seen from China
seen from United States
seen from Australia
seen from China
seen from United States
seen from China
seen from Germany
seen from China
seen from Germany
seen from Singapore
seen from China
seen from China
seen from United States
seen from Russia
seen from United States
seen from China
seen from China
Cassie animorphs is very loveable
Reading 12
1) The first reading was called "Change on a Dime: Agile Design" from UX Magazine. It was written by John Anderson and is about being able to deal with changing specifications for a design. It describes agile development as a "movement away from the typical waterfall model of software development that requires an initial comprehensive design." Instead, agile deals with many iterations with much smaller deliverables. Anderson discusses that you will probably not have an opportunity to make a big upfront design but instead will have to wait after development has begun to start designing. You also has to be able to react to quick changes in the course of development. Anderson recommends that you keep designs simple and maintain consistency through development. Also, he says to avoid the "design vortex" which I believe means to be able to stop designing at certain points when it really isn't necessary to get the whole picture across. Finally, he says to stay focused on your project and to consider the benefits of agile development. The second reading was about submitting a successful CHI paper. It addresses the introduction, the review form, making a significant contribution, and offering benefit to the reader, ensuring results are valid, gaining credit for originality, and describing the work clearly and concisely.
2) Something I would like to discuss in class is the specific instances in which agile design would come up and when it is best to use it. I think it would also be useful to see some designs that were designed in that way as compared to designs that were laid out from the start, and see if there are any noticeable differences in the interface.
3) Another thing I would like to discuss is validity of results/what sort of results we're actually looking for. I'm still not solid on the concept of analyzing our results and presenting them in a formal way because we do not have that much to measure with our product until it is a fully functioning application, which I don't think we will get to in this time.
you're not getting any sleep tonight