Prototyping can either be a mandatory dependency or discretionary dependency, based on the terms and conditions of the contract / nature of a project. For example, if prototype is one of the deliverable as per terms of contract then it would become a mandatory dependency. There may be some cases like mission critical applications, building a prototype is part of your project plan, when it becomes a mandatory dependency
makev1701
Tue, 07/02/2013 - 22:59
Permalink
Correct answer is 2
Correct answer is 2 Mandatory - you must prototype before you can test
rjbuzzing
Wed, 07/03/2013 - 01:29
Permalink
I am not sure why. Because to
I am not sure why. Because to my knowledge Prototype is always a good practice (discretionary) but not mandatory one.
Any more thoughts Folks !
vijayavadrevu
Wed, 07/03/2013 - 08:15
Permalink
Prototyping can either be a
Prototyping can either be a mandatory dependency or discretionary dependency, based on the terms and conditions of the contract / nature of a project. For example, if prototype is one of the deliverable as per terms of contract then it would become a mandatory dependency. There may be some cases like mission critical applications, building a prototype is part of your project plan, when it becomes a mandatory dependency
Otherwise, it can be a discretionary dependency
It all depends on the nature of project
These are only my views.
Regards
Vijaya
rjbuzzing
Wed, 07/03/2013 - 13:52
Permalink
But if it doesn't mentions
But if it doesn't mentions anything about the project instead just says - Prototype is ______ dependency ?