After this chapter the student should have acquired the following knowledge and skills: Problems with requirements engineering practices, seven distinct tasks, inception, elicitation, elaboration, negotiation, specification, validation, requirements management. | Requirements Engineering Process Tasks Lecture-4 Recap Problems with requirements engineering practices Seven distinct tasks Inception Elicitation Elaboration Negotiation Specification Validation Requirements Management RE Tasks (Cont ) Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Quality Function Deployment This is a technique that translates the needs of the customer into technical requirements for software It emphasizes an understanding of what is valuable to the customer and then deploys these values throughout the engineering process through functions, information, and tasks It identifies three types of requirements Normal requirements: These requirements are the objectives and goals stated for a product or system during meetings with the customer Expected requirements: These requirements are implicit to the product or system and may be so fundamental that the customer does not explicitly state them Exciting requirements: These . | Requirements Engineering Process Tasks Lecture-4 Recap Problems with requirements engineering practices Seven distinct tasks Inception Elicitation Elaboration Negotiation Specification Validation Requirements Management RE Tasks (Cont ) Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Quality Function Deployment This is a technique that translates the needs of the customer into technical requirements for software It emphasizes an understanding of what is valuable to the customer and then deploys these values throughout the engineering process through functions, information, and tasks It identifies three types of requirements Normal requirements: These requirements are the objectives and goals stated for a product or system during meetings with the customer Expected requirements: These requirements are implicit to the product or system and may be so fundamental that the customer does not explicitly state them Exciting requirements: These requirements are for features that go beyond the customer's expectations and prove to be very satisfying when present Elicitation Work Products A statement of need and feasibility A bounded statement of scope for the system or product A list of customers, users, and other stakeholders who participated in requirements elicitation A description of the system's technical environment A list of requirements (organized by function) and the domain constraints that apply to each A set of preliminary usage scenarios (in the form of use cases) that provide insight into the use of the system or product under different operating conditions Any prototypes developed to better define requirements The work products will vary depending on the system, but should include one or more of the following items Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Elaboration Task During elaboration, the software engineer takes the information obtained during inception .
