Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Tham khảo tài liệu 'seventh edition - chương 10', công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả | Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 10 REQUIREMENTS Overview Determining what the client needs Overview of the requirements workflow Understanding the domain The business model Initial requirements Initial understanding of the domain: The MSG Foundation case study Initial business model: The MSG Foundation case study Overview (contd) Initial requirements: The MSG Foundation case study Continuing the requirements workflow: The MSG Foundation case study Revising the requirements: The MSG Foundation case study The test workflow: The MSG Foundation case study The classical requirements phase Rapid prototyping Overview (contd) Human factors Reusing the rapid prototype CASE tools for the requirements workflow Metrics for the requirements workflow Challenges of the requirements workflow The Aim of the Requirements Workflow To answer the question: What must the product be able to do? . | Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 10 REQUIREMENTS Overview Determining what the client needs Overview of the requirements workflow Understanding the domain The business model Initial requirements Initial understanding of the domain: The MSG Foundation case study Initial business model: The MSG Foundation case study Overview (contd) Initial requirements: The MSG Foundation case study Continuing the requirements workflow: The MSG Foundation case study Revising the requirements: The MSG Foundation case study The test workflow: The MSG Foundation case study The classical requirements phase Rapid prototyping Overview (contd) Human factors Reusing the rapid prototype CASE tools for the requirements workflow Metrics for the requirements workflow Challenges of the requirements workflow The Aim of the Requirements Workflow To answer the question: What must the product be able to do? 10.1 Determining What the Client Needs Misconception We must determine what the client wants “I know you believe you understood what you think I said, but I am not sure you realize that what you heard is not what I meant!” We must determine what the client needs Determining What the Client Needs (contd) It is hard for a systems analyst to visualize a software product and its functionality The problem is far worse for the client A skilled systems analyst is needed to elicit the appropriate information from the client The client is the only source of this information Determining What the Client Needs (contd) The solution: Obtain initial information from the client Use this initial information as input to the Unified Process Follow the steps of the Unified Process to determine the client’s real needs 10.2 Overview of the Requirements Workflow First, gain an understanding of the application domain (or domain, for short) The specific environment in which the target product is to operate .
