New game
Download
Get Academic Plan
Share game
Integrate it into your platform

You can integrate the game into an LMS compatible with LTI 1.1 or LTI 1.3 such as Canvas, Moodle, or Blackboard. This way, the scores will be automatically saved into the platform’s gradebook.
Download
You have exceeded the maximum number of games you can integrate into Google Classroom with your current Plan.

To integrate as many games as you want in Google Classroom, you need an Academic Plan or a Commercial Plan.

You have exceeded the maximum number of games you can integrate into Microsoft Teams with your current Plan.

To integrate as many games as you want in Microsoft Teams, you need an Academic Plan or a Commercial Plan.

Downloading games is an exclusive feature for users with an Academic Plan or a Commercial Plan.

Get your Academic Plan or your Commercial Plan now and start integrating your games into your LMS, website or blog.

If you wish, you can download a demo game here and test its integration:

Modelos Tradicionales de Software

Yes or No

Played 0

About this activity

Apuesta por las afirmaciones: ¿Verdadero o Falso?

Created by

Mexico

Download the paper version to play

Make your own free game from our game creator
Compete against your friends to see who gets the best score in this game

Top Games

%
Anonymous
Anonymous
%
%
%
You have exceeded the maximum number of games you can print with your current Plan.

To print as many games as you want, you need an Academic Plan or a Commercial Plan.

Print your game
Modelos Tradicionales de Software
 

Modelos Tradicionales de SoftwareOnline version

Apuesta por las afirmaciones: ¿Verdadero o Falso?

by masha y oso
1

El modelo en cascada sigue una secuencia de fases bien definidas.

2

En el modelo en V, las pruebas no se relacionan con los requisitos de cada fase.

3

El prototipo rápido equivale a un modelo de desarrollo ágil puro.

4

El modelo en cascada permite cambios fáciles en las fases iniciales.

5

En modelos tradicionales, los cambios tardíos pueden aumentar costos y retrasos.

6

El desarrollo en cascada entrega el software al final de cada sprint corto de 2-4 semanas.

7

El modelo espiral combina desarrollo y gestión de riesgos en bucles iterativos.

8

El desarrollo incremental entrega incrementos funcionales en etapas sucesivas.

9

El modelo en V extiende la verificación y validación a lo largo del ciclo de vida.

10

El modelo espiral evita la evaluación de riesgos.

Are you sure you want to leave the page?

If you leave the page, you will lose your game progress.