chúng ta phải thêm một bước để mã của chúng tôi cần phải nhận được tất cả các yếu tố tbody trong bảng (HTML cho phép nhiều hơn một tồn tại), sau đó nhận được tất cả các hàng bên trong mỗi tbody. Quá trình này thực sự sẽ yêu cầu hai cho vòng một để bước qua | Requirements elicitation and analysis 153 interviewees may not wish to reveal the actual rather than the theoretical structure to a stranger. In general most people are reluctant to discuss political and organisational issues that may affect the requirements. Effective interviewers have two characteristics 1. They are open-minded avoid preconceived ideas about the requirements and are willing to listen to stakeholders. If the stakeholder comes up with surprising requirements they are willing to change their mind about the system. 2. They prompt the interviewee to start discussions with a question a requirements proposal or by suggesting working together on a prototype system. Saying to people tell me what you want is unlikely to result in useful information. Most people find it much easier to talk in a defined context rather than in general terms. Information from interviews supplements other information about the system from documents user observations and so on. Sometimes apart from information from documents interviews may be the only source of information about the system requirements. However interviewing on its own is liable to miss essential information so it should be used alongside other requirements elicitation techniques. Scenarios People usually find it easier to relate to real-life examples than to abstract descriptions. They can understand and critique a scenario of how they might interact with a software system. Requirements engineers can use the information gained from this discussion to formulate the actual system requirements. Scenarios can be particularly useful for adding detail to an outline requirements description. They are descriptions of example interaction sessions. Each scenario covers one or more possible interactions. Several forms of scenarios have been developed each of which provides different types of information at different levels of detail about the system. Using scenarios to describe requirements is an integral part of agile
