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:

Fases del desarrollo de software

Yes or No

(1)
Played 5

About this activity

Fases y verificación del desarrollo

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
Fases del desarrollo de software
 

Fases del desarrollo de softwareOnline version

Fases y verificación del desarrollo

by Jorge Valenzuela
1

El análisis de requisitos identifica qué debe hacer el software.

2

El mantenimiento corrige errores y mejora el rendimiento tras la entrega.

3

Las pruebas de aceptación verifican que el software cumple los requisitos del usuario.

4

Las pruebas de integración sustituyen a las pruebas unitarias.

5

La fase de mantenimiento ocurre solo si hay fallos críticos en producción.

6

El usuario final nunca participa en la validación del software.

7

El diseño de software crea la arquitectura y los componentes.

8

En el modelo en cascada, nunca se revisan los requisitos durante el desarrollo.

9

El desarrollo implica escribir código y realizar pruebas unitarias.

10

El desarrollo ágil evita todo tipo de documentación.

Are you sure you want to leave the page?

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