software processes. objectives to introduce software process models to describe three generic...
TRANSCRIPT
![Page 1: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/1.jpg)
Software Processes
![Page 2: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/2.jpg)
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 that supports software process activities
![Page 3: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/3.jpg)
Outline• Software Process Models• Process Iteration• Process Activities• The Rational Unified Process• Computer-aided Software Engineering
![Page 4: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/4.jpg)
Outline
•Software Process Models• Process Iteration• Process Activities• The Rational Unified Process• Computer-aided Software Engineering
![Page 5: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/5.jpg)
The Software Process• “Software Process is a structure imposed on the
development of a software product. Similar terms include software life cycle and software development process.”
• It depends on many factors. For example; • type of product (real time/ embedded /information system/ safety
critical), • environment (single user/ networked/ distributed) in which it is
developed and needs to be deployed, • functional requirements, • time and budget, • skills and expertise of development team
Accordingly there are many process models available.
![Page 6: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/6.jpg)
Fundamental Activities• A structured set of fundamental activities required to
develop a software system
1. Specification s/w requirements (functional, non-functional, environment/domain)
2. Design s/w design according to requirements specification
3. Implementation Production of s/w meeting specification
4. Validation (Verification) Ensure that the software does what the clients want
5. Evolution Maintenance – Meeting Dynamic environment changes
![Page 7: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/7.jpg)
(CS340 J. Knight & T. Horton 2008) 7
The Software Lifecycle
![Page 8: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/8.jpg)
Generic Software Process Models
• Software process model• An abstract representation (simple/complex) of a process. • It presents a description of a process from some particular
perspective.
• Generic Models• The waterfall model
• Separate and distinct phases of specification and development.
• Evolutionary development• Specification, development and validation are interleaved.
• Reuse-based (Component-based) software engineering• The system is assembled from existing components.
![Page 9: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/9.jpg)
Waterfall Model
![Page 10: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/10.jpg)
Waterfall Model Phases• The sequential arrangement of development phases:
• Requirements analysis and definition (client)• System and software design• Implementation and unit testing• Integration and system testing• Operation and maintenance (client)
• 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.
![Page 11: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/11.jpg)
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.
Appropriate when requirements are well-understood and stable at start
![Page 12: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/12.jpg)
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.
![Page 13: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/13.jpg)
Evolutionary Development
![Page 14: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/14.jpg)
Evolutionary Development
• Problems• Lack of process visibility at client management level (less regular
reports/documentation… the system is changing continuously)• 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
Appropriate when requirements are not well-understood at start
![Page 15: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/15.jpg)
Component-Based Software Engineering
• Based on systematic reuse• Systems are integrated from
• Existing components (available in the library of the software house)• COTS (Commercial-off-the-shelf) systems (available or to be purchased
• The final product is assembled using existing components.
• Advantages• Minimum s/w development
• Less cost• Less risk• Less time• Reliable• Less testing
• Gaining more place in the market
![Page 16: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/16.jpg)
Reuse-Oriented Development• Process stages:
• Component analysis• Search for components covering most required functionality
• Requirements modification• To match existing reuse components
• System design with reuse• Design framework for reuse components• Design non available reuse components
• Development and integration• Develop non available reuse components• Integration of reuse & developed components
• This approach is becoming increasingly used as component standards have emerged.
![Page 17: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/17.jpg)
Reuse-Oriented Development
![Page 18: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/18.jpg)
Outline• Software Process Models
•Process Iteration• Process Activities• The Rational Unified Process• Computer-aided Software Engineering
![Page 19: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/19.jpg)
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 for iterations• Incremental delivery• Spiral development
![Page 20: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/20.jpg)
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.
• Incremental delivery: 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.
![Page 21: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/21.jpg)
Incremental Development
![Page 22: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/22.jpg)
Incremental Development Advantages
• System functionality is available earlier• Early involvement of client• Early increments act as a prototype to help elicit
requirements for later increments• Lower risk of overall project failure• High priority increment delivered first• The highest priority system services tend to receive the
most testing (first delivered)
![Page 23: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/23.jpg)
eXtreme Programming “XP”• XP is the most famous of the agile methods
• New 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• Pairwise programming
• See www.extremeprogramming.org
![Page 24: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/24.jpg)
eXtreme Programming “XP”• Claims to be good for risky projects with dynamic
requirements, and when continuous customer involvement is crucial (possible).
• Emphasizes• Team development: pair programming• Write test before code (unit testing)
![Page 25: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/25.jpg)
Spiral Development• Best features of waterfall & prototyping models
+ Risk Analysis (missed in other models)
• 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
![Page 26: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/26.jpg)
Spiral Model of the Software Process
![Page 27: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/27.jpg)
Spiral Model Sectors• Objective setting
• Specific objectives for the phase are identified
• Risk Analysis• 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• Simulation, benchmarks: to further define requirements
• Reviewing/Planning• Review the project with client• Plan the next phase of the spiral if further loop is needed.
![Page 28: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/28.jpg)
Outline• Software Process Models• Process Iteration
•Process Activities• The Rational Unified Process• Computer-aided Software Engineering
![Page 29: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/29.jpg)
Process Activities• Software specification• Software design and implementation• Software validation• Software evolution
![Page 30: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/30.jpg)
Software Specification Process (Requirements Engineering Process)• The process of establishing
• What services are required (Functional Requirements)• Constraints on the system’s operation and development (Non-
functional Requirements)
• Requirements engineering process• Feasibility study• Requirements elicitation and analysis• Requirements specification• Requirements validation
![Page 31: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/31.jpg)
The Requirements Engineering Process
![Page 32: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/32.jpg)
Software Design and Implementation
• The process of converting the system specification into an executable system
• Software design• System architecture design• Software structure that realises the specification• Interface, Data Structures, Database, Algorithm, GUI
• Implementation• Translate design into an executable program
• The activities of design and implementation are closely related and may be inter-leaved
![Page 33: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/33.jpg)
Design Process Activities
1. Architectural design
2. Abstract specification
3. System/subsystems Interface design
4. Component design
5. Data structure (Database) design
6. Algorithm design
![Page 34: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/34.jpg)
The Software Design Process
![Page 35: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/35.jpg)
Design Methods• Systematic approaches to developing a software design• Structured methods: Set of notations & guidelines for s/w
design• Graphical methods• CASE tools
• The design is usually documented as a set of graphical models
• Possible models• Process Model (Data-flow model)• Information/Data model (Entity-relation-attribute model)• Structural model: sys components and their interactions are
documented• Object-Oriented model:
• Inheritance model of the system• Interactions between objects
![Page 36: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/36.jpg)
Programming and Debugging• Translating a design into a program (programming) and
removing errors from that program (debugging)
• 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
![Page 37: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/37.jpg)
The Debugging Process
![Page 38: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/38.jpg)
Software Validation/Verification• Validation: Are we building the right product (satisfying
client requirements)• Verification: Are we building the product right (standards
of the development process)
• 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
• Test Cases / Test Scenarios• 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
![Page 39: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/39.jpg)
The testing process
![Page 40: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/40.jpg)
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
![Page 41: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/41.jpg)
Testing Phases
![Page 42: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/42.jpg)
Software Evolution (Maintenance)• Software is inherently flexible and can change
• So, s/w must be designed to respond to Dynamic changes in Business Environment• As requirements change through changing business environment, the
software that supports the business must also evolve and change• Maintenance/changes
• Adaptive• Corrective• Perfective
• Although there has been a demarcation between development and evolution this is increasingly irrelevant as fewer and fewer systems are completely new
![Page 43: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/43.jpg)
System Evolution (Maintenance)
![Page 44: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/44.jpg)
Outline• Software Process Models• Process Iteration• Process Activities
•The Rational Unified Process• Computer-aided Software Engineering
![Page 45: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/45.jpg)
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
![Page 46: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/46.jpg)
RUP Phase Model
![Page 47: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/47.jpg)
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
![Page 48: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/48.jpg)
RUP Good Practice
• Develop software iteratively• Manage requirements• Use component-based architectures• Visually model software• Verify software quality• Control changes to software
![Page 49: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/49.jpg)
Static Workflows
![Page 50: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/50.jpg)
Outline• Software Process Models• Process Iteration• Process Activities• The Rational Unified Process• Computer-aided Software Engineering
![Page 51: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/51.jpg)
CASE: Computer Aided Software Engineering• CASE tools
• Software tools 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
![Page 52: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/52.jpg)
CASE Technology• Case technology
• Led to significant improvements in the software process• However, magnitude improvements were not as predicted• Software engineering requires creative thought - this is not
readily automatable• Software engineering is a team activity and, for large
projects, much time is spent in team interactions. CASE technology does not really support these
![Page 53: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/53.jpg)
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
• S/W Process perspective / S/W Activity based• Tools are classified according to s/w process activities that are
supported
• Integration perspective• Tools are classified according to their organisation into
integrated units
![Page 54: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/54.jpg)
Functional Tool Classification
![Page 55: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/55.jpg)
Activity-Based Tool Classification
![Page 56: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/56.jpg)
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
![Page 57: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/57.jpg)
Tools, Workbenches, Environments
![Page 58: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/58.jpg)
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.
![Page 59: Software Processes. Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline](https://reader035.vdocuments.mx/reader035/viewer/2022062314/56649e615503460f94b5ce6b/html5/thumbnails/59.jpg)
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.