tailieunhanh - Lecture Software requirements engineering - Lecture­ 5: Requirements engineering process tasks

After this chapter the student should have acquired the following knowledge and skills: Software requirements engineering tasks: Inception, elicitation, elaboration, negotiation; negotiation; specification; validation; requirements management. | Requirements Engineering Process Tasks Lecture-5 Recap Software requirements engineering tasks Inception Elicitation Elaboration Negotiation Todays lecture 3 Negotiation Specification Validation Requirements management Negotiation Task 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 Management Validation Inception Elicitation Elaboration Negotiation Specification Specification Task A specification is the final work product produced by the . | Requirements Engineering Process Tasks Lecture-5 Recap Software requirements engineering tasks Inception Elicitation Elaboration Negotiation Todays lecture 3 Negotiation Specification Validation Requirements management Negotiation Task 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 Management Validation Inception Elicitation Elaboration Negotiation Specification Specification Task A specification is the final work product produced by the requirements engineer It is normally in the form of a software requirements specification It serves as the foundation for subsequent software engineering activities It describes the function and performance of a computer-based system and the constraints that will govern its development It formalizes the informational, functional, and behavioral requirements of the proposed software in both a graphical and textual format Typical Contents of a Software Requirements Specification Requirements Required states and modes Software requirements grouped by capabilities (., functions, objects) Software external interface requirements Software internal interface requirements Software internal data requirements Other software requirements (safety, security, privacy, environment, hardware, software, communications, quality, personnel, training, logistics, etc.) Design and implementation constraints Typical Contents of a Software Requirements Specification Qualification provisions to ensure each .

TỪ KHÓA LIÊN QUAN
crossorigin="anonymous">
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.