BugWerk from the bird`s eye view

Components & Subprojects

The BugWerk infrastructure consists of 3 types of modules:

  • Sensor Modules are bundled with the application that is to be observed. These modules care for the collection of occuring incidents, drop redundant reports, enrich and hold them until the delivery to the Aggregation Service Provider is performed using internal distribution mechanisms.
    The use of Sensor Modules is optional (but encouraged where applicable), you are free to develop own implementations to connect to the Aggregation Service Provider. BugWerk currently provides a Java Sensor Module (BugTrap).
  • The Aggregation Service Provider offers so called distribution channels (interfaces of particular transport protocols like SOAP Webservices) to receive incident reports delivered by the Sensor Modules. Next to offering these interfaces the main role of the Aggregator is the management of received incidents: automated grouping of similar incidents into Tickets, access via a Webinterface to view Incidents/Tickets and setup of trackable projects and forwarding of Tickets to Issue Managers.
    This role is fulfilled by the Naggregator J2EE Server.
  • The Bugtracker is your typical Bug Tracking Program, just like Bugzilla or Mantis. BugWerk does not offer an issue manager as there are loads of established and working systems, instead the Aggregation Service offers a forwarding mechanism to different Bugtrackers.

The typical journey of an Incident report

  1. An incident occurs in the application.
  2. The incident gets treated and documented in the erroneous application.
  3. Optionally: a GUI dialog could be displayed, asking the user to accept the submission of accumulated reports.
  4. The incident gets reported to the report Aggregation Server.
  5. The incident gets forwarded from the Aggregator to a Bugtracker.