Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Annotation Systems of Systems (SoS) have become increasingly complex and are frequently used in highly distributed, dynamic, and open environments SoS have emerged as a new class of evolving software systems, where constituent systems (themselves systems in their own right) work cooperatively in order to fulfill specific missions SoS are characterized by managerial and operational independence, geographic distribution, evolutionary development, and creation of emergent behavior These characteristics have therefore raised substantial challenges to software engineering researchers and practitioners.

Systems software

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

This book constitutes the proceedings of the 8th European Conference on Software Architecture, ECSA 2014, held in Vienna, Austria, in August 2014. The 16 full papers and 18 short papers presented in this volume were carefully reviewed and selected from 91 submissions. They are organized in topical sections named: architecture decisions and knowledge; architecture patterns and anti-patterns; reference architectures and metamodels; architecture description languages; enterprise architecture, SOA and cloud computing; components and connectors; quality attributes; and architecture analysis and verification.

Computer science. --- Computer communication systems. --- Software engineering. --- Programming languages (Electronic computers). --- Computer logic. --- Management information systems. --- Computer Science. --- Software Engineering. --- Logics and Meanings of Programs. --- Computer Communication Networks. --- Management of Computing and Information Systems. --- Information Systems Applications (incl. Internet). --- Programming Languages, Compilers, Interpreters. --- Logic design. --- Information Systems. --- Design, Logic --- Design of logic systems --- Digital electronics --- Electronic circuit design --- Logic circuits --- Machine theory --- Switching theory --- Computer software engineering --- Engineering --- Informatics --- Science --- Software architecture --- Architecture, Software --- Computer software --- Computer software architecture --- Architecture --- Design --- Application software. --- Communication systems, Computer --- Computer communication systems --- Data networks, Computer --- ECNs (Electronic communication networks) --- Electronic communication networks --- Networks, Computer --- Teleprocessing networks --- Data transmission systems --- Digital communications --- Electronic systems --- Information networks --- Telecommunication --- Cyberinfrastructure --- Electronic data processing --- Network computers --- Computer science logic --- Logic, Symbolic and mathematical --- Computer languages --- Computer program languages --- Computer programming languages --- Machine language --- Languages, Artificial --- Application computer programs --- Application computer software --- Applications software --- Apps (Computer software) --- Computer-based information systems --- EIS (Information systems) --- Executive information systems --- MIS (Information systems) --- Sociotechnical systems --- Information resources management --- Management --- Distributed processing --- Communication systems

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Technical debt is a metaphor that software developers and managers increasingly use to communicate key trade-offs between business constraints and internal quality issues, especially those related to time to market. While other software engineering disciplines---such as software sustainability, maintenance and evolution, refactoring, software quality, and empirical software engineering---have produced results relevant to managing technical debt, none of them alone suffices to model, manage, and communicate the different facets of the complex trade-offs involved in managing technical debt. Similarly, while many software engineering practices can be used to get ahead of technical debt, organizations struggle with managing technical debt routinely and strategically. Technical debt draws on research from many domains that is becoming part of the answer to the technical-debt question: how do we quantify and monitor the economic impact of decisions over time? This research includes software engineering disciplines in software aging and decay, risk management, qualitative methods and appreciation for context, software metrics, program analysis, and software quality.

Software engineering

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

The Transactions on Pattern Languages of Programming subline aims to publish papers on patterns and pattern languages as applied to software design, development, and use, throughout all phases of the software life cycle, from requirements and design to implementation, maintenance and evolution. The primary focus of this LNCS Transactions subline is on patterns, pattern collections, and pattern languages themselves. The journal also includes reviews, survey articles, criticisms of patterns and pattern languages, as well as other research on patterns and pattern languages. This book, the second volume in the Transactions on Pattern Languages of Programming series, presents five papers that have been through a careful peer review process involving both pattern experts and domain experts. The papers demonstrate techniques for applying patterns in an industrial or research setting. Some have confronted the topic within software engineering; others offer approaches in other pattern domains, which is an indication of the diverse fields where patterns are applied.

Software patterns --- Software architecture --- Programming languages (Electronic computers) --- Engineering & Applied Sciences --- Computer Science --- Software patterns. --- Software architecture. --- Computer languages --- Computer program languages --- Computer programming languages --- Machine language --- Architecture, Software --- Computer software --- Computer software architecture --- Patterns, Software --- Architecture --- Design --- Computer science. --- Computer organization. --- Software engineering. --- Computer programming. --- Programming languages (Electronic computers). --- Management information systems. --- Computer Science. --- Software Engineering/Programming and Operating Systems. --- Programming Techniques. --- Programming Languages, Compilers, Interpreters. --- Computer Systems Organization and Communication Networks. --- Management of Computing and Information Systems. --- Computer-based information systems --- EIS (Information systems) --- Executive information systems --- MIS (Information systems) --- Sociotechnical systems --- Information resources management --- Management --- Electronic data processing --- Languages, Artificial --- Computers --- Electronic computer programming --- Electronic digital computers --- Programming (Electronic computers) --- Coding theory --- Computer software engineering --- Engineering --- Organization, Computer --- Informatics --- Science --- Communication systems --- Programming --- Development --- Computer network architectures. --- Information Systems. --- Architectures, Computer network --- Network architectures, Computer --- Computer architecture

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Information Technology --- Computer Science (Hardware & Networks)