Len Bass from SEI presents the Architectural Trade Off Analysis Method and its relation to architectural evaluation questions: criteria for evaluation, participants, how to focus on the part of the architecture under evaluation, how to know what to look for and how results are presented. He also shows that the highest risk is things omitted, not things that were incorrect.
Guy L. Steele heads the Sun Programming Language Research Group. He's held positions at Carnegie-Mellon University, Tartan Laboratories, and Thinking Machines Corporation and is the author or co-author of several books on languages (Common Lisp, C, High Performance Fortran, the Java Language Specification) as well as "The Hacker's Dictionary" (also known on the Internet as the "Jargon File").
This talk introduces two broad principles for strategic design. 'Context mapping' addresses the fact that different groups model differently. 'Core domain' distills a shared vision of the system's "core domain" and provides a systematic guide to when "good enough" is good enough versus when to push for excellence.
This talk will outline some of the foundations of domain-driven design:How models are chosen and evaluated;How multiple models coexist;How the patterns help avoid the common pitfalls, such as overly interconnected models;How developers and domain experts together in a DDD team engage in deeper exploration of their problem domain and make that understanding tangible as a practical software design.
Dragos Manolescu shares insights gained from growing ThoughtWorks' architecture evaluation practice and evaluating several architectures for Global 1000 companies. These insights aim at preparing people interested in commissioning, managing, performing, participating in, or analyzing the results of architecture evaluation to tackle the realities of the front line.
In this presentation, which was recorded at JAOO, Software AG's Ivo Totev introduces his views on SOA and SOA Governance. Topics covered include how SOA governance can be defined, why governance is needed, and what areas it can be decomposed into. Totev also describes a SOA registry/repository solution, which in Totev's opinion is something that should be introduced in the earliest stages.
As Edd Dumbill wrote, "the subtle elegance of the Ruby idiom is a slowly appreciated and highly satisfying flavour." It's true that some of the best things about Ruby aren't obvious to newcomers. In this talk Glenn Vanderburg demonstrates some of the subtle beauty that experienced Rubyists know and love.
In this presentation recorded at JAOO, IBM's Rod Smith discusses how technologies such as Wikis are combined with Web services and Atom and RSS feeds to form mashups, enabling the next wave of DIY-IT by combining the flexibility of user-oriented information architecture provided by active content with that of content-in-flight to provide an easy-to-use end-user integration platform.
The presentation shows how to involve on-site customers in the evolution of their DSL syntax and how it leads to higher-quality, more correct software. The process of moving from a draft DSL syntax to implementation via TDD will be explained in depth.
We've come a long way from the first versions of J2EE. We've learned to avoid invasive programming models, we've developed a rich set of frameworks and APIs, we know how to develop apps based around simple objects. Are we there yet? Most of us would answer no. If we're not there yet, then where are we headed next? Spring founder Rod Johnson explores this issue. Recorded at JAOO Sept 2006.
In this presentation, Mikkel Hippe Brun, Chief Consultant at Danish National IT and Telecom Agency, introduces Denmark's national Service Oriented Infrastructure, which is based on a number of replicated UDDI registries and interoperability profiles based on the WS-*architecture and the UBL standard. Among the topics covered is the difference between SOA within and across company boundaries.
Ian Cartwright presents some of his work (developed with Martin Fowler) on Event Patterns, including: Event Sourcing, Event Collaboration, Parallel Model, and Retroactive Event. These patterns can be used in scenarios where a sequence of domain model changes may need to be recorded, reversed, corrected, or simply observed.