ATAM: Method for architecture evaluation (Technical report. Carnegie Mellon University. Software Engineering Institute) Review
Showing posts with label architecture. Show all posts
Showing posts with label architecture. Show all posts
Wednesday, April 6, 2011
Saturday, January 22, 2011
Using the Architecture Tradeoff Analysis Method[superscript SM] to evaluate a reference architecture: A case study (Technical note / Carnegie Mellon. Software Engineering Institute)
Using the Architecture Tradeoff Analysis Method[superscript SM] to evaluate a reference architecture: A case study (Technical note / Carnegie Mellon. Software Engineering Institute) Review
Using the Architecture Tradeoff Analysis Method[superscript SM] to evaluate a reference architecture: A case study (Technical note / Carnegie Mellon. Software Engineering Institute) Feature
Rerate Products
Customer Review
Wednesday, February 17, 2010
A Generic Fault-Tolerant Architecture for Real-Time Dependable Systems
A Generic Fault-Tolerant Architecture for Real-Time Dependable Systems Review
A Generic Fault-Tolerant Architecture for Real-Time Dependable Systems Feature
The design of computer systems to be embedded in critical real-time applications is a complex task. Such systems must not only guarantee to meet hard real-time deadlines imposed by their physical environment, they must guarantee to do so dependably, despite both physical faults (in hardware) and design faults (in hardware or software). A fault-tolerance approach is mandatory for these guarantees to be commensurate with the safety and reliability requirements of many life- and mission-critical applications.
A Generic Fault-Tolerant Architecture for Real-Time Dependable Systems explains the motivations and the results of a collaborative project(*), whose objective was to significantly decrease the lifecycle costs of such fault-tolerant systems. The end-user companies participating in this project currently deploy fault-tolerant systems in critical railway, space and nuclear-propulsion applications. However, these are proprietary systems whose architectures have been tailored to meet domain-specific requirements. This has led to very costly, inflexible, and often hardware-intensive solutions that, by the time they are developed, validated and certified for use in the field, can already be out-of-date in terms of their underlying hardware and software technology.
The project thus designed a generic fault-tolerant architecture with two dimensions of redundancy and a third multi-level integrity dimension for accommodating software components of different levels of criticality. The architecture is largely based on commercial off-the-shelf (COTS) components and follows a software-implemented approach so as to minimise the need for special hardware. Using an associated development and validation environment, system developers may configure and validate instances of the architecture that can be shown to meet the very diverse requirements of railway, space, nuclear-propulsion and other critical real-time applications. This book describes the rationale of the generic architecture, the design and validation of its communication, scheduling and fault-tolerance components, and the tools that make up its design and validation environment. The book concludes with a description of three prototype systems that have been developed following the proposed approach.
(*) Esprit project No. 20716: GUARDS: a Generic Upgradable Architecture for Real-time Dependable Systems.
Rerate Products
Customer Review
Thursday, January 14, 2010
Model Driven Architecture
Model Driven Architecture Review
Model Driven Architecture Feature
This book constitutes the refereed proceedings of the 4th European Conference on Model Driven Architecture - Foundations and Applications, ECMDA-FA 2008, held in Berlin, Germany, in June 2008.
The 31 revised full papers presented - 21 research papers and 10 industry papers - were carefully reviewed and selected from 87 submissions. The papers address all current issues of model-driven architecture, i.e. model management, executable models, concrete syntaxes, aspects, and concerns, validation and testing, model-based systems engineering, model-driven development and service-oriented architectures, and the application of model-driven development. The papers are organized in topical sections on model management, executable models, concrete syntaxes, aspects and concerns, validation and testing, model-based systems engineering, model-driven development and service-oriented architectures, as well as surveys on applying model-driven development.
Rerate Products
Customer Review
Friday, October 30, 2009
Just Enough Software Architecture: A Risk-Driven Approach
Just Enough Software Architecture: A Risk-Driven Approach Review
Just Enough Software Architecture: A Risk-Driven Approach Feature
This is a practical guide for software developers, and different than other software architecture books. Here's why:
It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face.
It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties.
It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts.
It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail.
It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.
Rerate Products
Customer Review
Subscribe to:
Posts (Atom)