Get flash to fully experience Pearltrees
Understanding nonfunctional requirements — which some people call software quality attributes or nonbehavioral requirements — can make a big difference when you’re building software. But a lot of people have trouble taking a somewhat theoretical idea and applying it to a real-life project.
If you're new here, you may want to subscribe to my RSS feed . Thanks for visiting! Sharebar
Editor’s Note: This guest post is written by Uzi Shmilovici , the founder and CEO of Future Simple , the company behind Base CRM . The first image that comes to my mind when I think about business computing is the dystopic scene from the 1984 Apple commercial : A swarm of employees wearing the same uniforms and marching in unison into their offices where they are forced to use certain devices and software. They sit down in front of their PCs, open a business application their company paid millions of dollars to implement and, in a disciplined manner, fill out forms to populate the company’s database so their managers will be happy.
My team uses FitNesse extensively to create automated acceptance tests for our systems. Recently we’ve added Selenium RC running from within FitNesse to our toolbox. There’s a lot of buzz lately over the creation of Domain Specific Languages (DSL), driven in no small part to create a syntax for the application code that is readable by the business partners and testers. We accomplish the same goal (or at least try to) by using FitNesse fixtures to effectively create a DSL for our applications that our tester can use to specify and verify the expected behavior of the system.