Create a new QSOS template

From QSOS wiki

Jump to: navigation, search

Contents

Summary

This howto first exposes best practices when designing a functional grid of a type of software not covered yet by QSOS. It then focuses on how to formalize that grid in the XML QSOS format and contibute it back to all.

Step 1 - Design the grid

Here comes a few best practices that we recommand you to consider when designing a new functional grid.

What to do before starting

  • Communicate in the mailing-list on your difficulties, doubts or misunderstandings, you’ll be given useful advices, ideas or remarks.

Organize your grid

  • Always bear in mind that your grid might be used in contexts you don’t know yet. So try to be as generic as possible.
  • Regroup your criteria in hierachical levels, your grid will become more structured and readable. However, it is recommanded to limit the number of levels to 3 or 4 maximum.
  • The structure often reveals itself as you design the grid, so do not panic if you don’t have in mind the global view of it at the early beginning.
  • Do not hesitate to reorganize the grid if it simplifies its reading and its use.
  • Systematically look for already available information as well as your own expertise:
    • Use the Internet to find existing comparisons which could give you new ideas and make you pinpoint criteria you didn’t think of before yet.
    • Check feature lists available on websites of type of software you are evaluating.
    • Always consider several software when designing the functional grid. This will prevent you from building a grid for a specific product only.
    • Also consider proprietary products! At this stage the most important objective is to make sure you didn’t forget an important aspect of the grid on the way.
  • Avoid irrelevant criteria (at least to your eyes), like:
    • Subjectives criteria which will be difficult or even impossible to evaluate (like “Performances” for instance). If you still miss such a criterion, it needs probably to be split in more objective subcriteria (for instance: “Ergonomics” could decome “Ergonomics/GUI global coherence”, “Ergonomics/Help/General Help”, “Ergonomics/Help/Contectual Help”, etc.).
    • Too precise crireria or criteria without real new value (like “Number of entries in the menu” for instance).
    • Redundant criteria.

Non scored criteria

QSOS allows non scored criteria that still carry information and value the the grid.

A common dilemna could be illustrated like this: “Should there be one lonely criterion enumerating all possible supported web browser, or should there rather be a single subcriterion per supported browser, the whole being grouped under a single upper-level criteria?”.

Each option has pros and cons, a best practise is to consider the middle path. In our example it could be: “Supported Web browsers/Internet Explorer” (to be scored), “Supported Web browsers/Mozilla Firefox” (to be scored), “Supported Web browsers/Safari” (to be scored), “Supported Web browsers/Konqueror” (to be scored) et “Supported Web browsers/Autres navigateurs” (non scored list).

Includes

Check if some includes can be integrated in your grid.

Evaluate if you can factorize a group of criteria into an include.

Step 2 - Format the grid in a QSOS XML document

Functional grids have to be formalized in the QSOS XML format to be usable.

More information on QSOS templates XML formats.

You have for now three options to produce the XML document:

  • You can directly write it with a text editor of your choice. You’ll have to write the QSOS tags by yourself. A good practise is to reuse an already existing XML grid.
  • You can post your grid in clear text on the QSOS mailing list, somebody (another user or even a project admin) will probably format it for you.
  • You can use a beta version of the “QSOS XUL Template Editor” tool to generate the file without entering any XML tag (CVS access). NB: the “xulrunner” framework from Mozilla must be installed on your computer for the editor to run.

Whatever options you choose, do not forget to:

  • Fill all the tags of the XML format (or provide information for somebody else to do it), more particularly the , and tags since they convey the signification of your criteria’s scores.
  • Specify header information like the software family, your name and email address, etc.

We known that for the time being this step is not very simple so do not hesitate to ask for help on the mailing list if you’re stuck or lost.

Step 3 - Share your grid and follow its evolution

Once your grid formatted, it is fundamental to contribute it back to the QSOS community so others can use it to evaluate software from this family. Also future evolutions of the grid can then be managed in the QSOS repository.

  • Post your grid on the qsos-general@nongnu.org mailing list.
  • It will be added to the QSOS CVS by a QSOS admin and the whole QSOS community will be able to access it.
Personal tools