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.