However, the cascade model for development of the games like path of the jedi game in some of its variants is one of the most currently used, its effectiveness and simplicity in software rather small and some medium companies, but never (or very rarely) it is used in its pure form, as mentioned above. Instead, there is always some feedback between stages, that is not completely predictable or rigid, and this gives opportunity to the development of software products in which there are some uncertainties, changes and developments during the life cycle. For example, once captured (elicited) and the requirements specified (first stage) can be passed to the design of the system, but during this last phase will most likely be making adjustments in the requirements (even minimal), and for failure is detected, or ambiguities that those requirements have changed or evolved, so you should go back to the first or previous stage, make the appropriate adjustments and then again with the design, the latter is known as feedback.
Leave a Reply