Service-Oriented Methodology for Systems Development

Realigning Research and Practice in Information Systems Development, 2001

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.

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.

2008 IEEE Congress on Services Part II (services-2 2008), 2008

Some IT companies, such as IBM, are pushing research and education in Service Science. This is due to the transition of their business models from producing hardware and software to providing services, as well as service-oriented vision changes the way people design software systems. People believe that service is the common language between business developers and IT engineers and service bridges the gap between business requirements and IT implementation. But people still do not know clearly how to use the service related theories in software system analysis and design. This paper attempts to explore this unknown topic. We want to reveal how software can become a service and suggest guidelines for analyzing and implementing service-oriented systems.

20

2009

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.

2006

Service Oriented Architectures (SOA) are rapidly emerging as the premier integration and architectural approach in contemporary, complex, heterogeneous computing environments. SOA is not simply about deploying software: it also requires that organisations evaluate their business models, come up with service-oriented analysis and design techniques, deployment and support plans, and carefully evaluate partner/customer/supplier relationships.

2009

At the end of the 1960s, demand for increasingly complex functionalities of information systems caused a software crisis, which was successfully surmounted by transition from structural to object-oriented programming. Until the end of the 1990s, object was the basis of every information system, and consequently, development methodologies that were mostly used were object-oriented methodologies such as Rational Unified Process – RUP. At the end of the 1990s, a new set of information requirements was noticed. These were requirements for transparent system integration; namely, the need for one system to communicate with another internal or external system became one of the most dominant needs. As a response to the newly created state, there appeared a new concept, the service concept. The service imposes itself as a solution, which will try, like objects at the end of 1960s, to face the newly created information requirements. This work will attempt to provide insight into similarities and differences between objects and service as the basic concepts within the object and service orientation, as well as the influence they exert on the overall information system development.

IEEE Transactions on Systems, Man, and Cybernetics - Part A: Systems and Humans, 2000

The rapidly emerging technology of Web services paves a new cost-effective way of engineering software to quickly develop and deploy Web applications by dynamically integrating other independently developed Web-service components to conduct new business transactions. This paper reports our efforts on designing and developing a Web service of pass-through authentication (PTA) for 12 online electronic-payment Web applications. In accordance with how a PTA service is developed and integrated with a corresponding back-end e-payment system, our strategies can be categorized in three stages: end-to-end integration stage, Web-services-enabled stage, and Web-services-oriented stage. Derived from real-world industrial experience, this three-stage pathway can be applied to a broad range of Web-application development projects to guide smooth transformation from a specific application-oriented design and development model toward a reusable Web-services-oriented model. Furthermore, this paper contributes to an engineering process that leads to practical Web-services-oriented software development. New research issues revealed by this project are also reported.

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...