It is difficult to gather together the opinions of several dozen of users if there is no a well-structured organizational chart, such as a use case. Problems arise if you have to listen to several users and if you are dealing with the most vociferous and stubborn client. You can overlook the requirements that are important for a particular class of users, or include requirements that do not reflect the needs of the majority of the users. In order to maintain balance, it is necessary to attract a few hot supporters of the product, who have the authority to speak on behalf of the respective classes of users, each of which must be supported by several representatives of the same class of users.
In the process of gathering information, it is sometimes found that the project boundaries are not defined correctly – they are either too broad or too narrow. In the first case, you will have to collect additional data to formulate adequate commercial and client concepts, and at that the process will be inevitably drawn out to a great length. In the second case, the important needs expressed by users go beyond the boundaries of the current project. This means that certain boundaries may be too narrow to obtain satisfactory results. Thus, the information collection process sometimes entails changing the image or boundaries of the project.
Using offshore software testing means reducing development costs without sacrificing the product’s or project’s quality. Ukrainian experts offer you a wide range of qa services to ensure success of your project.
It is often said that the requirements define what the system should do, then how the chosen solution will be implemented relates to the project’s design. Although this formulation is temptingly brief, in fact, it is primitive. The information gathering process should be focused on this ITO but the analysis and design phases are divided by a blurred line but by not a clear boundary. Analysis models, sketches of what is seen on the screen, and prototypes help in the collection of information to more clearly express user needs and avoid mistakes and omissions. Perceive models and design solutions developed in the process of formulating requirements, as conceptual proposals that simplify effective interaction, rather than as limitations of the capabilities available to the developer. Explain to users that these tools are just for illustrating ideas and should not necessarily be used practically.
Comments are closed.