Execution Protocol for OOPs through Java Lab
These guidelines outline the mandatory procedures and phases that must be followed for the successful
completion and submission of the assigned project.
- Experiment Allocation and Access:Students are strictly required to access and work only on
the specific experiment allocated to them. This allocation must align precisely with the mapping
information provided in the Student and Experiment Mapping Sheet.
- Adherence to the Software Development Life Cycle (SDLC): All project work must be conducted
sequentially through the established phases of the Software Development Life Cycle (SDLC). Failure
to complete a phase or obtain required approvals will halt progress to the next stage.
- Phase A: Analysis and Design (Gate 1)
A comprehensive Analysis and Design phase must be completed first.
The resulting documentation (e.g., design diagrams, functional specifications) must be presented to
the examiner.
Formal Approval from the examiner is mandatory before proceeding to the implementation stage.
- Phase B: Implementation and Testing:
The Implementation (coding) phase may only begin after formal design approval has been granted.
Upon completion of coding, a thorough Testing phase must be executed.
A prerequisite for the final submission is that all predefined test cases must pass successfully.
- Phase C: Assessment and Conclusion
The functional results and successful test reports must be presented to the examiner for the final Viva Voce assessment.
Upon successful completion of the Viva Voce, the project procedure is officially concluded, and the student may be dismissed from the laboratory.
All sections of the SDLC must be strictly followed and documented. 🤞