Process Framework Activities
Process Framework Activities
Process Framework Activities
A generic process framework encompasses five activities which are given below
one by one:
1. Communication:
In this activity, heavy communication with customers and other stakeholders,
requirement gathering is done.
2. Planning:
In this activity, we discuss the technical related tasks, work schedule, risks,
required resources etc.
3. Modeling:
Modelling is about building representations of things in the ‘real world’.In
modelling activity, a product’s model is created in order to better
understanding and requirements.
4. Construction:
In software engineering, construction is the application of set of procedures
that are needed to assemble the product. In this activity, we generate the
code and test the product in order to make better product.
5. Deployment:
In this activity, a complete or non-complete products or software are
represented to the customers to evaluate and give feedback. on the basis of
their feedback we modify the products for supply better product.
• Risk management
• Software quality assurance(SQA)
• Software configuration management(SCM)
• Measurement
• Formal technical reviews(FTR)
Umbrella Activities:
Software engineering is a collection of co-related steps. These steps are presented or accessed
in different approaches in different software process models. Umbrella activities are a set of steps
or procedure that the software engineering team follows to maintain the progress, quality, change
and risks of the overall development tasks. These steps of umbrella activities will evolve through
the phases of generic view of software development.
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’.