tailieunhanh - Lecture Software requirements engineering - Lecture­ 19: Negotiation and specification process

After this chapter the student should have acquired the following knowledge and skills: Negotiation process, activities, negotiation meetings, requirement prioritization, specification, writing functional requirements. | Negotiation and Specification Process Lecture-19 Recap Negotiation process Activities Negotiation meetings Requirement prioritization Today’s lecture Negotiation process Specification Writing functional requirements Negotiation 4 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 Requirements A description of how the system should behave, or of a system property or attribute. They might be a constraint on the development process of the system. 5 Requirements . | Negotiation and Specification Process Lecture-19 Recap Negotiation process Activities Negotiation meetings Requirement prioritization Today’s lecture Negotiation process Specification Writing functional requirements Negotiation 4 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 Requirements A description of how the system should behave, or of a system property or attribute. They might be a constraint on the development process of the system. 5 Requirements (Cont) A user-level facility Word processor must include a spell checking and correction command A very general system property The system must ensure that personal information is never made available without authorization A specific constraint on the system The sensor must be polled 10 times per second A constraint on the development of the system The system should be developed using C# 6 Requirements (Cont ) Requirements therefore invariably contain a mixture of problem information, statements of system behavior and properties and design and manufacturing constraints. The primary measure of success of a software system is the degree to which it meets the purpose for which it was intended. 7 Functional Requirements What inputs the system should accept What outputs the system should produce What data the system should store that other systems might use What computations the system should perform The timing and synchronization of the above 8 How detailed requirements should be? .