<?xml version="1.0" encoding="UTF-8" standalone="yes"?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><rss xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" version="2.0"><channel><title>Testing</title><managingEditor>noemail@noemail.org (--dawn)</managingEditor><generator>Blogger</generator><convertLineBreaks xmlns="http://www.blogger.com/atom/ns#">false</convertLineBreaks><link>http://www.tincat-group.com/mewsings/testing</link><language>en-us</language><itunes:explicit>no</itunes:explicit><itunes:owner><itunes:email>noemail@noemail.org</itunes:email></itunes:owner><item><title>Constraints Factored In and Out</title><link>http://www.tincat-group.com/mewsings/testing/2006/05/constraints-factored-in-and-out.html</link><author>noemail@noemail.org (--dawn)</author><guid isPermaLink="false">tag:blogger.com,1999:blog-20629668.post-114745065042790858</guid><description>



It's time to factor constraints into the equation.  A constraint is any component of software, including code, metadata, or data, designed to limit possibilities.  Constraints implement "business" rules such as only men may be elders in churches in Sioux Center, IA.  


Every aspect of a software product is constraining.  Remove all constraints from software and you no longer have software. </description><draft xmlns="http://purl.org/atom-blog/ns#">false</draft></item></channel></rss>