---
Video Title: Maintenance Activities
Description: Maintenance Activities
Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm
Lecture By: Mr. Arnab Chakraborty, Tutorials Point India Private Limited
---

Maintenance activities.

IEEE, they have provided one framework for
this maintenance activities.

We are going to discuss
that one and that very

maintenance
activity has got multiple different phases.

So, let us go through that.

So, IEEE provides a framework for
sequential maintenance process activities.

And it can be used to in the iterative
manner and can be extended.

So, that the customized items and the
processes can also get included.

So, this is
the respective maintenance activities

and it has
got multiple different phases are there.

So, identification and tracing.

Next one is our analysis, then design,
implementation, system testing,

acceptance testing and then delivery.

And we shall be having next maintenance
management.

So, these are the different phases are
there.

So, let us discuss one by one.

So, at first we are starting with this
identification and tracing.

So, it involves activities pertaining to
identification

of the requirement
of the modification or maintenance.

So, it is generated
by the user data.

So, here the maintenance type is
classified also.

So, in this particular case, in case of
identification and tracing, this

particular request will be generated by
the users and that will be verified by the

respective error logs and the error
report.

And in this particular
phase, this particular

maintenance type will be also categorized
or classified.

Next one is our analysis.

The modification is analyzed for its
impact on the system.

So, if we carry out
the respective maintenance

required, then
what will be the impact on the system?

Including safety and the security
implications.

So, if portable impact
is severe and then in that

case,
alternative solution will be looked for.

And if you find that, if you carry out the
straight maintenance activity on this

particular system, but the effect will be
severe, then in that case we should look

for some alternative also.

Then a set of required
modifications is then

materialized into
requirement specifications.

Now, you see this particular maintenance
requirement will be generated and

requirement specifications will be also
mentioned.

The cost of modification maintenance is
analyzed and estimation is concluded.

Estimation means the cost estimation will
be concluded.

So, that will be done in the analysis
phase.

So, next one is our design phase.

So, new modules which need to be replaced
or modified are designed against recommend

specifications.

So, set in
the previous stage and test cases are

created for validation
and also for verification.

So, here in this case in this particular
design phase, the verification and also

the validation
will be done against the recommend

specification set which
we got on the in the previous stage.

Next one we are going for the
implementation.

So, the new modules
are coded with the help of

structured
design and created in the design step.

So, now we are going
for the coding for the

actual implementation
of the maintenance process.

So, the new modules are coded with With
help of the structure design created in

the design step and every programmer is
expected to do unit testing in parallel.

So, unit testing means that very
module which will be generated

or the set of modules which are going
to be generated.

Each and every module, each and every unit
will be tested individually, giving

certain set of inputs,
outputs will be obtained

and that will
be matched with the expected output.

So, in this way, the unit testing will be
Next, we are going for the system testing.

So, integration testing is done among
newly created modules.

So, now integration testing is also carried
out between new modules and the system.

So, this new modules will get integrated
with the system.

So, whether this integration is working
fine or not, whether this pre-existing

modules and this new module which has been
developed for this maintenance purpose,

whether the communications are done
properly, whether Whether they are getting

integration, integrated properly or not
that will be tested here.

So, finally, the system
is tested as a whole

following the regression
testing procedure.

So, you know that in case of regression
testing, but having some existing system

and where for the maintenance process,
we used to include some new code,

new module there and the regression
testing will be checking whether this new

module introduction is leaving some bad
effect on the system or not.

Next one, we are going for the acceptance
testing.

So, after testing the
system internally, it is

tested for
acceptance with the help of the users.

And if at this particular state,
the user complaints some issues they are

addressed or noted to address in the next
iteration of the framework.

Next one is the delivery.

After acceptance test, the system is
deployed all over the organization either

by small update package or fresh
installation of the system.

And the final
testing takes place at the client end after

the software is
delivered to them after the installation.

So, training facility is provided if
required in addition to the hard copy of

the respective user manual.

So, these are the different phases we are
having and the last phase whatever you are

having that is the maintenance management.

So, configuration management is an
essential part of system maintenance.

So, it is added
with the version control tool to control

the versions and semi
versions or the patch management.

So, in this way the maintenance management
will be there.

We know that each and every case the
version is having two parts.

One is the major version, major part and
the one is the minor part.

So, this version controlling.

So in this way, we have discussed what are
the different maintenance activities and

what is that very framework which was
proposed by IEEE.

Thanks for watching this video.