Software process and process models in Software Engineering - Step-by-Step Execution

Concept Flow - Software process and process models

Start: Need for software

↓

Define requirements

↓

Choose process model

↓

Plan and design

↓

Implement code

↓

Test software

↓

Deploy software

↓

Maintain software

↓

End

This flow shows the main stages in a software process, guided by a chosen process model that organizes these steps.

Execution Sample

Software Engineering

1. Requirements gathering
2. Design
3. Implementation
4. Testing
5. Deployment
6. Maintenance

This list shows the typical steps in a software process model.

Analysis Table

Step	Action	Purpose	Output
1	Requirements gathering	Understand what the software must do	Requirements document
2	Design	Plan how to build the software	Design specifications
3	Implementation	Write the actual code	Working software modules
4	Testing	Find and fix errors	Test reports and fixed software
5	Deployment	Make software available to users	Installed software
6	Maintenance	Update and fix software after release	Software updates and patches
7	End	Process complete	Software in use

💡 All steps completed, software is delivered and maintained

State Tracker

Phase	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
Software state	None	Requirements defined	Design ready	Code written	Tested software	Deployed software	Maintained software

Key Insights - 3 Insights

Why do we need different process models instead of just one?

Different projects have different needs; some need flexibility (like Agile), others need strict steps (like Waterfall). The execution_table shows the general steps, but models arrange or repeat these differently.

Is testing done only once after coding?

No, testing can happen multiple times. Some models test after each step or iteration. The execution_table shows testing as a step, but in practice it can be ongoing.

What happens if requirements change during the process?

Process models like Agile allow revisiting requirements and adapting. The flow diagram shows a linear path, but some models loop back to earlier steps.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after Step 3 (Implementation)?

A Requirements document

B Test reports

C Working software modules

D Installed software

💡 Hint

Check the 'Output' column for Step 3 in the execution_table.

At which step does the software become available to users according to the execution_table?

A Step 4 Testing

B Step 5 Deployment

C Step 6 Maintenance

D Step 2 Design

💡 Hint

Look for the step with output 'Installed software' in the execution_table.

If requirements change after Step 2, which process model characteristic helps handle this best?

A Iterative and flexible steps

B Strict linear steps

C No testing

D Skipping deployment

💡 Hint

Refer to key_moments about handling changing requirements.

Concept Snapshot

Software process models organize the steps to build software: requirements, design, implementation, testing, deployment, and maintenance.
Models differ in how they arrange these steps (linear, iterative, incremental).
Choosing the right model helps manage project needs and changes.
Testing and maintenance are ongoing parts of the process.
Understanding these steps helps deliver quality software on time.

Full Transcript

The software process is a set of steps to create software, starting from understanding what is needed, planning, coding, testing, delivering, and maintaining it. Different process models arrange these steps differently to suit project needs. For example, the Waterfall model follows a strict sequence, while Agile allows repeating steps and adapting to changes. The execution table shows the main steps and their outputs, helping visualize how software moves from idea to use. Key moments include understanding why multiple models exist, that testing is not just one step, and how to handle changing requirements. This knowledge helps beginners see how software is built in a clear, step-by-step way.

Practice

1. What is the main purpose of a software process in software engineering?

easy

A. To design the hardware for running software

B. To write the actual code for the software

C. To organize and manage the steps of software development

D. To market the software to customers

Solution

1. Step 1: Understand the role of a software process

   A software process is a set of organized activities that guide how software is developed.

2. Step 2: Identify the main goal of the process

   The main goal is to organize and manage development steps to ensure quality and efficiency.

3. Final Answer:

   To organize and manage the steps of software development -> Option C

4. Quick Check:

   Software process = Organize development steps [OK]

Hint: Software process means managing development steps [OK]

Common Mistakes:

• Confusing process with coding
• Thinking process is about hardware
• Mixing process with marketing

2. Which of the following is a correct characteristic of the Waterfall model?

easy

A. It follows a linear and sequential flow of phases

B. It uses iterative cycles to refine the product

C. It is best suited for projects with changing requirements

D. It allows going back to previous phases easily

Solution

1. Step 1: Recall Waterfall model basics

   The Waterfall model is a traditional software process model with distinct phases done one after another.

2. Step 2: Identify the correct characteristic

   It follows a linear and sequential flow, meaning each phase must finish before the next starts.

3. Final Answer:

   It follows a linear and sequential flow of phases -> Option A

4. Quick Check:

   Waterfall = Linear sequence [OK]

Hint: Waterfall means linear steps, no going back easily [OK]

Common Mistakes:

• Thinking Waterfall is iterative
• Assuming it handles changing requirements well
• Confusing it with Agile

3. Consider this simplified code snippet representing phases in a software process model:

phases = ['Requirements', 'Design', 'Implementation', 'Testing']
for i in range(len(phases)):
    print(phases[i])
    if i == 2:
        print('Review before Testing')

What will be the output?

medium

A. Requirements
Design
Implementation
Testing
Review before Testing

B. Review before Testing
Requirements
Design
Implementation
Testing

C. Requirements
Design
Review before Testing
Implementation
Testing

D. Requirements
Design
Implementation
Review before Testing
Testing

Solution

1. Step 1: Understand the loop and conditions

   The loop prints each phase in order. When index i is 2 (third item), it prints 'Review before Testing' before continuing.

2. Step 2: Trace the output line by line

   Prints 'Requirements', 'Design', 'Implementation', then 'Review before Testing', then 'Testing'.

3. Final Answer:

   Requirements Design Implementation Review before Testing Testing -> Option D

4. Quick Check:

   Print phases in order + review at i=2 [OK]

Hint: Print phases; add review after Implementation (index 2) [OK]

Common Mistakes:

• Printing review after Testing instead of before
• Mixing order of phases
• Misunderstanding loop index

4. A team uses an iterative process model but finds their software keeps breaking after each iteration. What is the most likely cause?

medium

A. They are skipping the design phase entirely

B. They are not testing the software after each iteration

C. They are using the Waterfall model instead

D. They are adding too many features at once

Solution

1. Step 1: Understand iterative model basics

   Iterative models build software in repeated cycles, testing and improving each time.

2. Step 2: Identify why software breaks after iterations

   If testing is skipped after each iteration, bugs accumulate causing breakage.

3. Final Answer:

   They are not testing the software after each iteration -> Option B

4. Quick Check:

   Iterative needs testing each cycle [OK]

Hint: Iterative means test after every cycle [OK]

Common Mistakes:

• Confusing skipping design with testing
• Thinking Waterfall causes iterative breakage
• Assuming feature count is main cause

5. A software team wants to deliver a working product quickly and improve it based on user feedback. Which process model suits this best?

hard

A. Agile model

B. Spiral model

C. Waterfall model

D. V-Model

Solution

1. Step 1: Understand the team's goal

   The team wants fast delivery and continuous improvement from user feedback.

2. Step 2: Match goals to process models

   Agile model focuses on quick releases and adapting based on feedback, unlike Waterfall or V-Model which are more rigid.

3. Final Answer:

   Agile model -> Option A

4. Quick Check:

   Fast delivery + feedback = Agile [OK]

Hint: Agile = quick delivery + user feedback [OK]

Common Mistakes:

• Choosing Waterfall for flexibility
• Confusing Spiral with quick delivery
• Assuming V-Model supports fast changes