4.1 Phase 1: Exploratory Analysis
In this section, we discussed insights gained from the analysis of the demographic information vis-a-vis their expectation from autoML or general ML experience. Three key factors emerged prominently from this exploratory analysis, which are discussed as follows:
4.1.1 Learning Curve
One notable observation was that individuals with previous programming experience found it comparatively easier to learn machine learning. On the other hand, participants without prior programming experience faced difficulties in grasping machine learning concepts. Figure 4 illustrates the results, indicating that the introduction of AutoML could potentially alleviate the learning curve associated with machine learning. Out of the participants, 27 individuals (77.1%) agreed that AutoML could facilitate the learning process, while 8 participants (22.9%) expressed disagreement. This highlights the high expectations placed on AutoML in terms of its usability by the respondents.
4.1.2 Apathy Issues
AutoML, which aims to address the AI skills gap, has encountered a lack of enthusiasm among university students in Nigeria, especially those attending universities in the Southwestern region. Our study uncovered a low level of experience in AutoML among the respondents, largely due to a lack of awareness. Figure 5 highlights this issue, with 60% of the participants indicating that they are hearing about AutoML for the first time.
4.1.3 Expectation from AutoML
We conducted further analysis on participants who had no prior experience in using AutoML. We wanted to understand their willingness to use AutoML if given access or exposure, as well as their expectations and design suggestions for the platform. The results, shown in Figure 6, indicate that 92.9% of the participants have positive expectations from using an AutoML tool to enhance their performance in machine learning projects. This high positive response rate can be attributed to the potential for increased productivity and reduced reliance on human intervention in machine learning projects, as highlighted by [22].
When asked about design suggestions, the participants emphasized the importance of simplicity and ease of understanding and interpreting results. They suggested considering the assessment quality of unsupervised learning results and incorporating an interface for data uploading. Additionally, they highlighted the need for the output of trained data to be presented in a way that even machine learning newbies can comprehend without extensive assistance from ML professionals. Furthermore, an analysis of the participants' programming language preferences revealed that 76.32% of them started their programming journey with Python. Based on this, we recommend that AutoML platforms be designed in a way that can generate Python code. This would enable newbies to view and learn from the underlying code behind their AutoML projects, further enhancing their understanding and learning experience.
4.2 Phase 2: Exploratory Analysis
In this phase, we focused on participants who had prior experience with AutoML to gather insights into their usability experience. For those who did not have experience with AutoML, we organized a 3-day workshop dedicated to AutoML. The results and findings from that workshop will be published in a future article. In this section, we will discuss the insights gained from analyzing the demographic information in relation to the usability experience of those participants who had prior experience with AutoML.
4.2.1 Gender Issues in Adoption of autoML
Our study revealed a significant gender disparity among the respondents, with males accounting for 87.5% and females comprising only 12.5%. Despite the distribution and administration of questionnaires to both genders, this outcome reflects a consistent trend of low technology adoption by females, which aligns with concerns raised by [23]. The underrepresentation of females in automated environments, where they make up less than 11%, puts them at a higher risk of job loss due to automation. Therefore, it is crucial for developers and usability testers to prioritize gender-friendly and inclusive programming environments that cater to individuals from diverse backgrounds. Considering gender diversity in the design and development of AutoML platforms, as emphasized by [24], becomes highly imperative in addressing this disparity.
4.2.2 Rigidity
Our findings also revealed that a significant number of respondents who identified themselves as programming experts do not utilize AutoML. Instead, they prefer the traditional approach of running and evaluating their machine learning models. This sentiment aligns with concerns raised by Naik (2022), who highlights that experts perceive AutoML as too restrictive, as it only handles a small portion of the end-to-end process. According to Naik, the most impactful task in machine learning, which is feature engineering, is domain-specific and cannot be fully automated. Consequently, AutoML is seen as a job generator that facilitates the execution of a series of experiments based on a predefined framework.
4.3 Usability Issues of AutoML
Usability is a measure of how well a specific user (Newbie, ML expert, ML enthusiast or Domain expert) can use a product or design (in this case, AutoML) to achieve a defined goal effectively, efficiently, and satisfactorily (reference). This section was targeted at users who have autoML experience. Some common autoML platforms used are BigML and, Rapid Miner. A total of 16 participants with autoML experience took part in this section. Figure 7 shows a distribution of the years of experience of using autoML.
Usability scale [20] and ISO Usability [21] metrics were adopted to evaluate usability issues on autoML. A 5-likert scale was used for this measure. Details uncovered are discussed as follows:
4.3.1 Ease of Use and Usage Frequency
Figure 8 provides insights into participants' perceptions of the ease of use and frequency of usage of AutoML. Regarding ease of use, 23.07% of participants strongly agreed that AutoML is easy to use, 53.8% agreed, 15.4% were neutral, and 7.8% strongly disagreed. In terms of frequency of usage, 25% of users strongly agreed that they like to use AutoML frequently, 37.5% agreed, 31.25% were neutral, and 6.25% strongly disagreed. Interestingly, we observed a similar distribution on the extreme ends of the scale for both ease of use and usage frequency, but some differences in the middle range. This indicates that while ease of use is important, it does not necessarily guarantee that users will always prefer to use the system frequently. Upon further investigation, these differences in frequency and ease of usage could be attributed to factors such as limited feature engineering modules and use cases, as well as limitations in the explainability and interpretability of AutoML. Furthermore, an analysis of the participants' programming language preferences revealed that 76.32% of them started their programming journey with Python. Based on this, we recommend that AutoML platforms be designed in a way that can generate Python code. This would enable newbies to view and learn from the underlying code behind their AutoML projects, further enhancing their understanding and learning experience.
4.3.2 Technical Support
Figure 9 displays the participants' responses regarding their need for technical support and the requirement to learn a lot to use AutoML effectively. The results indicate that 12.5% strongly disagreed, 31.25% disagreed, 37.5% were neutral, and 18.75% agreed with the need for technical support. Similarly, 18.75% strongly disagreed, 25% disagreed, 37.5% were neutral, and 18.75% agreed with the requirement to learn a lot before using AutoML. Interestingly, the ratio of participants who agreed and those who were neutral is the same for both the need for technical support and the need to learn a lot. This suggests that some existing AutoML platforms still require users to have a certain level of technical knowledge to operate effectively. This finding contradicts the original purpose of AutoML, which aimed to simplify the process. Therefore, further research at the intersection of AI and HCI is needed to address this technicality and make AutoML more user-friendly. These findings align with the results of [25], which revealed that many current AutoML systems still rely heavily on human intervention.
4.3.3 Confidence
According to Sakpere (2019), confidence is key to continuation of a task or engaging a new environment/learning paradigm. As a result, in this research we sought to understand the confidence level of users in using autoML. 18.75% strongly agreed to a high level of confidence using autoML, 62.5% agreed, 12.5% were indifferent and 6.25% disagreed.
4.3.4 User Experience
From the responses gathered, users' experiences with AutoML can be summarized as follows:
- Easy understanding of machine learning concepts without coding: Users found that AutoML provided a simplified approach to grasp the fundamental concepts of machine learning without the need for extensive coding knowledge.
- Elimination of complexity in machine learning project workflow: Users appreciated how AutoML streamlined the workflow associated with machine learning projects, removing the complexities and making the process more accessible and manageable.
- Development of models in a short time with minimal effort: Users expressed satisfaction with the efficiency of AutoML, as it allowed them to develop models within a short timeframe and with reduced effort compared to traditional approaches.
Flexibility in using different learning algorithms: Users found it intriguing that AutoML offered the flexibility to experiment with various learning algorithms without requiring significant changes to the underlying code structure. This flexibility enhanced their ability to explore different approaches and optimize their models.
Overall, users had positive experiences with AutoML, highlighting its ability to simplify the understanding of machine learning concepts, streamline project workflows, and provide efficient model development with flexibility in algorithm selection.
4.4 Learning via AutoML
The findings as from the survey regarding participants' opinions on AutoML and its role in learning machine learning which is summarized in table 1 is explained as follows:
- General perception of AutoML for learning ML: 12% of the participants strongly agreed that autoML is an ideal tool for learning ML, while 37.5% agreed, 18.75% were neutral, 12% disagreed, and 18.75% strongly disagreed. This indicates a mixed opinion among users regarding the suitability of autoML for learning ML.
- Comparison of autoML with Python for learning ML: When specifically comparing autoML to Python, 18.75% of participants strongly agreed that autoML is easier to use for learning ML, 43.75% agreed, 6.25% were neutral, 12.5% disagreed, and 18.75% strongly disagreed. These results suggest that while some participants find autoML more user-friendly than Python, there are still others who prefer traditional programming languages like Python for learning ML.
- Combination of autoML with a programming language for learning ML: Regarding the combination of autoML with a programming language for learning ML, 37.5% of participants strongly agreed that autoML is best used in conjunction with a programming language, another 37.5% agreed, 12.5% were neutral, 6.25% disagreed, and 6.25% strongly disagreed. This indicates that many participants recognize the value of combining autoML with a programming language to enhance their learning experience.
- AutoML suitability for newbie: With respect to recommendation of autoML for newbies to learn machine learning, 6.25% of participant strongly agreed that autoML is suitable for newbies to learn machine learning, 43.75% agreed, 6.25% were neutral, 31.25% disagreed, and 12.5% strongly disagreed. This implies that many participants do not perceive autoML has a platform for newbies to learn the intricacies of machine learning coding.
- AutoML application domain suitability: We further investigated if autoML is either suitable for business or educational purposespurpose. 18.75% strongly agreed autoML is suitable for business purposes and not educational purposespruposes, another 43.75% agreed, 18.75% are indifferent, 12.5% disagree and 6.25% agree.
Table 1: Research Questions on the contribution of AutoML to Learning ML
Insight Questions
|
Strongly Agree ( %)
|
Agree
( %)
|
Neutral
( %)
|
Disagree
( %)
|
Strongly Disagree ( %)
|
Is AutoML ideal for Learning?
|
12
|
37.5
|
18.75
|
12
|
18.75
|
Is AutoML better than Python?
|
18.75
|
43.75
|
6.25
|
12.5
|
18.75
|
Should AutoML be combined with other Programming Language?
|
37.5
|
37.5
|
12.5
|
6.25
|
6.25
|
I will encourage a newbie to use autoML for learning machine learning techniques
|
6.25
|
43.75
|
6.25
|
31.25
|
12.5
|
AutoML is best suitable for developing business solutions and not necessarily for educational/learning purposes
|
18.75
|
43.75
|
18.75
|
12.5
|
6.25
|
4.5 Evaluation of Computational Capabilities of Cloud-Based/autoML Tools Compared to Generic ML Tools
The evaluation of the computational capabilities of cloud-based/autoML tools compared to generic ML tools can be summarized as follows:
- Training Time on cloud-based Tools is faster
Out of 16 respondents, 31.3% of them agreed while 43.8% strongly agreed that the training time on cloud-based tools is faster. But 12.5% of them disagreed and another 12.5% were indifferent/neutral. This is summarized on table 2
- Reproducibility is Better Using Cloud-based Tools
In the result of 16 responses, 13 participants (81.3%) agreed that reproducibility, which is the ability to replicate an ML operation carried out and getting the same results as the original work, is better using cloud-based tools, 2 participants (12.4%) strongly agreed, nobody disagreed, while 1 person was indifferent.
Table 2: Users’ Perception on Cloud-Based ML Tools as compared to Traditional ML Tools
Evaluation Metrics
|
Fast (%)
|
Faster (%)
|
Slow (%)
|
Indifferent (%)
|
Training Time
|
31.30
|
43.80
|
12.50
|
12.50
|
Reproducibility
|
81.30
|
12.50
|
0.00
|
6.30
|
- Classification Algorithm Performs Better
Out of 16 responses who use classification algorithms on autoML, 6 participants (37.5%) agreed that classification algorithm in autoML performs better, which is the ability to correctly classify an object, 3 participants (18.8%) strongly agreed, 3 people disagreed, while 4 people were indifferent as shown in table 3.
Table 3: Users’ Perception on Speed of Cloud-Based ML Tools as compared to Traditional ML Tools
Evaluation Metrics
|
Fast (%)
|
Faster (%)
|
Slow (%)
|
Slower (%)
|
Indifferent (%)
|
Classification Performance
|
37.50
|
18.80
|
18.80
|
-
|
25.00
|
Confidentiality (Security)
|
37.50
|
18.80
|
31.30
|
-
|
12.50
|
Tuning & Optimization
|
18.80
|
6.30
|
25.00
|
25.00
|
25.00
|
- Confidentiality (Security)
A recent research has expressed privacy concerns about the use of autoML (Sun et. al., 2020). These privacy concerns vary from leakage of training data to inference attack. As a result, in this research we sought to understand user’s experience and confidence with respect to their view of autoML's ability to ensure confidentiality of training data compared to other traditional platforms or approaches. Out of 16 responses, 6 participants agreed confidentiality of training data on autoML is better, 3 strongly agreed, 2 are indifferent and 5 disagree.
- Hyperparameter Tuning and Optimization
In machine learning, hyperparameter tuning or optimization is needed to choose a set of optimal parameters for a learning algorithm. This process has often been regarded as tedious and the traditional brute force approach has not been efficient (Sandha et. Al., 2020). It's believed that autoML is useful in finding optimal hyperparameters. As a result, during the usability study, we sought to understand users' experience with respect to using autoML for finding an optimal hyper parameter especially when compared to traditional approach. 1 participant strongly agreed that the use of autoML performs better for finding optimal parameters, 3 people agreed, 4 were indifferent, 4 disagreed and 4 strongly disagreed.
4.6 Design Recommendations
After identifying usability issues in autoML, we proceeded to involve participants in providing suggestions for enhancing the design of autoML and the factors that should be considered during its development.
4.6.1. Enhancing Usability and Acceptance of AutoML: Design Insights
The insights gathered from participants regarding design suggestions to enhance the usability and widespread acceptance of AutoML can be grouped into the following key themes:
User Interface and Ease of Use
Participant 26 emphasizes the need for a user-friendly interface that simplifies the upload of data and the presentation of trained data. The aim is to enable individuals new to machine learning to comprehend and interpret training outcomes independently, without relying on professional assistance.
Participant 19 provides a comprehensive list of recommendations: Ensuring explainability and interpretability of the system, crafting a user-friendly interface, offering robust documentation, allowing customization, ensuring flexibility, and prioritizing privacy and security considerations.
Enhancements and Technical Adjustments
One participant, represented by Participant 31, suggests adopting a Python-based platform with necessary plugins. The ease of library installation should be clearly communicated, as challenging installations of machine learning libraries could discourage users.
A call for more advanced feature engineering modules is made by Participant 3. They highlight that existing AutoML solutions often lack comprehensive feature engineering capabilities, which are crucial for optimizing the performance of machine learning models. Additionally, Participant 13 emphasizes the importance of improving explainability and interpretability features within AutoML systems, underscoring the need for transparent model outcomes.
Accessibility and Scope
Participant 14 underscores the significance of evaluating the quality of unsupervised learning results, particularly in the absence of a benchmark for comparison. Participant 20 reflects on the limited range of use cases for AutoML due to the dynamic nature of the problems addressed in everyday scenarios.
These insights offer valuable guidance for refining the design of AutoML, enhancing its usability, and expanding its applicability across diverse contexts.
4.6.2 Considerations in AutoML Design
Participants further pointed out factors to be considered in autoML design. These are:
Handling Diverse Data Types
"Taking into account the prevalence of common data types, AutoML should also cater to complex data types to ensure versatility in its applications."
"Prioritize ease of use, comprehensive documentation, and well-commented program codes to enhance the user experience."
Synergy between HCI and AI Methodologies
The feedback or comments given is as follows:
Participant ID
|
Comments
|
P31
|
Implementing a robust user interface and an interactive platform is pivotal in elevating the user experience
|
P26
|
Promote clear comprehension and meaningful interpretation of trained data by focusing on intuitive design
|
P21
|
Center the design around optimizing the user experience.
|
P22
|
Yes, particularly for individuals less familiar with coding. This AutoML could significantly assist them in harnessing its capabilities
|
Unknown
|
Absolutely, considering the ongoing shift towards AI and data science in the realm of computing. Aligning HCI practices with this trend can result in an enhanced platform that instills confidence.
|
4.7 Limitation and Future Work
Our participants are basically Africans with the majority being male. We also have a larger percentage of the participants to be Machine Learning enthusiasts with intermediate level of programming. Also, our research did not indicate whether the participants are active users of AutoML or non-active users. Soon, we hope to take this work further by engaging frequent users of various AutoML environments to ascertain the level of satisfaction using such platforms and identify areas of concern.