The phases and related steps of the generic view of software engineering are complemented by a number of umbrella activities. Typical activities in this category include:
- Software project tracking and control: When plan, tasks, models all have been done then a network of software engineering tasks that will enable to get the job done on time will have to be created.
- Formal technical reviews: This includes reviewing the techniques that has been used in the project.
- Software quality assurance: This is very important to ensure the quality measurement of each part to ensure them.
- Software configuration management: Software configuration management (SCM) is a set of activities designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products.
- Document preparation and production: All the project planning and other activities should be hardly copied and the production get started here.
- Re-usability management: This includes the backing up of each part of the software project they can be corrected or any kind of support can be given to them later to update or upgrade the software at user/time demand.
- Measurement & Metrics: This will include all the measurement of every aspects of the software project.
- Risk management: Risk management is a series of steps that help a software team to understand and manage uncertainty. It’s a really good idea to identify it, assess its probability of occurrence, estimate its impact, and establish a contingency plan that─ ‘should the problem actually occur’.
Read More: What are the types or categories of risks in software engineering? Explain the process of risk management.