Help:RQ

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

BookWithISBN

Properties

	documentation	type	name	label	allowedValues	mandatory	uploadable
RQ RQProfilename	name of this profile of requirements	Types/Text	RQProfilename	RQProfilename
RQ RQid	unique id for this requirement, technical key	Types/Text	RQid	RQid
RQ RQnumber	hierarchical number of this requirement, understandable key	Types/Text	RQnumber	RQnumber
RQ basedOn	description of the source of this requirement, e.g. interview or document	Types/Text	basedOn	basedOn
RQ comment	any comments about this requirement	Types/Text	comment	comment
RQ description	description of this requirement/ document	Types/Text	description	description
RQ design	design / technical requirement which is not simulated	Types/Boolean	design	design
RQ enteredBy	who has entered this requirement	Types/Text	enteredBy	enteredBy
RQ enteredOn	when was this requirement first entered	Types/Date	enteredOn	enteredOn
RQ kind	the kind of this requirement, can be functional, non funcional, organisational, usecase	Types/Text	kind	kind	functional, non functional, organisational, usecase
RQ myRQProfile	myRQProfile	Types/Page	myRQProfile	myRQProfile
RQ name	name of the requirement	Types/Text	name	name		true
RQ negative	A non-requirement - what is explicitely NOT required. It doesn`t have any AKs.	Types/Boolean	negative	negative
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
RQ priority	priority of this Requirement (e.g. values 1..9 or A,B,C) - may change during a project	Types/Text	priority	priority
RQ qualityAcceptance	quality acceptance - date/ name/ comment	Types/Text	qualityAcceptance	qualityAcceptance
RQ state	lifecycle state of this requirement	Types/Text	state	state	new, verifyable, accepted, integrated, validated
RQ weight	Effect that this requirement has on the realisation (e.g. values 1..9). May change during the project.	Types/Text	weight	weight
RQ what	the content of this requirement. What is expected?	Types/Text	what	what		true
RQ why	why is the content of this requirement expected? What is it good for?	Types/Text	why	why

uml

see also

• List of RQs
• Help:RQ
• Concept:RQ
• Category:RQ
• Template:RQ
• Form:RQ

related topics:

• Concept:AC
• Concept:OQ