feed icon rss

Your email was sent successfully. Check your inbox.

An error occurred while sending the email. Please try again.

Proceed reservation?

Export
Filter
Type of Medium
Language
Region
Virtual Catalogues
Subjects(RVK)
Access
  • 1
    Online Resource
    Online Resource
    Cambridge, Massachusetts :Morgan Kaufmann Publishers,
    UID:
    almahu_9949697783402882
    Format: 1 online resource (433 pages)
    Edition: First edition.
    ISBN: 0-12-809338-2
    Content: Software Architecture for Big Data and the Cloud is designed to be a single resource that brings together research on how software architectures can solve the challenges imposed by building big data software systems. The challenges of big data on the software architecture can relate to scale, security, integrity, performance, concurrency, parallelism, and dependability, amongst others. Big data handling requires rethinking architectural solutions to meet functional and non-functional requirements related to volume, variety and velocity. The book's editors have varied and complementary backgrounds in requirements and architecture, specifically in software architectures for cloud and big data, as well as expertise in software engineering for cloud and big data. This book brings together work across different disciplines in software engineering, including work expanded from conference tracks and workshops led by the editors. Discusses systematic and disciplined approaches to building software architectures for cloud and big data with state-of-the-art methods and techniques Presents case studies involving enterprise, business, and government service deployment of big data applications Shares guidance on theory, frameworks, methodologies, and architecture for cloud and big data
    Note: Includes index. , Front Cover -- Software Architecture for Big Data and the Cloud -- Copyright -- Contents -- Contributors -- About the Editors -- Foreword by Mandy Chessell -- Amnesia or Progress? -- The Legacy of Data Warehousing -- Looking Back at the Impact of Big Data Technology -- The Impact of Cloud Technology -- Conclusion -- Foreword by Ian Gorton -- Preface -- Introduction -- Why a New Book on Software Architecture for Big Data and the Cloud? -- Book Outline -- Part I: Concepts and Models -- Part II: Analyzing and Evaluating -- Part III: Technologies -- Part IV: Resource Management -- Part V: Looking Ahead -- 1 Introduction. Software Architecture for Cloud and Big Data: An Open Quest for the Architecturally Signi cant Requirements -- 1.1 A Perspective into Software Architecture for Cloud and Big Data -- 1.2 Cloud Architecturally Signi cant Requirements and Their Design Implications -- 1.2.1 Dynamism and Elasticity as Cloud Architecturally Signi cant Requirements -- 1.2.2 Multitenancy as Cloud Architecturally Signi cant Requirement -- 1.2.3 Service Level Agreements (SLAs) Constraints as Cloud Architecturally Signi cant Requirement -- 1.2.4 Cloud Marketplaces as Architecturally Signi cant Requirement -- 1.2.5 Seeking Value as Cloud Architecturally Signi cant Requirement -- 1.3 Big Data Management as Cloud Architecturally Signi cant Requirement -- 1.3.1 Big Data Analytics Enabled by the Cloud and Its Architecturally Signi cant Requirements -- 1.3.2 Architecturally Signi cant Requirements in Realm of Competing Big Data Technologies -- References -- Part 1 Concepts and Models -- 2 Hyperscalability - The Changing Face of Software Architecture -- 2.1 Introduction -- 2.2 Hyperscalable Systems -- 2.2.1 Scalability -- 2.2.2 Scalability Limits -- 2.2.3 Scalability Costs -- 2.2.4 Hyperscalability -- 2.3 Principles of Hyperscalable Systems. , 2.3.1 Automate and Optimize to Control Costs -- 2.3.1.1 Automation -- 2.3.1.2 Optimization -- 2.3.2 Simple Solutions Promote Scalability -- 2.3.3 Utilize Stateless Services -- 2.3.4 Observability is Fundamental to Success at Hyperscale -- 2.4 Related Work -- 2.5 Conclusions -- References -- 3 Architecting to Deliver Value From a Big Data and Hybrid Cloud Architecture -- 3.1 Introduction -- 3.2 Supporting the Analytics Lifecycle -- 3.3 The Role of Data Lakes -- 3.4 Key Design Features That Make a Data Lake Successful -- 3.5 Architecture Example - Context Management in the IoT -- 3.6 Big Data Origins and Characteristics -- 3.7 The Systems That Capture and Process Big Data -- 3.8 Operating Across Organizational Silos -- 3.9 Architecture Example - Local Processing of Big Data -- 3.10 Architecture Example - Creating a Multichannel View -- 3.11 Application Independent Data -- 3.12 Metadata and Governance -- 3.13 Conclusions -- 3.14 Outlook and Future Directions -- References -- 4 Domain-Driven Design of Big Data Systems Based on a Reference Architecture -- 4.1 Introduction -- 4.2 Domain-Driven Design Approach -- 4.3 Related Work -- 4.4 Feature Model of Big Data Systems -- 4.4.1 Data -- 4.4.2 Information Management -- 4.4.3 Interface and Visualization -- 4.4.4 Data Processing -- 4.4.5 Data Storage -- 4.4.6 Data Analysis -- 4.4.7 Feature Constraints -- 4.5 Deriving the Application Architectures and Example -- 4.5.1 Feature Modeling -- 4.5.2 Design Rule Modeling -- 4.5.3 Associating Design Decisions With Features -- 4.5.4 Generation of the Application Architecture and the Deployment Diagram -- 4.5.5 Deriving Big Data Architectures of Existing Systems -- 4.5.5.1 Facebook -- 4.5.5.2 Twitter -- 4.5.5.3 Energy management system -- 4.6 Conclusion -- References -- 5 An Architectural Model-Based Approach to Quality-Aware DevOps in Cloud Applications. , 5.1 Introduction -- 5.2 A Cloud-Based Software Application -- 5.3 Differences in Architectural Models Among Development and Operations -- 5.4 The iObserve Approach -- 5.5 Addressing the Differences in Architectural Models -- 5.5.1 The iObserve Megamodel -- 5.5.2 Descriptive and Prescriptive Architectural Models in iObserve -- 5.5.3 Static and Dynamic Content in Architectural Models -- 5.6 Applying iObserve to CoCoME -- 5.6.1 Applying the iObserve Megamodel -- 5.6.2 Applying Descriptive and Prescriptive Architectural Models -- 5.6.3 Applying Live Visualization -- 5.7 Limitations -- 5.8 Related Work -- 5.9 Conclusion -- References -- 6 Bridging Ecology and Cloud: Transposing Ecological Perspective to Enable Better Cloud Autoscaling -- 6.1 Introduction -- 6.2 Motivation -- 6.3 Natural Ecosystem -- 6.4 Transposing Ecological Principles, Theories and Models to Cloud Ecosystem -- 6.5 Ecology-Inspired Self-Aware Pattern -- 6.6 Opportunities and Challenges -- 6.7 Related Work -- 6.8 Conclusion -- References -- Acknowledgement -- Part 2 Analyzing and Evaluating -- 7 Evaluating Web PKIs -- 7.1 Introduction -- 7.2 An Overview of PKI -- 7.3 Desired Features and Security Concerns -- 7.4 Existing Proposals -- 7.4.1 Classic -- 7.4.2 Difference Observation -- 7.4.2.1 Perspectives -- 7.4.2.2 DoubleCheck -- 7.4.2.3 Convergence -- 7.4.2.4 Certi cate patrol -- 7.4.2.5 CertLock -- 7.4.2.6 TACK -- 7.4.3 Scope Restriction -- 7.4.3.1 Public key pinning (PKP) -- 7.4.3.2 DANE -- 7.4.3.3 CAge -- 7.4.4 Certi cate Management Transparency -- 7.4.4.1 Sovereign keys -- 7.4.4.2 Certi cate transparency -- 7.4.4.3 Accountable key infrastructure -- 7.4.4.4 Certi cate issuance and revocation transparency -- 7.4.4.5 Attack resilient public-key infrastructure -- 7.4.4.6 Distributed transparent key infrastructure -- 7.5 Observations -- 7.5.1 Property Perspective -- 7.5.2 System Perspective. , 7.6 Conclusion -- References -- 8 Performance Isolation in Cloud-Based Big Data Architectures -- 8.1 Introduction -- 8.2 Background -- 8.2.1 Cloud Computing -- 8.2.2 Big Data Architecture -- 8.3 Case Study and Problem Statement -- 8.3.1 Case Study -- 8.3.2 Problem Statement -- 8.4 Performance Monitoring in Cloud-Based Systems -- 8.5 Application Framework for Performance Isolation -- 8.6 Evaluation of the Framework -- 8.6.1 Evaluation Results -- 8.7 Discussion -- 8.8 Related Work -- 8.9 Conclusion -- References -- 9 From Legacy to Cloud: Risks and Bene ts in Software Cloud Migration -- 9.1 Introduction -- 9.2 Research Method -- 9.2.1 Pilot Study -- 9.2.2 Search Strategy -- 9.2.2.1 Research question -- 9.2.2.2 Data sources -- 9.2.2.3 Search query -- 9.2.2.4 Search process -- 9.2.2.5 Selection of primary studies -- 9.2.2.6 Included and excluded studies -- 9.2.2.7 Search result management -- 9.2.2.8 Quality assessment of primary studies -- 9.2.3 Data Extraction -- 9.2.4 Data Analysis Method -- 9.3 Results -- 9.3.1 Overview of Primary Studies and Quality Evaluation -- 9.3.2 Bene ts and Risks -- 9.3.3 General Measures -- 9.3.4 Models and Frameworks for Cloud Migration -- 9.4 Discussion -- 9.4.1 Findings and Lessons Learned -- 9.4.2 Threats to Validity -- 9.5 Conclusion -- References -- 10 Big Data: A Practitioners Perspective -- 10.1 Big Data Is a New Paradigm - Differences With Traditional Data Warehouse, Pitfalls and Consideration -- 10.1.1 Differences With Traditional Data Warehouse -- 10.1.2 Pitfalls -- 10.1.2.1 Insuf cient volume of data -- 10.1.2.2 Not having a business challenge -- 10.1.2.3 Ignoring the data quality -- 10.1.2.4 Big data can predict the future -- 10.1.3 Considerations -- 10.2 Product Considerations for Big Data - Use of Open Source Products for Big Data, Pitfalls and Considerations. , 10.2.1 The Use of Open Source Product for Big Data -- 10.2.2 Pitfalls -- 10.2.2.1 Not focusing on business needs and falling to the latest hype -- 10.2.2.2 Not focusing on operational & -- nonfunctional requirements -- 10.2.2.3 Lack of suf cient document and or community base support -- 10.2.2.4 Not planning for separate environment to prove version compatibility -- 10.2.3 Considerations -- 10.3 Use of Cloud for hosting Big Data - Why to Use Cloud, Pitfalls and Consideration -- 10.3.1 Why to Use Cloud? -- 10.3.2 Pitfalls -- 10.3.2.1 Not knowing where the data will be stored -- 10.3.2.2 Not understanding the SLA with the cloud provider -- 10.3.2.3 Not understanding how to transfer data to cloud -- 10.3.2.4 Not knowing the processing pro le required as cloud can scale -- 10.3.3 Consideration -- 10.4 Big Data Implementation - Architecture De nition, Processing Framework and Migration Pattern From Data Warehouse to Big Data -- 10.4.1 Patterns for Transitioning From Data Warehouse to Big Data -- 10.5 Conclusion -- References -- Part 3 Technologies -- 11 A Taxonomy and Survey of Stream Processing Systems -- 11.1 Introduction -- 11.2 Stream Processing Platforms: A Brief Background -- 11.2.1 Requirements of Stream Processing Platforms/Engines -- 11.2.2 Generic Model of Modern Stream Processing Platforms/Engines -- 11.3 Taxonomy -- 11.3.1 Functional Aspects -- 11.3.1.1 Data streaming -- 11.3.1.2 Data execution -- 11.3.1.3 Data processing -- 11.3.1.4 Fault tolerance -- 11.3.2 Nonfunctional Aspects -- 11.3.2.1 Cost -- 11.3.2.2 Technical support -- 11.3.2.3 User community -- 11.4 A Survey of Stream Processing Platforms -- 11.4.1 Data Stream Management Systems -- 11.4.2 Complex Event Processing Systems -- 11.4.3 Stream Processing Platforms/Engines -- 11.4.3.1 Apache storm -- 11.4.3.2 Yahoo! S4 -- 11.4.3.3 Apache Samza -- 11.4.3.4 Spring XD. , 11.4.3.5 Spark streaming.
    Additional Edition: ISBN 0-12-805467-0
    Language: English
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 2
    Online Resource
    Online Resource
    Waltham, Massachusetts :Morgan Kaufmann,
    UID:
    almahu_9948025556402882
    Format: 1 online resource (421 p.)
    Edition: 1st edition
    ISBN: 0-12-417168-0
    Content: 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 detail the techniques required to achieve quality management in software architecting, and the best way to apply these techniques effectively in various application domains (especially in cloud, mobile and ultra-large-scale/internet-scale architecture) Taken together, these approaches show how to assess
    Note: Description based upon print version of record. , ""Front Cover""; ""Relating System Quality and Software Architecture""; ""Copyright""; ""Contents""; ""Acknowledgements""; ""About the Editors""; ""List of Contributors""; ""Foreword by Bill Curtis Managing Systems Qualities through Architecture""; ""About the Author""; ""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""; ""About the Author""; ""Preface"" , ""Part 1: Human-centric Evaluation for System Qualities and Software Architecture""""Part 2: Analysis, Monitoring, and Control of Software Architecture for System Qualities""; ""Part 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 architecture""; ""1.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 Perceived""; ""Introduction""; ""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 subjects""; ""2.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"" , English
    Additional Edition: ISBN 0-12-417009-9
    Additional Edition: ISBN 1-322-01794-8
    Language: English
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 3
    Online Resource
    Online Resource
    Amsterdam, [Netherlands] :Elsevier,
    UID:
    almahu_9949697615102882
    Format: 1 online resource (432 pages) : , illustrations
    Edition: 1st edition
    ISBN: 0-12-802891-2
    Content: Managing Trade-Offs in Adaptable Software Architectures explores the latest research on adapting large complex systems to changing requirements. To be able to adapt a system, engineers must evaluate different quality attributes, including trade-offs to balance functional and quality requirements to maintain a well-functioning system throughout the lifetime of the system. This comprehensive resource brings together research focusing on how to manage trade-offs and architect adaptive systems in different business contexts. It presents state-of-the-art techniques, methodologies, tools, best practices, and guidelines for developing adaptive systems, and offers guidance for future software engineering research and practice. Each contributed chapter considers the practical application of the topic through case studies, experiments, empirical validation, or systematic comparisons with other approaches already in practice. Topics of interest include, but are not limited to, how to architect a system for adaptability, software architecture for self-adaptive systems, understanding and balancing the trade-offs involved, architectural patterns for self-adaptive systems, how quality attributes are exhibited by the architecture of the system, how to connect the quality of a software architecture to system architecture or other system considerations, and more. Explains software architectural processes and metrics supporting highly adaptive and complex engineering Covers validation, verification, security, and quality assurance in system design Discusses domain-specific software engineering issues for cloud-based, mobile, context-sensitive, cyber-physical, ultra-large-scale/internet-scale systems, mash-up, and autonomic systems Includes practical case studies of complex, adaptive, and context-critical systems
    Note: Front Cover -- Managing Trade-offs in Adaptable Software Architectures -- Copyright -- Contents -- Contributors -- About the Editors -- Foreword by David Garlan -- Foreword by Nenad Medvidovic Behold the Golden Age of Software Architecture -- References -- Foreword by Paris Avgeriou -- Foreword by Rogério de Lemos -- Preface -- Introduction -- Part I: Concepts and Models for Self-Adaptive Software Architectures -- Part II: Analyzing and Evaluating Trade-offs in Self-Adaptive Software Architectures -- Part III: Managing Trade-offs in Self-Adaptive Software Architectures -- Part IV: Quality Assurance in Self-Adaptive Software Architectures -- Chapter 1: Managing Trade-Offs in Adaptable Software Architectures -- 1.1. Introduction -- 1.2. Background -- 1.3. Trade-Offs in Adaptive Systems Design -- 1.4. Runtime Trade-Offs in Self-Adaptive Systems -- 1.5. Challenges and the Road Ahead -- 1.5.1. How to Architect for Adaptability? -- 1.5.2. Adaptability in Modern Systems -- 1.5.2.1. Cloud computing -- 1.5.2.2. Service-based adaptation to QoS -- 1.5.2.3. Cyber-physical systems -- References -- Part I: Concepts and Models for Self-Adaptive Software Architectures -- Chapter 2: Architecting Software Systems for Runtime Self-Adaptation: Concepts, Models, and Challenges -- 2.1. Introduction -- 2.2. Motivation: A Web-Mashup Application -- 2.3. Adaptation vs. Self-Adaptation -- 2.3.1. Basic Definitions -- 2.3.2. Architecting Software for Adaptation and Self-Adaptation -- 2.3.2.1. Architecting for adaptation -- 2.3.2.2. Architecting for self-adaptation -- 2.3.2.3. Implications of self-adaptation -- 2.4. Foundational Concepts for Architecting Self-Adaptive Software -- 2.4.1. Fundamental Dimensions of Self-Adaptive Software -- 2.4.2. Self-Adaptation Goals -- 2.4.2.1. Self-properties as self-adaptation goals. , 2.4.2.2. Nonfunctional requirements as self-adaptation goals -- 2.4.3. Self-Adaptation Fundamental Properties -- 2.4.4. Sensors and Effectors -- 2.4.5. Uncertainty and Dynamic Context -- 2.5. Reference Models for Architecting Self-Adaptive Software -- 2.5.1. The Feedback Loop Model of Control Theory -- 2.5.2. The MAPE-K Model -- 2.5.3. Kramer and Magees Self-Management Reference Model -- 2.5.4. The DYNAMICO Reference Model -- 2.5.4.1. The control objectives feedback loop (CO-FL) -- 2.5.4.2. The adaptation feedback loop (A-FL) -- 2.5.4.3. The context monitoring feedback loop (M-FL) -- 2.5.5. The Autonomic Computing Reference Architecture (ACRA) -- 2.6. Major Architectural Challenges in Self-Adaptation -- 2.7. Summary -- References -- Chapter 3: A Classification Framework of Uncertainty in Architecture-Based Self-Adaptive Systems With Multiple Quality Re... -- 3.1. Introduction -- 3.1.1. Background -- 3.1.1.1. Self-adaptive systems -- 3.1.1.2. Architecture-based self-adaptation -- 3.1.1.3. Architecture-based self-adaptive systems with multiple quality requirements -- 3.1.1.4. Uncertainty in architecture-based self-adaptive systems -- 3.1.2. Related Work -- 3.2. Study Design -- 3.2.1. Research Questions -- 3.2.2. Search Strategy -- 3.2.2.1. Search scope and automatic search -- 3.2.2.2. Overview of search process -- 3.2.2.3. Refining the search results -- 3.2.2.3.1. Inclusion criteria -- 3.2.2.3.2. Exclusion criteria -- 3.2.3. Data Extraction -- 3.2.4. Data Items -- 3.2.5. Quality Assessment of Selected Papers -- 3.3. Results -- 3.3.1. Quality of Selected Papers -- 3.3.2. RQ1: What Are the Current Architecture-Based Approaches Tackling Uncertainty in Self-Adaptive Systems With Multipl... -- 3.3.3. RQ2: What Are the Different Uncertainty Dimensions Which Are Explored by These Approaches?. , 3.3.3.1. RQ2.a: What Are the Options for These Uncertainty Dimensions? -- 3.3.4. RQ3: What Sources of Uncertainties Are Addressed by These Approaches? -- 3.3.5. RQ4: How Are the Current Approaches Classified According to the Proposed Uncertainty Classification Framework? -- 3.4. Discussion -- 3.4.1. Analysis of Derived Sources of Uncertainty Based on Uncertainty Dimensions -- 3.4.1.1. Environment uncertainty -- 3.4.1.2. Goals uncertainty -- 3.4.1.3. Adaptation functions uncertainty -- 3.4.1.4. Model uncertainty -- 3.4.2. Main Findings and Implications for Researchers -- 3.4.2.1. Model uncertainty is investigated in both design and runtime -- 3.4.2.2. Uncertainty is often explored at scenario level regardless of emerging time -- 3.4.2.3. Uncertainty starting to get acknowledged in both design and runtime -- 3.4.2.4. Current approaches mainly focus on tackling uncertainty due to variability through approaches in both design and... -- 3.4.2.5. Most commonly addressed source of uncertainty is dynamicity of environment -- 3.4.2.6. Future goal changes is the second most important uncertainty source -- 3.4.3. Limitations of the Review and Threats to Validity -- 3.4.3.1. Bias -- 3.4.3.2. Domain of study -- 3.5. Conclusion and Future Work -- Appendix -- References -- Chapter 4: An Architecture Viewpoint for Modeling Dynamically Configurable Software Systems -- 4.1. Introduction -- 4.2. Architecture Viewpoints -- 4.3. Case Study: DDSCM Systems -- 4.4. Metamodel for Runtime Adaptability Viewpoint -- 4.5. Runtime Adaptability Viewpoint -- 4.5.1. Method for Applying the Adaptability Viewpoint -- 4.6. Case Study-Adaptability View of the SCM Software Architecture -- 4.7. Related Work -- 4.7.1. Quality Concerns in Software Architecture Modeling -- 4.7.2. Architectural Approaches for Runtime Adaptability -- 4.8. Conclusion -- References. , Chapter 5: Adaptive Security for Software Systems -- 5.1. Introduction -- 5.2. Motivation -- 5.3. Security Engineering State-of-the-Art -- 5.3.1. Design-Time Security Engineering -- 5.3.1.1. Early-stage security engineering -- 5.3.1.2. Later-stage security engineering -- 5.3.2. Security Retrofitting -- 5.3.3. Adaptive Application Security -- 5.4. Runtime Security Adaptation -- 5.4.1. Supporting Manual Adaptation Using MDSE@R -- 5.4.2. Automated Adaptation Using Vulnerability Analysis and Mitigation -- 5.4.2.1. OCL-based vulnerability analyzer -- 5.4.2.2. Vulnerability mitigation -- 5.4.2.3. Vulnerability mitigation component -- 5.5. Usage Example -- 5.5.1. Task 1-Model Galactic System Description-One-Time Task -- 5.5.2. Task 2-Model Swinburne Security Needs -- 5.5.3. Task 3-System-Security Weaving -- 5.5.4. Task 4-Galactic Security Testing -- 5.5.5. Task 5-Galactic Continuous Vulnerability Analysis and Mitigation -- 5.6. Discussion -- 5.7. Chapter Summary -- Appendix -- Platform Implementation -- MDSE@R: Model-Driven Security Engineering at Runtime -- Vulnerability Analysis and Mitigation -- References -- Part II: Analyzing and Evaluating Trade-Offs in Self-Adaptive Software Architectures -- Chapter 6: Automated Inference Techniques to Assist With the Construction of Self-Adaptive Software -- 6.1. Introduction -- 6.2. Motivating Application -- 6.3. Shortcomings With the State-of-the-Art -- 6.3.1. Goal Management -- 6.3.2. Change Management -- 6.4. Overview of Inference-Based Techniques -- 6.5. Learning-Based Approach for Goal Management -- 6.5.1. Learning Cycle -- 6.5.2. Adaptation Cycle -- 6.5.3. Experimental Results -- 6.5.4. Noteworthy Research Challenges and Risks -- 6.5.4.1. Extraneous and confounding variables -- 6.5.4.2. Overhead of monitoring and learning -- 6.5.4.3. Adaptation in the presence of uncertainty. , 6.5.4.4. Structure of learned model -- 6.6. Mining-Based Approach for Change Management -- 6.6.1. Mining for Runtime Dependencies -- 6.6.2. Using the Mined Dependencies -- 6.6.3. Experimental Results -- 6.6.4. Noteworthy Research Challenges and Risks -- 6.6.4.1. Long-living transactions and high workload -- 6.6.4.2. Overhead of mining and updating predictions -- 6.6.4.3. Transaction coverage and other forms of mining -- 6.7. Related Work -- 6.8. Conclusion -- References -- Chapter 7: Evaluating Trade-Offs of Human Involvement in Self-Adaptive Systems -- 7.1. Introduction -- 7.2. Motivating Scenario -- 7.2.1. System Objectives -- 7.2.2. Adaptation Mechanisms -- 7.3. Related Work -- 7.4. Analyzing Trade-Offs in Self-Adaptation -- 7.4.1. Adaptation Model -- 7.4.1.1. Tactic -- 7.4.1.2. Strategy -- 7.4.1.3. Utility profile -- 7.4.2. Adaptation Strategy Selection -- 7.5. Analyzing Trade-Offs of Involving Humans in Adaptation -- 7.5.1. Human Model -- 7.5.1.1. Opportunity -- 7.5.1.2. Willingness -- 7.5.1.3. Capability -- 7.5.2. Integrating Human and Adaptation Models -- 7.5.2.1. Tactics -- 7.5.2.2. Strategies -- 7.6. Reasoning About Human-in-the-Loop Adaptation -- 7.6.1. Model Checking Stochastic Multiplayer Games -- 7.6.2. Formal Model -- 7.6.2.1. Player definition -- 7.6.2.2. Environment -- 7.6.2.3. Human model -- 7.6.2.4. System -- 7.6.2.5. Adaptation logic -- 7.6.2.6. Utility profile -- 7.6.3. Analysis -- 7.6.3.1. Strategy utility -- 7.6.3.2. Strategy selection -- 7.7. Conclusion -- References -- Chapter 8: Principled Eliciting and Evaluation of Trade-Offs When Designing Self-Adaptive Systems Architectures -- 8.1. Introduction -- 8.2. Requirements for Automated Architecture Design and Analysis -- 8.3. The DuSE Approach for Automated Architecture Design and Analysis -- 8.3.1. The Rationale -- 8.3.2. The Approach -- 8.3.3. Tool Support. , 8.4. Automating the Design and Analysis of Self-Adaptive Systems Architectures.
    Additional Edition: ISBN 0-12-802855-6
    Language: English
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 4
    UID:
    almahu_9948026538902882
    Format: 1 online resource (0 p.)
    Edition: 1st edition
    ISBN: 0-12-802541-7
    Content: Software Quality Assurance in Large Scale and Complex Software-intensive Systems presents novel and high-quality research related approaches that relate the quality of software architecture to system requirements, system architecture and enterprise-architecture, or software testing. Modern software has become complex and adaptable due to the emergence of globalization and new software technologies, devices and networks. These changes challenge both traditional software quality assurance techniques and software engineers to ensure software quality when building today (and tomorrow’s) adaptive, context-sensitive, and highly diverse applications. This edited volume presents state of the art techniques, methodologies, tools, best practices and guidelines for software quality assurance and offers guidance for future software engineering research and practice. Each contributed chapter considers the practical application of the topic through case studies, experiments, empirical validation, or systematic comparisons with other approaches already in practice. Topics of interest include, but are not limited, to: quality attributes of system/software architectures; aligning enterprise, system, and software architecture from the point of view of total quality; design decisions and their influence on the quality of system/software architecture; methods and processes for evaluating architecture quality; quality assessment of legacy systems and third party applications; lessons learned and empirical validation of theories and frameworks on architectural quality; empirical validation and testing for assessing architecture quality. Focused on quality assurance at all levels of software design and development Covers domain-specific software quality assurance issues e.g. for cloud, mobile, security, context-sensitive, mash-up and autonomic systems Explains likely trade-offs from design decisions in the context of complex software system engineering and quality assurance Includes practical case studies of software quality assurance for complex, adaptive and context-critical systems
    Note: Description based upon print version of record. , Front Cover -- Software Quality Assurance -- Copyright Page -- Contents -- List of Contributors -- Biography -- Deployability -- Release Plan -- Moving Through the Tool Chain -- Trade-offs -- General Scenarios and Tactics -- Microservices -- Continuous Deployment -- Roll Back -- The Number of Quality Attributes Is Growing -- References -- Foreword -- References -- Preface -- Introduction -- Why a New Book on Software Quality -- Book Outline -- 1 Quality concerns in large-scale and complex software-intensive systems -- 1.1 Introduction -- 1.2 Software Quality Management -- 1.3 Software Quality Models -- 1.4 Addressing System Qualities -- 1.5 Assessing System Qualities -- 1.5.1 Assessment Processes -- 1.5.2 Metrics and Measurements -- 1.6 Current Challenges and Future Directions of Software Quality -- 1.7 Conclusion -- References -- 2 An introduction to modern software quality assurance -- 2.1 Introduction -- 2.2 Requirement Conformance Versus Customer Satisfaction -- 2.3 Measurement -- 2.4 Quality Perspectives -- 2.5 Quality Models -- 2.6 Non-Functional Requirements -- 2.7 Cost of Quality -- 2.8 Verification and Validation -- 2.9 Role of Formal Methods -- 2.10 Role of Testing and Automated Testing -- 2.11 Reliability -- 2.12 Security -- 2.13 Safety -- 2.14 Reviews and Usability -- 2.15 Reviews and Postmortems -- 2.16 User Experience -- 2.17 Social Media, Cloud Computing, and Crowdsourcing -- 2.18 Maintenance and Change Management -- 2.19 Defect Analysis and Process Improvement -- 2.20 Role of Product and Process Metrics -- 2.21 Statistical SQA -- 2.22 Change Management -- 2.23 Agile Development Processes -- 2.24 Conclusions/Best Practices -- References -- 3 Defining software quality characteristics to facilitate software quality control and software process improvement -- 3.1 Overview -- 3.2 Process Based Approaches to Software Quality. , 3.3 Review of the Structure and Utility of Software Quality characterization Models -- 3.3.1 Quality Factor Perspectives and Definitions -- 3.3.2 Defining Criteria for Quality Factors -- 3.3.3 Metrics for Defining the Presence of Quality Factors -- 3.3.3.1 Metric versus measurement -- 3.4 Defining an Organization's Software Quality Characterization Model -- 3.4.1 Step 1: Document the Quality Factors and Model Hierarchy -- 3.4.2 Step 2: Document the Quality Characterization Model's Internal Metrics -- 3.4.3 Step 3: Document the Quality Characterization Model's External Metrics -- 3.4.3.1 Which external metrics should be documented as requirements? -- 3.4.3.2 Which external metrics should be subjected to dynamic testing? -- 3.5 Software Quality Control's Utilization of the Quality Characterization Model -- 3.5.1 Systems Analysis -- 3.5.2 Systems Design -- 3.5.3 Development -- 3.5.4 Testing the Presence of External Metrics for a Given Quality Factor -- 3.6 SPI Utilization of the Quality Characterization Model -- 3.6.1 Measuring and Monitoring Quality Factors and Related Metrics -- 3.6.2 Process Improvements Related to Software Quality Characterization Models -- 3.7 Concluding Remarks -- References -- 4 Quality management and software process engineering -- 4.1 Motivation -- 4.2 Our Notion of Process -- 4.3 Quality Management -- 4.4 Software Process (SP) -- 4.5 Software Quality -- 4.6 Quality Management Through SP Engineering -- 4.6.1 Localizing Focus on Quality -- 4.6.1.1 Requirements engineering and management -- 4.6.1.2 Engineering technical specifications -- 4.6.1.3 System architectural design -- 4.6.1.4 System engineering design -- 4.6.1.5 Software architectural design -- 4.6.1.6 Software engineering design -- 4.6.1.7 Software construction engineering -- 4.6.1.8 Software installation engineering -- 4.6.1.9 Software commissioning engineering. , 4.6.1.10 Software operations engineering -- 4.6.1.11 Software maintenance engineering -- 4.6.1.12 Software re(verse) engineering -- 4.6.2 Controls Based on "Progress" and Life cycle Models of SP -- 4.6.3 Process Quality and Quality Management -- 4.6.4 Contextual Constraints -- 4.7 Conclusion -- References -- 5 Architecture viewpoints for documenting architectural technical debt -- 5.1 Introduction -- 5.2 Background and Related Work -- 5.2.1 Architectural Technical Debt -- 5.2.2 Technical Debt Documentation -- 5.3 Typical Stakeholders and Concerns -- 5.3.1 ATD Stakeholders -- 5.3.2 Concerns on ATD -- 5.4 ATD Viewpoints -- 5.4.1 ATD Detail Viewpoint -- 5.4.2 ATD Decision Viewpoint -- 5.4.3 ATD-Related Component Viewpoint -- 5.4.4 ATD Distribution Viewpoint -- 5.4.5 ATD Stakeholder Involvement Viewpoint -- 5.4.6 ATD Chronological viewpoint -- 5.5 Case Study -- 5.5.1 Study Objective and Research Questions -- 5.5.2 Study Execution -- 5.5.2.1 Case description -- 5.5.2.2 Data collection -- 5.5.2.2.1 Data to be collected -- 5.5.2.2.2 Data collection method -- 5.5.2.2.3 Data collection process -- 5.5.3 Results -- 5.5.3.1 Understandability of ATD viewpoints (RQ1) -- 5.5.3.2 Ease of collecting the required information and documenting ATD views (RQ2) -- 5.5.3.3 Usefulness in understanding ATD (RQ3) -- 5.5.4 Interpretation -- 5.5.4.1 Interpretation of the results regarding RQ1 -- 5.5.4.2 Interpretation of the results regarding RQ2 -- 5.5.4.3 Interpretation of the results regarding RQ3 -- 5.5.5 Implications for Research and Practice -- 5.5.6 Threats to Validity -- 5.6 Conclusions and Future Work -- Acknowledgment -- Appendix A. ATD Concerns -- Appendix B. Viewpoint Definitions and Correspondence Rules -- B.1 Metamodel of ATD Viewpoints -- B.2 ATD Decision Viewpoint -- B.2.1 Model kind -- B.3 ATD-Related Component Viewpoint -- B.3.1 Model kind. , B.4 ATD Distribution Viewpoint -- B.4.1 Model kind -- B.5 ATD Stakeholder Involvement Viewpoint -- B.5.1 Model kind -- B.6 ATD Chronological Viewpoint -- B.6.1 Model kind -- B.7 ATD Detail Viewpoint -- B.7.1 Model kind -- B.8 Correspondences Between Viewpoints -- References -- 6 Quality management and Software Product Quality Engineering -- 6.1 Limitations of the Current Software Practices -- 6.1.1 Quality Management During the Lifecycle -- 6.1.2 Managing Software Quality Requirements -- 6.1.3 Support for Utilizing Institutional Knowledge -- 6.2 Principles of Software Product Quality Engineering -- 6.2.1 Holistic View of Product Quality -- 6.2.2 Engineering Quality with Patterns -- 6.2.2.1 Structure of a quality pattern -- 6.2.2.2 Catalog of quality patterns -- 6.2.2.3 Functional Correctness Patterns -- 6.2.3 Compositional Traceability -- 6.2.4 Process-Product Correlation -- 6.3 Case Study -- 6.3.1 Process Instantiation and Configuration Structure -- 6.3.2 Software Quality Requirements -- 6.3.3 Consistency Tracker -- 6.4 Conclusion -- References -- 7 "Filling in the blanks": A way to improve requirements management for better estimates -- 7.1 Introduction -- 7.2 Meeting the "Voice of the Customer": QFD -- 7.3 "Filling in the Blanks": How to Further Improve Estimation Capability? -- 7.3.1 What Could be Missing? Coming Back to Early Phases… -- 7.3.2 Working on Requirements -- 7.3.3 Working with Stakeholders (with the Proper Requirements) -- 7.4 Improving QFD: QF2D -- 7.5 QF2D: Example Calculation -- 7.6 Conclusions and Next Steps -- References -- 8 Investigating software modularity using class and module level metrics -- 8.1 Introduction -- 8.2 Software Quality Measurement -- 8.3 Software Measurement -- 8.4 Software Modularity -- 8.5 Coupling and Cohesion Metrics -- 8.6 Coupling and Cohesion Metrics at Higher Levels of Granularity. , 8.7 Coupling and Cohesion Metrics Utilized in This Study -- 8.8 Empirical Study -- 8.9 Objectives and Research Questions -- 8.10 Empirical Design -- 8.10.1 System Selection -- 8.10.2 Data Collection and Analysis -- 8.11 Results -- 8.11.1 RQ1: Can we Characterize through Metrics, HLMs in Weka, and Thus Indicate Good/bad Candidate, HLMs? -- 8.11.2 RQ2: Are Coupling Metrics at this High Level of Modularity Reflective of Coupling Metrics at Lower Levels of Granula... -- 8.12 Discussion -- 8.13 Validity and Reliability -- 8.14 Conclusion -- Acknowledgment -- References -- 9 Achieving quality on software design through test-driven development -- 9.1 Introduction -- 9.2 Evidences on the Influence of TDD on Software Quality -- 9.3 TDD as a Design Technique -- 9.4 Modeling Relations with TDD -- 9.4.1 Mock Objects -- 9.4.2 Designing Dependencies -- 9.4.3 Hierarchy and Abstractions -- 9.5 Large Refactorings -- 9.6 Combining TDD with Other Design Techniques -- 9.6.1 Architectural Design -- 9.6.2 Domain Modeling -- 9.6.3 Design Patterns -- 9.7 Preparing for TDD in a Software Project -- 9.8 Continuous Inspection -- 9.9 Conclusions -- References -- 10 Architectural drift analysis using architecture reflexion viewpoint and design structure reflexion matrices -- 10.1 Introduction -- 10.2 Reflexion Modeling -- 10.3 Reflexion Modeling Using Software Architecture Viewpoints -- 10.4 Reflexion Viewpoint -- 10.5 Design Structure Matrix -- 10.6 Design Structure Reflexion Matrix -- 10.7 Possible Applications -- 10.8 Conclusion -- References -- 11 Driving design refinement: How to optimize allocation of software development assurance or integrity requirements -- 11.1 Introduction -- 11.2 Safety Requirements in ARP4754-A -- 11.3 The Issue of Independence in ARP4754-A -- 11.4 Challenges in Requirements Allocation-The Research Problem -- 11.5 Automatic Allocation of DALs. , 11.5.1 HiP-HOPS. , English
    Additional Edition: ISBN 0-12-802301-5
    Language: English
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 5
    Online Resource
    Online Resource
    Waltham, Massachusetts :Morgan Kaufmann,
    UID:
    almahu_9949698075102882
    Format: 1 online resource (380 p.)
    Edition: 1st edition
    ISBN: 0-12-410507-6
    Content: Economics-driven Software Architecture presents a guide for engineers and architects who need to understand the economic impact of architecture design decisions: the long term and strategic viability, cost-effectiveness, and sustainability of applications and systems. Economics-driven software development can increase quality, productivity, and profitability, but comprehensive knowledge is needed to understand the architectural challenges involved in dealing with the development of large, architecturally challenging systems in an economic way. This book covers how to apply economic consider
    Note: Description based upon print version of record. , ""Front Cover""; ""Economics-Driven Software Architecture""; ""Copyright Page""; ""Contents""; ""Acknowledgments""; ""About the Editors""; ""List of Contributors""; ""Foreword by John Grundy Economics-Driven Software Architecting""; ""Requirements impact on architecture economics""; ""Technology impact on architecture economics""; ""Environmental impact on architecture economics""; ""Process impact on architecture economics""; ""Team impact on architecture economics""; ""Business impact on architecture economics""; ""About the Author""; ""References""; ""Foreword by Len Bass"" , ""About the Author""""References""; ""Preface""; ""Introduction""; ""Issues in economics-based and value-oriented software design""; ""Book overview""; ""Part 1�Fundamentals""; ""Part 2�Economics-driven architecting: design mechanisms and evaluation""; ""Part 3�Managing architectural economics""; ""Part 4�Linking architecture inception and evolution to economics: experiences and approaches""; ""Reference""; ""1 Economics-Driven Software Architecture: Introduction""; ""1.1 Introduction""; ""1.2 Architecture and project management""; ""1.3 Architecture-based economic modeling"" , ""1.4 Architecture-based benefit modeling""""1.5 Architecture and risk management""; ""1.6 Architecture and agility""; ""1.7 Runtime economics-driven architecting""; ""1.8 Final thoughts""; ""References""; ""I: Fundamentals of Economics-Driven Software Architecture""; ""2 Economic Models and Value-Based Approaches for Product Line Architectures""; ""2.1 Introduction""; ""2.2 Background""; ""2.2.1 Fundamentals of SPLE""; ""2.2.2 Economic models""; ""2.2.3 Software architecture""; ""2.3 Research framework""; ""2.4 Economic models for software product lines"" , ""2.5.4 Issue-based variability management""""2.5.5 Value-based portfolio optimization""; ""2.5.6 Discussion and summary""; ""2.6 Discussion on architectural issues""; ""2.7 Related work""; ""2.8 Conclusion""; ""References""; ""3 Aspects of Software Valuation""; ""3.1 Introduction""; ""3.2 Basics of economic analysis""; ""3.3 Valuation of software""; ""3.3.1 Valuating a commercial software product""; ""3.3.2 Valuating in-house (Internally Developed) software""; ""3.3.3 Generalizing the valuation approach""; ""3.4 Capitalize software investments or not?""; ""3.4.1 What is capitalization?"" , ""3.4.2 Basic depreciation accounting"" , English
    Additional Edition: ISBN 0-12-410464-9
    Additional Edition: ISBN 1-306-85976-X
    Language: English
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 6
    UID:
    almahu_9948025599602882
    Format: 1 online resource (xl, 392 pages) : , illustrations (some color)
    Edition: 1st edition
    ISBN: 0-12-407885-0
    Series Statement: Gale eBooks
    Content: Agile software development approaches have had significant impact on industrial software development practices. Today, agile software development has penetrated to most IT companies across the globe, with an intention to increase quality, productivity, and profitability. Comprehensive knowledge is needed to understand the architectural challenges involved in adopting and using agile approaches and industrial practices to deal with the development of large, architecturally challenging systems in an agile way. Agile Software Architecture focuses on gaps in the requirements of a
    Note: Description based upon print version of record. , Machine generated contents note: Chapter 1: Introduction to ASA ASA: The State-of-the-Art ASA: Industrial/commercial perspective ASA: Current Challenges and Future Directions Part I: Fundamentals of Agile Architecting Chapter 2: The DCI Paradigm: Beyond Class-Oriented Architecture to Object Orientation Chapter 3: Refactoring software architecture Chapter 4: Architecture Decisions: Who, How and When? Part II: Managing Software Architecture in Agile Projects Chapter 5: Combining agile development and variability handling to achieve adaptable software architectures Chapter 6: Agile software architecture knowledge management Chapter 7: Continuous software architecture analysis Chapter 8: Bridging user stories and software architectures: a guidance support for agile architecting Part III: Agile Architecting in Specific Domains Chapter 9: Architecture-centric testing for security: An agile perspective Chapter 10: Multi-tenancy multi-target architectures: Extending multi-tenancy architectures for agile deployment and development Part IV: Industrial Viewpoints on Agile Architecting Chapter 11: Bursting the Agile Bubble Anti-Pattern Chapter 12: Building a Platform for Innovation: Architecture and Agile as Key Enablers Chapter 13: Opportunities, threats and limitations of emergent architecture Chapter 14: Aviva GI: Architecture as a Key Driver for Agile Success. , English
    Additional Edition: ISBN 0-12-407772-2
    Additional Edition: ISBN 1-306-17613-1
    Language: English
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 7
    UID:
    b3kat_BV023275385
    Format: xxxv, 316 S. , 235 mm x 155 mm
    ISBN: 9783540775829 , 354077582X
    Note: Literaturverz. S. [269] - 293
    Language: English
    Subjects: Computer Science
    RVK:
    Keywords: Software Engineering ; Requirements engineering ; Entscheidungsfindung ; Rationalprinzip
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 8
    UID:
    edoccha_BV042314369
    Format: 1 Online-Ressource (xl, 392 Seiten) : , Illustrationen, Diagramme.
    ISBN: 978-0-12-407772-0 , 978-0-12-407885-7
    Note: Focuses on principles of Agile software development and gaps in the requirements of applying architecture-centric approaches. Readers will learn how Agile and architectural cultures can co-exist and support each other according to the context
    Additional Edition: Erscheint auch als Druck-Ausgabe, Paperback ISBN 978-0-12-407772-0
    Language: English
    Subjects: Computer Science
    RVK:
    Keywords: Agile Softwareentwicklung ; Aufsatzsammlung
    URL: Volltext  (URL des Erstveröffentlichers)
    Author information: Ali Babar, Muhammad
    Author information: Brown, Alan W. 1962-
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 9
    Online Resource
    Online Resource
    Cambridge, MA :Morgan Kaufmann Publishers,
    UID:
    almafu_BV045131364
    Format: 1 Online-Ressource (XXXVIII, 432 Seiten) : , Illustrationen, Diagramme.
    ISBN: 978-0-12-809338-2
    Content: Software architecture for Big Data and the Cloud is designed to be a single resource that brings together research on how software architectures can solve the challenges imposed by building big data software systems. The challenges of big data on the software architecture can relate to scale, security, integrity, performance, concurrency, parallelism, and dependability, amongst others. Big data handling requires rethinking architectural solutions to meet functional and non-functional requirements related to volume, variety and velocity. The book's editors have varied and complementary backgrounds in requirements and architecture, specifically in software architectures for cloud and big data, as well as expertise in software engineering for cloud and big data. This book brings together work across different disciplines in software engineering, including work expanded from conference tracks and workshops led by the editors
    Additional Edition: Erscheint auch als Druck-Ausgabe ISBN 978-0-12-805467-3
    Language: English
    Subjects: Computer Science
    RVK:
    Keywords: Softwarearchitektur ; Big Data ; Cloud Computing
    URL: Volltext  (URL des Erstveröffentlichers)
    URL: Volltext  (URL des Erstveröffentlichers)
    Author information: Heisel, Maritta
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 10
    UID:
    almafu_BV042314369
    Format: 1 Online-Ressource (xl, 392 Seiten) : , Illustrationen, Diagramme.
    ISBN: 978-0-12-407772-0 , 978-0-12-407885-7
    Note: Focuses on principles of Agile software development and gaps in the requirements of applying architecture-centric approaches. Readers will learn how Agile and architectural cultures can co-exist and support each other according to the context
    Additional Edition: Erscheint auch als Druck-Ausgabe, Paperback ISBN 978-0-12-407772-0
    Language: English
    Subjects: Computer Science
    RVK:
    Keywords: Agile Softwareentwicklung ; Aufsatzsammlung
    URL: Volltext  (URL des Erstveröffentlichers)
    Author information: Ali Babar, Muhammad
    Author information: Brown, Alan W. 1962-
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
Close ⊗
This website uses cookies and the analysis tool Matomo. Further information can be found on the KOBV privacy pages