Simulating the final design of an application in order to ensure that the development is
progressing as expected is referred to as:
A.
Analyzing requirements
B.
Prototyping
C.
Software testing
D.
Flowcharting
Simulating the final design of an application in order to ensure that the development is progressing as expected is referred to as:
Simulating the final design of an application in order to ensure that the development is
progressing as expected is referred to as:
I think we can rule out the very early steps of Analyzing requirements and Flowcharting here. Of the remaining two, Prototyping sounds more correct to me. In software development, it is generally accepted that a prototype functions, similar to an alpha, which aligns with a prototype. Software testing is a more broad term and can occur before and after a final design or simulation there of is available.
Thoughts?
Well… I got what you wanted to say. But… Here is a tiny “But”.
This question is about Understanding Application Lifecycle Management.
In general, there are basically 5 steps in this cycle including requirements,
design, development, testing, delivery, and release management, but not Prototyping.
And of course, therefore, it is turned out that the correct answer to the question is C.
Simulating the final design of an application is *Prototyping* because testing is last part and other two comes on 1st 2nd stage
pars
anjay
I agree that prototyping is typically not included in the SDL hierarchy definition, therefore may disqualify it right away? Although, prototyping does sound more precisely like an alpha testing procedure, rather than the broadly termed software testing. I’m torn, but to be safe, i’m going with software testing….???