tailieunhanh - Lecture Software requirements engineering - Lecture 7: Requirements elicitation process
After this chapter the student should have acquired the following knowledge and skills: The requirements elicitation process, requirements analysis and negotiation, stakeholders, list the possible stakeholders for a library cataloguing system, elicitation techniques, specific elicitation techniques,. | Requirements Elicitation Process Lecture-7 Recap 2 Inception Process Elicitation Process The requirements elicitation process 3 Requirements analysis and negotiation 4 Today’s lecture Software Requirements Engineering 5 Elicitation process Stakeholders 6 Stakeholders are the people who are needed to ensure the success of a project. It is essential to find out whom they are, what their attitudes are, and what their interests are. Some of them have to contribute with money and effort, and they must feel they get something in return, otherwise they won’t support the project and they may even obstruct it. During stakeholder analysis you try to get answers to these questions: 7 Who are the stakeholders? (Initially you know only a few of them.) What goals do they see for the system? (Many stakeholders look not only at their own goals, but also at other stakeholder’s goals.) Why would they like to contribute? (Their reward.) What risks and costs do they see? What kind of solutions, . | Requirements Elicitation Process Lecture-7 Recap 2 Inception Process Elicitation Process The requirements elicitation process 3 Requirements analysis and negotiation 4 Today’s lecture Software Requirements Engineering 5 Elicitation process Stakeholders 6 Stakeholders are the people who are needed to ensure the success of a project. It is essential to find out whom they are, what their attitudes are, and what their interests are. Some of them have to contribute with money and effort, and they must feel they get something in return, otherwise they won’t support the project and they may even obstruct it. During stakeholder analysis you try to get answers to these questions: 7 Who are the stakeholders? (Initially you know only a few of them.) What goals do they see for the system? (Many stakeholders look not only at their own goals, but also at other stakeholder’s goals.) Why would they like to contribute? (Their reward.) What risks and costs do they see? What kind of solutions, suppliers, and resources do they see? (Should we replace the old system or extend it? Make it ourselves or buy it?) Who are the stakeholders? 8 If the product is to be used internally in a large company, stakeholders might include: The sponsor who pays for the product. He wants value for his money. Daily users from various departments. They have to live with the product and, without their support, there will be no success. Managers of the departments. They want business advantages from the system. The company’s customers (clients of the system). Often they will see changes too, and without their support there will be no business advantages. Business partners, for instance suppliers, carriers, and banks. If they will see changes, their support is essential too. Cont . 9 Authorities, for instance safety inspectors, auditors, local government. IT people and hotline staff in case the product is to be developed in-house. Other people providing resources for the product. If we talk about product .
đang nạp các trang xem trước
