Next: Is there a QoS
Up: Discussion
Previous: Related Work
Contents
Index
There are several synonyms for the role names we have chosen for the PCM process model.
- Component Developer: Application Component Provider, Component Implementer, Component Programmer
We chose ''component developer'' because it is quite generic, should be known to most software engineers, and describes the tasks of this role best.
- Software Architect: System Architect, Component Assembler, System Assembler, Architect, Application Assembler
It might be argued that this role does not only deal with software, but also has an influence on the hardware environment. Therefore the more broad term 'system' instead of 'software' could be used. However, the term software architect is quite established and the tasks involving the hardware environment of the component-based system could be delegated to the deployer. The term component assembler is sometimes used in the literature, it is, however, a too restricted term for the tasks of this role.
- Deployer: System Allocator, Component Deployer, Assembly Allocator, System Administrator, Resource Specifier, Execution Environment Modeller, Middleware Expert, Deployment Expert
In J2EE the term 'deployment' is used for assembling components and allocating them on resources. In the PCM, we explicitly separate between assembly and allocation, as the former is conducted by the software architect and the latter by the deployer. We chose the most generic term 'deployer' for the role, which is responsible for specifying the resource environment and allocating component assemblies to resources.
- QoS Analyst: Performance Analyst, Reliability Specialist, QoS Expert, QoS Evaluator, QoS Manager
As we do not want to restrict our model to performance or reliability analyses we chose the collective term 'QoS' (Quality-of-service), which covers performance, reliability, availability, etc. The goal of this role is to come up with an analyses of the QoS properties of an application, so we chose the term 'QoS analyst'.
- Domain Expert: Business Expert, Usage Modeller
We are not sure, if there are dedicated roles for specifying user behaviour in IT organisations. Therefore we chose the term 'domain expert', because this role might be involved into other tasks related to requirements analyses in addition to the task of usage modelling.
Next: Is there a QoS
Up: Discussion
Previous: Related Work
Contents
Index
Snowball
2007-03-16