Scenario
Ben, a recruiter for a Software company, is looking for a student in the Computer Science department to develop software for mobile devices.
Ben goes to the MIT Jobs site and signs up for an account by providing his name, his role (recruiter), his email address, name of the Company he represents and the password for the website. Next, Ben creates a job post with the following specifications: position- Software Developer, type- internship, Course: 6, job group- Software, required competences- Java, location- Cambridge Massachusetts, application instructions- send resume by email, and deadline: March 11, 2010.
Alyssa is an undergraduate student in Computer Science. She has taken a core Java class (6.005) and is very apt in Java. She is also proficient in Python and C++. She is looking for a summer internship with a tech company. She logs into the MIT Jobs site (using her MIT certificates), She selects the department (Electrical Engineering and Computer Science), the job type (Internship) and job group (Software). She sees a listing of opportunities available for her. She finds the post made by Ben, which fits perfectly with her needs and is still within the deadline for applying.
Alyssa decides to contact Ben to inquire about the posting, and get some more details about the project. She writes the message to Ben and sends it. Ben receives the message and replies. They set up follow-up interview times.
Dragos, an undergraduate at MIT studying Computer Science, is also looking for an internship during the summer. Like Alyssa, he is also good in Java. He already interviewed for a company that he is very interested in, but he would like to keep himself posted on a few other interesting opportunities for which he is qualified. He goes to the MIT Jobs site and decides to follow Ben’s job posting so that he gets updates about the posting.
Ben is interested in meeting more people for the position, but he did not receive enough replies. Thus he updates the job position and postpones the deadline by a week. Dragos receives this update. Other applicants send their resume via email to Ben, but none of them has a resume as good as Alyssa's.
Ben then decides that Alyssa will fill the position, and sends an update to all followers of the post that the position is closed. Dragos receives an update regarding the same.
1 Comment
Vijay Umapathy
In Design 1 Analysis: "The interface is easy to learn since it uses several common affordances. The homepage is very similar to some webpages to social networks that are widely used, like Facebook, Twitter and Gmail. The tabs resemble the organization of a webrowser." - WHICH common affordances? What SPECIFICALLY is similar to Facebook/Twitter? Labels? Following? Be specific - thats very important when you articulate any design.
In Design 2 Analysis: "The interface is learnable as it uses many of the commonly employed affordances, such as buttons, and links." I can't think of the last web interface that had NO buttons or NO links. I'd like to see you guys get more specific here and really focus for Learnability on factors like similar UI features to both websites like Facebook/Twitter that one could argue are commonly used, and also physical real-world interfaces, as well as how well the UI features model whats going on under the hood.
Other than those issues, nice job with the rework - I think the 4th design you added is a good distinction from the other 3. Also nice work making the domain consistent with your designs in GR2.