Component-based software engineering: putting the pieces together
Component-based software engineering: putting the pieces together
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
Service-Oriented Architecture: Concepts, Technology, and Design
Service-Oriented Architecture: Concepts, Technology, and Design
Software Product Line Engineering: Foundations, Principles and Techniques
Software Product Line Engineering: Foundations, Principles and Techniques
web services customization: a composition-based approach
ICWE '06 Proceedings of the 6th international conference on Web engineering
Service-Oriented Architecture (SOA): A Planning and Implementation Guide for Business and Technology
Service-Oriented Architecture (SOA): A Planning and Implementation Guide for Business and Technology
A theoretical foundation of variability in component-based development
Information and Software Technology
An aspect-oriented framework for service adaptation
ICSOC'06 Proceedings of the 4th international conference on Service-Oriented Computing
Practical methods for adapting services using enterprise service bus
ICWE'07 Proceedings of the 7th international conference on Web engineering
End-to-end reliability of service oriented applications
Information Systems Frontiers
Enhancing the OPEN Process Framework with service-oriented method fragments
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
Service-oriented computing (SOC) has several unique features which are not typically presented in conventional object-oriented development (OOD) and component-based development (CBD), including the commonalty of service functionality, publish and discovery paradigm of services and dynamic composition of possibly 3rd party's independent unit services. Hence, OOD and CBD-based analysis and design methods are not effective and expressive enough to model service-oriented applications. Rather, Service-Oriented Analysis and Design (SOAD) has to be defined by using some of the two modeling paradigms and by adding SOC-unique modeling mechanisms. In this paper, we first present a technical comparison among OOD, CBD and SOAD to derive the design criteria for SOAD. And, we define the key artifacts that have to be delivered during SOAD. Based on this, we present a SOAD process which takes service requirements as the initial input and delivers service specifications, compositions, and verified service components as the final deliverables. Each of the five phases in the process is defined with its overview, artifacts, and work instructions. Finally, we present a case study of applying our process to a service domain to reveal its effectiveness and applicability. Once the proposed SOAD is well applied, SOAD artifacts can be more systematically and efficiently implemented with current SOA standards.