Verification cases and procedure for IP-core development

The main objective is to perform the module level testing of requirement (MLITP) given and verify the completeness, compliance and correctness of the implemented functionality with reference to the Hardware Design Data (HDD) requirements followed by functional required document(FRD) mapped to hardware required document (HRD) . Basically, this paper tells about for any module under functionality testing to perform as per the requirement, some mapping to be follow as per DO-254 which includes the safety analysis as priority and traceability requirement plays a vital activity to complete the functionality testing under test cases scenarios. Regardless of whether the design and verification tools can demonstrate that a plan is practically right under all conditions that were considered, design errors in the hardware can even now happen because of conditions beyond the scope of the design tools. The most ideal approach to maintain a strategic distance from these mistakes is to have an accomplished design and verification staff with the learning of the device confinements. This will enable the group to distinguish potential issues while still in the design phase and permit error mitigation techniques to be incorporated