service & component-oriented software engineering

home

projects...

SeCSE

BANKSEC

CBSEnet

ECO-ADM

people

publications

dept...

home

research

uni home

introduction

The Computing Department at Lancaster University has been active in the fields of component and service-oriented software engineering for a number of years now, and these pages are aimed at providing a single point of access to information about those projects and some of the resources that have come from them. They are not intended to replace other department pages, or the individual project websites and much information can be found in these places.

Component-based development proceeds by composing software systems from pre-fabricated components (often third-party black-box software). A typical component-based system architecture comprises a set of components that have been purposefully designed and structured to ensure that they fit together (i.e. have pluggable interfaces) and have an acceptable match with a defined system context. Service-oriented development proceeds by integrating disparate heterogeneous software services from a range of providers. A service-oriented architecture is a means of designing software systems to provide services to either end user applications or other services through published and discoverable interfaces. A typical service-oriented architecture comprises a service requestor, service provider and service broker (registry) that interact through standard messaging protocols (e.g. HTTP and SOAP) that support the publishing, discovery and binding of services. However, the diverse nature of software systems means that it is unlikely that systems will be developed using a purely service or component-based approach. Rather, a hybrid model of software development where components and services co-exist in the same system is likely to emerge. The projects described here have looked at all aspects of the software development process and include:

  • Methods & processes

  • Requirements definition

  • Software system architecture & patterns

  • Verification

  • Component selection & negotiation

  • Change management

It is expected that the pages will be developed in the future and to that end, if you think something should be accessible here which isn't, please let us know. For the moment, these pages are being maintained by John Hutchinson, so contact him at:

 

Last updated:28/01/2005