complete solution
How is prototype model used in software or system development? Does it
require users or clients to be involved? - correct answers The prototype model
is used to test core functionalities, enable decision-making, and discover ways
to improve software. It involves stakeholders, including end-users and clients,
togather feedback and implement necessary changes before creating the final
product.
A prototype is an incomplete system. Correct or incorrect? - correct answers
Correct
Gathering and analyzing the system requirement are only needed in a
standard SDLC but can be ignored in prototype model. Correct or incorrect? -
correct answers Incorrect
How is a prototype improved (by developers)? - correct answers Developers
improve a prototype by collecting feedback from stakeholders, refining the
model based on the received feedback, implementing changes, and repeating
this process until the prototype meets the requirements.
In which stage is the approved prototype in the production phase? - correct
answers Product implementation and maintenance stage
What four types of prototype models are introduced by this article? What
factors can determine the type of prototype models to be used? - correct
answers The article introduces Rapid throwaway prototype, Evolutionary
prototype, Incremental prototype, and Extreme prototype. Factors determining
the type include the project objective, timelines and the availability of
resources.
, Generally, sharing the results of your prototype test with the key stakeholders
is a bad idea and should be avoided. Correct or incorrect? - correct answers
Incorrect
Because changing product requirements is a serious issue and can
dramatically impact the project, it's not considered to be an appropriate
situation to use a prototype model. Correct or incorrect? - correct answers
Incorrect
Good Requirements - correct answers states something that is necessary,
verifiable, and attainable.
Simple sentences will most often suffice for a good requirement. Correct or
incorrect? - correct answers Correct
Two common problems in writing requirements are - correct answers · Making
bad assumptions
· Writing implementation (HOW) instead of requirements (WHAT)
Documenting the budget and schedule information of the program or project
can eliminate the bad assumptions problem. Correct or incorrect? - correct
answers Correct
What do the term "implementation trap" and "subject trap" mean in the context
of writing requirements? What's their effect on writing good requirements? -
correct answers Implementation trap refers to detailing design or low-level
implementation specifics instead of high-level requirements, potentially
leading to missing important requirements.