//]]>

Relating Software Requirements and Architectures (Record no. 21841)

000 -LEADER
fixed length control field 04798nam a22004575i 4500
003 - CONTROL NUMBER IDENTIFIER
control field OSt
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20140310151122.0
007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION
fixed length control field cr nn 008mamaa
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 110801s2011 gw | s |||| 0|eng d
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9783642210013
978-3-642-21001-3
050 #4 - LIBRARY OF CONGRESS CALL NUMBER
Classification number QA76.758
082 04 - DEWEY DECIMAL CLASSIFICATION NUMBER
Classification number 005.1
Edition number 23
264 #1 -
-- Berlin, Heidelberg :
-- Springer Berlin Heidelberg :
-- Imprint: Springer,
-- 2011.
912 ## -
-- ZDB-2-SCS
100 1# - MAIN ENTRY--PERSONAL NAME
Personal name Avgeriou, Paris.
Relator term editor.
245 10 - IMMEDIATE SOURCE OF ACQUISITION NOTE
Title Relating Software Requirements and Architectures
Medium [electronic resource] /
Statement of responsibility, etc edited by Paris Avgeriou, John Grundy, Jon G. Hall, Patricia Lago, Ivan Mistrík.
300 ## - PHYSICAL DESCRIPTION
Extent XXVIII, 387p. 124 illus.
Other physical details online resource.
505 0# - FORMATTED CONTENTS NOTE
Formatted contents note Introduction: relating requirements and architectures -- Part 1 Theoretical Underpinnings and Reviews -- Anticipating Change in Requirements Engineering -- Traceability in the Co-evolution of Architectural Requirements and Design -- Understanding Architectural Elements from Requirements Traceability Networks -- Part 2 Tools and Techniques -- Goal-Oriented Software Architecting -- Product-Line Models to Address Requirements Uncertainty, Volatility and Risk -- Systematic Architectural Design based on Problem Patterns -- Adaptation Goals for Adaptive Service-oriented Architectures -- Business Goals and Architecture -- Part 3 Experiences from Industrial Projects -- A Reference Architecture for Consumer Electronics Products and its Application in Requirements Engineering -- Using Model-Driven Views and Trace Links to Relate Requirements and Architecture: A Case Study -- Managing Artifacts with a Viewpoint-Realization Level Matrix -- Onions, Pyramids & Loops - From Requirements to Software Architecture -- Part 4 Emerging Issues in Relating Software Requirements and Architecture -- Synthesizing Architecture from Requirements: A Genetic Approach -- How Software Architecture can Frame, Constrain and Inspire System Requirements -- Economics-driven Architecting for Non functional Requirements in the Presence of Middleware -- Conclusions.
520 ## - SUMMARY, ETC.
Summary, etc Why have a book about the relation between requirements and software architecture? Understanding the relation between requirements and architecture is important because the requirements, be they explicit or implicit, represent the function, whereas the architecture determines the form. While changes to a set of requirements may impact on the realization of the architecture, choices made for an architectural solution may impact on requirements, e.g., in terms of revising functional or non-functional requirements that cannot actually be met. Although research in both requirements engineering and software architecture is quite active, it is in their combination that understanding is most needed and actively sought. Presenting the current state of the art is the purpose of this book. The editors have divided the contributions into four parts: Part 1 “Theoretical Underpinnings and Reviews” addresses the issue of requirements change management in architectural design through traceability and reasoning. Part 2 “Tools and Techniques” presents approaches, tools, and techniques for bridging the gap between software requirements and architecture. Part 3 “Experiences from Industrial Projects” then reports on case studies from industry, while part 4 on “Emerging Issues” details advanced topics such as synthesizing architecture from requirements or the role of middleware in architecting for non-functional requirements. The final chapter is a conclusions chapter identifying key contributions and outstanding areas for future research and improvement of practice. The book is targeted at academic and industrial researchers in requirements engineering or software architecture. Graduate students specializing in these areas as well as advanced professionals in software development will also benefit from the results and experiences presented in this volume.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Computer science.
Topical term or geographic name as entry element Software engineering.
Topical term or geographic name as entry element Information Systems.
Topical term or geographic name as entry element Computer Science.
Topical term or geographic name as entry element Software Engineering.
Topical term or geographic name as entry element Management of Computing and Information Systems.
700 1# - ADDED ENTRY--PERSONAL NAME
Personal name Grundy, John.
Relator term editor.
Personal name Hall, Jon G.
Relator term editor.
Personal name Lago, Patricia.
Relator term editor.
Personal name Mistrík, Ivan.
Relator term editor.
710 2# - ADDED ENTRY--CORPORATE NAME
Corporate name or jurisdiction name as entry element SpringerLink (Online service)
773 0# - HOST ITEM ENTRY
Title Springer eBooks
776 08 - ADDITIONAL PHYSICAL FORM ENTRY
Display text Printed edition:
International Standard Book Number 9783642210006
856 40 - ELECTRONIC LOCATION AND ACCESS
Uniform Resource Identifier http://dx.doi.org/10.1007/978-3-642-21001-3
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Source of classification or shelving scheme
Item type E-Book
Copies
Price effective from Permanent location Date last seen Not for loan Date acquired Source of classification or shelving scheme Koha item type Damaged status Lost status Withdrawn status Current location Full call number
2014-04-23AUM Main Library2014-04-23 2014-04-23 E-Book   AUM Main Library005.1