Team members: Mohammad Al-Subaie Ahmed Al-Saleh Faisal Al-Eshiwy Mohammad Al-Dulaijan Ali Al-Nuami

Outline About jUCMNav System. Phase 1: Test Plan. Phase 2: Generating Test cases (Junit). Phase 3: Input Space Partitioning.

About jUCMNav System jUCMNav is a free, Eclipse-based graphical editor and an analysis and transformation tool for the User Requirements Notation (URN). URN is intended for the elicitation, analysis, specification, and validation of requirements. URN combines two complementary views: one for goals provided by the Goal-oriented Requirement Language (GRL) and one for scenarios provided by the Use Case Map (UCM) notation.

Phase 1: Test Plan Roles of each team member: MemberRole Ahmed Al-SalehResponsible for Inspection (PM) Mohammad Al-DulaijanResponsible for Inspection Mohammad Al-SubaieResponsible for Test Plan Faisal Al-EshiwyResponsible for Test Plan Ali Al-NuamiResponsible for Test Scheduling

Phase 1: Test Plan In this phase we developed the test plan document, containing : Software Project Introduction: This section describes project overview and deliverables. Software Overview: This section provide the software size information jUCMNav contains 1737 Classes & LOC

Phase 1: Test Plan Software Inspection After performing software inspection on 151 classes we found the following results: Total number of defects is 334 defects. No. of Defects per class is 2.2 defects. No. of Defects per type is 11.3 defects. Test Plan In this section, 33 TCs were created without looking on the internal design of the system.

Phase 2: Generating Test cases (Junit) Roles of each team member: MemberRole Ahmed Al-SalehWorked on Generating TCs Mohammad Al-DulaijanWorked on Generating TCs Mohammad Al-SubaieWorked on Generating TCs Faisal Al-EshiwyWorked on Generating TCs (PM) Ali Al-NuamiWorked on Generating TCs

In this phase we generated test cases using Junit. Configuration Details UCM\Scenario package was chosen to apply Junit test on it. UCM\Scenario package contains 9 major classes. Coverage Level Total number of TCs generated is approx. 68 TCs. The coverage level were 49% of the package. Phase 2: Generating Test cases (Junit)

Phase 3: Input Space Partitioning Roles of each team member: MemberRole Ahmed Al-SalehWorked on partitioning system inputs Mohammad Al-DulaijanWorked on partitioning system inputs Mohammad Al-SubaieWorked on partitioning system inputs (PM) Faisal Al-EshiwyWorked on partitioning system inputs Ali Al-NuamiWorked on partitioning system inputs

In this phase we conducted Input Space Partitioning for UCM\Scenario package. Input Space Partitioning Based Testing. We used interface-based input space partitioning. For the coverage, we used All Combination Coverage (ACoC) Each Choice Coverage (ECC). We created 196 Combination for the methods tested in Phase 2. Phase 3: Input Space Partitioning

Thank You Very Much