# **Verification and Validation (VV)** _(Approval of the Verification and Validation Procedure indicates an understanding of the purpose and content described in this document. By signing this deliverable, each individual agrees on proposed subsystems roles and business logic it is responsible for._ **Document Revision History** | Version | Date | Change Information | Author | Approver | | ------- | ---- | ------------------ | ------ | -------- | | V1.0 | Feb 25, 2026 | Initial Draft | Melisha Dsouza | Pooja Thorat | ### **1. Introduction** Once the planning of the project and the development is done then it comes to the picture- Verification and validation of the implementation. It is the process that ensures quality and required delivery. In the process described we will educate ourselves regarding the Verification and validation process inside Enovate works project-wise. ### **2. Purpose, Goals and Objective** The purpose to implement this process into the project life cycle is to ensure quality delivery. The ultimate goal and objective of the process are to ensure that whatever has been developed satisfies the requirement and meets the quality standards. ### **3. Policies** Requirements shall be maintained in JIRA under issue type- Story. The statuses of the requirement are hence maintained in Jira at all times. - **Ensure Requirements are implemented and recorded** - Project Manager shall take a Requirement review and shall ensure that all requirements are recorded correctly in JIRA by the project Coordinator or BA. - BA along with the project managers needs to ensure that the requirements are marked Done by the developer. - **Perform Validation** - When the requirements are recorded in jira then they shall be assigned to a tester for test case writing. Tester shall provide the test data to the test cases. When the requirements are being validated then the outcome shall not be different from the test data. If the results are not as expected then bugs should be created and linked to the requirement with its assignee. - **Select the set of requirements to be validated along with its method** - Project manager shall provide the set of selected requirements to be validated to the Tester along with the method required and environment in a mail with all stakeholders of the project in cc. The method can be manual, automation, etc with an environment of local, staging or production. - **Provide the Testing environment for verification or Validation** - It should be project Managers' responsibility to keep the environment updated as per needs of the verification and validation. This responsibility can also be designated to senior developers or team lead. - **Keep Updating the procedure** - BA is responsible for updating the procedure as well as the requirements in the form of change requests. The updated procedure shall be shared with all stakeholders via mail. - **Refine Criteria** - BA is responsible to refine criteria of verification and validation and the updated criteria shall be shared with all stakeholders via mail. - **Analyze and share results** - Tester(on client side) is responsible for sharing the status of the validation and verification progress with the team members by sending a status mail to the project manager. The Project manager should ensure that the statuses of development tasks/ client tasks are updated and the tasks submitted for managerial tasks are reviewed in a timely manner. ### **4. Process Flow** ```mermaid flowchart TD A[Requirements Finalized & Locked] --> B[BA / Project Coordinator Enters Requirements in JIRA] B --> C[Project Owner Reviews Requirements] C --> D[Project Plan Completed] D --> E[Create Milestones Sprints in JIRA] E --> F[Assign Requirements to QA for Test Case Writing] D --> G[Project Manager Creates & Assigns Dev Tasks] G --> H[Developers Write Unit Test Cases] H --> I[PM Reviews Unit Test Cases] I --> J[Developers Perform Unit Testing] J --> K[Task Completion by Developer] K --> L[PM Reviews Completed Tasks] L --> M[PM Shares Built Requirements Codes with QA / Client QA] M --> N[Email with Environment & Credentials Shared to Stakeholders] N --> O[QA / Client QA Performs Testing] O --> P[Log Bugs Linked to Test Cases / Requirements] P --> Q[QA Sends Test Summary Mail to Stakeholders] Q --> R[Developers Fix Bugs] R --> L %% Governance R --> S[Update Status of Requirements, Tasks, Test Cases & Bugs] S --> T[Ensure All Items are Properly Linked in JIRA] ``` **The following steps or process needs to be followed for Verification and Validation:** 1. Once the requirements are finalized and locked, the Project Coordinator or Business Analyst is supposed to enter the requirements in JIRA. The recorded requirements should be then reviewed by the Project owner. 2. After the completion of the project plan, the Project coordinator or Business Analyst is supposed to create the required milestones as sprints into JIRA and should assign the requirements to the Quality Analyst to write test cases for them. 3. As per the project plan, the Project manager is supposed to create tasks for developers and should assign them. 4. Developers are then supposed to write their unit test cases for the tasks and should perform them before giving them to the Quality Analyst for testing. The project manager is supposed to review the unit test cases for developers. 5. As the developer finishes their assigned task, the project manager is supposed to review the tasks and provide the findings if required to the developer. 6. Project manager when finished a set or requirements or as per plan, provides the Quality Analyst (On client side)/ Client with the set of Requirements(codes) to be tested. These built requirements should be written down in mail to be tested and shared with all stakeholders, stating the environment they need to be tested on and also the credentials if required. 7. Client’s Quality Analyst performs testing and assigns bugs to the developer linked with the test cases and if there is absence of test cases then to requirements/tasks as per project needs. The summary mail for testing is required by Quality Analyst and shared with all stakeholders at the end of one test cycle. 8. Developers now can fix the bugs and provide for retesting with the same steps to be followed from step 5. 9. At all times the statuses of requirements, test cases, tasks, unit test cases, and bugs should be timely updated with their current status. 10. At all times, requirements, tasks, bugs and test cases (QA and Unit, both) should be linked together. ### **5. Work Product** **The work product of the Enovate for Validation and Verification is,** - Unit test case reports in or from Jira - Traceability matrix in or from jira - Task Traceability matrix in or from jira - VV checklist ### **6. References** | Process Elements | File Name or Reference | |------------------|------------------------| | Documents | Procedure Document <br> Project Charter <br> SRS | | Checklist | VV Checklist | | Plan | Project Plan <br> Release Plan <br> Test Plan | ### **7. Records of Verification And Validation** | Record | Where to Get It? | |----------------------|------------------| | Procedure Document | VV Process Area in GitLab / Team files of the particular project | | Requirements | Recorded in Jira as a Development Task | | Test Plan | PLAN Process Area in GitLab / Team files of the particular project | | Test Cases | Jira | | Unit Test Cases | Jira | | Milestones | Project Charter of PLAN Process Area in GitLab / Team files of the particular project | | Release Plans | PLAN Process Area in Jira / GitLab of the particular project | | Tasks | Jira | | Traceability Reports | Jira | ### **8. Roles and Responsibilities** | Role | Responsibilities | |------|------------------| | Project Owner | • Be clear about project requirements <br> • Verify and check project timelines <br> • Handle the process after client acceptance | | Business Analyst / Project Coordinator | • Maintain thorough knowledge of all requirements <br> • Prepare Project Charter <br> • Communicate and resolve customer-related issues <br> • Record MOM (Minutes of Meeting) <br> • Assist PM in preparing Project Plan <br> • Prepare Release Plan <br> • Review Test Plan <br> • Ensure successful project delivery <br> • Prepare Test Plan | | Quality Analyst | • Prepare Test Plan <br> • Create Test Cases <br> • Provide testing reports when required | | Team Leader | • Understand Project Plan <br> • Prepare Task List <br> • Allocate tasks to resources <br> • Update estimated hours and dates in task allocation and ensure alignment with Project Plan <br> • Support developers in resolving critical technical issues <br> • Ensure delivery within timelines as per Release Plan <br> • Record MOM in Jira <br> • Keep PM informed about required plan changes and team issues | | Project Manager | • Prepare Resource Plan (part of Detailed Project Plan) <br> • Review Design Documents (HLD, LLD, Design Docs, etc.) <br> • Resolve escalated issues from project team <br> • Monitor project progress and update PC/BA/Customer <br> • Periodically seek customer feedback <br> • Record MOM | | Developer | • Understand Project Plan and requirements <br> • Create Unit Test Cases with expected inputs and outputs for assigned tasks <br> • Execute Unit Test Cases and update status regularly | ### **9. Ways of validation and Verification to perform** **Unit Testing** Unit testing is the **testing at the code level** and helps **eliminate issues at an early stage**, mainly the developer is responsible to perform the unit test for his code while not all the defects cannot be discovered at the unit testing. Integration testing is associated with the high-level design phase. Integration testing ensures the integration between all system modules after adding any new functions or updates. **Functional Testing (On client test)** Functional testing is associated with the low-level design phase which ensures that collections of codes and units are working together, probably to execute new functions or services. System testing is associated with the system requirements and design phase. It combines the software, hardware, and the integration of this system with the other external systems. **User Acceptance Testing** User Acceptance testing is associated with the business and operations analysis phase. The customer users are the main performers of this testing based on test cases and scenarios that cover the business requirements to ensure that they have delivered the right software as per the specifications. ### **10. Skills Required** | Role | Skills | |------|--------| | Quality Analyst | • Manual Testing <br> • Automation Script Testing <br> • Jira Tool <br> • Creating and Running Test Cycles <br> • Report Writing for Test Cycles | | Developers | • Unit Testing <br> • Jira Tool | | Project Manager / Team Lead | • Jira Tool <br> • Unit Testing Skills | | Project Coordinator / Project Owner | • Jira Tool <br> • Basic Quality Analysis Knowledge | ### **11. Verification and Validation** - Periodic reviews of the process and work will be done by BA/ Team Manager. - Requirements once added are reviewed by the Project owner as per the project plan created. - The requirements are reviewed by BA or project coordination as per the plan created. - Unit test cases added by developer for the tasks assigned to the developer shall be reviewed by the project managers and the conclusion and Milestone reviews shall take place as per the project plan by the project manager. - Findings for all the reviews shall be maintained in the review report or in jira. Results for the reviews shall be shared with the concerned stakeholder via mails. - All managerial tasks and required information will be maintained in jira. - This provides awareness of and insight into software requirements at an appropriate level of abstraction and in a timely manner. - The time between validation and verification should meet the needs of the organization. ### **12. Measurements** The number of defects received from clients and compared on all releases. ### **13. Entry and Exit Criteria** - **Entry Criteria** - SRS - Design - Project Plan - Milestone delivery plan - **Exit Criteria** - Test Cases - Automation scripts - Traceability matrix ### **14. Acronyms and Abbreviation** | Acronym / Term | Description / Definition | |----------------|--------------------------| | VV | Validation and Verification | | RTM | Requirement Traceability Matrix | | PM | Project Manager | | PL | Project Leader | | PC | Project Coordinator | | BA | Business Analyst | | CM | Configuration Management | | HRM | Human Resource Management | | TC | Test Cases |