Seventh Edition - Chương 10
Số trang: 124
Loại file: ppt
Dung lượng: 7.99 MB
Lượt xem: 10
Lượt tải: 0
Xem trước 10 trang đầu tiên của tài liệu này:
Thông tin tài liệu:
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ả
Nội dung trích xuất từ tài liệu:
Seventh Edition - Chương 10 Slide 10..1Object-Oriented and Classical Software EngineeringSeventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu © The McGraw-Hill Companies, 2007 CHAPTER 10 Slide 10..2REQUIREMENTS © The McGraw-Hill Companies, 2007 Overview Slide 10..3 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 © The McGraw-Hill Companies, 2007 Overview (contd) Slide 10..4 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 © The McGraw-Hill Companies, 2007 Overview (contd) Slide 10..5 Human factors Reusing the rapid prototype CASE tools for the requirements workflow Metrics for the requirements workflow Challenges of the requirements workflow © The McGraw-Hill Companies, 2007 The Aim of the Requirements Workflow Slide 10..6 To answer the question: What must the product be able to do? © The McGraw-Hill Companies, 200710.1 Determining What the Client Needs Slide 10..7 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 © The McGraw-Hill Companies, 2007Determining What the Client Needs (contd) Slide 10..8 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 © The McGraw-Hill Companies, 2007Determining What the Client Needs (contd) Slide 10..9 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 © The McGraw-Hill Companies, 200710.2 Overview of the Requirements Workflow Slide 10..10 First, gain an understanding of the application domain (or domain, for short) The specific environment in which the target product is to operate Second, build a business model Model the client’s business processes Third, use the business model to determine the client’s requirements Iterate the above steps © The McGraw-Hill Companies, 2007 Definitions Slide 10..11 Discovering the client’s requirements Requirements elicitation (or requirements capture) Methods include interviews and surveys Refining and extending the initial requirements Requirements analysis © The McGraw-Hill Companies, 2007 10.3 Understanding the Domain Slide 10..12 Every member of the development team must become fully familiar with the application domain Correct terminology is essential Construct a glossary A list of technical words used in the domain, and their meanings © The McGraw-Hill Companies, 2007 10.4 Business Model Slide 10..13 A business model is a description of the business processes of an organization The business model gives an understanding of the client’s business as a whole This knowledge is essential for advising the client regarding computerization The systems analyst needs to obtain a detailed understanding of the various business processes Different techniques are used, primarily interviewing © The McGraw-Hill Companies, 2007 10.4.1 Interviewing Slide 10..14 The requirements team meet with the client and users to extract all relevant information © The McGraw-Hill Companies, 2007 Interviewing (contd) Slide 10..15 There are two types of questions Close-ended questions require a specific answer Open-ended questions are posed to encourage the person being interviewed to speak out There are two types of interviews In a structured interview, specific preplanned questions are asked, frequently close-ended In an unstructured interview, questions are posed in response to the answers received, frequently open- ended © The McGraw-Hill Companies, 2007 Interviewing (contd) Slide 10..16 Interviewing is not easy An interview that is too unstructured will not yield much relevant information The interviewer must be fully familiar with the application domain The interviewer must remain open-minded at all times After the inter ...
Nội dung trích xuất từ tài liệu:
Seventh Edition - Chương 10 Slide 10..1Object-Oriented and Classical Software EngineeringSeventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu © The McGraw-Hill Companies, 2007 CHAPTER 10 Slide 10..2REQUIREMENTS © The McGraw-Hill Companies, 2007 Overview Slide 10..3 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 © The McGraw-Hill Companies, 2007 Overview (contd) Slide 10..4 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 © The McGraw-Hill Companies, 2007 Overview (contd) Slide 10..5 Human factors Reusing the rapid prototype CASE tools for the requirements workflow Metrics for the requirements workflow Challenges of the requirements workflow © The McGraw-Hill Companies, 2007 The Aim of the Requirements Workflow Slide 10..6 To answer the question: What must the product be able to do? © The McGraw-Hill Companies, 200710.1 Determining What the Client Needs Slide 10..7 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 © The McGraw-Hill Companies, 2007Determining What the Client Needs (contd) Slide 10..8 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 © The McGraw-Hill Companies, 2007Determining What the Client Needs (contd) Slide 10..9 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 © The McGraw-Hill Companies, 200710.2 Overview of the Requirements Workflow Slide 10..10 First, gain an understanding of the application domain (or domain, for short) The specific environment in which the target product is to operate Second, build a business model Model the client’s business processes Third, use the business model to determine the client’s requirements Iterate the above steps © The McGraw-Hill Companies, 2007 Definitions Slide 10..11 Discovering the client’s requirements Requirements elicitation (or requirements capture) Methods include interviews and surveys Refining and extending the initial requirements Requirements analysis © The McGraw-Hill Companies, 2007 10.3 Understanding the Domain Slide 10..12 Every member of the development team must become fully familiar with the application domain Correct terminology is essential Construct a glossary A list of technical words used in the domain, and their meanings © The McGraw-Hill Companies, 2007 10.4 Business Model Slide 10..13 A business model is a description of the business processes of an organization The business model gives an understanding of the client’s business as a whole This knowledge is essential for advising the client regarding computerization The systems analyst needs to obtain a detailed understanding of the various business processes Different techniques are used, primarily interviewing © The McGraw-Hill Companies, 2007 10.4.1 Interviewing Slide 10..14 The requirements team meet with the client and users to extract all relevant information © The McGraw-Hill Companies, 2007 Interviewing (contd) Slide 10..15 There are two types of questions Close-ended questions require a specific answer Open-ended questions are posed to encourage the person being interviewed to speak out There are two types of interviews In a structured interview, specific preplanned questions are asked, frequently close-ended In an unstructured interview, questions are posed in response to the answers received, frequently open- ended © The McGraw-Hill Companies, 2007 Interviewing (contd) Slide 10..16 Interviewing is not easy An interview that is too unstructured will not yield much relevant information The interviewer must be fully familiar with the application domain The interviewer must remain open-minded at all times After the inter ...
Tìm kiếm theo từ khóa liên quan:
phần mềm công nghệ phần mềm tài liệu phần mềm thiết kế phần mềm lý thuyết phần mềmGợi ý tài liệu liên quan:
-
62 trang 390 3 0
-
Giáo trình Công nghệ phần mềm nâng cao: Phần 2
202 trang 214 0 0 -
Giáo trình Công nghệ phần mềm nâng cao: Phần 1
151 trang 189 0 0 -
Báo cáo chuyên đề Công nghệ phần mềm: Pattern searching
68 trang 184 0 0 -
Lecture Introduction to software engineering - Week 3: Project management
68 trang 161 0 0 -
Xây dựng mô hình và công cụ hỗ trợ sinh tác tử giao diện
13 trang 160 0 0 -
6 trang 153 0 0
-
Giáo trình tóm tắt Công nghệ phần mềm
149 trang 152 0 0 -
Bài giảng Phân tích thiết kế phần mềm: Chương 1 - Trường ĐH Ngoại ngữ - Tin học TP.HCM
64 trang 148 0 0 -
Cuộc chiến Phân kỳ - Tích hợp nhiều tranh cãi bậc nhất trong giới marketing
3 trang 148 0 0