Requerimientos NO funcionales
Non-functional software requirements should be defined at the beginning of the development process because they impact its quality. These requirements are classified in: quality attributes, constraints, external interfaces, user interfaces and errors control. Los requerimientos NO funcionales de un...
Saved in:
| Institution: | Fundación Universitaria Konrad Lorenz |
|---|---|
| Main Authors: | , |
| Format: | Objeto de aprendizaje |
| Language: | Español |
| Published: |
Facultad de Matemáticas e Ingenierías
2019-12-11
|
| Subjects: | |
| Online Access: | https://repositorio.konradlorenz.edu.co/handle/001/1527 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Summary: | Non-functional software requirements should be defined at the beginning of the development process because they impact its quality. These requirements are classified in: quality attributes, constraints, external interfaces, user interfaces and errors control.
Los requerimientos NO funcionales de un software deben definirse desde el inicio del proceso de desarrollo ya que influyen altamente en su calidad. Dentro de los requerimientos NO funcionales se encuentran: atributos de calidad, restricciones, interfaces externas, interfaces de usuario y control de errores.
Os requisitos de software não-funcionais devem ser definidos no início do processo de desenvolvimento, pois afetam sua qualidade. Esses requisitos são classificados em: atributos de qualidade, restrições, interfaces externas, interfaces de usuário e controle de erros.
|
|---|---|
| Physical Description: | 868352 bytes |
