Understanding service-oriented software

Abstract

I E E E P u b l i s h e d b y t h e I E E E C o m p u t e r S o c i e t y I E E E S O F T W A R E 7 1evolution. While they address some aspects of the problem, however, understanding the software still poses some difficulty. This shift toward service orientation compels us to consider its implications for software understanding, which is potentially the primary cost in software engineering. 2 Using an example of on-the-fly software services construction, we discuss the problems software engineers still face when working with service-oriented software. We also introduce some new issues that they must consider, including how to address service provision difficulties and failures. The service-oriented visionSoftware evolution still poses a significant problem for many organizations despite new development methods that promise to enable flexibility and simplify systems' evolution as business needs change. Among the largest costs is the time software engineers spend trying to understand existing software, either to fix bugs or add functionality. We use the term software understanding to mean the application of techniques and processes that facilitate understanding of the software. We need this understanding to ensure the software evolves through the application of various maintenance activities.The SaaS framework, advanced as a solution to the evolution issue, 3 automatically discovers fine-grained software services, negotiates to acquire them, and composes, binds, executes, and unbinds them. This process potentially occurs for every execution of the software, and would Understanding ServiceOriented Software M any hail service-oriented software as the next revolution in software development. Web services' capabilities are constantly expanding from simple message passing toward the construction of full-fledged applications such as those envisaged by the UK's Pennine Group in their Software as a Service (SaaS) framework. 1 These new, service-oriented approaches appear to many to solve the significant issue of software inflexibility that arises during maintenance and service-oriented software Nicolas Gold and Andrew Mohan, UMIST Claire Knight, Volantis Systems Malcolm Munro, University of DurhamService-oriented software lets organizations create new software applications dynamically to meet rapidly changing business needs. As its construction becomes automated, however, software understanding will become more difficult.

Review of Mining Techniques Used in the Log Data Processing Based on Hadoop and Cloud Computing Environment

“…With the fast advancement of the Web, SaaS applications conveyed as administrations through web turn into an important alternative of traditional software [2,3]. SaaS applications are conveyed in dynamic data centers [4] with distributed computing innovations overseeing assets to accomplish adaptability and scalability [5,6].…”

Ontological Support for the Evolution of Future Services Oriented Architectures

“…But this flexibility may create significant problems when the composite application needs to evolve. Several authors have pointed out characteristics of SOA that may make such maintenance difficult [3][4] [9]. An important part of any maintenance task is acquiring the knowledge needed to make changes to the software; changes made based on incomplete understanding may fail with disastrous results.…”

“…Such systems present several software engineering challenges because they need to orchestrate diverse services having different owners, and have complex reliability requirements. While developing SOA applications presents many software engineering challenges, managing the evolution of such systems presents even greater challenges [3] [4].…”

Big Data Analytics for developing countries – Using the Cloud for Operational BI in Health

“…When the software that's made available as a service is a database system, the model is often labeled as Database-as-a-Service (DaaS). From an historical research perspective, it is important to recognize that early visions of turning software into a service (Turner et al, 2003) suggested use of multiple low-level services and providing a larger service using SOA (Gold et al, 2004;Papazoglou, 2003). But when considered today, SaaS is generally a single ASP product with little integration with other open services (Sun et al, 2007;Wei & Blake, 2010) and sometimes deliberately as walledgardens to cause lock-ins (Cerbo et al, 2012).…”