Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Use case

Customers want to manage more than requirements. They also want to manage dictionaries, for example:

  • An index of all error messages in the application,
  • A list of part numbers.

We've arbitrarily defined that the property named "Type" would be a special case, it will contain the type of requirement. This is a standard property, as defined in  Properties and RY Reports.

Tip
titleIf you are already using "Type" for another purpose

If your documentation already uses the "Type" for another purpose, it is not a problem. The only drawback is that the inline creation pop-up will contain a lot of entries in the drop-down. Given the pop-up is only used to create types, the UX impact will be limited.

...

Tip
titleRelease 1.4

Those features were published in version 1.4 in March 2016.

Annotate keywords, error messages and part numbers

We're introducing the dictionary blueprint in Requirement Yogi. It starts with a template where people can enter any kind of key/description entry:

Image Added

The user can assign a color to distinguish, for example, error messages from normal messages:

Image Added

Importing documents from the customer

People often have to quickly import new requirements from the customer. Requirement Yogi makes it very efficient. On a page, select a candidate for a requirement key. In the inline pop-up, click "Define as a requirement" or press Alt + Shift + R:

Image Added

 

The list of types appear:

Image Added

After you click Create, the requirement will be added to the blueprint page. All references in the page (and optionally in the space) will be transformed to links.

To speed up the conversion, if all requirements on your page start with "ODIS", then they can all be transformed and added to the blueprint.

This is a standard property, as defined in Properties and RY Reports.

Specification

Types rely on features which are already available in Requirement Yogi:

...

PropertyValueEffectNotes
TypeAny string
  • The type will be displayed in the requirement properties,
  • When using the inline creation popup, the type will be suggested,
  • If you already use the "Type" property in your documentation, then they will be visible in the inline creation pop-uppopup. We think this is a minor inconvenience.
_formatting#color; bold; italic; underlined;
  • All requirements with this formatting will be formatted accordingly.
  • Elements must be in the
same
  • specific order, followed by a semi-colon and an optional space.
  • The first item is a color, in hex/css format, such as " #ff0000" for red.
  • Note that this property is not searchable, since it contains "_"
.

 

Demonstration

  • .

...

 

The list of types appear:

Image Removed

...

...

Creating a new type

If you haven't defined any type yet, the form suggests to.

...

It

...

 will use a blueprint to create the type.

...