Implications of a Service-Oriented View of Software
2001, Realigning Research and Practice in Information Systems Development
https://doi.org/10.1007/978-0-387-35489-7_17…
13 pages
1 file
Sign up for access to the world's latest research
Abstract
A change in attitudes and approaches to software development is emergingfrom the software engineering community, in which software is no longer regarded as a product, but as a service. This paper outlines the history of this change and reviews the implications of a service-oriented approach to information systems development. The chief impact is the need for software engineers, information systems developers, and managers to take a much broader view of the development and deployment process, with far reaching implications for traditional IS departments.
Related papers
2009
Service-Oriented Architecture (SOA) constitutes a modern, standards-based and technology-independent paradigm and architectural style for distributed enterprise computing. The SOA style promotes the publishing, discovery, and binding of loosely-coupled, network-accessible software services. With SOA systems operating in distributed and heterogeneous execution environments, the engineers of such systems are confined by the limits of traditional software engineering. In this position paper, we scrutinize the fundamental tenets underpinning the development and maintenance of SOA systems. In particular, we introduce software service engineering as an emerging discipline that entails a departure from traditional software engineering disciplines, embracing the 'open world assumption'. We characterize software service engineering via seven defining tenets. Lastly, we survey related research challenges.
2005
Leveraging a service-oriented paradigm would significantly affect the way people build software systems. However, to achieve this ambitious vision a solid software development methodology should be in place, comprising specific, service-context patterns as well as appropriate supporting tools which altogether integrate methods and best practices into a stable development environment.
Innovations in Information Technology ( …, 2012
Service-oriented software engineering (SOSE) is a software engineering approach for building service-oriented solutions by utilizing service-oriented computing paradigm constructs and concepts. Different methods exist to develop service-oriented software. However, no standardized set of service-oriented principles has been defined yet. This paper surveys current principles and provides a comparison framework to identify which are most considered by different SOSE methods at various stages of solution life cycle.
2007
Service-oriented software engineering (SOSE) aims to design, develop and maintain service oriented applications in a systematic approach. Due to the complexity that is introduced when software programs as services can be discovered, composed, instantiated, executed at runtime, SOSE poses new challenges in the way software is engineered as opposed to traditional software systems. In order for service-oriented systems to succeed, a well focused SOSE research agenda is needed. This paper proposes a model that can help researchers to identify the novelty of SOSE challenges and their research scope, and thus further helps to build the SOSE research agenda. To give an example of how to apply the proposed model, this paper explores the SOSE challenges that relate to business benefits by presenting a worked out instance of the model.
Abstract—A critical issue in the design and construction of any complex software system is its architecture. Software architecture as an important column of software development process has various methods and roadmaps that all of them have some common principles and inception. Architecture-based approaches have been promoted as a means of controlling the complexity of systems construction and evolution.
Method engineering techniques albeit proven effective for paradigms such as function, object and component, are pertinent to limited aspects of service orientation (SO). The comparison frameworks show that the pro- duced methods neither conform to SO design principles nor to SOA, which is an issue. This paper proposes a framework to guide engineering methods for service-oriented software engineering. It describes a method by its aggregates and the relationships between elements such as Service Science (SS), SO, SOA, SOC, and Web. The paper also describes the guidance for method engineering. The framework consists of two layered categories of entities: (C1) conceptual foundation entities: SS, SO, and SOA, and (C2) realization infrastructure entities: SOC and Web. These entities request and provide services from/to each other. The framework comprehensively describes the SOSE environment, enforces the construct service with fundamental properties and principles, produces SOSE methods t...
Mark keith is an assistant professor of information systems, Marriott School of Management, Brigham Young university. he received his Ph.D. in information systems from Arizona State university. his recent research interests concern It project methodology, the service-oriented paradigm, and information privacy with mobile technologies. his research has
International Journal of Systems and Service-Oriented Engineering
Method engineering techniques albeit proven effective for paradigms such as function, object and component, are pertinent to limited aspects of service orientation (SO). The comparison frameworks show that the produced methods neither conform to SO design principles nor to SOA, which is an issue. This paper proposes a framework to guide engineering methods for service-oriented software engineering. It describes a method by its aggregates and the relationships between elements such as Service Science (SS), SO, SOA, SOC, and Web. The paper also describes the guidance for method engineering. The framework consists of two layered categories of entities: (C1) conceptual foundation entities: SS, SO, and SOA, and (C2) realization infrastructure entities: SOC and Web. These entities request and provide services from/to each other. The framework comprehensively describes the SOSE environment, enforces the construct service with fundamental properties and principles, produces SOSE methods tha...
Lecture Notes in Business Information Processing, 2009
Service-oriented System engineering (SOSE) and traditional software engineering mainly differ for their focus and aims. These differences are reflected by a number of aspects peculiar to SOSE (service aspects). In this paper we specifically discuss three service aspects: the relevance of cross-organizational collaboration, increased importance of the identification of stakeholders, and the need for increased effort at run-/change time. We argue that SOSE methodologies provide better guidance on their application when service aspects are emphasized in associated process models. By highlighting the three service aspects in a process model of the methodology defined in a large European project, we show specifically how each aspect provides guidance for engineering service-oriented systems in practice.
2005
Due to an enhanced customer focus in the planning, development and delivery of IT services, service-oriented IT management has become increasingly important. This paper investigates to what effect service-oriented IT management has already been put into place in European companies. Benefit and cost categories of integrating service-oriented principles into IT management processes are analyzed. Additionally success factors for implementing serviceoriented IT management are investigated. For this purpose, six case studies were conducted. The situation of IT management before and after implementation was analyzed and comments are made on the corresponding transformation projects. Based on the case studies, this paper shows three typical benefit categories of service-oriented IT management. Eight cost categories for implementing and operating service-oriented IT management processes are discussed and six success factors of pertinent re-organization projects are identified. Findings can serve as guidelines for other IT organizations and can be used as enabler for getting informed decisions regarding the initiation of service-oriented IT management. Finally, the article highlights four current trends for service-oriented IT management and further research is outlined.

Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.