1. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 1 Software Process Models

2. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 2 Objectives l To introduce software process models l To describe three generic process models and when they may be used l To outline process models for requirements engineering, software development, testing and evolution l To explain the Rational Unified Process model l To introduce CASE technology to support software process activities

3. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 3 Topics covered l Software process models l Process iteration l Process activities l The Rational Unified Process l Computer-aided software engineering

4. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 4 The software process l A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. l A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.

5. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 5 Generic software process models l The waterfall model Separate and distinct phases of specification and development. l Evolutionary development Specification, development and validation are interleaved. l Component-based software engineering The system is assembled from existing components. l There are many variants of these models e.g. formal development where a waterfall-like process is used but the specification is a formal specification that is refined through several stages to an implementable design.

6. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 6 Waterfall model

7. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 7 Waterfall model phases l Requirements analysis and definition l System and software design l Implementation and unit testing l Integration and system testing l Operation and maintenance l The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. One phase has to be complete before moving onto the next phase.

8. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 8 Waterfall model problems l Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. l Therefore, this model is only appropriate when the requirements are well-understood and changes will be fairly limited during the design process. l Few business systems have stable requirements. l The waterfall model is mostly used for large systems engineering projects where a system is developed at several sites.

9. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 9 Evolutionary development l Exploratory development Objective is to work with customers and to evolve a final system from an initial outline specification. Should start with well-understood requirements and add new features as proposed by the customer. l Throw-away prototyping Objective is to understand the system requirements. Should start with poorly understood requirements to clarify what is really needed.

10. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 10 Evolutionary development Concurrent activities Validation Final version Development Intermediate versions Specification Initial version Outline description

11. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 11 Evolutionary development l Problems Lack of process visibility; Systems are often poorly structured; Special skills (e.g. in languages for rapid prototyping) may be required. l Applicability For small or medium-size interactive systems; For parts of large systems (e.g. the user interface); For short-lifetime systems.

12. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 12 Component-based software engineering l Based on systematic reuse where systems are integrated from existing components or COTS (Commercial-off-the-shelf) systems. l Process stages Component analysis; Requirements modification; System design with reuse; Development and integration. l This approach is becoming increasingly used as component standards have emerged.

13. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 13 Reuse-oriented development

14. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 14 Process iteration l System requirements ALWAYS evolve in the course of a project so process iteration where earlier stages are reworked is always part of the process for large systems. l Iteration can be applied to any of the generic process models. l Two (related) approaches Incremental delivery; Spiral development.

15. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 15 Incremental delivery l Rather than deliver the system as a single delivery, the development and delivery is broken down into increments with each increment delivering part of the required functionality. l User requirements are prioritised and the highest priority requirements are included in early increments. l Once the development of an increment is started, the requirements are frozen though requirements for later increments can continue to evolve.

16. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 16 Incremental development Validate increment Develop system increment Design system architecture Integrate increment Validate system Define outline requirements Assign requirements to increments System incomplete Final system

17. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 17 Incremental development advantages l Customer value can be delivered with each increment so system functionality is available earlier. l Early increments act as a prototype to help elicit requirements for later increments. l Lower risk of overall project failure. l The highest priority system services tend to receive the most testing.

18. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 18 Incremental development disadvantages l Increments should be relatively small and still deliver some functionality l Might be difficult to map customer requirements into increments l High level requirements may not be sufficient to define system architecture

19. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 19 Agile software development l Lightweight process for incremental delivery l Manifesto: We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

20. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 20 Extreme programming l An agile method l “Extreme” because: Extreme customer involvement On-site customer Extreme iterative development Incremental planning, small releases, continuous integration, sustainable pace Extreme teamwork Pair programming, collective ownership Extreme defect prevention Simple design, test-first development, refactoring

21. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 21

22. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 22 Extreme programming practices 1

23. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 23 Extreme programming practices 2

24. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 24 Extreme programming l An approach to development based on the development and delivery of very small increments of functionality. l Relies on constant code improvement, user involvement in the development team and pairwise programming. l Covered in Chapter 17

25. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 25 Spiral development l Process is represented as a spiral rather than as a sequence of activities with backtracking. l Each loop in the spiral represents a phase in the process. l No fixed phases such as specification or design - loops in the spiral are chosen depending on what is required. l Risks are explicitly assessed and resolved throughout the process.

26. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 26 Spiral model of the software process

27. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 27 Spiral model sectors l Objective setting Specific objectives for the phase are identified. l Risk assessment and reduction Risks are assessed and activities put in place to reduce the key risks. l Development and validation A development model for the system is chosen which can be any of the generic models. l Planning The project is reviewed and the next phase of the spiral is planned.

28. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 28 Process activities l Software specification l Software design and implementation l Software validation l Software evolution

29. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 29 Software specification l The process of establishing what services are required and the constraints on the system’s operation and development. l Requirements engineering process Feasibility study; Requirements elicitation and analysis; Requirements specification; Requirements validation.

30. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 30 The requirements engineering process Feasibility study Requirements elicitation and analysis Requirements specification Requirements validation Feasibility report System models User and system requirements Requirements document

31. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 31 Software design and implementation l The process of converting the system specification into an executable system. l Software design Design a software structure that realises the specification; l Implementation Translate this structure into an executable program; l The activities of design and implementation are closely related and may be inter-leaved.

32. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 32 Design process activities l Architectural design l Abstract specification l Interface design l Component design l Data structure design l Algorithm design

33. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 33 The software design process

34. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 34 Components of a design method l A set of system models l Rules that apply to these models l Guidelines for ‘good’ design l Design process model l Format of design document

35. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 35 Structured methods l Systematic approaches to developing a software design. l The design is usually documented as a set of graphical models. l Possible models Object model; Sequence model; State transition model; Structural model; Data-flow model.

36. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 36 Programming and debugging l Translating a design into a program and removing errors from that program. l Programming is a personal activity - there is no generic programming process. l Programmers carry out some program testing to discover faults in the program and remove these faults in the debugging process.

37. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 37 The debugging process

38. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 38 Software validation l Verification and validation (V & V) is intended to show that a system conforms to its specification and meets the requirements of the system customer. l Involves checking and review processes and system testing. l System testing involves executing the system with test cases that are derived from the specification of the real data to be processed by the system.

39. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 39 The testing process Component testing System testing Acceptance testing

40. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 40 Testing stages l Component or unit testing Individual components are tested independently; Components may be functions or objects or coherent groupings of these entities. l System testing Testing of the system as a whole. Testing of emergent properties is particularly important. l Acceptance testing Testing with customer data to check that the system meets the customer’s needs.

41. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 41 Testing phases

42. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 42 Software evolution l Software is inherently flexible and can change. l As requirements change through changing business circumstances, the software that supports the business must also evolve and change. l Although there has been a demarcation between development and evolution (maintenance) this is increasingly irrelevant as fewer and fewer systems are completely new.

43. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 43 System evolution

44. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 44 The Rational Unified Process l A modern process model derived from the work on the UML and associated process. l Normally described from 3 perspectives A dynamic perspective that shows phases over time; A static perspective that shows process activities; A practice perspective that suggests good practice.

45. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 45 RUP phase model

46. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 46 RUP phases l Inception Establish the business case for the system. l Elaboration Develop an understanding of the problem domain and the system architecture. l Construction System design, programming and testing. l Transition Deploy the system in its operating environment.

47. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 47 RUP good practice l Develop software iteratively l Manage requirements l Use component-based architectures l Visually model software l Verify software quality l Control changes to software

48. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 48 Static workflows

49. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 49 Dynamic Phases and Static Workflows

50. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 50 Computer-aided software engineering l Computer-aided software engineering (CASE) is software to support software development and evolution processes. l Activity automation Graphical editors for system model development; Data dictionary to manage design entities; Graphical UI builder for user interface construction; Debuggers to support program fault finding; Automated translators to generate new versions of a program.

51. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 51 Case technology l Case technology has led to significant improvements in the software process. However, these are not the order of magnitude improvements that were once predicted Software engineering requires creative thought - this is not readily automated; Software engineering is a team activity and, for large projects, much time is spent in team interactions. CASE technology does not really support these.

52. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 52 CASE classification l Classification helps us understand the different types of CASE tools and their support for process activities. l Functional perspective Tools are classified according to their specific function. l Process perspective Tools are classified according to process activities that are supported. l Integration perspective Tools are classified according to their organisation into integrated units.

53. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 53 Functional tool classification

54. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 54 Activity-based tool classification

55. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 55 CASE integration l Tools Support individual process tasks such as design consistency checking, text editing, etc. l Workbenches Support a process phase such as specification or design, Normally include a number of integrated tools. l Environments Support all or a substantial part of an entire software process. Normally include several integrated workbenches.

56. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 56 Tools, workbenches, environments

57. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 57 Key points l Software processes are the activities involved in producing and evolving a software system. l Software process models are abstract representations of these processes. l General activities are specification, design and implementation, validation and evolution. l Generic process models describe the organisation of software processes. Examples include the waterfall model, evolutionary development and component-based software engineering. l Iterative process models describe the software process as a cycle of activities.

58. Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 4 Slide 58 Key points l Requirements engineering is the process of developing a software specification. l Design and implementation processes transform the specification to an executable program. l Validation involves checking that the system meets to its specification and user needs. l Evolution is concerned with modifying the system after it is in use. l The Rational Unified Process is a generic process model that separates activities from phases. l CASE technology supports software process activities.