Relating Software Requirements and Architectures

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...

Πλήρης περιγραφή

Λεπτομέρειες βιβλιογραφικής εγγραφής
Συγγραφή απο Οργανισμό/Αρχή: SpringerLink (Online service)
Άλλοι συγγραφείς: Avgeriou, Paris (Επιμελητής έκδοσης), Grundy, John (Επιμελητής έκδοσης), Hall, Jon G. (Επιμελητής έκδοσης), Lago, Patricia (Επιμελητής έκδοσης), Mistrík, Ivan (Επιμελητής έκδοσης)
Μορφή: Ηλεκτρονική πηγή Ηλ. βιβλίο
Γλώσσα:English
Έκδοση: Berlin, Heidelberg : Springer Berlin Heidelberg : Imprint: Springer, 2011.
Θέματα:
Διαθέσιμο Online:Full Text via HEAL-Link
Πίνακας περιεχομένων:
  • 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.