Software Engineering (part 4)

Slide 1: Software Processes ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1

Slide 2: Objectives To introduce software process models q To describe three generic process models and q when they may be used To describe outline process models for q requirements engineering, software development, testing and evolution To explain the Rational Unified Process model q To introduce CASE technology to support q software process activities ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 2

Slide 3: Topics covered Software process models q Process iteration q Process activities q The Rational Unified Process q Computer-aided software engineering q ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 3

Slide 4: The software process A structured set of activities required to develop a q software system • Specification; • Design; • Validation; • Evolution. A software process model is an abstract q representation of a process. It presents a description of a process from some particular perspective. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 4

Slide 5: Generic software process models The waterfall model q • Separate and distinct phases of specification and development. Evolutionary development q • Specification, development and validation are interleaved. Component-based software engineering q • The system is assembled from existing components. There are many variants of these models e.g. formal q 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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 5

Slide 6: Rsoftwa equir ement definiti Waterfall model SImplu yand stem tion Inte rOp am tio syst aio t ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 6

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

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

Slide 9: Evolutionary development Exploratory development q • 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. Throw-away prototyping q • Objective is to understand the system requirements. Should start with poorly understood requirements to clarify what is really needed. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 9

Slide 10: Conc ent r acti vities In Evolutionary development Speci tion vrs e DeInt me te Outline vlida elopm vr e descrip Fin Vv ae tion ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 10

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

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

Slide 13: Reuse-oriented development Requirem Compoi Requi S ste y val specificati analysis modif with Deve andst S y ratio ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 13

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

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

Slide 16: Incremental development Assign Desi Definetei o tolid requirem arV chite esys Developy Vlida s a stem teInteg rea F a t incrincr ement incr ement eme S y ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 16

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

Slide 18: Extreme programming An approach to development based on the q development and delivery of very small increments of functionality. Relies on constant code improvement, user q involvement in the development team and pairwise programming. Covered in Chapter 17 q ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 18

Slide 19: Spiral development Process is represented as a spiral rather than q as a sequence of activities with backtracking. Each loop in the spiral represents a phase in q the process. No fixed phases such as specification or design q - loops in the spiral are chosen depending on what is required. Risks are explicitly assessed and resolved q throughout the process. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 19

Slide 20: DeterEvs, mineanala tiss,Risk v Risk e ysis obje v andti alua te v e alternaerri e anal constr,Opiden eso aintsRisk ysis Spiral model of the software process a- analks1 ysismo Pr be otot Pr,tion pr oto ype ototy Risk Pr oto- Rysis Eanal EWDe VIplan type Rquir e Conce ements cleSim ula tions ,Cod Life-cy Oper aequir trlida ion S/W Pr odu emen desi des Dequir eRnelop eAccep emen vphase lopme vtest a Integ tion planelvp Unit t Design Integ rion,odu aServic xt V&V andre av ttest ion Plan testDe verif ne xt-l ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 20

Slide 21: Spiral model sectors Objective setting q • Specific objectives for the phase are identified. Risk assessment and reduction q • Risks are assessed and activities put in place to reduce the key risks. Development and validation q • A development model for the system is chosen which can be any of the generic models. Planning q • The project is reviewed and the next phase of the spiral is planned. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 21

Slide 22: Process activities Software specification q Software design and implementation q Software validation q Software evolution q ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 22

Slide 23: Software specification The process of establishing what services are q required and the constraints on the system’s operation and development. Requirements engineering process q • Feasibility study; • Requirements elicitation and analysis; • Requirements specification; • Requirements validation. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 23

Slide 24: Rquir e Rqui emen Fasibilit easibilit elicita studeme ypor Rq analva ysise e em spec The requirements engineering process F S stem e mode rt y User requ Rq e em do ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 24

Slide 25: Software design and implementation The process of converting the system q specification into an executable system. Software design q • Design a software structure that realises the specification; Implementation q • Translate this structure into an executable program; The activities of design and implementation are q closely related and may be inter-leaved. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 25

Slide 26: Design process activities Architectural design q Abstract specification q Interface design q Component design q Data structure design q Algorithm design q ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 26

Slide 27: Rquiresig eAbstrta ementsA The software design process specifica tiondesig D stru vities Da AractCom chitectur alarface A Interd e designstru specifica tion des design Da ta S stemspe y specifica Softwesti especifi Inter p face Com ar tion tio chitectur e tionspeci tion Desig oduc ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 27

Slide 28: Structured methods Systematic approaches to developing a q software design. The design is usually documented as a set of q graphical models. Possible models q • Object model; • Sequence model; • State transition model; • Structural model; • Data-flow model. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 28

