Functional - testing that stuff does what it's meant to do - functionality wise
Non-Functional - I guess this is our GUI testing, making sure everything's the right size/alignment/spelling etc.
User Acceptance - we're given a list of stuff our software should do under certain conditions. We have to test that it does so. If it does, they buy it. If not, they walk away (or give us another chance if they're nice)
All of our customers want our software to do slightly different things, to fit into their production environments.
Difference between functional and non-functional is pretty much a) does it do what it is supposed to do and b) does it not do what it is not supposed to do. User acceptance is a check list of pass requirements.
Where i work:
Functional: the we (the dev's) can make it behave how we want
non-functional: the opposite of above
user-acceptance: a none-dev person can use the software, it doesn't crash and is intuitive 'path of least astonishment' - it does what the user would normally expect - eg you click a button marked 'copy files' and it doesn't pop up a picture of a teapot
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.