- Barajar
ActivarDesactivar
- Alphabetizar
ActivarDesactivar
- Frente Primero
ActivarDesactivar
- Ambos lados
ActivarDesactivar
- Leer
ActivarDesactivar
Leyendo...
Cómo estudiar sus tarjetas
Teclas de Derecha/Izquierda: Navegar entre tarjetas.tecla derechatecla izquierda
Teclas Arriba/Abajo: Colvea la carta entre frente y dorso.tecla abajotecla arriba
Tecla H: Muestra pista (3er lado).tecla h
Tecla N: Lea el texto en voz.tecla n
Boton play
Boton play
11 Cartas en este set
- Frente
- Atrás
|
Software process models
|
-Waterfall model
-Incremental devolopment -Reuse-oriented software engineering |
|
Waterfall model
(Plan-driven) |
1. Requirements analysis and definition
2. System and software design 3. Implementation and unit testing 4. Integration and system testing. 5. Operation and maintenance |
|
Waterfall model characteristics
|
The result of one phase is a document.
Iterations can be very costly and involve significant rework. It takes much time. |
|
When to use waterfall model
|
When requirements are well understood and unlikely to change during system development.
|
|
Incremental development (Plan-driven or agile, or a mix)
|
Developing an initial implementation, exposing this to user comment and evolving it through several versions until an adequate system has been developed.
|
|
When to use incremental development
|
For most business, e-commerce, and personal systems.
Small projects. |
|
Incremental development characteristics
|
It's cheaper and easier to make changes in the software as it is being developed in small increments evaluated by the client.
|
|
Benefits of incremental development
|
1. The amount of analysis and documentation is much less.
2. It is easier to get customer feedback by demonstrations on the development. 3. More rapid delivery and deployment of useful software |
|
Problems of incremental development
|
1. The process is not visible, difficult for managers to measure progress.
2. Incorporating for their software changes becomes increasingly difficult and costly |
|
Reuse-oriented model
|
1. Component analysis: search for components to reuse.
2. Requirements modification: to reflect the available components. If impossible, repeat step 1. 3. System design with reuse: framework is designed or one is reused. 4. Development and integration: software that cannot be externally procured is develop. Integration. |
|
Benefits of reuse-oriented model
|
Reducing the amount of salt were to be developed and reducing costs and risks. Faster delivery.
|
