The application shall implement the following functional parts:

• Multi-user application, i.e. different users for individual process roles.
• Creation and maintenance of products and product versions
• Maintenance of product teams for individual products
• Creation of tickets with assignment of product versions as source or target version
• Processing of tickets along a process definition
• Distribution of process tasks to assigned product teams
• Processing of individual process steps by owners of the respective process role in forms provided for this purpose
• Generation of lists and graphical evaluations incl. MS Office export

A ticket is a request or error message from the ticket creator that is to be processed or answered by an expert.

Examples for Products are software applications for which a user can create an inquiry and thus a ticket.

Since reported errors in such products are solved by product updates, maintenance of"product versions" should also be made possible. Thus, the ticket creator can assign the affected product version to his ticket and the processor can schedule the bug fix for a future product version.

The creation and processing of tickets should follow a process that defines different process steps (=work steps) for different process roles:

• After a ticket has been created, a manager should check the ticket and decide on its further processing, i.e. accept or reject the ticket.
• If the ticket is accepted, a developer should process the ticket, i.e., implement a change (e.g., a bug fix) for a product version.
• Finally, a tester should check whether the problem described in the ticket has been solved and close the ticket.
• The creator should be able to see the active process step for his tickets.