Help:RQ
Jump to navigation
Jump to search
Help for RQ
| icon | Topic | name | pluralName | documentation |
|---|---|---|---|---|
| RQ | RQ | RQs | a Requirement describes the expected behaviour of a system |
Documentation
a Requirement describes the expected behaviour of a system
Example RQs
Properties
| documentation | type | name | label | allowedValues | mandatory | uploadable | |
|---|---|---|---|---|---|---|---|
| RQ RQProfilename | name of this profile of requirements | Types/Text | RQProfilename | RQProfilename | false | false | |
| RQ RQid | unique id for this requirement, technical key | Types/Text | RQid | RQid | false | false | |
| RQ RQnumber | hierarchical number of this requirement, understandable key | Types/Text | RQnumber | RQnumber | false | false | |
| RQ basedOn | description of the source of this requirement, e.g. interview or document | Types/Text | basedOn | basedOn | false | false | |
| RQ comment | any comments about this requirement | Types/Text | comment | comment | false | false | |
| RQ description | description of this requirement/ document | Types/Text | description | description | false | false | |
| RQ design | design / technical requirement which is not simulated | Types/Boolean | design | design | false | false | |
| RQ enteredBy | who has entered this requirement | Types/Text | enteredBy | enteredBy | false | false | |
| RQ enteredOn | when was this requirement first entered | Types/Date | enteredOn | enteredOn | false | false | |
| RQ kind | the kind of this requirement, can be functional, non funcional, organisational, usecase | Types/Text | kind | kind | functional, non functional, organisational, usecase | false | false |
| RQ myRQProfile | None | Types/Page | myRQProfile | myRQProfile | false | false | |
| RQ name | name of the requirement | Types/Text | name | name | true | false | |
| RQ negative | A non-requirement - what is explicitely NOT required. It doesn`t have any AKs. | Types/Boolean | negative | negative | false | false | |
| RQ owner | who is in charge of this requirement and owns it - meaning that this person is willing to accept the implications of realizing this requirements in terms of cost, time and other follow-up results | Types/Text | owner | owner | false | false | |
| RQ priority | priority of this Requirement (e.g. values 1..9 or A,B,C) - may change during a project | Types/Text | priority | priority | false | false | |
| RQ qualityAcceptance | quality acceptance - date/ name/ comment | Types/Text | qualityAcceptance | qualityAcceptance | false | false | |
| RQ state | lifecycle state of this requirement | Types/Text | state | state | new, verifyable, accepted, integrated, validated | false | false |
| RQ weight | Effect that this requirement has on the realisation (e.g. values 1..9). May change during the project. | Types/Text | weight | weight | false | false | |
| RQ what | the content of this requirement. What is expected? | Types/Text | what | what | true | false | |
| RQ why | why is the content of this requirement expected? What is it good for? | Types/Text | why | why | false | false |
uml
see also
related topics: