This document discusses software process models and activities. It explains that a software process is a set of structured activities used to develop software, including specification, design, implementation, validation, and evolution. Process models provide abstract representations of processes. Process descriptions typically discuss activities, products, roles, and pre- and post-conditions. Plan-driven processes plan all activities in advance, while agile processes use incremental planning and are more flexible to change. Most practical processes incorporate elements of both plan-driven and agile approaches.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
19 views6 pages
2 Software Processes 1
This document discusses software process models and activities. It explains that a software process is a set of structured activities used to develop software, including specification, design, implementation, validation, and evolution. Process models provide abstract representations of processes. Process descriptions typically discuss activities, products, roles, and pre- and post-conditions. Plan-driven processes plan all activities in advance, while agile processes use incremental planning and are more flexible to change. Most practical processes incorporate elements of both plan-driven and agile approaches.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6
Chapter 2 – Software Processes
Lecture 1
Chapter 2 Software Processes 1
Topics covered
Software process models
Process activities Coping with change The Rational Unified Process An example of a modern software process.
Chapter 2 Software Processes 2
The software process
A structured set of activities required to develop a
software system. Many different software processes but all involve: Specification – defining what the system should do; Design and implementation – defining the organization of the system and implementing the system; Validation – checking that it does what the customer wants; Evolution – changing the system in response to changing customer needs. A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective. Chapter 2 Software Processes 3 Software process descriptions
When we describe and discuss processes, we usually
talk about the activities in these processes such as specifying a data model, designing a user interface, etc. and the ordering of these activities. Process descriptions may also include: Products, which are the outcomes of a process activity; Roles, which reflect the responsibilities of the people involved in the process; Pre- and post-conditions, which are statements that are true before and after a process activity has been enacted or a product produced.
Chapter 2 Software Processes 4
Plan-driven and agile processes
Plan-driven processes are processes where all of the
process activities are planned in advance and progress is measured against this plan. In agile processes, planning is incremental and it is easier to change the process to reflect changing customer requirements. In practice, most practical processes include elements of both plan-driven and agile approaches. There are no right or wrong software processes.
Chapter 2 Software Processes 5
Thank you for using PDF Editor 6 Professional.
You can only convert up to 5 pages in the trial version.
To get the full version, please purchase the program here: