Reusing single system requirements from application family requirements
Proceedings of the 21st international conference on Software engineering
Writing Effective Use Cases
Requirements Classification and Reuse: Crossing Domain Boundaries
ICSR-6 Proceedings of the 6th International Conerence on Software Reuse: Advances in Software Reusability
ICSR-7 Proceedings of the 7th International Conference on Software Reuse: Methods, Techniques, and Tools
Semantic Matching of Web Services Capabilities
ISWC '02 Proceedings of the First International Semantic Web Conference on The Semantic Web
Quality driven web services composition
WWW '03 Proceedings of the 12th international conference on World Wide Web
COMO: A UML-Based Component Development Methodology
APSEC '99 Proceedings of the Sixth Asia Pacific Software Engineering Conference
A framework for semantic web services discovery
Proceedings of the 7th annual ACM international workshop on Web information and data management
Supporting use case based requirements engineering
Information and Software Technology
A mathematical reusability model for quantifying the reduction in development effort
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
Service-oriented systems are systems that combine services that are dispersed over the Internet. System development is normally done by defining a business process or workflow which specifies which services are to be invoked in what order. The specification of the workflow can be done in a top down manner, i.e., the developer first develops an initial specification (workflow), searches for Web services, and then refines the workflow so that the Web services can be invoked. In this paper, we propose supporting the development of the workflow (specifically BPEL document) by suggesting previous development results that could be reused. We focus on requirements (specifically use cases) and correlate use case steps with BPEL activities. This information is stored in a repository. When developing a new service-oriented system, the developer first describes a new use case. This is used to search for similar use cases and their corresponding BPEL documents. The developer uses the information to define the new service-oriented system.