Service-Oriented Software Development

This paper describes a methodology for planning and executing software development projects based on the service-oriented paradigm called Service-Oriented Software Development (SOSD). This does not refer to a methodology for developing software services or service-oriented architectures. Rather, it is a method for managing the process of software development in a service-oriented approach in which the actions performed by individuals and groups are modeled as “services” which can be choreographed and orchestrated. SOSD has been adopted informally by many organizations in various forms and it runs somewhat contrary to some of the recent trends toward agile development methodologies. Interestingly, it performs well in certain situations where agile methods tend to break down. In addition to describing the basics of SOSD and its theoretical underpinnings, we outline its benefits and potential shortcomings. As evidence, project data is provided from a Fortune 500 company which has gradually adopted SOSD over the last two years.

[1]  Tore Dybå,et al.  Empirical studies of agile software development: A systematic review , 2008, Inf. Softw. Technol..

[2]  I. Foster,et al.  Service-Oriented Science , 2005, Science.

[3]  James D. Thompson.  Organizations in Action , 1967 .

[4]  Carliss Y. Baldwin,et al.  Managing in an age of modularity. , 1997, Harvard business review.

[5]  Julie Smith David,et al.  Business Process Agility , 2005, AMCIS.

[6]  Eric Newcomer,et al.  Understanding Web Services: XML, WSDL, SOAP, and UDDI , 2002 .

[7]  Sanjay Bose,et al.  Impact of service-oriented architecture on enterprise systems, organizational structures, and individuals , 2005, IBM Syst. J..

[8]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

[9]  James C. Spohrer,et al.  A research manifesto for services science , 2006, CACM.

[10]  Pablo Castells,et al.  A Flexible Model for Locating Services on the Web , 2007, Int. J. Electron. Commer..

[11]  George Mangalaraj,et al.  Challenges of migrating to agile methodologies , 2005, CACM.

[12]  Prashant Jain,et al.  Using a model-driven transformational approach and service-oriented architecture for service delivery management , 2007, IBM Syst. J..

[13]  G. Hoetker.  Do Modular Products Lead to Modular Organizations , 2006 .

[14]  Alan R. Hevner,et al.  Design Science in Information Systems Research , 2004, MIS Q..

[15]  Amit P. Sheth,et al.  Semantics to energize the full services spectrum , 2006, CACM.

[16]  R. Langlois.  Modularity in technology and organization , 2002 .

[17]  Jeff Sutherland,et al.  Distributed Scrum: Agile Project Management with Outsourced Development Teams , 2007, 2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07).

[18]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[19]  Thomas Erl,et al.  Service-Oriented Architecture: Concepts, Technology, and Design , 2005 .

[20]  D. L. Parnas,et al.  On the criteria to be used in decomposing systems into modules , 1972, Software Pioneers.