Enviar pesquisa
Carregar
Software Engineering - Ch4
•
6 gostaram
•
8,825 visualizações
S
Siddharth Ayer
Seguir
Tecnologia
Negócios
Denunciar
Compartilhar
Denunciar
Compartilhar
1 de 50
Baixar agora
Baixar para ler offline
Recomendados
Software Engineering - Ch5
Software Engineering - Ch5
Siddharth Ayer
Software maintenance
Software maintenance
Indu Sharma Bhardwaj
The Software Development Process
The Software Development Process
Cesar Augusto Nogueira
Prototyping model
Prototyping model
Shirley Jenifer Joseph
SDLC ITS MODEL AND SOFTWARE TESTING
SDLC ITS MODEL AND SOFTWARE TESTING
Abhinav Shukla
SDLC - Software Development Life Cycle
SDLC - Software Development Life Cycle
Saravanan Manoharan
Component Based Software Engineering
Component Based Software Engineering
SatishDabhi1
Chapter 16
Chapter 16
Benjamin Yu
Recomendados
Software Engineering - Ch5
Software Engineering - Ch5
Siddharth Ayer
Software maintenance
Software maintenance
Indu Sharma Bhardwaj
The Software Development Process
The Software Development Process
Cesar Augusto Nogueira
Prototyping model
Prototyping model
Shirley Jenifer Joseph
SDLC ITS MODEL AND SOFTWARE TESTING
SDLC ITS MODEL AND SOFTWARE TESTING
Abhinav Shukla
SDLC - Software Development Life Cycle
SDLC - Software Development Life Cycle
Saravanan Manoharan
Component Based Software Engineering
Component Based Software Engineering
SatishDabhi1
Chapter 16
Chapter 16
Benjamin Yu
Chapter 03
Chapter 03
ppp mmm
Software requirements
Software requirements
Dr. Loganathan R
Component based software engineering
Component based software engineering
Charotar University Of Science And Technology,Gujrat
Software quality assurance
Software quality assurance
Aman Adhikari
Waterfall model
Waterfall model
Manusha Dilan
Software Development Life Cycle-SDLC
Software Development Life Cycle-SDLC
Adeel Rasheed
Incremental model
Incremental model
Comsat Institute of information technology
Software Evolution
Software Evolution
Md. Shafiuzzaman Hira
Software Testing Life Cycle
Software Testing Life Cycle
Udayakumar Sree
Non Functional Requirement.
Non Functional Requirement.
Khushboo Shaukat
Software Quality Assurance (May – 2019) [Choice Based | Question Paper]
Software Quality Assurance (May – 2019) [Choice Based | Question Paper]
Mumbai B.Sc.IT Study
Ch2-Software Engineering 9
Ch2-Software Engineering 9
Ian Sommerville
Designing Techniques in Software Engineering
Designing Techniques in Software Engineering
kirupasuchi1996
Ch 4 software engineering
Ch 4 software engineering
Mohammed Romi
unit testing and debugging
unit testing and debugging
KarthigaGunasekaran1
Software development life cycle
Software development life cycle
Gurban Daniel
SDLC - Software Development Life Cycle
SDLC - Software Development Life Cycle
Suresh Koujalagi
Software Engineering Process Models
Software Engineering Process Models
Satya P. Joshi
Software testing & Quality Assurance
Software testing & Quality Assurance
Webtech Learning
Sdlc models
Sdlc models
Vatsana Technologies Pte Ltd
Software Engineering - Ch7
Software Engineering - Ch7
Siddharth Ayer
Software Engineering - Ch1
Software Engineering - Ch1
Siddharth Ayer
Mais conteúdo relacionado
Mais procurados
Chapter 03
Chapter 03
ppp mmm
Software requirements
Software requirements
Dr. Loganathan R
Component based software engineering
Component based software engineering
Charotar University Of Science And Technology,Gujrat
Software quality assurance
Software quality assurance
Aman Adhikari
Waterfall model
Waterfall model
Manusha Dilan
Software Development Life Cycle-SDLC
Software Development Life Cycle-SDLC
Adeel Rasheed
Incremental model
Incremental model
Comsat Institute of information technology
Software Evolution
Software Evolution
Md. Shafiuzzaman Hira
Software Testing Life Cycle
Software Testing Life Cycle
Udayakumar Sree
Non Functional Requirement.
Non Functional Requirement.
Khushboo Shaukat
Software Quality Assurance (May – 2019) [Choice Based | Question Paper]
Software Quality Assurance (May – 2019) [Choice Based | Question Paper]
Mumbai B.Sc.IT Study
Ch2-Software Engineering 9
Ch2-Software Engineering 9
Ian Sommerville
Designing Techniques in Software Engineering
Designing Techniques in Software Engineering
kirupasuchi1996
Ch 4 software engineering
Ch 4 software engineering
Mohammed Romi
unit testing and debugging
unit testing and debugging
KarthigaGunasekaran1
Software development life cycle
Software development life cycle
Gurban Daniel
SDLC - Software Development Life Cycle
SDLC - Software Development Life Cycle
Suresh Koujalagi
Software Engineering Process Models
Software Engineering Process Models
Satya P. Joshi
Software testing & Quality Assurance
Software testing & Quality Assurance
Webtech Learning
Sdlc models
Sdlc models
Vatsana Technologies Pte Ltd
Mais procurados
(20)
Chapter 03
Chapter 03
Software requirements
Software requirements
Component based software engineering
Component based software engineering
Software quality assurance
Software quality assurance
Waterfall model
Waterfall model
Software Development Life Cycle-SDLC
Software Development Life Cycle-SDLC
Incremental model
Incremental model
Software Evolution
Software Evolution
Software Testing Life Cycle
Software Testing Life Cycle
Non Functional Requirement.
Non Functional Requirement.
Software Quality Assurance (May – 2019) [Choice Based | Question Paper]
Software Quality Assurance (May – 2019) [Choice Based | Question Paper]
Ch2-Software Engineering 9
Ch2-Software Engineering 9
Designing Techniques in Software Engineering
Designing Techniques in Software Engineering
Ch 4 software engineering
Ch 4 software engineering
unit testing and debugging
unit testing and debugging
Software development life cycle
Software development life cycle
SDLC - Software Development Life Cycle
SDLC - Software Development Life Cycle
Software Engineering Process Models
Software Engineering Process Models
Software testing & Quality Assurance
Software testing & Quality Assurance
Sdlc models
Sdlc models
Destaque
Software Engineering - Ch7
Software Engineering - Ch7
Siddharth Ayer
Software Engineering - Ch1
Software Engineering - Ch1
Siddharth Ayer
Software Engineering - Ch11
Software Engineering - Ch11
Siddharth Ayer
Software Engineering - Ch6
Software Engineering - Ch6
Siddharth Ayer
software engineering
software engineering
ramyavarkala
Software Engineering - Ch8
Software Engineering - Ch8
Siddharth Ayer
software engineering notes for cse/it fifth semester
software engineering notes for cse/it fifth semester
rajesh199155
Architectural patterns for real-time systems
Architectural patterns for real-time systems
sommerville-videos
Software engineering lecture notes
Software engineering lecture notes
Siva Ayyakutti
Software Engineering ppt
Software Engineering ppt
shruths2890
Software engineering presentation
Software engineering presentation
MJ Ferdous
Destaque
(11)
Software Engineering - Ch7
Software Engineering - Ch7
Software Engineering - Ch1
Software Engineering - Ch1
Software Engineering - Ch11
Software Engineering - Ch11
Software Engineering - Ch6
Software Engineering - Ch6
software engineering
software engineering
Software Engineering - Ch8
Software Engineering - Ch8
software engineering notes for cse/it fifth semester
software engineering notes for cse/it fifth semester
Architectural patterns for real-time systems
Architectural patterns for real-time systems
Software engineering lecture notes
Software engineering lecture notes
Software Engineering ppt
Software Engineering ppt
Software engineering presentation
Software engineering presentation
Semelhante a Software Engineering - Ch4
Software Engineering - Ch17
Software Engineering - Ch17
Siddharth Ayer
Evolution-2.ppt
Evolution-2.ppt
sandeep792081
ch5.pdf
ch5.pdf
Rayver4
Software Processes
Software Processes
university of education,Lahore
Software Processes
Software Processes
Mayuran Ramanathan
Ch1
Ch1
srvnsmile
about how software prototyping helps in SDLC
about how software prototyping helps in SDLC
shettyplacement08
Ch5
Ch5
Ankita Rana
Bai giang-se-20jan14
Bai giang-se-20jan14
TRAN Khanh Dung, Khoa CNTT, Đại Học Xây Dựng
project managnement.ppt
project managnement.ppt
ssuser8c0d24
Project Management.pdf
Project Management.pdf
HughMungus22
Project Management (Soft)
Project Management (Soft)
Ahmad Basim Hamza
Unit-3-Risk-mgmt.ppt
Unit-3-Risk-mgmt.ppt
joshimeet479
Introduction to Software Enigneering
Introduction to Software Enigneering
university of education,Lahore
Structured system analysis and design
Structured system analysis and design
Jayant Dalvi
Lect3 ch15-unit2
Lect3 ch15-unit2
Mobeen Mustafa
S.E Lec #1.pptx
S.E Lec #1.pptx
RaajpootQueen
SDLC
SDLC
Fayis-QA
Ch1
Ch1
guestfea9c55
Project Scheduling, Planning and Risk Management
Project Scheduling, Planning and Risk Management
university of education,Lahore
Semelhante a Software Engineering - Ch4
(20)
Software Engineering - Ch17
Software Engineering - Ch17
Evolution-2.ppt
Evolution-2.ppt
ch5.pdf
ch5.pdf
Software Processes
Software Processes
Software Processes
Software Processes
Ch1
Ch1
about how software prototyping helps in SDLC
about how software prototyping helps in SDLC
Ch5
Ch5
Bai giang-se-20jan14
Bai giang-se-20jan14
project managnement.ppt
project managnement.ppt
Project Management.pdf
Project Management.pdf
Project Management (Soft)
Project Management (Soft)
Unit-3-Risk-mgmt.ppt
Unit-3-Risk-mgmt.ppt
Introduction to Software Enigneering
Introduction to Software Enigneering
Structured system analysis and design
Structured system analysis and design
Lect3 ch15-unit2
Lect3 ch15-unit2
S.E Lec #1.pptx
S.E Lec #1.pptx
SDLC
SDLC
Ch1
Ch1
Project Scheduling, Planning and Risk Management
Project Scheduling, Planning and Risk Management
Último
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Edi Saputra
Top 10 Most Downloaded Games on Play Store in 2024
Top 10 Most Downloaded Games on Play Store in 2024
SynarionITSolutions
Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...
Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...
apidays
Powerful Google developer tools for immediate impact! (2023-24 C)
Powerful Google developer tools for immediate impact! (2023-24 C)
wesley chun
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Miguel Araújo
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
The Digital Insurer
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
ThousandEyes
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
sammart93
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
UK Journal
Partners Life - Insurer Innovation Award 2024
Partners Life - Insurer Innovation Award 2024
The Digital Insurer
Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
panagenda
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
The Digital Insurer
A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)
Gabriella Davis
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
Martijn de Jong
Automating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps Script
wesley chun
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Safe Software
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
Andrey Devyatkin
Artificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : Uncertainty
Khushali Kathiriya
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc
Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Juan lago vázquez
Último
(20)
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Top 10 Most Downloaded Games on Play Store in 2024
Top 10 Most Downloaded Games on Play Store in 2024
Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...
Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...
Powerful Google developer tools for immediate impact! (2023-24 C)
Powerful Google developer tools for immediate impact! (2023-24 C)
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
Partners Life - Insurer Innovation Award 2024
Partners Life - Insurer Innovation Award 2024
Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
Automating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps Script
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
Artificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : Uncertainty
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Software Engineering - Ch4
1.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes
2.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 2 Objectives ● To introduce software process models ● To describe three generic process models and when they may be used ● To describe outline process models for requirements engineering, software development, testing and evolution ● To explain the Rational Unified Process model ● To introduce CASE technology to support software process activities
3.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 3 Topics covered ● Software process models ● Process iteration ● Process activities ● The Rational Unified Process ● Computer-aided software engineering
4.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 4 The software process ● A structured set of activities required to develop a software system • Specification; • Design; • Validation; • Evolution. ● A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.
5.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 5 Generic software process models ● The waterfall model • Separate and distinct phases of specification and development. ● Evolutionary development • Specification, development and validation are interleaved. ● Component-based software engineering • The system is assembled from existing components. ● 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.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 6 Waterfall model
7.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 7 Waterfall model phases ● Requirements analysis and definition ● System and software design ● Implementation and unit testing ● Integration and system testing ● Operation and maintenance ● 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.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 8 Waterfall model problems ● Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. ● Therefore, this model is only appropriate when the requirements are well-understood and changes will be fairly limited during the design process. ● Few business systems have stable requirements. ● The waterfall model is mostly used for large systems engineering projects where a system is developed at several sites.
9.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 9 Evolutionary development ● 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. ● Throw-away prototyping • Objective is to understand the system requirements. Should start with poorly understood requirements to clarify what is really needed.
10.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 10 Evolutionary development
11.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 11 Evolutionary development ● Problems • Lack of process visibility; • Systems are often poorly structured; • Special skills (e.g. in languages for rapid prototyping) may be required. ● Applicability • For small or medium-size interactive systems; • For parts of large systems (e.g. the user interface); • For short-lifetime systems.
12.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 12 Component-based software engineering ● Based on systematic reuse where systems are integrated from existing components or COTS (Commercial-off-the-shelf) systems. ● Process stages • Component analysis; • Requirements modification; • System design with reuse; • Development and integration. ● This approach is becoming increasingly used as component standards have emerged.
13.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 13 Reuse-oriented development
14.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 14 Process iteration ● 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. ● Iteration can be applied to any of the generic process models. ● Two (related) approaches • Incremental delivery; • Spiral development.
15.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 15 Incremental delivery ● 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. ● User requirements are prioritised and the highest priority requirements are included in early increments. ● Once the development of an increment is started, the requirements are frozen though requirements for later increments can continue to evolve.
16.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 16 Incremental development
17.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 17 Incremental development advantages ● Customer value can be delivered with each increment so system functionality is available earlier. ● Early increments act as a prototype to help elicit requirements for later increments. ● Lower risk of overall project failure. ● The highest priority system services tend to receive the most testing.
18.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 18 Extreme programming ● An approach to development based on the development and delivery of very small increments of functionality. ● Relies on constant code improvement, user involvement in the development team and pairwise programming. ● Covered in Chapter 17
19.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 19 Spiral development ● Process is represented as a spiral rather than as a sequence of activities with backtracking. ● Each loop in the spiral represents a phase in the process. ● No fixed phases such as specification or design - loops in the spiral are chosen depending on what is required. ● Risks are explicitly assessed and resolved throughout the process.
20.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 20 Spiral model of the software process
21.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 21 Spiral model sectors ● Objective setting • Specific objectives for the phase are identified. ● Risk assessment and reduction • Risks are assessed and activities put in place to reduce the key risks. ● Development and validation • A development model for the system is chosen which can be any of the generic models. ● Planning • The project is reviewed and the next phase of the spiral is planned.
22.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 22 Process activities ● Software specification ● Software design and implementation ● Software validation ● Software evolution
23.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 23 Software specification ● The process of establishing what services are required and the constraints on the system’s operation and development. ● Requirements engineering process • Feasibility study; • Requirements elicitation and analysis; • Requirements specification; • Requirements validation.
24.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 24 The requirements engineering process
25.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 25 Software design and implementation ● The process of converting the system specification into an executable system. ● Software design • Design a software structure that realises the specification; ● Implementation • Translate this structure into an executable program; ● The activities of design and implementation are closely related and may be inter-leaved.
26.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 26 Design process activities ● Architectural design ● Abstract specification ● Interface design ● Component design ● Data structure design ● Algorithm design
27.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 27 The software design process
28.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 28 Structured methods ● Systematic approaches to developing a software design. ● The design is usually documented as a set of graphical models. ● Possible models • Object model; • Sequence model; • State transition model; • Structural model; • Data-flow model.
29.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 29 Programming and debugging ● Translating a design into a program and removing errors from that program. ● Programming is a personal activity - there is no generic programming process. ● Programmers carry out some program testing to discover faults in the program and remove these faults in the debugging process.
30.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 30 The debugging process
31.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 31 Software validation ● Verification and validation (V & V) is intended to show that a system conforms to its specification and meets the requirements of the system customer. ● Involves checking and review processes and system testing. ● 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.
32.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 32 The testing process
33.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 33 Testing stages ● Component or unit testing • Individual components are tested independently; • Components may be functions or objects or coherent groupings of these entities. ● System testing • Testing of the system as a whole. Testing of emergent properties is particularly important. ● Acceptance testing • Testing with customer data to check that the system meets the customer’s needs.
34.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 34 Testing phases
35.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 35 Software evolution ● Software is inherently flexible and can change. ● As requirements change through changing business circumstances, the software that supports the business must also evolve and change. ● Although there has been a demarcation between development and evolution (maintenance) this is increasingly irrelevant as fewer and fewer systems are completely new.
36.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 36 System evolution
37.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 37 The Rational Unified Process ● A modern process model derived from the work on the UML and associated process. ● Normally described from 3 perspectives • A dynamic perspective that shows phases over time; • A static perspective that shows process activities; • A practive perspective that suggests good practice.
38.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 38 RUP phase model
39.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 39 RUP phases ● Inception • Establish the business case for the system. ● Elaboration • Develop an understanding of the problem domain and the system architecture. ● Construction • System design, programming and testing. ● Transition • Deploy the system in its operating environment.
40.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 40 RUP good practice ● Develop software iteratively ● Manage requirements ● Use component-based architectures ● Visually model software ● Verify software quality ● Control changes to software
41.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 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 change management This supporting workflow managed changes to the system (see 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.
42.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 42 Computer-aided software engineering ● Computer-aided software engineering (CASE) is software to support software development and evolution processes. ● 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.
43.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 43 Case technology ● 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.
44.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 44 CASE classification ● Classification helps us understand the different types of CASE tools and their support for process activities. ● Functional perspective • Tools are classified according to their specific function. ● Process perspective • Tools are classified according to process activities that are supported. ● Integration perspective • Tools are classified according to their organisation into integrated units.
45.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 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
46.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 46 Activity-based tool classification
47.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 47 CASE integration ● Tools • Support individual process tasks such as design consistency checking, text editing, etc. ● Workbenches • Support a process phase such as specification or design, Normally include a number of integrated tools. ● Environments • Support all or a substantial part of an entire software process. Normally include several integrated workbenches.
48.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 48 Tools, workbenches, environments
49.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 49 Key points ● Software processes are the activities involved in producing and evolving a software system. ● Software process models are abstract representations of these processes. ● General activities are specification, design and implementation, validation and evolution. ● Generic process models describe the organisation of software processes. Examples include the waterfall model, evolutionary development and component- based software engineering. ● Iterative process models describe the software process as a cycle of activities.
50.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 4 Slide 50 Key points ● Requirements engineering is the process of developing a software specification. ● Design and implementation processes transform the specification to an executable program. ● Validation involves checking that the system meets to its specification and user needs. ● Evolution is concerned with modifying the system after it is in use. ● The Rational Unified Process is a generic process model that separates activities from phases. ● CASE technology supports software process activities.
Baixar agora