Beta Systems Software AG - Support - Requirement-Management
Description of the integrated requirement process
The requirement process is part of Beta Systems' product development process. The name
"Integrated requirement process“ derives from our set goal of handling requirements from all
external and internal sources coherently and transferring them into product development as part of
a single comprehensible process.
If, as a Beta Systems customer, you would like to submit a new requirement, you can enter all
the necessary details
on the relevant form
after logging in. You can save your requirement initially as a draft, with "draft" status, in
case you want to revise it again, and can also delete your requirement while it has "draft" status,
should you wish to.
You can submit requirements in German or in English, and their further processing will take
place in the language of your choice.
Once the requirement has been sent, using the "send to Beta " button, it is given the status
"new". The Support employee responsible for the product at Beta Systems is automatically informed
of it by e-mail. The Support Team for the respective product then checks the requirement for
completeness. If they have any queries, the Support Team will contact you to clear up any
ambiguities. Finally, Support refers the requirement to the relevant Product Line Manager. The
requirement's status then changes to that of "in evaluation".
The Product Line Manager is also automatically informed by email of the submission of a new
requirement. He evaluates all requirements in terms of their potential usefulness to customers, and
arranges for an estimate of implementation costs: In doing this he also takes the opinions of the
user groups into consideration. User groups can inspect all requirements submitted by customers for
the respective product.
The result of this thorough examination is a recommendation to the Product Board – a
committee made up of representatives from the areas of Sales and Marketing, the Business Unit,
Product Line Management, and Development Management.
The Product Board decides on the extent of the next product release, and therefore also on a
product's further development and the implementation of requirements.
Each requirement which has been approved for the next product release as a result of the
Product Board's decision is given the status "accepted for next release".
Where a requirement basically can and should be implemented, but not in the next release, it
receives the status “open”. Requirements with "open" status are resubmitted to the Product Board
for a decision on inclusion in the next product release.
If the requirement is implemented and the solution becomes available, its status is set to
"available" and the relevant version entered.
Where Beta Systems cannot fulfill a requirement, the Product Line Manager records the reason
for its rejection, specifying exactly why the requirement cannot be implemented. The requirement's
status is then set to "rejected".
