In my last post, I outlined what I think are the twelve key constraints you need to think about if you are going to build high quality software that people want to use. As I mentioned, thinking through this needn’t be a mind sapping endeavour, and for some things you may just decide it’s not important right now. Here’s the rub though; once you’ve decided something is important enough to define as a constraint on your system you’d better think about how you’re going to test it. If not, you may as well kiss the requirement goodbye as eventually people will stop paying attention to it. Here’s how I would go about testing each of those twelve constraints:
Read More
Pages
Categories
- 1 (4)
- Engineering (41)
- Agile Software Development (14)
- Continuous Integration (17)
- Flash & Actionscript (21)
- Quality Software (10)
- Rails (7)
- Ruby (7)
- Software Craftsmanship (8)
- Software Estimation (4)
- Test Driven Development (12)
- Tablets (2)
- Travelling Light (2)
Archives