TAILIEUCHUNG - 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 (., 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 .

• Kỹ thuật lập trình
• Elaboration process
• Negotiation process
• Software requirements engineering
• Lecture Software requirements engineering
• Software engineering
• Requirements engineering
• Scenario based modeling
• Swimlane diagram
• Software requirements engineering
• Lecture Software requirements engineering
• Object oriented analysis
• Class modeling
• Flow oriented modeling
• MODELING EXTEMPORANEOUS ELABORATION
• Marie A
• Bienkowski Bell
• Long Papers
• scientific reports
• model language
• process natural language
• Marketing communications
• Integrated marketing communications
• Integrated marketing program
• Communication process
• Basic model of communication
• Elaboration Likelihood Model
• Behavioral modeling