Verifying Software Change Requirements Through Conceptual Class Diagrams Comparison
An existing software system sometimes needs to be redesigned to accommodate various change requirements. A system analyst gathers new user requirements to analyze software requirements and create a conceptual model of the new version of the system. While certain requirements of the existing software system should remain in the new version of the system, some of them may be dropped and some new requirements are to be added. Since incomplete software requirements will lead to incorrect design of the new system, the system analyst needs to verify that the gathered requirements for the new system are complete, i.e. those that should be retained in the new system are not missing and those that are changed or newly introduced are included.