V-MODEL METHODOLOGY (Gankesh)Figure 1: (Meenakshi Agarwal n.d.) shows the diagram of the V-Model.ACTIVITIES INVOLVED IN METHODOLOGYV-Model,otherwise known as the verification and validation modelis an extension model ofthe waterfall model. This model is executed in a highly disciplined sequential manner whereeach phase is to be finished before the beginning of the next phase. Furthermore, every singlephase in the development cycle must incorporate an associated testing phase which is plannedin parallel to the development phase. In the V-Model, one side of the V represents theverification phase while the other represents the validation phase hence its’ name, V-Model.V-model is very highly suggested to be used for this project as it is known as StructuredMethodology. Since, it is a Covid-19 season I personally highly recommend all therequirements to be gathered in the early phase itself because it will be hard for us to meet theusers in person after we started developing the system.
Verification PhaseIn this phase, a static analysis technique is done without code execution. Evaluation of theproduct development takes place to ensure it meets the needs of thestakeholders ofStaffAttendancesystem.Validation PhaseIn this phase, a dynamic analysis method is applied while the code is getting executed andthusthesoftwareundergoesvalidationtodeterminewhetheritfulfilsthestakeholder'sexpectation or not.Design Phase1. Requirement Analysis-A process of communicating with the users to record & understand their needs andexpectations of the system (otherwise known as Requirement Collection). Detailedand thorough communication is important and needs to be managed well becausemost users are not decisive on what is needed and wanted.Staff Attendance Systemisan attendance marking system for the staffs. Hence, we are making analysis based ontheinformation and data given out by the stakeholders ofStaff Attendancesystem.2. System Design-The system designed is done with detailing of hardware and communication setup forthe software product in focus. This design is based on all user ofStaff Attendancesystemsatisfaction. We need to able to achieve of the requirements made by all thestakeholders of theapplicationto design a suitable and proper system for them.3. Architectural design-Otherwise known as High Level Design (Agarwal, 2019), a breakdown of the systemdesign is then done in detail, separating the system into modules/sections which hostsdifferent functionalities which in thisStaff Attendanceproject different modules arerequired for each user interface. Data exchange between core modules, internal andexternal subsystems are clarified and noted down.
4. Module Design-Otherwise known as Low Level Design (Agarwal, 2019), the entireStaffAttendanceapplicationis divided into smaller modules where each intended moduleis specified. Compatibility with other modules in the system architecture and otherexternal subsystems areprioritized.