Skip to main content
Post Closed as "Needs details or clarity" by durron597, Ixrec, user40980, jwenting, user53019
spelling, formatting
Source Link
gnat
  • 20.9k
  • 29
  • 115
  • 295

does Does RAD allowsallow you changes or modification after the cutover phase without the need to redo the system?

likeLike other agile models, that is a close loop where changes after the system development can still be implemented without the need to redo the whole system, is this possible for the RAD model as well. since?

Since I was told that in the waterfallWaterfall model, if there are changes after the development, it can only be implemented by redoing the whole system since it is a one way approach unlike agile where you can just go back to the development stage again.

Example:

afterAfter the cutover phase of the system, when it is already released for a few months, then the client decided that "hey iI want this and that to be implemented iI think it would make the system better with it". canCan this be done immediately following the process model of the RAD and just directly proceed to construction phase, or do we need to recreate the entire RAD process from the start or the requirements planning phase?

fromFrom what iI understood of waterfallWaterfall method, if a change is needed during the maintenance period or way after the system has been completed, it is a requirement to redo the entire waterfallWaterfall process and start from the start, which is very different for agile models where you can just go to the development stage to apply the necessary changes.

does RAD allows you changes or modification after the cutover phase without the need to redo the system?

like other agile models that is a close loop where changes after the system development can still be implemented without the need to redo the whole system, is this possible for the RAD model as well. since I was told that in the waterfall model if there are changes after the development it can only be implemented by redoing the whole system since it is a one way approach unlike agile where you can just go back to the development stage again.

Example:

after the cutover phase of the system, when it is already released for a few months, then the client decided that "hey i want this and that to be implemented i think it would make the system better with it". can this be done immediately following the process model of the RAD and just directly proceed to construction phase, or do we need to recreate the entire RAD process from the start or the requirements planning phase?

from what i understood of waterfall method if a change is needed during the maintenance period or way after the system has been completed, it is a requirement to redo the entire waterfall process and start from the start which is very different for agile models where you can just go to the development stage to apply the necessary changes.

Does RAD allow you changes or modification after the cutover phase without the need to redo the system?

Like other agile models, that is a close loop where changes after the system development can still be implemented without the need to redo the whole system, is this possible for the RAD model as well?

Since I was told that in the Waterfall model, if there are changes after the development, it can only be implemented by redoing the whole system since it is a one way approach unlike agile where you can just go back to the development stage again.

Example:

After the cutover phase of the system, when it is already released for a few months, then the client decided that "hey I want this and that to be implemented I think it would make the system better with it". Can this be done immediately following the process model of the RAD and just directly proceed to construction phase, or do we need to recreate the entire RAD process from the start or the requirements planning phase?

From what I understood of Waterfall method, if a change is needed during the maintenance period or way after the system has been completed, it is a requirement to redo the entire Waterfall process and start from the start, which is very different for agile models where you can just go to the development stage to apply the necessary changes.

added 784 characters in body
Source Link

like other agile models that is a close loop where changes after the system development can still be implemented without the need to redo the whole system, is this possible for the RAD model as well. since I was told that in the waterfall model if there are changes after the development it can only be implemented by redoing the whole system since it is a one way approach unlike agile where you can just go back to the development stage again.

Example:

after the cutover phase of the system, when it is already released for a few months, then the client decided that "hey i want this and that to be implemented i think it would make the system better with it". can this be done immediately following the process model of the RAD and just directly proceed to construction phase, or do we need to recreate the entire RAD process from the start or the requirements planning phase?

from what i understood of waterfall method if a change is needed during the maintenance period or way after the system has been completed, it is a requirement to redo the entire waterfall process and start from the start which is very different for agile models where you can just go to the development stage to apply the necessary changes.

like other agile models that is a close loop where changes after the system development can still be implemented without the need to redo the whole system, is this possible for the RAD model as well. since I was told that in the waterfall model if there are changes after the development it can only be implemented by redoing the whole system since it is a one way approach unlike agile where you can just go back to the development stage again.

like other agile models that is a close loop where changes after the system development can still be implemented without the need to redo the whole system, is this possible for the RAD model as well. since I was told that in the waterfall model if there are changes after the development it can only be implemented by redoing the whole system since it is a one way approach unlike agile where you can just go back to the development stage again.

Example:

after the cutover phase of the system, when it is already released for a few months, then the client decided that "hey i want this and that to be implemented i think it would make the system better with it". can this be done immediately following the process model of the RAD and just directly proceed to construction phase, or do we need to recreate the entire RAD process from the start or the requirements planning phase?

from what i understood of waterfall method if a change is needed during the maintenance period or way after the system has been completed, it is a requirement to redo the entire waterfall process and start from the start which is very different for agile models where you can just go to the development stage to apply the necessary changes.

Source Link

does RAD allows you changes or modification after the cutover phase without the need to redo the system?

like other agile models that is a close loop where changes after the system development can still be implemented without the need to redo the whole system, is this possible for the RAD model as well. since I was told that in the waterfall model if there are changes after the development it can only be implemented by redoing the whole system since it is a one way approach unlike agile where you can just go back to the development stage again.