Danh mục

Lecture Introduction to software engineering - Week 2: Software processes

Số trang: 55      Loại file: pdf      Dung lượng: 1.06 MB      Lượt xem: 18      Lượt tải: 0    
tailieu_vip

Hỗ trợ phí lưu trữ khi tải xuống: 1,000 VND Tải xuống file đầy đủ (55 trang) 0

Báo xấu

Xem trước 6 trang đầu tiên của tài liệu này:

Thông tin tài liệu:

Lecture Introduction to software engineering - Week 2: Software processes. In this chapter, you will learn to: Software process models, process activities, copingwith change, process improvement.
Nội dung trích xuất từ tài liệu:
Lecture Introduction to software engineering - Week 2: Software processes Week 2: Software Processes Nguyễn Thị Minh Tuyền CuuDuongThanCong.com https://fb.com/tailieudientucntt Topics covered 1. Software process models 2. Process activities 3. Coping with change 4. Process improvement 2 CuuDuongThanCong.com https://fb.com/tailieudientucntt Definitions £ What is a process? £ Four activities that are fundamental to software engineering? £ What is process model? 3 CuuDuongThanCong.com https://fb.com/tailieudientucntt The software process £ A structured set of activities required to develop a software system. £ 4 fundamental activities: p Specification – defining what the system should do; p Design and implementation – defining the organization of the system and implementing the system; p Validation – checking that it does what the customer wants; p Evolution – changing the system in response to changing customer needs. £ A software process model p Is an abstract representation of a process. p Presents a description of a process from some particular perspective. 4 CuuDuongThanCong.com https://fb.com/tailieudientucntt Software process descriptions £ When we describe and discuss processes, we usually talk about p the activities in these processes such as specifying a data model, designing a user interface, etc. and p the ordering of these activities. £ Process descriptions may also include: p Products, which are the outcomes of a process activity; p Roles, which reflect the responsibilities of the people involved in the process; p Pre- and post-conditions, which are statements that are true before and after a process activity has been enacted or a product produced. 5 CuuDuongThanCong.com https://fb.com/tailieudientucntt Plan-driven and agile processes £ Plan-driven processes are processes where all of the process activities are planned in advance and progress is measured against this plan. £ In agile processes, planning is incremental and it is easier to change the process to reflect changing customer requirements. £ In practice, most practical processes include elements of both plan-driven and agile approaches. £ There are no right or wrong software processes. 6 CuuDuongThanCong.com https://fb.com/tailieudientucntt Topics covered 1. Software process models 2. Process activities 3. Coping with change 4. Process improvement 7 CuuDuongThanCong.com https://fb.com/tailieudientucntt Software process models £ The waterfall model p Plan-driven model. Separate and distinct phases of specification and development. £ Incremental development p Specification, development and validation are interleaved. May be plan-driven or agile. £ Reuse-oriented software engineering p The system is assembled from existing components. May be plan-driven or agile. £ In practice, most large systems are developed using a process that incorporates elements from all of these models. 8 CuuDuongThanCong.com https://fb.com/tailieudientucntt The waterfall model Requirements definition System and software design Implementation and unit testing Integration and system testing Operation and maintenance 9 CuuDuongThanCong.com https://fb.com/tailieudientucntt Waterfall model phases £ The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. £ In principle, a phase has to be complete before moving onto the next phase. 10 CuuDuongThanCong.com https://fb.com/tailieudientucntt Waterfall model problems £ Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. p Only appropriate when the requirements are well-understood and changes will be fairly limited during the design process. p Few business systems have stable requirements. £ Mostly used for large systems engineering projects where a system is developed at several sites. p The plan-driven nature of the waterfall model helps coordinate the work. 11 CuuDuongThanCong.com https://fb.com/tailieudientucntt £ An importa ...

Tài liệu được xem nhiều: