Relating system quality and software architecture /

System Quality and Software Architecture collects state-of-the-art knowledge on how to intertwine software quality requirements with software architecture and how quality attributes are exhibited by the architecture of the system. Contributions from leading researchers and industry evangelists detai...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Otros Autores: Mistrík, Ivan (Editor )
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Waltham, MA : Morgan Kaufmann, [2014]
Temas:
Computer systems > Quality control.
Software architecture.
Systèmes informatiques > Qualité > Contrôle.
Architecture logicielle.
Software architecture
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • Foreword by Bill Curtis: Managing Systems Qualities through Architecture
  • Foreword by Richard Mark: Soley Software Quality Is Still a Problem; Quality Testing in Software
  • Enter Automated Quality Testing
  • Whither Automatic Software Quality Evaluation?
  • Architecture Intertwined with Quality
  • Preface
  • Part 1: Human-centric Evaluation for System Qualities and Software Architecture.
  • Part 2: Analysis, Monitoring, and Control of Software Architecture for System QualitiesPart 3: Domain-specific Software Architecture and Software Qualities
  • Chapter 1: Relating System Quality and Software Architecture: Foundations and Approaches
  • Introduction
  • Quality
  • Architecture
  • System
  • Architectural scope
  • System quality and software quality
  • 1.1. Quality Attributes
  • 1.2. State of the Practice
  • 1.2.1. Lifecycle approaches
  • 1.2.1.1. Waterfall
  • 1.2.1.2. Incremental
  • 1.2.1.3. Iterative
  • 1.2.1.4. Agile
  • 1.2.2. Defining requirements
  • 1.2.3. Defining the architecture.
  • 1.2.3.1. Documenting an architecture1.2.4. Assessing an architecture
  • 1.2.4.1. Quantitative versus qualitative approaches
  • 1.2.4.2. Scenario-based evaluation
  • 1.2.4.3. Experience-based evaluation
  • 1.3. State of the Art
  • 1.3.1. Loose coupling
  • 1.3.2. Designing for reuse
  • 1.3.3. Quality-centric design
  • 1.3.4. Lifecycle approaches
  • 1.3.5. Architecture representation
  • 1.3.6. Qualities at runtime through self-adaptation
  • 1.3.7. A value-driven perspective to architecting quality
  • References
  • Part I: Human-Centric Evaluation for Systems Qualities and Software Architecture.
  • Chapter 2: Exploring How the Attribute Driven Design Method Is PerceivedIntroduction
  • 2.1. Background
  • 2.1.1. ADD method
  • 2.1.2. Technology acceptance model
  • 2.2. The Empirical Study
  • 2.2.1. Research questions
  • 2.2.2. Experiment design and study variables
  • 2.2.3. Participants and training
  • 2.2.4. The architecting project
  • 2.2.5. Data collection
  • 2.3. Results
  • 2.3.1. Questionnaire reliability
  • 2.3.2. Descriptive statistics
  • 2.3.2.1. Usefulness of ADD method
  • 2.3.2.2. Ease of use of ADD method
  • 2.3.2.3. Willingnes of use
  • 2.3.3. Hypotheses tests
  • 2.4. Discussion.
  • 2.4.1. ADD issues faced by subjects2.4.1.1. Team workload division and assignment
  • 2.4.1.2. No consensus in terminology
  • 2.4.1.3. ADD first iteration
  • 2.4.1.4. Mapping quality attributes to tactics, and tactics to patterns
  • 2.4.2. Analysis of the results
  • 2.4.3. Lessons learned
  • 2.4.4. Threats to validity
  • 2.5. Conclusions and Further Work
  • References
  • Chapter 3: Harmonizing the Quality View of Stakeholders
  • Introduction
  • 3.1. Adopted Concepts of the UFO
  • 3.1.1. Selection of the Foundational Ontology
  • 3.2. Assessment and Related Concepts
  • 3.2.1. Specification-level concepts.

Ejemplares similares