A Taxonomy of Service Engineering Stakeholder Types Qing Gu 1 , Michael Parkin 2 , and Patricia Lago 1 1 Department of Computer Science, VU University Amsterdam, The Netherlands 2 European Research Institute for Service Science, Tilburg University, The Netherlands Abstract. The support of stakeholders is critical to the success of any project, and is equally important in SOA-related projects. Traditional software development methodologies no longer meet the requirements for developing service-based applications, or SBAs, due to the shift away from monolithic application development to service provision and com- position. This shift introduces more types of stakeholders, each of which can take multiple roles within the lifecycle of the SBA, and who have an interest in or are influenced by the service-oriented software process. To understand these stakeholder types and roles, this paper presents an initial set of stakeholder types and roles solicited from within the EC’s Network of Excellence in Software Services and Systems (S-Cube). By describing these stakeholder types in the context of the S-Cube ser- vice engineering lifecycle, we demonstrate the lifecycle phases each stake- holder and role is involved in during the development and operation of SBAs. The stakeholder roles and types found and the methodology we describe for their discovery aids the identification of the requirements for these stakeholders and contributes to research in service engineering methodologies. Keywords: SOA, Service-Oriented Software Engineering, Stakeholders. 1 Introduction A stakeholder can be defined as “any group or individual who can affect or is affected by the achievement of the organization’s objectives” [5]. In the field of software engineering, the identification of stakeholders and how to address their concerns has been of significance in the areas of requirements engineering and architectural design [3,25]. In this paper, we take the stakeholder concept and apply it to service-oriented software engineering (SOSE) with the aim of identi- fying groups or individuals who can effect or who are effected by the engineering of Service-Based Applications (SBAs). SBAs are composed of one or more software services each realizing an in- dependent business function, possibly spread across organizations. An SBA is different to, for example, a component-based application as the owner of an SBA generally does not own or control all of the services the SBA contains, whilst in W. Abramowicz et al. (Eds.): ServiceWave 2011, LNCS 6994, pp. 206–219, 2011. c  Springer-Verlag Berlin Heidelberg 2011