testing - testability of a design -


much has been written testing of code. how ensure our design functionally correct in first place? have junit testing java code, there tools can used, say, test uml based design, tests expressed in form of functional requirements?

these vague thoughts, wanted know if there's methodical, automatable approach testing design first. in other words, can have 'test driven design'?

interesting topic!

firstly, no software architects in personal network use uml way design systems, , know of no software architects create uml @ level of detail required execute mechanical test.

secondly, have deep dislike of uml modeling tools. if such formal verification method implemented, it's in rational rose - swore long ago i'd never go anywhere near again.

however, having said - in formal software shops, it's common have requirements tracability, typically implemented matrix shows business requirements on 1 axis, , design artifacts on other. way, can see whether requirements not matched corresponding solution, or if there elements in solution not meet specific business requirement.

keeping matrix updated pain, it's not used in agile teams, if you're building softwware bank or space shuttle, valuable technique.

this tells whether design complete - though not whether it's "right".

there's no way know of tell whether design "right" without either building , testing, or relying on human experience , knowledge.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -