Better assessment, brighter future

  • Is Questify a Saas solution?

    Questify is not currently a 'pure' SaaS solution. This is because it is not hosted in the Cloud. We are able to offer a range of solutions, including full installation of the platform at your preferred location. We can also host the platform for you.
  • Is Questify open source?

    Questify is licence-based. The software remains the property of Cito.
  • Is Questify available to purchase?

    You can buy user rights for various Questify modules. These are granted in the form of a licence. We can discuss these with you and decide on the best solution together. Please feel free to contact us and we will explain how the system works.

  • Is a demo environment available?

    We can visit you to give you a demonstration or we can provide a demo over the Internet (via Go-To Meeting). This enables us to speak to you directly and to answer any questions. It also lets us demonstrate Questify’s features and possibilities.
  • Can Questify provide the hosting?

    We can host the platform for you. There are various options here as well.
  • How do you manage the status of an item?

    You can change the status of an item by choosing from a list of options in the selection field. We can work with you to define and amend these options, if necessary. These could include status levels. such as 'in development,' 'for correction,' 'ready for 1st, 2nd, 3rd review', 'ready for pre-testing', 'adjustment required,' 'final', or 'not for use'. Status fields can be defined/configured at the application level. They are linked to actions, such as 'allow', 'alert' and 'forbid'. This means that if you link the status 'draft' to the action 'alert', then an alert will be displayed when attempting to publish tests containing draft items.
  • What item types can be used in Questify?

    Questify Builder features a wide range of item types, based on item templates. We select or compile these templates together with the client. if required, new templates can also be developed. This makes it possible to have multiple templates associated with an item type (for example, a multiple-choice item). Templates could be created for a single-column or two-column display, for example. Items are based on the IMS international standard (QTI). This means that they can be played back seamlessly through the Questify Player. We currently have more than 100 item templates in use. Examples of these are as follows:
    • ChoiceInteraction: multiple-choice item, multiple response
    • TextEntryInteraction: short-answer question, single line of text/textbox
    • ExtendedTextInteraction: essay (open-ended) question, cannot be scored automatically – usually requires manual assessment.
    • OrderInteraction: ordering question, place in the correct order
    • PositionObjectInteraction: click object in an image; drag & drop question in which elements can be positioned freely on a stage (graphic image)
    • GapMatchInteraction: drag & drop question, in which elements must be placed in pre-defined gaps in a text or on a stage (stage in graphic version)
    • GraphicGapMatchInteraction: drag & drop in a graphic image
    • InlineChoiceInteraction: multiple-choice item, usually a drop-down
    • ChoiceInteractionLikert: unscored survey item, e.g. answering on a scale of excellent - good - satisfactory - mediocre - unsatisfactory)
    • MatchInteraction: matrix item
    • HotspotInteraction: hot spot item
    Questify Builder uses the above item types (templates). These can contain moving images such as Flash or a video file. We are happy to deal with any special requirements you may have. New item types can be developed, based on existing templates, or new templates can be developed from scratch.
  • What information can I add to an item?

    If you are assigned the role of item author, you can add comments and information to items. This can be done either via the text input fields or by adding parameters/characteristics to the item. The parameters of an item could include domain, context (traffic situation), item type, scoring (number of points), key, name, keyword(s), subject, target group, item number, objectives or difficulty index. If parameter information is available, then there is no limit to the number of parameters which can be added. Psychometric data can also be incorporated as an item parameter at a later date (after pre-testing, for example). This is useful because parameters can then be used as item selection criteria (search function). This will also improve the quality of the test and item banks.
  • What metadata is assigned to an item?

    Building an item can involve various stages. When you save an item, metadata is normally generated automatically. Items are assigned a version number and, where necessary, a code. The item's creator is also recorded, as well as the date, time and bank from which the item was taken. You can manually add the status description, version, status, item type, context, domain and test score. You also have the option of defining specific parameters (open-ended, list, multiple-choice) at the item bank level. These could include the structure, domain and origin of the material.
  • How are item versions managed?

    All changes are saved. This includes any changes made to items, media files, tests (and test packages), templates and test blueprints.
    Items with the same identification number are assigned a version number. Additional data is also stored, including the item's creator, the date and time. The most recent version is saved and the version number is retained throughout the entire production process. Sometimes, an item with a previous version number may have already been published. This doesn't matter as the version number will be included during analysis and reporting until the item has been replaced with a copy with the new version number (and ID number). When this item is published in a new item bank, the system will always use the most recent version.
  • Can a test blueprint be used?

    Yes, you can create test blueprints with two dimensions. There is no limit, in principle, to the item specifications. However, these need to be entered and defined within the item bank. These include selection options, the domain, item difficulty index, p-value, context, item type, subject, number of points, specific legal texts, curriculum, author and keywords. You can also add new item selection variables, such as specific psychometric data.
  • Can a test be assembled from subtests?

    Yes, different test series can be linked together as subtests during assembly. You can think of this as arranging the items into chapters and sections. A 'foreword' and 'introduction' can be added, if necessary. These can be displayed during test administration as information screens between the different sections. You could display a screen stating that a section is now complete, for example, and that the candidate may proceed to the following section.
  • Can we use inclusion and exclusion groups?

    Yes, tests can be assembled manually by selecting items from the item bank (simultaneously or separately). You can also assemble tests using the selection tools (inclusion and exclusion groups) and test blueprints. These functions enable you to automatically assemble multiple test proposals from the item bank, based on selection criteria. This allows you to take closely related groups of items (inclusion groups) into account, as they may be derived from a common source. It also enables you to take into account groups, which must never appear in the same test (exclusion groups). These might include duplicate groups, for example.
  • Which tools can be used?

    Tools that can be customised (depending on the driver [Player] that is used) are magnifying glass, notepad, calculator, spell checker, character selector, highlighter, ruler, set square, formula editor, and even audio. New tools can also be developed, if required.
  • How is the search function set up?

    Questify Builder has a variety of search functions. Users can search the item bank, media bank, or templates and are then able to select such things as column headings (parameters/characteristics), create groups (based on item type, for example), search by keyword, or apply filters. Users can also search content, including the content of an item (full text search) in a bank or test.
  • Can we create tests ourselves using Questify?

    The Questify team provides in-depth training. We would be delighted to put together a training package proposal for you. We can provide training on an individual basis, or it can be based on the 'train-the-trainer' concept. The training course will prepare you fully for creating your own tests.
  • Can we log in from a different location and work on our tests?

    We will define the architecture with you during the consultation. We can implement a customised solution, depending on your security requirements. It is also possible to log in remotely from home.
  • Can we control user access levels and permissions?

    User roles and associated permissions can be set up for the Builder module. These can include guest, item author, test developer, item bank manager and application manager. These roles and permissions can be customised.
  • Can we keep our own candidate administration system?

    You can continue to use your current administration module or e-learning environment. Questify is module based. Because we use open standards, we can use 'Learning Tool Interoperability' (IMS LTI standard) to link your candidate data to our playback environment (Player).
  • Can tests be published on paper?

    Yes, tests can be published on paper. However, the item type must support paper publication. Audio and video files cannot be printed, for instance. The remainder of the item content can, however, be printed.
  • Is Questify Builder platform-independent?

    Questify runs on the Windows operating system.
    System requirements for the Builder module:
    • Client
      Microsoft Windows Vista SP2 or later
      Microsoft .NET Framework 4.5
      Media codecs [dependent on requirements: WEBM, OGG, MP3 etc.]
    • Server
      Windows Server 2008 R2 (For the ClickOnce deployment model, or XCOPY can be deployed via Virtual App)
      Microsoft SQL Server 2008R2 [Standard or Enterprise]
  • Is Questify Player platform-independent?

    Questify runs on the Windows operating system.
    We are currently working on making the platform independent of the Player module. The anticipated system requirements are:
    • Client
      HTML5 compatible browser [IE9, Chrome, Firefox]
      Lockdown browser [multi-platform: Windows, MacOS, Linux]
      Media codecs [dependent on requirements: WEBM, OGG, MP3, etc.]
    • Server
      Web platform: Apache Tomcat 7
      Java 7 VM [supports Windows, Linux etc.]
      Database [supports most SQL DBs, such as MS SQL and Oracle]
  • How is the item bank secured?

    The Questify Builder is based on a roles/permissions security structure. Users can access only those item banks in which they play a role. They can only perform those tasks (authoring items, publishing tests, defining parameters), which are associated with the permissions for that role. Just as with status fields, roles can be defined/configured at the application level.