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

After this chapter the student should have acquired the following knowledge and skills: Elaboration process, negotiation process, negotiation process, activities, negotiation meetings, requirement piroritization. | Negotiation Process Lecture-18 Recap Elaboration process Negotiation process Today’s lecture Negotiation process Activities Negotiation meetings Requirement piroritization Negotiation as a process 4 Negotiation 5 During negotiation, the software engineer reconciles the conflicts between what the customer wants and what can be achieved given limited business resources Requirements are ranked (i.e., prioritized) by the customers, users, and other stakeholders Risks associated with each requirement are identified and analyzed Rough guesses of development effort are made and used to assess the impact of each requirement on project cost and delivery time Using an iterative approach, requirements are eliminated, combined and/or modified so that each party achieves some measure of satisfaction Stages 6 Art of negotiation 7 Recognize that it is not competition Map out a strategy Listen actively Focus on the other party’s interests Don’t let it get personal Be creative Be ready to commit . | Negotiation Process Lecture-18 Recap Elaboration process Negotiation process Today’s lecture Negotiation process Activities Negotiation meetings Requirement piroritization Negotiation as a process 4 Negotiation 5 During negotiation, the software engineer reconciles the conflicts between what the customer wants and what can be achieved given limited business resources Requirements are ranked (i.e., prioritized) by the customers, users, and other stakeholders Risks associated with each requirement are identified and analyzed Rough guesses of development effort are made and used to assess the impact of each requirement on project cost and delivery time Using an iterative approach, requirements are eliminated, combined and/or modified so that each party achieves some measure of satisfaction Stages 6 Art of negotiation 7 Recognize that it is not competition Map out a strategy Listen actively Focus on the other party’s interests Don’t let it get personal Be creative Be ready to commit 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. 8 Software Requirements Engineering Meeting steps 9 Requirement Prioritization (RP) 10 In software engineering, if requirements are not elicited properly its not possible to successfully achieve the product which customer exactly wants. So requirement engineering consists of different phases such as, requirement elicitation, specification, negotiation, validation etc. So RP is the part of RE in .