DMTD- Use case specification.docx - V-MODEL...

This preview shows page 1 - 4 out of 8 pages.

V-MODEL METHODOLOGY (Gankesh) Figure 1: (Meenakshi Agarwal n.d.) shows the diagram of the V-Model. ACTIVITIES INVOLVED IN METHODOLOGY V-Model, otherwise known as the verification and validation model is an extension model of the waterfall model. This model is executed in a highly disciplined sequential manner where each phase is to be finished before the beginning of the next phase. Furthermore, every single phase in the development cycle must incorporate an associated testing phase which is planned in parallel to the development phase. In the V-Model, one side of the V represents the verification 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 Structured Methodology. Since, it is a Covid-19 season I personally highly recommend all the requirements to be gathered in the early phase itself because it will be hard for us to meet the users in person after we started developing the system.
Verification Phase In this phase, a static analysis technique is done without code execution. Evaluation of the product development takes place to ensure it meets the needs of the stakeholders of Staff Attendance system. Validation Phase In this phase, a dynamic analysis method is applied while the code is getting executed and thus the software undergoes validation to determine whether it fulfils the stakeholder's expectation or not. Design Phase 1. Requirement Analysis - A process of communicating with the users to record & understand their needs and expectations of the system (otherwise known as Requirement Collection). Detailed and thorough communication is important and needs to be managed well because most users are not decisive on what is needed and wanted. Staff Attendance System is an attendance marking system for the staffs. Hence, we are making analysis based on the information and data given out by the stakeholders of Staff Attendance system. 2. System Design - The system designed is done with detailing of hardware and communication setup for the software product in focus. This design is based on all user of Staff Attendance system satisfaction. We need to able to achieve of the requirements made by all the stakeholders of the application to design a suitable and proper system for them. 3. Architectural design - Otherwise known as High Level Design (Agarwal, 2019), a breakdown of the system design is then done in detail, separating the system into modules/sections which hosts different functionalities which in this Staff Attendance project different modules are required for each user interface. Data exchange between core modules, internal and external subsystems are clarified and noted down.
4. Module Design - Otherwise known as Low Level Design (Agarwal, 2019), the entire Staff Attendance application is divided into smaller modules where each intended module is specified. Compatibility with other modules in the system architecture and other external subsystems are prioritized.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture