SOA Governance: An Enterprise View
Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.
- SOA,
Tracking change and innovation in the enterprise software development community
Posted by Kurt Christensen on Jan 02, 2007 06:10 PM
Gojko Adzic has produced a short tutorial [pdf] on getting FitNesse to work for .NET applications. FitNesse is an enhancement to Fit, the acceptance testing framework developed by Ward Cunningham:Fit works by reading tables in HTML files, produced with a tool like Microsoft Word. Each table is interpreted by a "fixture" that programmers write. The fixture checks the examples in the table by running the actual program.FitNesse leverages Fit to provide a collaborative environment for developers and business users to create the acceptance tests which are then automated with Fit test fixtures:
FitNesse is an HTML and wiki "front-end" to FIT. While Fit makes it possible to run test tables, it does not itself provide an easy means of creating those tables or displaying the results of those tests. This is where FitNesse comes in. FitNesse makes it really easy to create, run, organize, annotate, and share Fit tests throughout a software development team.Fit and FitNesse are powerful tools for agile development teams. The issue, writes Gojko, is that the FitNesse documentation focuses on the Java implementation, which too often leaves .NET users to fend for themselves:
The online user guide deals only with the Java integration, and .Net implementation has a lot of subtle differences. Details of those specifics are scattered throughout the Internet, so I spent quite some time collecting partial information from blogs, but on the end, all the roads lead to the debugger. FitNesse.Net is, fortunately, open source, so I got the source code from Sourceforge and found what is really going on. As I could not find a complete, consolidated guide that explains how to start testing .Net code with FitNesse, I decided to write one myself and share it, so that others do not have to learn it from the debugger.Gojko's tutorial helps .NET users new to FitNesse get up and running, from download to installation to writing their first test fixtures. Anyone seeking information beyond this can find it in the book Fit for Developing Software, by Rick Mugridge and Ward Cunningham.
Hacking 101 -The Top 10 Attacks in Web Applications
Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21
Six Free Project Management Certification Training Courses
The Agile Business Analyst: Skills and Techniques needed for Agile
Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.
This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.
This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.
Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.
Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.
Jinesh Varia talks about the architecture of one of Amazon's web services called Alexa. Jinesh explains how Amazon has reached scalability, performance and reduced costs for the Alexa service.
David Douglas and Robin Dymond discuss about companies adopting Agile, but don't go all the way, resulting in failure and rejection of it, and predictably having a negative impact on Agile's future.
Kenji Hiranabe talks about Toyota's development process of a new car. Kenji shares his experience meeting Nobuaki Katayama, former Chief Engineer at Toyota, and the lessons he learned from him.
No comments
Reply