Specific roles for the categories

Provider
The roles played during the life cycle of a service, from a provider’s perspective would mainly be:

System Administrator: This role will have all the privileges available and in addition will be able to assign various roles and privileges to other users of the system, in short provision users. They will also be responsible for maintaining security related artifacts such as Certificates, CRL locations.

Business Service Analyst or Business Analyst: In this role the user will ensure that the business requirements are met by different services that would be offered and would help others understand the business value of the service.

Line of Business Representative: These users will communicate business requirements and identify business services. Will also be responsible for providing Consumers to access services and define consumer specific terms such as security, SLA and other policies which need to be enforced. Could also create composite applications using existing services Note: this role will surface mostly in a brokered proxy mode.

Service Administrator – The users of this role will be solely responsible for a service or a group of services, will track usage and monitor them for the purpose of ROI and also track and maintain the life cycle of a Service such as versioning, deprecation, EOL. Apart from this will also be responsible for managing all other artifacts associated with the Service such as Dependency Profile, impact analysis.

Service designers/Developer – The users of this role will focus mainly on the development of the Services and would interact with the Business Analyst and the Service Owners.
Service Testers – In this role a user will test and maintain the services in terms of the business requirements as well as policy compliance.

Service Monitoring Representatives: In this role users will monitor all services and help in resolving all SLA related activities.

Note: Any other user apart from this will be treated as a guest user. (Please check the Consumer section for more details on the guest user’s access privileges)

Consumer
The roles played by the consumer are limited to service subscription, usage and view statistics.
1) Service User: A service user will be able to use a service or a group of services and will not be able to view statistical data associated with the services in terms of response time, faults, number of hits, service usage, and service usage by user for a particular consumer organization.
2) Power User: These users will be more from the top management of an organization and apart from being able to use a service will be able to access statistical data, view the availability of new services provided by the provider organization and subscribe for them.
3) Service Monitoring Rep: These users will just monitor the statistics of the services that are being consumed. In case of breach of contract will initiate a dialog with the provider organization.
4) Guest: A guest users would be required so that people without any credential can come and view available services. They would not be able to use any service but can request for a subscription. The provider organization should be able to receive this request and process it.
The life cycle of such request would be
a. Depending on the service the service provider will be notified with users details which the guest user needs to provide while requesting for a subscription, typically the details would be i) User Name ii) Organization name iii) address iv) email v) phone vi) fax.
b. Once the request is received by the provider organization the processing will start. The subscription work flow could be made part of our application or could be done offline.
5) Anonymous User: When a proxy service is used by user without any credentials the request shall be treated as an anonymous access and if for the service anonymous access is allowed then a proper response will be sent back to the requester or else a SOAP fault can be generated which will detail the cause of failure.

Intermediary
The Roles for this category will be in line with the provider organization and behave exactly like the provider roles but with some added responsibilities.
System Administrator: This role will have all the privileges available and in addition will be able to assign various roles and privileges to other users of the system, in short provision users such as Consumers and internal users. They will also be responsible for maintaining security related artifacts such as Certificates, CRL locations.

Service owners – The users of this role will be solely responsible for a proxy service or a group of proxy services, will track usage and monitor them for the purpose of ROI and also track and maintain the life cycle of a Service such as versioning, deprecation, EOL. Apart from this will also be responsible for managing all other artifacts associated with the proxy Service such as WSDL and impact analysis.

Runtime Policy designers/Developer – The users of this role will focus mainly on creating policies for the proxy services and would interact with the Service Owners. The policies being SLA, Security, Transformation, Routing, Logging and monitoring.
Service Testers – In this role a user will test and maintain the proxy services in terms of the business requirements as well as runtime policy compliance.
Service Monitoring Representatives: In this role users will monitor all proxy services and help in resolving all SLA related activities.

Anonymous User:
The only exception being that the users:
Will not be responsible for creating Web Services.

Privileges
The roles described above will have CRUD operations on application specific privileges. The identified privileges are, broken down by app category.