Problem 4: Rule-based methods The goal is to build a rule-based classifier to predict the class label based on these attributes. Here's the dataset: Age Income Education Temperature ID (Continuous) (Ordinal) (Nominal) (Continuous) Outcome 1 28 Medium Bachelor's 75.5 Yes 2 35 High Master's 68.2 No 3 40 Low High School 80.0 Yes 4 25 Medium PhD 72.8 No 5 45 High Bachelor's 78.1 Yes CO 6 30 Medium High School 69.5 No 7 38 Low Master's 77.3 Yes 8 00 22 High PhD 74.9 No 9 33 Medium High School 70.4 No 10 42 Low Bachelor's 76.7 Yes 1. Initial Rule Generation: Generate an initial rule that classifies instances based on a single attribute with the highest information gain or Gini index. 2. Rule Expansion: Expand the rule from question 1 by incorporating another attribute to improve the classification accuracy. 5 3. Handling Continuous Attributes: Propose a method to handle continuous attributes in rule-based classification, especially for attributes like 'Age' and 'Temperature.' 4. Discrete Attribute Rule: Create a rule based on a discrete attribute with more than two categories, like 'Education.' 5. Rule Evaluation: Evaluate the rules generated so far on the training dataset. Identify any instances that are misclassified. 6. Pruning Rules: Discuss the concept of rule pruning and why it might be necessary in rule-based methods. Provide an example of when rule pruning could be beneficial. 7. Handling Missing Values: Discuss how rule-based methods handle instances with missing attribute values and propose a strategy to address missing values in this dataset.

Question part 3: Draw a UML class diagram with all the classes and relationships.   More info:  In this last and final part of the course work you are required to change the definition of the Item_in_Stock class to make it an abstract class and change the getItemCat(), getItemName() and getItemDescription() definitions to make them abstract methods. You are then required to design and implement three classes which are derived from Item_in_Stock class to fully demonstrate the concept of inheritance and polymorphism. Implementation of HP_Laptop class in part II should have given you an idea of inheritance and polymorphism. Three sub classes, one class against each category (Computers, Laptops and Accessories), should contain appropriate constructors, instance variables, setter and getters methods and overridden methods for getItemName(), getItemDescription() and get_Item_details() method. You should be creative and come up with your own ideas of sub-classes.   (please see the photo if…

The technique of packaging an objects attributes into a cohesive unit that can be used as an undivided entity is ____________. a. inheritance b. encapsulation c. polymorphism d. interfacing

Task 4 Develop a class diagram for following description: Develop a class diagram for following description: The telephone agent uses an order registry and customer catalog to obtain access to an order & a customer respectively. The order registry uses an order number as a qualifier to select particular order instance. A customer catalog uses customer name and phone number as a qualifier to select particular customer. The attributes of an order are the order numbers and time when it is placed. The order consists of many items. An item has item_number, a quantity, unit price. It also has reference to catalog item which represents listing. When an order is cancelled or corrmitted, it cancels or commits each of its items first. When an order's total price method is invoked, the order calls the total price method of each of items and returns the sum.

Please written by computer source

Object Oriented Analysis Systems Creating a complete class diagram for the "Housekeeper service system" if given you an overview of the classes, attributes, and associations you would need: 1. *User*   - Attributes: name, password, mobile phone, email   - Methods: updatePassword(), updateMobilePhone() 2. *System Administrator*   - Inherits from User   - Attributes: level Of Access   - Methods: registerWorker(), registerCustomer(), updateServices(), addOffers() 3. *Worker*   - Attributes: age, nationality, specialty, evaluation degree   - Methods: displayAssignedVisits(), submitLeaveOfAbsence() 4. *Customer*   - Inherits from User   - Attributes: nationality ID, addresses   - Methods: selectServices(), chooseVisitTime(), confirmServiceInformation(), makePayment(), getTransactionInformation() 5. *Address*   - Attributes: street name, building number, zip code, city   - Methods: addAddress(), deleteAddress(), updateAddress(), setDefaultAddress() 6. *Payment*   - Attributes: transaction…

Class Employee Employee -Name (string) -ID(integer) -Address(string) -Salary(double) -Nationality(string) -ExtraWHours(int) +>( Name,ID) +void setdata( Address,Salary, ExtraWHours) 1. Regarding to the UML diagram create class Customer 2. Create the constructer Employee that read the Employee Name and ID and set the Nationality to Kuwaiti 3. Use the method setdata that set the remaining class data , this method verify that the number of extra working hours is greater than 5 to set the number to ExtraWHour otherwise set the number 1 + Overtime() to this data member + . get methods 4. create gets methods for all data member 5. calculate Employee overtime in Overtime method this method return double value after calculating the overtime by using the following formula Overtime = (Salary * 0.25)* ExtraWHours Test File 1. declare the object Employee1 with Name Fahad and id 7788 2. Ask the user to enter object data (Address, Salary, ExtraWHours) for the Employee1l objects 3. Set the data for…

Map the following UML class diagram to code. You only need to construct both classes and realize the many-to-many association relationship. No methods implementation is required Student Course

The degree of interaction within a module is referred to as: O Cohesion O Association O Aggregation O Coupling Which of the following is not a type of association relationship in class diagrams: O Aggregation O A uni-directional association O Inheritance O A bi-directional association O Composition

draw the UML diagram