Slide 29: Programming and debugging Translating a design into a program and q removing errors from that program. Programming is a personal activity - there is no q generic programming process. Programmers carry out some program testing q to discover faults in the program and remove these faults in the debugging process. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 29

Slide 30: The debugging process DRpam esig Locarpr teepair e R- e err o or g err err or orra ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 30

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

Slide 32: S ste y Ac Comp The testing process testi te testing ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 32

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

Slide 34: Testing phases RquirSub-n etionyinteg ementsM Sintegu ySSrDet stemstem specifica p specific tionion design desi yStest stem Acceptan rinteg t aystem tr aSub ionion tinte testtionan plan testa pla Accepta Service test r at ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 34

Slide 35: Software evolution Software is inherently flexible and can change. q As requirements change through changing q business circumstances, the software that supports the business must also evolve and change. Although there has been a demarcation q between development and evolution (maintenance) this is increasingly irrelevant as fewer and fewer systems are completely new. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 35

Slide 36: Definey Asses ProM System evolution require syste cha sy Existi N system s ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 36

Slide 37: The Rational Unified Process A modern process model derived from the work q on the UML and associated process. Normally described from 3 perspectives q • A dynamic perspective that shows phases over time; • A static perspective that shows process activities; • A practive perspective that suggests good practice. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 37

Slide 38: RUP phase model Phas Incepti Elabo Con Ta r ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 38

Slide 39: RUP phases Inception q • Establish the business case for the system. Elaboration q • Develop an understanding of the problem domain and the system architecture. Construction q • System design, programming and testing. Transition q • Deploy the system in its operating environment. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 39

Slide 40: RUP good practice Develop software iteratively q Manage requirements q Use component-based architectures q Visually model software q Verify software quality q Control changes to software q ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 40

Slide 41: Static workflows Workflow Description Business modelling The business processes are modelled using business use cases. Requirements Actors who interact with the system are identified and use cases are developed to model the system requirements. Analysis and design A design model is created and documented using architectural models, component models, object models and sequence models. Implementation The components in the system are implemented and structured into implementation sub-systems. Automatic code generation from design models helps accelerate this process. Test Testing is an iterative process that is carried out in conjunction with implementation. System testing follows the completion of the implementation. Deployment A product release is created, distributed to users and installed in their workplace. Configuration and This supporting workflow managed changes to the system (see change management Chapter 29). Project management This supporting workflow manages the system development (see Chapter 5). Environment This workflow is concerned with making appropriate software tools available to the software development team. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 41

Slide 42: Computer-aided software engineering Computer-aided software engineering (CASE) is q software to support software development and evolution processes. Activity automation q • 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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 42

Slide 43: Case technology Case technology has led to significant q 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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 43

Slide 44: CASE classification Classification helps us understand the different types q of CASE tools and their support for process activities. Functional perspective q • Tools are classified according to their specific function. Process perspective q • Tools are classified according to process activities that are supported. Integration perspective q • Tools are classified according to their organisation into integrated units. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 44

Slide 45: Functional tool classification Tool type Examples Planning tools PERT tools, estimation tools, spreadsheets Editing tools Text editors, diagram editors, word processors Change management tools Requirements traceability tools, change control systems Configuration management tools Version management systems, system building tools Prototyping tools Very high-level languages, user interface generators Method-support tools Design editors, data dictionaries, code generators Language-processing tools Compilers, interpreters Program analysis tools Cross reference generators, static analysers, dynamic analysers Testing tools Test data generators, file comparators Debugging tools Interactive debugging systems Documentation tools Page layout programs, image editors Re-engineering tools Cross-reference systems, program re-structuring systems ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 45

Slide 46: Re-eng t ineering Activity-based tool classification Tsting tools e tools Debugg ing analys Prog sup ram Language-p tools Method t tools Prototypin Configurat managemen Change tooma Documenta Editing rific Planning t Specifica Design Implem Vlida e and a ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 46

Slide 47: CASE integration Tools q • Support individual process tasks such as design consistency checking, text editing, etc. Workbenches q • Support a process phase such as specification or design, Normally include a number of integrated tools. Environments q • Support all or a substantial part of an entire software process. Normally include several integrated workbenches. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 47

Slide 48: CSE A techno grEn yvir Tools, workbenches, environments Tolsronm Wed oInteg kbenc o FilePr Editorsoce tovired aen t and Compile compar agenvir ors onmonm AnalLan ysisTstin Pre ge- rGene aal-pu mmi design Multi-me o Single- wrwrwrwr kbenches ooo kbench kben kbe ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 48

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

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