Choose an application

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

In component-based software engineering, performance prediction approaches support the design of business information systems on the architectural level. They are based on behavior specifications of components. This work presents a round-trip approach for using, assessing, and certifying the accuracy of parameterized, probabilistic, deterministic, and concurrent performance specifications. Its applicability and effectiveness are demonstrated using the CoCoME benchmark.

Accuracy --- Component-Based Software Engineering (CBSE) --- Performance Prediction --- Common Component Modeling Example (CoCoME) --- Certification

Choose an application

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

A key aspect of cyber-physical systems (CPS) is their potential for integrating information technologies with embedded control systems and physical systems to form new or improved functionalities. CPS thus draws upon advances in many areas. This positioning provides unprecedented opportunities for innovation, both within and across existing domains. However, at the same time, it is commonly understood that we are already stretching the limits of existing methodologies. In embarking towards CPS with such unprecedented capabilities, it becomes essential to improve our understanding of CPS complexity and how we can deal with it. Complexity has many facets, including complexity of the CPS itself, of the environments in which the CPS acts, and in terms of the organizations and supporting tools that develop, operate, and maintain CPS. This book is a result of a journal Special Issue, with the objective of providing a forum for researchers and practitioners to exchange their latest achievements and to identify critical issues, challenges, opportunities, and future directions for how to deal with the complexity of future CPS. The contributions include 10 papers on the following topics: (I) Systems and Societal Aspects Related to CPS and Their Complexity; (II) Model-Based Development Methods for CPS; (III) CPS Resource Management and Evolving Computing Platforms; and (IV) Architectures for CPS.

component-based software engineering --- mode --- mode-switch --- complexity --- cyber-physical systems --- systems engineering --- uncertainty --- microgrid --- distributed design --- self-similar architecture --- plug-n-play --- distributed control --- distribution network --- field test --- autonomous cyber-physical systems --- resilience --- ethics --- nano-bio-info-cogno technologies --- smart cyber-physical systems --- self-generated intelligence --- ampliative reasoning mechanism --- procedural abduction --- data-driven system control --- run-time acquired data --- computational functions --- self-adaptation capability --- human/socially-centered applications --- embedded systems --- software component --- component-based development --- CBD --- GPU --- GPU component --- allocation --- component allocation --- architecture layer --- time-triggered system --- real-time --- adaptation --- scheduling --- multi-core --- real-time systems --- Fixed-Priority Preemptive Scheduling (FPPS) --- mixed-criticality systems --- n/a --- Cyber Physical Systems --- Reactive Systems --- Model-Based Design --- Embedded Systems --- Automatic Code Generation --- IDE --- Internet of Things --- model testing --- mutation testing --- energy consumption --- EAST-ADL

Choose an application

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

A revolutionary concept-based approach to thinking about, designing, and interacting with software As our dependence on technology increases, the design of software matters more than ever before. Why then is so much software flawed? Why hasn't there been a systematic and scalable way to create software that is easy to use, robust, and secure? Examining these issues in depth, The Essence of Software introduces a theory of software design that gives new answers to old questions. Daniel Jackson explains that a software system should be viewed as a collection of interacting concepts, breaking the functionality into manageable parts and providing a new framework for thinking about design. Through this radical and original perspective, Jackson lays out a practical and coherent path, accessible to anyone from strategist and marketer to UX designer, architect, or programmer⁰́₄for making software that is empowering, dependable, and a delight to use. Jackson explores every aspect of concepts⁰́₄what they are and aren⁰́₉t, how to identify them, how to define them, and more⁰́₄and offers prescriptive principles and practical tips that can be applied cost-effectively in a wide range of domains. He applies these ideas to contemporary software designs, drawing examples from leading software manufacturers such as Adobe, Apple, Dropbox, Facebook, Google, Microsoft, Twitter, and others. Jackson shows how concepts let designers preserve and reuse design knowledge, rather than starting from scratch in every project. An argument against the status quo and a guide to improvement for both working designers and novices to the field, The Essence of Software brings a fresh approach to software and its creation.

Software architecture. --- Computer software. --- Architecture, Software --- Computer software --- Computer software architecture --- Software, Computer --- Computer systems --- Architecture --- Design --- Development. --- Development of computer software --- Software development --- Abstraction (software engineering). --- Agile software development. --- Application programming interface. --- Assertion (software development). --- Authentication. --- Axiomatic design. --- Body of knowledge. --- Cognitive dimensions of notations. --- Command language. --- Component-based software engineering. --- Computer-aided design. --- Computing. --- Concept. --- Concepts (C++). --- Conceptual model. --- Cursor (user interface). --- Data model. --- Data set. --- Data type. --- Design knowledge. --- Design pattern. --- Design thinking. --- Design tool. --- Design. --- Designer. --- Diagram. --- Discoverability. --- Dropbox (service). --- Email. --- Engineering. --- Explanation. --- Functional requirement. --- GRASP (object-oriented design). --- Gmail. --- Graphical user interface. --- HTTPS. --- Implementation. --- Information infrastructure. --- Information processor. --- Infrastructure. --- Instance (computer science). --- Interaction design. --- Java (programming language). --- JavaScript. --- Macintosh. --- Metadata. --- Microsoft PowerPoint. --- Motivation. --- OS X. --- Obfuscation (software). --- Object Oriented Role Analysis and Modeling. --- Paragraph. --- Parameter (computer programming). --- Pixel. --- Plug-in (computing). --- Principle. --- Problem domain. --- Programmer. --- Programming idiom. --- Programming language. --- Programming style. --- Programming tool. --- Raw image format. --- Recursion (computer science). --- Rendering (computer graphics). --- Requirement. --- Semantics. --- Server (computing). --- Software architect. --- Software design. --- Software developer. --- Software development. --- Software engineer. --- Software engineering. --- Software industry. --- Software quality. --- Software requirements. --- Software system. --- Software. --- Specification language. --- Stash (software). --- Structuring. --- Subdomain. --- Synchronization (computer science). --- System administrator. --- Theorem. --- Turing Award. --- Twitter. --- Ubiquity (software). --- Uniform Resource Locator. --- Usability. --- Use case. --- User interface design. --- User interface. --- Variable (computer science). --- Version control. --- Website. --- Widget (GUI). --- Workaround. --- Workstation.