Variability

we currently lack support for designing variability-intensive service-oriented systems. Such systems during early design. Variability is introduced through variation points (i.e., predefined locations in the architecture where change may occur). At these variation points, variants are chosen when variability approaches with service-oriented design would allow us to handle different instances of the same SOA in different organizations and versions. These SOA could be adjusted to operate in diverse environments and within different contexts. However, we currently lack software engineering methods that support designing SOAs that can be adapted in different organizations and for changing situations. So far, variability in service-oriented systems has primarily been addressed at the business process level rather than at the architecture level [3,4]. Also, fundamental design principles of service orientation (e.g., loose coupling, abstraction) do not consider variability as a key issue [5]. Even though these ⇑ Corresponding author