Reference Architecture Technology  aggregated

Aggregated evidence

Contextual aspects: Software Project (214), Developer (76), Software Construction (41), Software Design (12), Reference Architecture (7), AUTOSAR Users (2), Automotive Software (2), AUTOSAR partner (2).
Effects: Productivity (209), Development Time (23), Communication (22), Risk (10), Reuse (9), Complexity (8), Maintenance Cost (7), Development Costs (6), Learning Curve (6), Standardization (6), Interoperability (6), Software Quality (6), Ease of Developing (6), Novel design solution (5), Best practices (5), Restriction (5), Best practices (5), Dependability (4), Alignment (4), Flexibility for Suppliers (4), Reputation (4), Terminology Conventions (4), Reliability (3), Latest technologies (3), Investment (3).
Moderators: Reuse (9), Tool Environment (7), Maturity (5), Open standards (4), Knowledge Repository (4), Regulative role (3), Vendor lock-in (3), Organizational thinking (3), Existing software (3).



Reference Architecture Technology  aggregated

Aggregated evidence

Contextual aspects: Software Project (214), Software team (147), Developer (76), Organization (41), Software Construction (41), Software Design (12), Reference Architecture (7), Enterprise Software (5).
Effects: Productivity (209), Development Time (23), Communication (22), Risk (10), Reuse (9), Complexity (8), Maintenance Cost (7), Learning Curve (6), Standardization (6), Interoperability (6), Software Quality (6), Ease of Developing (6), Development Costs (6), Restriction (5), Best practices (5), Novel design solution (5), Dependability (4), Alignment (4), Flexibility for Suppliers (4), Reputation (4), Terminology Conventions (4), Latest technologies (3), Investment (3), Reliability (3).
Moderators: Reuse (9), Tool Environment (7), Maturity (5), Open standards (4), Knowledge Repository (4), Organizational thinking (3), Existing software (3), Vendor lock-in (3), Regulative role (3).



AUTOSAR Technology

Evidence based on the paper "A Survey on the Benefits and Drawbacks of AUTOSAR"

Contextual aspects: Software Project (214), Developer (76), Software Construction (41), Software Design (12), Reference Architecture (7), AUTOSAR Users (2), Automotive Software (2), AUTOSAR partner (2), AUTOSAR (1).
Effects: Productivity (209), Development Time (23), Communication (22), Risk (10), Complexity (8), Maintenance Cost (7), Standardization (6), Ease of Developing (6), Development Costs (6), Software Quality (6), Learning Curve (6), Interoperability (6), Restriction (5), Novel design solution (5), Best practices (5), Reputation (4), Dependability (4), Alignment (4), Terminology Conventions (4), Investment (3).
Moderators: Reuse (9), Tool Environment (7), Knowledge Repository (4), Regulative role (3).



Reference Architecture Technology

Evidence based on the paper "Benefits and Drawbacks of Reference Architectures"

Contextual aspects: Software Project (214), Software Project (214), Developer (76), Software Construction (41), Software Design (12), Reference Architecture (7), Enterprise Software (5), Acquisition Organization (3), SRA Users Team (2), Reference Architecture Vendor (1), Consulting Company (1), Software Vendor (1).
Effects: Productivity (209), Experience (37), Development Time (23), Risk (10), Complexity (8), Maintenance Cost (7), Ease of Developing (6), Learning Curve (6), Development Costs (6), Standardization (6), Restriction (5), Reputation (4), Alignment (4), Dependability (4), Latest technologies (3), Reliability (3), Explicit Knowledge (1).



Kanban Technology  aggregated

Aggregated evidence

Contextual aspects: Software Project (214), Software team (147), Software development process (55), Kanban (41), Customer (8), Management (6).
Effects: Communication (22), Work Visibility (22), Control of project activities and tasks (20), Motivation (16), Flow of work (13), Team Cohesion (10), Workflow (10), Continuous learning (9), Collaboration (8), Task prioritization (8), Time to market (8), External Quality (7), Internal software quality (6), Customer satisfaction (5), Conformance (5), Strategic alignment (5), Dummy concept (3).
Moderators: Organizational Culture (16), Expertise (10), Supporting practices (10), Training (9), Managed communication between team and customer (5).



Kanban Technology  aggregated

Aggregated evidence

Contextual aspects: Software Project (214), Software team (147), Software development process (55), Kanban (41), Customer (8), Management (6).
Effects: Work Visibility (22), Communication (22), Control of project activities and tasks (20), Motivation (16), Flow of work (13), Workflow (10), Team Cohesion (10), Continuous learning (9), Task prioritization (8), Collaboration (8), Time to market (8), External Quality (7), Internal software quality (6), Conformance (5), Customer satisfaction (5), Strategic alignment (5), Dummy concept (3).
Moderators: Organizational Culture (16), Expertise (10), Supporting practices (10), Training (9).



TDD Technology  aggregated

Aggregated evidence

Contextual aspects: Software Project (214), Software team (147), TDD (103), TDD (103), Source Code (85), Source Code (85), Source Code (85), Developer (76), Code Quality (51), Maintenance (51), Code Quality (51), Computer Science Student (37), Change Density (33), Defect Density (32), Bowling Game (28), Testing (26), Development Time (23), External code quality (21), Software Development Methodology (16), Developers (16), Productivity (time spent) (15), Code Refactoring (14), Java Reusable Framework of Components (12), Java Rich Client (10), Compare (5), Implement (4), Implement (4), Comparison (3).
Effects: Coding tests (24), Test-First (8), Test-Last (7).



TDD Technology  aggregated

Aggregated evidence

Contextual aspects: TDD (103), Source Code (85), Developer (76), Developer (76), Pair Programming (22), JEF Framework (9), Programming (4).
Effects: Productivity (209), Code Quality (51), Defect Density (32), External code quality (21), Code Readability (21), Maintainability (20), Documentation Overhead (17), Number of Tests (17), Code Coverage (14), Perfective maintenance (13), Code Quality Confidence (Team) (10), Adaptative Software Changes (7), Ease of Refactoring (6), Mean Change Density (3), Preventive (2), Debugging Effort (2).
Moderators: Discipline (7), Skill (4).



TDD Technology  aggregated

Aggregated evidence

Contextual aspects: TDD (103), Source Code (85), Source Code (85), Source Code (85), Developer (76), Bowling Game (28), Testing (26), Develop (17), Developers (16), Java Rich Client (10), JEF Framework (9).
Effects: Code Quality (51), Code Quality (51), Change Density (33), Defect Density (32), Code Readability (21), Maintainability (20), Development speed (18), Documentation Overhead (17), Productivity(LOC/Man-Hour) (14), Code Quality Confidence (Team) (10), Productivity (output per unit effort) (7), Understandability (7), Test Case Quality (3).
Moderators: Experience (37).



Reference Architecture for variability-intensive service-oriented systems Technology

Evidence based on the paper "Constraints for the design of variability-intensive service-oriented reference architectures–An industrial case study"

Contextual aspects: Software Project (214), Developer (76), Software Construction (41), Software Design (12), Reference Architecture (7), Enterprise Software (5), Acquisition Organization (3), SRA Users Team (2), Reference Architecture for variability-intensive service-oriented systems (1).
Effects: Communication (22), Risk (10), Learning Curve (6), Interoperability (6), Standardization (6), Best practices (5), Flexibility for Suppliers (4).
Moderators: Maturity (5), Open standards (4), Organizational thinking (3), Existing software (3), Vendor lock-in (3).