Abstract:

The primary measure of success of a software system is the extent to which it meets the use for which it was planned. Software systems requirements is the process of discovering that purpose, by identifying users and their needs, and documenting these in a form that is amenable to analysis, communication, and subsequent implementation. Quality requirements are generally more difficult to express in a measurable way, making them more difficult to analyze. It is generally accepted that many systems are fail because they don’t satisfy the requirements of the users. Since project failure leads in tremendous loss of cost, time and effort, there is a crucial need for the establishment of a requirement analysis infrastructure that promotes user involvement and ensures requirement veracity at low expenditures. Requirements analysis is the process of identifying a user's needs and determining what to build in a system. Within requirements analysis the process of requirements elicitation in which implicit information about "what to build" is obtained from the user and his environment. In this paper, we develop a model that arranges all scenarios describing the interaction between the users and the system. This model improves the quality of requirements which gives a description of behavior of various quality parameters of requirements. The aim of this model is to improve the quality of a requirement specification.