list of dots

User Manual    [Previous]   [Next]   

Setting up Tasks

The following describes how to set up tasks in UmpleOnline. A task can be an assignment in a course that some students are asked to submit, or an experiment in modeling conducted by a researcher.

This is currently a beta feature. Please raise issues to help us improve it. Some aspects may not work perfectly yet, although it works and can be used in courses. We expect to take this out of beta in late September 2020.


 

People involved: We refer to the person creating a task (professor, teacher, researcher) as the requestor. We refer to the people doing the tasks (students, research subjects) as responders


 

Task names: Each task in UmpleOnline has a unique name that can contain alphanumeric characters, underscores and dots. Names are case insensitive and cannot contain spaces or special characters. Requestors should select a meaningful name. For example an assignment in a course at the University of Ottawa could have task name UOtt_2020_SEG2105F.A1 Responders would use this name to find the task or else they can be given a URL to be able to respond to the task (described below).


 

What information does the requestor provide to set up the task?

When setting up a task, the requestor provides the following information:

  • The requestor's name. This might be their personal name, the name of the course, the name of the institution, or a combination. Responders will see this at the top of their task instructions.

  • Instructions. These are written in Markdown format. So for example, to make a heading appear in the instructions, start a line with =, or more equals signs for lower-level headings. To make bullet lists start the line with *. To emphasize text in a line use * before and after. Use ``` before and after blocks of code. URLs will generate links to open a page in another browser tab.

    It is best to keep instructions relatively short as they take up space on the screen that will be unavailable for modeling, unless the responder asks for them to be hidden. For lengthy instructions, we suggest providing a link to another page. Instructions should include, if appropriate, a request for the responder to include their name and/or ID in the model. UmpleOnline is (at the current time) a login-free system, so responses will be anonymous by default.

  • An Umple model (optional). The requestor can populate Umpleonline in the normal way (i.e. text and diagram) with a model of any level of sophistication, including one with many tabs (Umple files). Initiating the request with a pre-prepared model can be useful when the instructions are to make improvements, or fix bugs, or add new features. Both requestors and responders have the power to use all the features of UmpleOnline when creating or responding to a request.

    If no Umple model is entered, then responders will have to start modeling from scratch, and will be presented with an empty text pane and diagram.

  • A completion URL (optional) After the responder completes and submits the task, they will be taken to this URL, and the taskname and the URL of the reponse will also be passed to the URL as additional arguments. This could be a URL in a custom tool, or in a survey tool like SurveyMonkey. More detailed explanation for how to do this is in a separate manual page. The completion URL can be used to ask questions in an experiment after the task is done, simply to record the response in a database, or to ask test questions of students.

    If no completion URL is given, the responder is returned to their model after submission, but it becomes read-only.

  • Is the task is an experiment requiring detailed logging? (this feature is still currently under development) The requestor can select a checkbox requesting that detailed logs of every stage of the modeling process be recorded, as performed by each responder. This is most useful for those conducting experiments. Researchers ought to have received ethics approval to run experiments that track data at this level of detail.


 

What is the process of setting up a task?

  1. Anyone can set up a task. Select the SAVE & LOAD menu in UmpleOnline From there click on Create a Task which appears below the TASK heading.

  2. The task creation pane will appear, allowing the requestor to enter the information described above (requestor name, instructions, model etc.). It is very important at this point to bookmark the URL that appears, or to copy and paste it somewhere safe. For security reasons it will not be possible for the requestor to edit their task or retrieve responses unless they know the randomly-generated URL.

  3. When task preparation is complete, or if the requestor wants to save their work, they select Submit Task

  4. The requestor can continue to edit the task, selecting Save Changes to this Task at any point. Any information can be edited except the task name.

  5. To test the task and see how it will appear to responders, the requestor can select Launch Participant URL in a new tab. Any work done will be recorded as an actual response, unless deleted. Another alternative for testing is to click Copy Participant URL and to paste this into the URL bar of the browser.


 

How do requestors ask responders to do a task?

There are two ways:

  • Give the responders the task name and ask them to go to the SAVE & LOAD menu, to select Load a Task and enter the task name.

  • Give them the URL obtained from selecting Copy Participant URL; clicking on this URL will create a new individual response (a new secret URL) for the person clicking. Note you can't give them the URL that appears from selecting Launch Participant URL in a new tab because that is an individual response from you and you would be giving all participants access to the same response!

Note: If the requestor edits the model of a task after a responder creates a response, the responder will not have access to rhe revised model. However, responders will have access to revised instructions.

Requestors can distribute the task name or the participant URL via email, a learning management system, or any other means.


 

How do responders respond to a task?

This information is in a separate manual page intended for responders. The tool is designed, however, such that responders should not need to access any help. They just read the instructions provided by the requestor, do the task, and submit.

There are a few points responders should be aware of in certain circumstances.

  1. Responders would benefit from bookmarking the URL of their response if they want to be able to continue their work in several sessions before submitting (if they lose their URL they will not be able to recover their work easily, although see below for alternatives).
  2. Responders ought to provide their name or other ID in their response as a comment, if the requestor wants this. So tell them to do so in your instructions.
  3. Responders need to choose Submit task when they are done.
  4. Responders cannot go back to edit their response after submitting (they can look at it, but it will be read only).
  5. A responder can delete their work by clicking on Cancel this task response before submission (but not afterwards).


 

How can the requestor obtain submissions?

Submissions can be obtained in the following ways. The first two of these will work even before submission.

Additionally, a responder could in some cases want to copy and paste their Umple model (text or diagram) into a separate file, and requestors might ask them to do this in the instructions

If a responder loses the URL of their submission, they might be able to obtain their model by clicking on the 'Restore Saved State' link that appears for a short period when UmpleOnline is relaunched. This does not, however, restore their submission: they would have to create a new submission and copy and paste the retrieved model into it.


 

How long do submissions persist?

It is intended that submissions will persist for a year after they are last edited, but it is recommended that requestors and responders not rely on this, and back up their Umple code somewhere else.


 

See here for the statement regarding privacy and other risks when using UmpleOnline.