Read Chapters $2$ and $11$ of the textbook. In order to complete this part, you will need to$$be familiar with the contents of these chapters.$$In this part of the assignments, we focus on the first diamond in the double diamond$$of design.$2\mathrm{.}1$ Discover and Define$$In the Discover phase, we observe the people $($at least $5$ people from the target$$population$),$ to find out about their problems, their goals, their concerns, their needs$$and requirements for being in the campus...$$Here is a list of the activities you need to do as part of this phase:$2\mathrm{.}1\mathrm{.}1$ Method: make observations$($i$)$ Use probes, contextual inquiry, or brainstorming to find out about the$$problems students $($they can be your friends $($if applicable$),$ roommates $($if$$applicable$),$ family members $($if applicable$)$ experience as University students.$$This can be in the context of:$$ Commuting$$ Health and safety$$ Wellness$$ Time management$$ Food and diet$$ Other opportunities or problems...$$Pay attention that the focus should be on the concerns thatUniversity students have.$($ii$)$ Report the documentation of the outcome of your sessions. Through scripting$$or taking note of the sessions, taking pictures of the boards of ideas, etc.$($iii$)$ Try to find commonalities in the data you collect through answering these$$questions: What are the problems or opportunities for design? What needs to be$$fixed$?$ What can be enhanced? What are the needs that cannot be addressed$$using the current interactive systems.$$Use the techniques and suggestions explained in the book for brainstorming or$$contextual inquiry and document your steps and findings.$2\mathrm{.}1\mathrm{.}2$ User profiles, Personas, Scenarios$$Based on the patterns you find in the data, develop at least $($i$)$ two user profiles.$$Develop $($ii$)$ a persona for each of these profiles with $($iii$)$ a scenario capturing how$$the user is expected to interact with the product.$2\mathrm{.}1\mathrm{.}3$ Establishing requirements$$We will use the Volere Requirements Specification Template to structure the design$$brief in this assignment. This should include a sub$-$section for each of Functional$$and Non$-$Functional Requirements. The Non$-$Functional Requirements section should$$contain sub$-$sub$-$sections for each of the following:$$ Look and Feel Requirements$$ Usability and Humanity Requirements$$ Performance Requirements$$ Operational and Environmental Requirements$$ Maintainability and Support Requirements$$ Security Requirements$$ Cultural and Political Requirements$$ Legal Requirements$$Locate an on$-$line source of information about the Volere Requirements Specification$$Template$.$ Obtain further information about each of these. Remember: the requirements$$should not be so specific as to determine the design of the interactive system. They$$should provide the criteria which determine whether a particular design can be$$considered or not. Many different potential designs can meet the requirements.$2\mathrm{.}1\mathrm{.}4$ Use cases$$Identify at least two use cases of the system. Associate the use cases with one of the$$roles in the system. You are free to use any of the use case styles introduced in the$$book or class.$2\mathrm{.}2$ Submission$$Deadlines are firm and no late submission would be acceptable.$$The written report for this assignment will contain:$$ An explanation of the technique used to gather data from users $($alongside some$$exemplary pictures or notes documented$),$ patterns found, $...$ Two user profiles$$ A persona for each user profile with a scenario capturing user interaction$$ Requirements$$ Two use cases of the system$$Marking Criteria$$Soundness:$$ completeness and appropriateness of the method chosen for discovery phase$$ the extent to which documentation provided touches upon critical points while$$being concise$$ user profiles are distinct from one another$$ distinction between user profiles and persona$$ completeness and appropriateness of requirements$$ requirements do not, in a sneaky way, specify the design $($design decisions and$$requirements are abstracted apart$)$ success in identifying use cases$$Presentation:$$caliber and quality of written report, pictures, etc.