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:

"Requerimientos, diseño y pruebas para el diseño de software"

Froggy Jumps

(1)
Played 5

About this activity

Conceptos Básicos.

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
"Requerimientos, diseño y pruebas para el diseño de software"
 

Froggy Jumps

"Requerimientos, diseño y pruebas para el diseño de software"Online version

Conceptos Básicos.

by 3205_Alondra Danely Rincón Coyote
1

Etapa donde se analiza si el desarrollo del software es viable técnica , económica y operativa.

2

Recopila la información necesaria para entender qué necesita el cliente o usuario.

3

Documento donde se plasman de manera clara, completa y detallada los requerimientos obtenidos.

4

Proceso para comprobar que los requerimientos definidos son correctos, completos realistas y cumplen con las necesidades del cliente.

5

Etapa en la que se define la estructura general del software.

6

Se enfoca en la parte visual y de interacción del sistema.

7

Diseño interno de cada módulo de sistema.

8

Etapa donde se modela y organiza la información que manejara el sistema.

9

Verifica funciones individuales durante la codificación del software.

10

Evalúa el sistema completo según requisitos.

11

Confirma que el sistema cumple lo esperado por el cliente.

Are you sure you want to leave the page?

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