SOFTWARE MANAGEMENT CHANGE
Change Management in software development refers to the transition from an existing state of
the software product to another improved state of the product. It controls, supports, and manages
changes to artifacts, such as code changes, process changes, or documentation changes. Where
CCP (Change Control Process) mainly identifies, documents, and authorizes changes to a
software application.
Each software development process follows Software Development Life Cycle (SDLC) where
each phase is accordingly followed to finally deliver a good quality software product. Change
Management does not come under any phases of SDLC still it has great importance in the entire
software development process. There are various types of change management tools that are used
for various purposes like to adopt, control, represent and effect the change required. For example
Change management tools for Flow Charting, Project Planning, Data collection, etc.
Process of Change Management:
When any software application/product goes for any changes in an IT environment, it undergoes
a series of sequential processes as follows:
Creating a request for change
Reviewing and assessing a request for change
Planning the change
Testing the change
Creating a change proposal
Implementing changes
Reviewing change performance
Closing the process
Importance of Change Management:
For improving performance
For increasing engagement
For enhancing innovation
For including new technologies
For implementing new requirements
For reducing cost
Source of Change:
There may be multiple reasons involved during the development process for which certain
changes are required to be implemented in the product. These sources are as follows:
Business reorganization
, New Market conditions
New equipment
Fixing any bugs/errors
New customer needs
Performance or reliability improvement
Budgetary or scheduling constraints
Key points to be considered during Change Management :
Reason of change
Result of change
The portion to be changed
Person will change
Risks involved in change
Alternative to change
Resources required for change
Relationship between changes
Types of Software Testing
Software testing can be stated as the process of verifying and validating that software or
application is bug-free, meets the technical requirements as guided by its design and
development, and meets the user requirements effectively and efficiently with handling all the
exceptional and boundary cases.
The process of software testing aims not only at finding faults in the existing software but also at
finding measures to improve the software in terms of efficiency, accuracy, and usability. It
mainly aims at measuring the specification, functionality, and performance of a software
program or application.
Testing is the process of executing a program with the aim of finding errors. To make our
software perform well it should be error-free. If testing is done successfully it will remove all the
errors from the software.
Principles of Testing:-
(i) All the test should meet the customer requirements
(ii) To make our software testing should be performed by a third party
(iii) Exhaustive testing is not possible. As we need the optimal amount of testing based on the
risk assessment of the application.
(iv) All the test to be conducted should be planned before implementing it
(v) It follows the Pareto rule (80/20 rule) which states that 80% of errors come from 20% of
Change Management in software development refers to the transition from an existing state of
the software product to another improved state of the product. It controls, supports, and manages
changes to artifacts, such as code changes, process changes, or documentation changes. Where
CCP (Change Control Process) mainly identifies, documents, and authorizes changes to a
software application.
Each software development process follows Software Development Life Cycle (SDLC) where
each phase is accordingly followed to finally deliver a good quality software product. Change
Management does not come under any phases of SDLC still it has great importance in the entire
software development process. There are various types of change management tools that are used
for various purposes like to adopt, control, represent and effect the change required. For example
Change management tools for Flow Charting, Project Planning, Data collection, etc.
Process of Change Management:
When any software application/product goes for any changes in an IT environment, it undergoes
a series of sequential processes as follows:
Creating a request for change
Reviewing and assessing a request for change
Planning the change
Testing the change
Creating a change proposal
Implementing changes
Reviewing change performance
Closing the process
Importance of Change Management:
For improving performance
For increasing engagement
For enhancing innovation
For including new technologies
For implementing new requirements
For reducing cost
Source of Change:
There may be multiple reasons involved during the development process for which certain
changes are required to be implemented in the product. These sources are as follows:
Business reorganization
, New Market conditions
New equipment
Fixing any bugs/errors
New customer needs
Performance or reliability improvement
Budgetary or scheduling constraints
Key points to be considered during Change Management :
Reason of change
Result of change
The portion to be changed
Person will change
Risks involved in change
Alternative to change
Resources required for change
Relationship between changes
Types of Software Testing
Software testing can be stated as the process of verifying and validating that software or
application is bug-free, meets the technical requirements as guided by its design and
development, and meets the user requirements effectively and efficiently with handling all the
exceptional and boundary cases.
The process of software testing aims not only at finding faults in the existing software but also at
finding measures to improve the software in terms of efficiency, accuracy, and usability. It
mainly aims at measuring the specification, functionality, and performance of a software
program or application.
Testing is the process of executing a program with the aim of finding errors. To make our
software perform well it should be error-free. If testing is done successfully it will remove all the
errors from the software.
Principles of Testing:-
(i) All the test should meet the customer requirements
(ii) To make our software testing should be performed by a third party
(iii) Exhaustive testing is not possible. As we need the optimal amount of testing based on the
risk assessment of the application.
(iv) All the test to be conducted should be planned before implementing it
(v) It follows the Pareto rule (80/20 rule) which states that 80% of errors come from 20% of
