Requirements Modelling and Specification for Service Oriented Architecture

2.8. Bibliographical Notes

In this chapter, I restricted myself to the discussion of software architecture as given by Bosch (2000). There is a substantial second part dealing with the actual development of product lines. The interested reader is recommended to consult this book.

A complementary discussion of architecture in a service-oriented context is provided by Erl (2005).

Dikel et al. (2001) provide an interesting slant on the topic of software architecture, in that they equate it much more with architectural vision than do most approaches. These authors view architecture mainly as the unifying vision that makes it possible to put together systems across departmental and organizational boundaries, in contrast with the islands of automation that Americans call 'stovepipes'. Sounds like SOA? The book is definitely pre-SOA but does have some useful insights. They focus almost entirely on 'product line' development, which was the fashion for a while - presumably because someone at the Sloan School of Management said once that there was money to be made, based on the common but absurd Empiricist premise that 'what was true yesterday will be true tomorrow'. SOA removes the need for a lot (though by no means all) of what is recommended: it is an architectural vision. Nevertheless, the book is worth a look at, especially because it presents much of its wisdom in the form of patterns and includes useful links to other relevant published patterns.

Graham (2009) discusses architectural ...