A software process is a coherent set of activities for building software. It answers: what do we do first? How do we know when we’re done? What happens when something goes wrong?
Framework Activities
These five activities appear in every methodology — the difference is how many times you repeat them and in what order.
- Communication — talk to stakeholders. Understand the problem before solving it. Requirements gathering, user research, stakeholder interviews.
- Planning — estimate effort, identify risks, define schedule, allocate resources.
- Modeling — create blueprints: architecture diagrams, database schemas, UI wireframes, API contracts. “Measure twice, cut once.”
- Construction — write code + run tests. The execution phase.
- Deployment — ship to production, train users, collect feedback.
Umbrella Activities
These run continuously across the entire project lifecycle, not just in one phase:
| Activity | What it does |
|---|---|
| Project tracking | Monitor progress vs plan, adjust when off-course |
| Risk management | Identify, analyze, and mitigate risks before they become problems |
| Quality assurance | Process audits, standards compliance, peer reviews |
| Technical reviews | Design reviews, code reviews — catch issues before they reach production |
| Measurement | Track metrics: velocity, defect density, code coverage |
| Configuration management | Version control, change tracking, build management |
| Reusability management | Identify and maintain reusable components |
Process Models
A process model is the specific arrangement of these activities:
| Model | Key characteristic |
|---|---|
| Waterfall | Linear, one pass through each activity |
| Agile | Repeated short cycles (sprints), continuous feedback |
| Spiral | Risk-driven, iterative with evaluation after each cycle |
| V-Model | Testing planned in parallel with each development phase |
Q: What’s the difference between a framework activity and an umbrella activity?
A: Framework activities are the main phases of development (communication, planning, modeling, construction, deployment). Umbrella activities run throughout the project — risk management, quality assurance, configuration management apply whether you’re in the planning phase or the testing phase.
Q: Do all projects need all five framework activities?
A: Every project needs all five, but the emphasis varies. A small internal tool might barely need planning or modeling. A safety-critical medical device spends most of its effort on modeling and testing. The presence is universal; the effort distribution is not.
Q: Why is risk management an umbrella activity rather than a phase?
A: Because new risks emerge throughout the project. The risk you identify during planning is different from the risk during deployment. Managing risk is a continuous activity, not a one-time checklist.
Premium Content
Unlock Software Engineering Processes and all premium lessons with a subscription.
From ₹199.99/year — See plans