Multi-dimensional requirement Classification

Requirement classification using multidimensional Methods goldway was published on 10:16:00

To facilitate sorting, analysis, and management of requirements, requirements are usually classified, but there is no need to classify a single requirement into only one class, several different classification methods should be derived from analysis, which is called multidimensional classification. Therefore, each requirement may belong to several different classes. Multidimensional requirement classification helps you:

• Overlapping and conflicting requirements discovered;
• Discover common and exceptional relationships between requirements;
• Improve requirement tracking capability;
• Locate missing requirements

Therefore, you may improve your requirements by merging, modifying, and adding multi-dimensional requirements.

The key to multi-dimensional requirement classification is to define a series of dimensions and describe them with corresponding keywords. Examples are as follows:

1. System refers to the requirements that will affect the system performance or reliability;
2. User Interfaces refer to requirements that involve user interfaces. The more detailed categories can be "user input", "data expression", and "error prompt;
3. Databases refer to the requirements for data that should be processed by the system.
4. Communication refers to the need for external communication functions in the system. Likewise, this can be subdivided into smaller categories that reflect data communication equipment;
5. Security refers to the requirements that may have security significance.

The above are some examples. You must find the most appropriate category for the requirement of being classified. Generally, we recommend that you have up to 5-6 classes. If the number is exceeded, the classification is too narrow, and there are only a few requirements for each class.

These categories define several keywords for each requirement, and you can search for the requirements and their dependencies through the keywords. Each requirement should have as many keywords as possible. For example, the requirement "graphic user interface that should provide account data" can be classified as "User Interface", "Database", and "security" at the same time ".