Kinh doanh - Marketing
Kinh tế quản lý
Biểu mẫu - Văn bản
Tài chính - Ngân hàng
Công nghệ thông tin
Tiếng anh ngoại ngữ
Kĩ thuật công nghệ
Khoa học tự nhiên
Khoa học xã hội
Văn hóa nghệ thuật
Sức khỏe - Y tế
Văn bản luật
Nông Lâm Ngư
Kỹ năng mềm
Luận văn - Báo cáo
Giải trí - Thư giãn
Tài liệu phổ thông
Văn mẫu
Giới thiệu
Đăng ký
Đăng nhập
Tìm
Danh mục
Kinh doanh - Marketing
Kinh tế quản lý
Biểu mẫu - Văn bản
Tài chính - Ngân hàng
Công nghệ thông tin
Tiếng anh ngoại ngữ
Kĩ thuật công nghệ
Khoa học tự nhiên
Khoa học xã hội
Văn hóa nghệ thuật
Y tế sức khỏe
Văn bản luật
Nông lâm ngư
Kĩ năng mềm
Luận văn - Báo cáo
Giải trí - Thư giãn
Tài liệu phổ thông
Văn mẫu
Thông tin
Điều khoản sử dụng
Quy định bảo mật
Quy chế hoạt động
Chính sách bản quyền
Giới thiệu
Đăng ký
Đăng nhập
0
Trang chủ
Công Nghệ Thông Tin
Kỹ thuật lập trình
Lecture Systems analysis and design methods (7/e): Chapter 6 – Whitten, Bentley
Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Systems analysis and design methods (7/e): Chapter 6 – Whitten, Bentley
Trọng Duy
119
50
ppt
Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Effective fact-finding techniques are crucial to the development of systems projects. In this chapter you will learn about techniques to discover and analyze information system requirements. You will learn how to use various fact- finding techniques to gather information about the system’s problems, opportunities, and directives. | Chapter 6 Fact-Finding Techniques for Requirements Discovery Objectives Define system requirements and differentiate between functional and nonfunctional requirements. Understand the activity of problem analysis and be able to create an Ishikawa (fishbone) diagram. Understand the concept of requirements management. Identify and characterize seven fact-finding techniques. Understand six guidelines for effective listening. Understand body language and proxemics. Characterize the typical participants in a JRP session. Complete the planning process for a JRP session. Describe benefits of JRP as fact-finding technique. Describe a fact-finding strategy that will make the most of your time with end-users. 6- 6- Introduction to Requirements Discovery Requirements discovery – the process and techniques used by systems analysts to identify or extract system problems and solution requirements from the user community. System requirement – something that the information system must do or a | Chapter 6 Fact-Finding Techniques for Requirements Discovery Objectives Define system requirements and differentiate between functional and nonfunctional requirements. Understand the activity of problem analysis and be able to create an Ishikawa (fishbone) diagram. Understand the concept of requirements management. Identify and characterize seven fact-finding techniques. Understand six guidelines for effective listening. Understand body language and proxemics. Characterize the typical participants in a JRP session. Complete the planning process for a JRP session. Describe benefits of JRP as fact-finding technique. Describe a fact-finding strategy that will make the most of your time with end-users. 6- 6- Introduction to Requirements Discovery Requirements discovery – the process and techniques used by systems analysts to identify or extract system problems and solution requirements from the user community. System requirement – something that the information system must do or a property that it must have. Also called a business requirement. 6- Functional vs. Nonfunctional Requirements Functional requirement - something the information system must do Nonfunctional requirement - a property or quality the system must have Performance Security Costs 6- Results of Incorrect Requirements The system may cost more than projected. The system may be delivered later than promised. The system may not meet the users’ expectations and they may not to use it. Once in production, costs of maintaining and enhancing system may be excessively high. The system may be unreliable and prone to errors and downtime. Reputation of IT staff is tarnished as failure will be perceived as a mistake by the team. 6- Relative Cost to Fix an Error 6- Criteria for System Requirements Consistent – not conflicting or ambiguous. Complete – describe all possible system inputs and responses. Feasible – can be satisfied based on the available resources and constraints. Required – .
TÀI LIỆU LIÊN QUAN
Lecture Introduction to systems analysis and design: Chapter 15 - Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 5 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 12 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 2 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 16 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 14 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 17 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 18 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 3 – Whitten, Bentley
Lecture Systems analysis and design methods (7/e): Chapter 19 – Whitten, Bentley
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.