Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
After studying this chapter you will be able to understand: Project management, responsibilities/tasks of a project manager, traditional vs. web project management, introduction to RE, RE basics, requirements specification, RE process, RE specifics in web engineering. | Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 1 Basharat Mahmood, COMSATS Institute of Information Technology, Islamabad, Pakistan. 2 Project management Responsibilities/tasks of a Project manager Planning Risk management People management Reporting Proposal writing Traditional vs. web project management Introduction to RE RE basics Requirements specification RE process RE specifics in web engineering Requirements Engineering: the principles, methods, & tools for drawing, describing, validating, and managing project goals and needs Given the complexity of Web apps, RE is a critical initial stage activity, but often poorly executed Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 4 Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 5 Costs: Inadequate software architectures “Unforeseen” problems budget overruns production delays “that’s not what I asked for” Low user acceptance Basharat Mahmood, . | Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 1 Basharat Mahmood, COMSATS Institute of Information Technology, Islamabad, Pakistan. 2 Project management Responsibilities/tasks of a Project manager Planning Risk management People management Reporting Proposal writing Traditional vs. web project management Introduction to RE RE basics Requirements specification RE process RE specifics in web engineering Requirements Engineering: the principles, methods, & tools for drawing, describing, validating, and managing project goals and needs Given the complexity of Web apps, RE is a critical initial stage activity, but often poorly executed Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 4 Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 5 Costs: Inadequate software architectures “Unforeseen” problems budget overruns production delays “that’s not what I asked for” Low user acceptance Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 6 Why requirement engineering: requirements don’t define themselves (Bell & Thayer, 1976) removal of mistakes post hoc is up to 200 times more costly (Boehm, 1981) iterative collection and refinement is the most important function of a software engineer (Brooks, 1987) Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 7 Why requirement engineering: A study based on 340 companies in Austria, more than two thirds consider the SRS as the major problem in development process (1995) A study on Web applications, 16% systems fully meet their requirement while 53% deployed systems do not (Cutter Consortium, 2000) Basharat Mahmood, Department of Computer Science, CIIT, Islamabad, Pakistan. 8 Why requirement engineering: A study among 8000 projects, 30% of projects fail before completion & almost half do not meet customer requirements (Standish group, 1994) Unclear objectives, unrealistic schedules & expectations, .
