Software architectures. Advances and applications (Q4936348)
From MaRDI portal
!
This is the item page for this Wikibase entity, intended for internal use and editing purposes. Please use the normal view instead:
scientific article; zbMATH DE number 1393393
| Language | Label | Description | Also known as |
|---|---|---|---|
| default for all languages | No label defined |
||
| English | Software architectures. Advances and applications |
scientific article; zbMATH DE number 1393393 |
Statements
26 January 2000
0 references
Software architectures
0 references
reuse
0 references
industrial applications
0 references
0.7915654182434082
0 references
0.7613222599029541
0 references
Software architectures. Advances and applications (English)
0 references
The book consists of 12 papers around software architecture. It starts with an introductory and historical perspective. There is given an historical perspective for where we are now with architectures and components with an introduction to the main concepts used in this book. The next three chapters focus on the concept of a component to develop software that is flexible and adaptable, and designed for maintenance and reuse. Components, scripts and glue are described, business component development is discussed and component kits and architectures with catalysis are explained. The following three chapters are centred on the wider concept of architectures, their role in meeting non-functional requirements, their design, examples, and customization. Reuse requires architecture, architectures through evaluation and transformation, and architecture with business components are the topics. Three chapters discuss industrial applications of software architectures and their business and organizational implications with an emphasis on product-line, and one chapter reflects on the lessons learnt within the user interface research community. In a final chapter is included the views of three industrialists on the current uptake, application, and problems of architecture approaches within the industry. The reader will look for a definition of architecture fruitless. And so, architecture is seen by the authors very differently. State of the art could be more clear by precise handling of terms.
0 references