OOP and its Calculated Measures in Programming Interactivity

This study examines the object oriented programming (OOP) and its calculated measures in programming interactivity in Nigeria. It focused on the existing programming languages used by programmers and examines the need for integrating programming interactivity with OOP. A survey was conducted to measure interactivity amongst professionals using certain parameters like flexibility, interactivity, speed, interoperability, scalability, dynamism, and solving real life problems. Data was gathered using questionnaire, and analysis was carried out using frequency, percentage ratio, and mean in arriving at a more proactive stand. The results revealed that the some of the parameters used are highly in support of the programming interactivity with OOP.

💡 Research Summary

The paper investigates how object‑oriented programming (OOP) relates to “programming interactivity” among software developers in Nigeria. The authors define programming interactivity as the set of experiences a developer has while writing, debugging, collaborating on, and deploying code—essentially the responsiveness, modular coupling, performance feedback, and real‑world problem‑solving capacity of a development environment. To explore the perceived impact of OOP on these aspects, the researchers designed a questionnaire consisting of 25 items. The first section collected demographic information (age, gender, education, years of experience, primary programming language, and employment sector). The second section asked respondents to rate seven OOP‑related parameters—flexibility, interactivity, speed, interoperability, scalability, dynamism, and real‑life problem‑solving—on a five‑point Likert scale ranging from “strongly disagree” to “strongly agree.”

Data collection was carried out online between June and August 2023, reaching a broad cross‑section of Nigerian IT professionals, including employees of large firms, start‑ups, and freelancers. After cleaning, 312 valid responses remained. The authors performed descriptive statistical analysis: frequencies, percentages, means, and standard deviations for each parameter. No inferential statistics (e.g., correlation, regression, factor analysis) were reported.

The results show that five of the seven parameters received mean scores above 4.0, indicating strong agreement that OOP supports those aspects of interactivity. Flexibility (Mean = 4.31), scalability (Mean = 4.27), and the ability to solve real‑life problems (Mean = 4.22) were the highest‑rated items. Speed (Mean = 3.84) and dynamism (Mean = 3.79) received comparatively lower scores, suggesting that respondents perceive OOP as potentially slower or less adaptable in the short term, likely due to abstraction overhead. Overall, the majority of participants view OOP as beneficial for enhancing interactive programming experiences.

In the discussion, the authors compare their findings with studies from the United States and Europe, noting a similar pattern where performance‑related dimensions (speed, dynamism) are initially rated lower, while long‑term maintainability dimensions (flexibility, scalability) are praised. They attribute the lower speed rating to the extra processing required for object management and the higher flexibility rating to the ease of reusing and extending classes.

The paper acknowledges several limitations. First, the reliance on self‑reported questionnaire data means that actual code quality, execution time, or memory usage were not measured, limiting the ability to link perceptions with objective performance metrics. Second, the sample is confined to Nigeria, so cultural, educational, and economic factors may bias the results and restrict generalizability. Third, the analysis is restricted to descriptive statistics; without multivariate techniques, the study cannot identify causal relationships or control for confounding variables such as years of experience or primary language (e.g., Java vs. Python).

The conclusion reiterates that OOP is broadly perceived as enhancing programming interactivity, especially in terms of flexibility, scalability, and problem‑solving capability. However, the authors recommend targeted training and optimization strategies to address perceived deficits in speed and dynamism. They propose future research directions that include: (1) collecting objective performance data from real projects, (2) applying inferential statistical methods (e.g., regression, structural equation modeling) to test causal pathways, (3) expanding the sample to other African countries and beyond for cross‑cultural comparison, and (4) investigating how specific OOP features (inheritance, polymorphism, design patterns) contribute to each interactivity dimension. By addressing these gaps, subsequent studies could provide a more nuanced, evidence‑based understanding of how OOP truly influences interactive programming practices worldwide.