College of Computer Engineering & ScienceRequirements Engineering SOEN $3331-201$Course project$-$ Deliverable#$3$Ms$.$ Irum NahviSubmission Date: $27/4/2024$Hadeel Almustaneer$-201601265$Asma Aldakhil $-202001042$Hessa Al Thani $-202001716$Malak Almusallam $-201700434$Alyah Aldaihani $-201900583$Amal Aldossary $-201901402$Appendix$$Appendix A$4-$Show to what extent your goals are covered by your use cases and$/$or scenarios and$/$or requirements, and demonstrate that each of your use cases or scenarios addresses at least one goal.$$To demonstrate how your goals are covered by your use cases and$/$or scenarios and$/$or requirements, you can create a matrix or mapping table. Here's how you might structure it$.$Goal IDGoal DescriptionUse Case$/$Scenario IDUse Case$/$Scenario Descriptionrequirements CoveredG$1$Increase user engagementUC$1$User RegistrationReq$1,$Req$2$G$2$Improve system performanceUC$2$Data ProcessingReq$3,$Req$4$G$3$Enhance data securityUC$3$User AuthenticationReq$5,$Req$6$In this table:"Goal ID$"$ represents a unique identifier for each goal."Goal Description" briefly describes each goal."Use Case$/$Scenario ID$"$ refers to the identifier of the use case or scenario."Use Case$/$Scenario Description" briefly describes the use case or scenario."Requirements Covered" lists the requirements associated with each use case or scenario$\mathrm{.}5.$ Requirements inspection and validation techniques used$$Requirements inspection techniques$$ Checklists:$$We used a checklist to ensure that the document sufficiently covers all relevant topics concerning practical applications of electrical conduction models.$$ Walkthroughs:We organized walkthrough sessions where stakeholders can review the document step$-$by$-$step to identify any gaps, inconsistencies, or ambiguities in the requirements.$$ Risk Analysis:we Conducted a risk assessment to determine the impact of potential flaws or inconsistencies in the document on the practical implementation of electrical conduction models.$$Requirements validation techniques$$ Prototyping:We created a prototype or simulation that demonstrates the practical applications of electrical conduction models in various sectors in order to assess the requirements' feasibility and appropriateness.$$ Model checking:We used model checking tools to ensure that the document's requirements are consistent with the expected outcomes and restrictions in real$-$world circumstances.$$ Use case testing:We created and runs use case tests based on document requirements to ensure that the system responds correctly to specific user actions or inputs.$$Key areas for quality evaluation:$$ Completeness:We checked if all practical applications of electrical conduction models have been appropriately explored.$$ Consistency:$$we checked for uniformity in terms, definitions, and examples across the document.$$ Validity:We ensured that the requirements appropriately reflect the needs and expectations of stakeholders regarding the practical uses of electrical conduction models.$$

Complete and formalaize $5$ use case using any US teamplet relevent to your project scope