Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Software requirements engineering - Lecture­ 10: Requirements elicitation process

After this chapter the student should have acquired the following knowledge and skills: Requirements negotiation, negotiation meetings, state of the art in requirement elicitation, visual requirements specification through annotate pro, stakeholder analysis, elicitation techniques,. | Requirements Elicitation Process Lecture-10 Recap Software Requirements Engineering 2 Elicitation process Elicitation techniques Document studies Questionnaire Brainstorming Focus groups Collaborative requirement gathering QFD Analysis Negotiation Requirements negotiation Disagreements about requirements are inevitable when a system has many stakeholders. Conflicts are not ‘failures’ but reflect different stakeholder needs and priorities Requirements negotiation is the process of discussing requirements conflicts and reaching a compromise that all stakeholders can agree to In planning a requirements engineering process, it is important to leave enough time for negotiation. Finding an acceptable compromise can be time-consuming 3 Software Requirements Engineering Negotiation meetings An information stage where the nature of the problems associated with a requirement is explained. A discussion stage where the stakeholders involved discuss how these problems might be resolved. All . | Requirements Elicitation Process Lecture-10 Recap Software Requirements Engineering 2 Elicitation process Elicitation techniques Document studies Questionnaire Brainstorming Focus groups Collaborative requirement gathering QFD Analysis Negotiation Requirements negotiation Disagreements about requirements are inevitable when a system has many stakeholders. Conflicts are not ‘failures’ but reflect different stakeholder needs and priorities Requirements negotiation is the process of discussing requirements conflicts and reaching a compromise that all stakeholders can agree to In planning a requirements engineering process, it is important to leave enough time for negotiation. Finding an acceptable compromise can be time-consuming 3 Software Requirements Engineering Negotiation meetings An information stage where the nature of the problems associated with a requirement is explained. A discussion stage where the stakeholders involved discuss how these problems might be resolved. All stakeholders with an interest in the requirement should be given the opportunity to comment. Priorities may be assigned to requirements at this stage. A resolution stage where actions concerning the requirement are agreed. These actions might be to delete the requirement, to suggest specific modifications to the requirement or to elicit further information about the requirement. 4 Software Requirements Engineering State of the art in requirement elicitation Software Requirements Engineering 5 Wiki-Based Stakeholder Participation in Requirements Engineering Decker et al. have proposed using Wikis as a platform for asynchronous collaboration of multiple stakeholders to elicit software requirements . They claim it to be a way to enhance stakeholders’ involvement in requirement engineering process. This wiki-based approach relies on a moderator, who provides information about the requirement topics, specifies content template and allocates requirements to stakeholders. Decker, B., Ras, E., Rech,