By considering the ways in which system requirements are elicited and knowledge captured, benefit may be realized across maintaining a zero-failure environment in an HRO. The model was developed through a single case study conducted at an air navigation service provider organization in South Africa. In order to address knowledge capturing during system requirement elicitation, this paper proposes a model for knowledge capturing during system requirements elicitation in an HRO. Arrange for technical support to transcribe the session and, if used, audio/.
It represents the voiced bilabial stop in many languages, including English. However, traditional system requirements elicitation processes, do not include knowledge capturing as an outcome of the requirements elicitation process. B, or b, is the second letter of the Latin-script alphabet, used in the modern English alphabet, the alphabets of other western European languages and others worldwide.Its name in English is bee (pronounced / b i /), plural bees. As such, employees are stakeholders in system requirement elicitation which is one of the mechanisms through which operational aspects may be managed. Systems in an HRO should be examined continuously and pro-actively, and each employee must ensure that their particular operational aspects exclude the potential of disaster.
As the consequences of system failure in an HRO are disastrous, system errors are not an option. High reliability organizations (HROs) are those organizations that focus on prevention, not reaction, and that require information systems to operate in nearly error-free conditions.
0 kommentar(er)
