An Automated Tool for Streamlining Software Engineering: Information Extraction and Decision
DOI:
https://doi.org/10.25195/ijci.v51i2.550Keywords:
Developer Decision Support, Code analysis, Software assessment, Software quality, Software metricAbstract
In the always-evolving and dynamic field of software development, good decision-making is absolutely critical. Developers have to regularly decide how best to apply features, optimize performance and debug issues. This process could be much improved by extracting actionable insights from software code. The presented work explores the tools and metrics available to enable developers to make data-driven decisions, therefore enhancing the development efficiency as well as code quality. Also, it introduces a new automated tool called CodeLens which analyzes software code, extract lines of code (LOC), documentation quality, complexity, and other key criteria. Through a consolidated view of such metrics, the tool helps developers evaluate code fit, spot possible bottlenecks, and prioritize optimization or refactoring efforts. Furthermore, the tool's support of Java and Python languages guarantees general applicability, hence fitting for many software projects.
Downloads
Downloads
Published
Issue
Section
License
Copyright (c) 2025 Iraqi Journal for Computers and Informatics
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
IJCI applies the Creative Commons Attribution (CC BY) license to articles. The author of the submitted paper for publication by IJCI has the CC BY license. Under this Open Access license, the author gives an agreement to any author to reuse the article in whole or part for any purpose, even for commercial purposes. Anyone may copy, distribute, or reuse the content as long as the author and source are properly cited. This facility helps in re-use and ensures that journal content is available for the needs of research.
If the manuscript contains photos, images, figures, tables, audio files, videos, etc., that the author or the co-authors do not own, IJCI will require the author to provide the journal with proof that the owner of that content has given the author written permission to use it, and the owner has approved that the CC BY license being applied to content. IJCI provides a form that the author can use to ask for permission from the owner. If the author does not have owner permission, IJCI will ask the author to remove that content and/or replace it with other content that the author owns or has such permission to use.
Many authors assume that if they previously published a paper through another publisher, they have the right to reuse that content in their PLOS paper, but that is not necessarily the case – it depends on the license that covers the other paper. The author must ascertain the rights he/she has of a specific license (a license that enables the author to use the content). The author must obtain written permission from the publisher to use the content in the IJCI paper. The author should not include any content in her/his IJCI paper without having the right to use it, and always give proper attribution.
The accompanying submitted data should be stated with licensing policies, the policies should not be more restrictive than CC BY.
IJCI has the right to remove photos, captures, images, figures, tables, illustrations, audio, and video files, from a paper before or after publication, if these contents were included in the author's paper without permission from the owner of the content.
