Formalization of domain problems described in the cause-and-effect diagram in the context of the software development process
The system analyst is responsible— in the early requirements elicitation process—for identifying the problems to be solved with a software application. Such identification is based on: (i) the analyst experience and knowledge about the domain area; and (ii) the stakeholder support. Problems are coll...
- Autores:
-
Vargas Agudelo, Fabio Alberto
Zapata Jaramillo, Carlos Mario
- Tipo de recurso:
- Part of book
- Fecha de publicación:
- 2020
- Institución:
- Tecnológico de Antioquia
- Repositorio:
- Repositorio Tdea
- Idioma:
- eng
- OAI Identifier:
- oai:dspace.tdea.edu.co:tdea/1109
- Acceso en línea:
- https://dspace.tdea.edu.co/handle/tdea/1109
- Palabra clave:
- Tecnología
Globalización
- Rights
- openAccess
- License
- http://purl.org/coar/access_right/c_abf2
| Summary: | The system analyst is responsible— in the early requirements elicitation process—for identifying the problems to be solved with a software application. Such identification is based on: (i) the analyst experience and knowledge about the domain area; and (ii) the stakeholder support. Problems are collected by the system analyst during the domain analysis for using them as the main input of the requirements specification. Such specification is consistent with the problems identified and the stakeholder needs. development process, goal-oriented software engineering (GORE) [1], and organizational analysis have diagrams for representing problems |
|---|