Tapestry for Nonbelievers
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
Tracking change and innovation in the enterprise software development community
Posted by Eric Evans on Nov 06, 2007 10:00 AM
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Rational Model Driven Development eKit: Examples, Tutorials, Webcasts
Introducing Project Zero: Building RESTful services for your Web application
RESTful todo list sample tutorial with Groovy & Project Zero
I do not see any control for pause/forward/play recorded presentation. It completed Eric's first part, but it is not playing the 2nd part of the talk. Do i need to wait for 30 minutes for the break between 2st part and 2nd part?
well, i found the controls by mouse over the video,
so i found the end of the talk, i guess that the 2nd part of talk is not posted yet. am I right?
this is a great talk i recommend for everyone. Very well put and clearly explained concepts
Yes, it seems to be based on true experience. I once used other names in this domain, like Trip, TripEvent(Stops), TripSections(Legs) etc, a bit abstract perhaps, but generic. Downside with "generic names" is that it doesn't tend to sound very much like the "domain language", which is important for communicating core concepts with the domain experts, upside with generic names is (for the designer) that the emerging model "invites" to discovering generic patterns and "meta solutions" (a kind of a "the trees don't obscure the forest effect" if undressing the names of domain specific implementations). This in turn increases "insights" in the problem domain. And yes, try to get as deep into the problem domain as possible by discussing many and all aspects with domain experts. Don't stop at the first bright idea. I like that. But, OTOH, do NOT assume that the domain experts _fully_ understand the principles involved!, instead DO assume that they know (the best) how to do the job the way they currently do it (which is not exactly the same...). What I am saying is that a thorough analysis in the pre-design stage is an unique occasion also for the domain experts (usually the end customer) to learn to even better understand the problem domain(s) at hand, and from that follows a unique opportunity to potentially *improve* the business concept(s). Well, that's my experience anyway. It would be really interesting to hear also the other half of the lecture, hopefully the second part will also be uploaded?
Hi Yale Yes you're right. the second part of the talk will be published soon:)
Hi, Can the video also be downloaded somewhere? My connection fails sometimes and the player wants to restart and I am not able to seek to the point where the player stopped the last time.
Unfortunately not, however we are working on a fix but it may not be around for another couple of months.
Hi Ivo , you should try OrbitDownloader. Its free and can download any types of video :)
A very good talk. Despite Evans' moments of awkwardness he gave a coherent and well expressed presentation with a thought-out example. As a practitioner the new and exciting bit was at the end: many models can work to our advantage. Often I will consider 'the context' of a system first, define the basics of 'it' and move on. Maybe, next time I will spare some thought for the many contexts and workout a framework for each of them. I can't wait to see how to make it work, in part two... how/where will it be advertised? Will there be a link from this presentation?
>> Despite Evans' moments of awkwardness Wow this really was an idiotic claim! What if Mr. Evans was only thinking very deep inbetween, trying to increase value by trying to avoid confusing you by introducing too much complexity too early? He's actually doing very good. He's allowing things to sink in. Would you know exactly why his very humble and pleasant performance sometimes makes a short brake for a moment of deeper reflexion? This is what designer's do. They stop and think where other ruch ahead and causes,um... "all sorts". Disregard this stupid comment. // Rolf Lampa, Sweden.
>> Disregard this stupid comment.
Well... this comment doesn't look very clever either...
It should of course have read:
"Disregard the quoted stupid (and mean) comment, by Corin Lawson"
Great how different the interpretation of "soon" can be.
Part two is now online on InfoQ: http://www.infoq.com/presentations/strategic-design-evans
Part two is now online on InfoQ: www.infoq.com/presentations/strategic-design-evans
Thanks. This second part was very good as well. What's really worth considering in any enterprise system is the approach to separate a system into :
- Core Domain(s)
- Sub Domains (generic or supporting dittos)
Very good talk and recommendations, with example of how to people tend to put too much effort into the wrong (sub) domains and so end up with a crappy designed Core Domain.
Eric demonstrates his experience - and matureness - as a designer of "real world business systems" when he points out that business systems actually has to incorporate ALSO messy and chaotic parts (for example for varying types and quality of in-data to the system) since this is an essential part of supporting (solving) the REAL business problems/situations. But - and here comes the point - although "messy parts" are unavoidable, make sure to keep those messy parts (domains) out of the "clean" and well designed Core Domain(s)!
No surprise, very good talk again! I look forward to seeing also the third (last?) part. :)
// Rolf Lampa
PS: Btw, was this video recorded in Sweden? (I think I saw the text "musikhuset" (music house) on that blue sign).
PS: Btw, was this video recorded in Sweden? (I think I saw the text "musikhuset" (music house) on that blue sign).
In Denmark actually, at the JAOO conference.
Kind regards
Niclas
where can i download the slides...? please... Thank you so much...
Hepl Blog >>> evden eve nakliyat
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.
Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.
Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.
David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.
Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.
In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.
18 comments
Reply