1. Present a clear and precise statement of your responsibilities/tasks.
2. Describe the Software Engineering methodologies and techniques used during your project and other ones that could have been used. Discuss any particular technology or technique you thought was particularly helpful. Choose at least 5 Software Engineering terms and describe how they fit (or not) within your project. Be specific. For example, if you choose the "paper prototyping" term, describe how paper prototypes were used, what worked, advantages/disadvantages, etc. Here is an example:
| "We used paper prototyping in our project. We first
spent 3 hours in creating storyboards, which were the basis for our paper
prototypes. They were useful in verifying that the typical course
of events in the expanded use cases --and hence in the system sequence
diagrams-- were fine. For example, by doing a walkthrough of different
scenarios of usage we found that we were lacking of the Preview
event in the system sequence diagrams related to the use cases: Create
a Survey and Modify a Survey. We notice that we did not allow
the user to preview the work in progress after a change was made.
Our team discussed the "HTML vs. paper" issue when doing our paper prototypes. We decided to _________________, because _________. In the Valtech slides, Chapter 4 (p. 5), it shows a link from use cases to prototypes, meaning that the prototypes can be generated from the use cases. However, I think it should be a bi-directional link. Prototypes also allow us to clarify some details in the use cases. We didn't have the opportunity to test our paper prototypes nor final prototypes with target users. Hence, non-functional requirements related to usability considered in our discussions (e.g. "The user should be able to create a survey easily within 5 minutes.") were not verified." |
Submit your Individual Report in HARDCOPY the day of the Final Demonstration.