How to Series Part 1: Beginner
So you have imported your requirements into the database and are staring at Requirements View asking yourself, what do I do now? I will help you to begin using Requirements View. The following picture is similar to what you should be viewing:
Seems a bit overwhelming with different colors, lots of buttons, drop downs and multiple columns. Let’s talk requirements view and how to use it for analysis.
Starting or importing a new requirements document will only show yellow blocks for requirements, like above (blue blocks are for baselined requirements, which will be discussed in a later blog). The staggering of requirements identifies parent-child relationships, which is a visual appetizer for quick identification. As if the numbering scheme were not enough?
You can add a new requirement by selecting → . The tool bar will change in which you can then add a parent requirement or a child requirement. Selecting each requirement gives you the name, number, and description fields to edit on the fly. Notice that the tool bar has changed:
All requirements can be edited directly from this view. If a requirement doesn’t seem to fit your criteria as a good requirement, you can transform the requirement to a statement. It’s nice to have the “More” drop down menu. Just select the unsatisfactory requirement, use the “More” drop down and select Transform → Statement.
The Quality Check feature was developed to identify parameters of what makes a good requirement. It is not set in stone and can be ignored if you wish, but why would you? The tool is helping you to write better requirements!
Now on the left hand side of this view is the sidebar. The side bar will also change so you can edit the quality score and any meta-data. Frankly, who needs entity view? When in requirements view, entities can be sorted by the class, label, or the label within the class. The sidebar will change based on what is selected in requirements view.
Requirements can be collapsed or expanded by clicking the “+” or “-” in the blocks of the parent requirements. Innoslate loads all requirements at once, so collapsing requirements helps manage the amount of requirements that are shown in this view.
There are 3 columns on the right of the requirement which generally are shortcuts to other parts of the requirement. In the picture above, it shows the rationale, quality score, and any labels associated with the requirement. These columns are sortable and can be changed to show other attributes associated with the requirement. Select the wrench in the upper right hand corner and select settings to change the columns.
The functionality of Requirements View is very powerful and can be underestimated because we tend to get infatuated with the entity view and database view, but Requirements View can do what most of the other Innoslate views do and still allow you to develop a good set of requirements which can be verified and justified with the Quality Checker. This is just the beginning. Stay tuned to our Summer Series to find out more.
For in depth information on requirements view refer to the Innoslate Requirements View documentation.
If you have any questions or difficulties, call us at 571.485.7800 or chat with us online. We are more than happy to help.