User roles and interactions
The business events scenario uses different roles to perform key tasks. The roles and their interactions are summarized here for scenario tasks.
Develop the solution
The following roles are involved in developing the software aspects of the solution:
- Software architect
- The software architect is responsible for dividing the required function between the components that make up a software solution. This person works with the specifications and standards used by existing IT systems, and determines where enhancements or new components must be written by the developer.
- Developer
- The developer is responsible for creating and testing the software components and linking them together. In some cases the developer might need information from the administrator, for example if the developer must use an existing transaction or temporary storage queue. After the developer finishes creating the software components, the developer gives those components to the administrator for deployment.
Deploy the solution
The following roles are involved in deploying the solution for production use, by installing, configuring, and testing the components that provide the solution.
- System administrator
- The administrator installs and configures the components that support the solution, in this case event processing. The administrator also deploys the software components given to them by the developer, in this case the event binding containing the capture specifications, and the dashboard application.
- Test implementer
- The test implementer runs the tests to validate the solution and ensure that the solution is ready for production use. For example, can the solution be started, stopped, backed up, and recovered after a system failure, as well as be maintained?
Figure 1. User role interactions to deploy the solution
