GR1 - Task analysis

User analysis

Computer Literacy is required for all users. Although ethnic backgrounds may vary, a reasonable command of the English language is assumed.

  • Typical MIT student browsing work/experience opportunities- 17 to 27 years old
  • College recruiters recruiting students for jobs/internships
  • Start up founder/president looking for partners
  • MIT Professors/graduate students seeking students to work on projects

Personas

John: John is a 20 year student at MIT. He is a sophomore pursuing his degree in Computer Science looking for a summer internship. He has attended the last two career fairs, but he didn’t get any offers. It is the spring semester and he is looking desperately for a summer internship in software development. He is looking through CareerBridge, company websites, contacting professors to find possible UROP's and also looking for possible opportunities to work with startups. He constantly keeps tracks of the e-mails he gets through the jobslists mailing list.

Ben: Ben is an MIT student studying Management (Course 15) who has a fantastic idea for a startup. He is looking for business partners to help him in the technical implementation of the product. Currently, he has e-mailed the Course 6 department mailing list, and other mailing lists such as individual dorms/fraternities. There is no web platform which can enable him to find partners from the entire MIT community, which he thinks is an obstacle to his finding the right partner.

Dr. Brian: Dr. Brian is an MIT professor in the Department of Economics. He developed a new model that describes better the interaction in the market, but he needs help developing a simulation to test this new model. He is looking for graduate students for RA’ships or undergraduate students to work as UROP’s in his lab. To advertise the position, he would send it to several department mailing lists.

Ms. Rose: Ms. Rose is an 40 year old campus recruiter for NuReax, a firm specialized in making nuclear reactors that is located in Chicago. The company is expanding and just hired Ms. Rose so the company can hire competent workers. She is advertising full-time and summer internship opportunities for MIT students at NuReax. She has been trying to advertise through department mailing lists, and also held a booth at the career fair. It is hard for her to keep track of the students who were interested in positions with the company; she has sign up sheets at info sessions and at the career fair, and also has resumes of students she received at the fair and also through career bridge or her company websites. To contact the interested students (e.g to remind them to apply online, or inform them of a deadline), she has to e-mail them all individually.

Task analysis

  • Sign up (only for non-MIT users e.g recruiters, start up founders etc).
    • Preconditions: none. Frequency: once.
    • Subtasks:
      • Enter name
      • Enter role (recruiter, start up founder etc)
      • Specify e-mail address
      • Specify other contact details.
  • Sign in
    • Preconditions: Sign up (using username and password for non-MIT users and using MIT certificate for MIT community)
  • Create Job Position:
    • Preconditon: Sign in
    • Subtasks:
      • Specify the position.
      • Specify the job group.
      • Specify the required competences.
      • Specify the location.
      • Specify instructions to apply (e.g. provide company website “Apply Online” link, careerbridge company posting link etc.)
      • Specify a deadline
      • Specify any other details.
  • Browse job postings
    • Precondition: Have MIT certificate
    • Subtasks: Select department (EECS, ME, Architecture etc.), job type (UROP, internship, job etc.,) and job group (software, hardware, nuclear fission etc.)
  • Follow job posting
    • Precondition: have MIT certificate
    • Subtasks:
      • Browse job postings
      • select that you want to follow a given posting
  • Send message (e.g. question) to creator of posting (Company recruiter, Professor, etc).
    • Precondition: Have MIT certificate, know what message you want to send to the creator of posting
    • Subtasks:
      • Browse job postings
      • Select the posting whose creator you want to contact
      • type and send the message
  • Send message to followers of posting
    • Precondition: Be creator of posting, know what message you want to send to followers.
    • Subtask: type and send the message
  • Edit job position:
    • Precondition: Sign in, be creator of the post you want to edit
    • Subtasks (all optional):
      • Change the location.
      • Change the required competences.
      • Change the deadline
      • Change any other details
  • Delete job posting
    • Preconditions: Sign in, be creator of the post you want to delete

Domain analysis

  • Each user has 1 account on the website. MIT users do not have to sign up for an account; they automatically have one once they log in with their certificates. Non-MIT users must sign up for an account with a username and password.
  • Both MIT and non-MIT accounts are allowed to create postings for positions.
  • Only MIT accounts are allowed to browse postings, and also view details of postings.
  • While navigating postings, MIT accounts can 'follow' postings. This means that they will be informed of any updates to the postings.
  • The account that created the posting can view the accounts following the posting, and send a cumulative message to these accounts.
  • Apart from a sending account and a receiving account, messages have an associated date, subject and content.
  • Messages can be part of a conversation, which is a thread of messages exchanged between 2 accounts.
  • While navigating postings, MIT accounts can communicate with the account that created the posting through messages (to ask questions etc.).
  • A posting can have 0 or 1 type ( e.g. UROP, fulltime job, part-time job, internship, startup etc), exactly 1 department (Computer Science, Mechanical Engineering etc.), and 1 or more job groups (e.g. software, hardware, computational biology, algorithms etc.)
  • No labels

2 Comments

  1. User Analysis - Nice job on the personas, which clearly define the types of people who will be posting / viewing posts.  However, you should have spoken with actual users to create these groups/personas, and there is no evidence here of that.

    Task Analysis - this is thorough and does a good job matching up to the goals of the system

    Domain Analysis - Looks good.  Can an account holder follow entire job groups in addition to just following posts, or is there some affordance to maybe specify your individual skills and subscribe to all posts that match?  Also, your domain should include skill areas as one property of a post as described in your user and task analysis.

  2. Nice fixes to the domain analysis :)