Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Stefan Tilkov on Nov 29, 2006
Since the merge between OMG and BPMI.org, BPMN [BPMN] – Business Process Modeling Notation – is recognized as the de-facto standard notation for representing processes. Until now, there has been no standard notation for designing business processes. Event Process Chains (EPC) is a great notation, but it is a propriatery one that is not only supported by IDS Scheer ARIS. UML Activity Diagrams [UML] are nice, but business analysts somehow cannot use them. Flowcharts are what they’d rather go for, but these tend to be limited to the modeling of single processes, which does not accommodate the requirements of a Service Oriented Architecture (SOA). Something better was needed, and this is why BPMI.org developed BPMN a couple of years ago.In BPM expert Bruce Silver's opinion, the availability of a BPMN modeler for Eclipse is significant because of its potential to link process modeling and execution via generation of BPEL:
Let’s face it, most business analysts have probably never heard of Eclipse, much less the Eclipse Foundation. But conversely, most developers have not yet made the connection that with BPMN, the model can actually generate the BPEL code. That code generation is not in the open source tool - it’s just a diagramming tool at this point - but the idea of business-driven process implementation will definitely be advanced here.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
No comments
Watch Thread Reply