3A) Software component cataloguing software: The software component cataloguing software consists 4M of a software component catalogue and various functions defined on these components catalogue. The software components catalogue should hold details of the components which are potentially reusable. The reusable components can be either design or code. The design might have been constructed using different design notations such as UML, ERD, structured design, etc. Similarly, the code might have been written using different programming languages. A cataloguer may enter components in the catalogue, may delete the components from the catalogue, and may associate reuse information with a catalogue component in the form of a set of key words. A user of the catalogue may query about the availability of a component using certain key words to describe the component. In order to help manage the component catalogue (1.e., periodically purge the unused components) the cataloguing software should maintain information such as how many times a CSE 3154 component has been used, and how many times the component has come up in a query but not used. Since the number of components usually tend to be very high, it is desirable to be able to classify the different types of components hierarchically. A user should be able to browse the components in each category. Give optimized Decision Tree and Decision Table for the problem, with proper actions and conditions interpretation