Software Quality Measurement Analysis on Academic Information Systems
Bibliographic record
Abstract
Measurement, which can be done directly or indirectly, is the process of providing a quantitative indication of the scope, quantity, dimension, capacity, or characteristics of a process or product.Software may be measured directly in a number of ways, such as cost, effort, amount of code lines, functionality, speed of execution, memory size, documentation, number of inputs and outputs, and flaws in individual units.In contrast, features like functionality, efficiency, dependability, and maintainability are measured by indirect metrics like software quality.A metric is a quantitative measure of the degree of an attribute of an object, system, or process that is produced by the gathering of data for measurement.These metrics need to be gathered and converted into indicators in order to assess the quality of the program.Metrics, or sets of metrics, known as indicators, give management thorough information about a product and aid in process and product control.A system is made up of several interrelated parts that work together to accomplish a certain objective.These systems are broken down into more manageable subsystems that assist the main system.This research seeks to examine how software quality is measured on Marshal Suryadarma Aerospace University's Academic Information System.In addition to helping university administration regulate and enhance the information systems in use, this research is anticipated to offer a thorough grasp of the application of metrics and indicators in assessing and enhancing the caliber of academic software.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.011 | 0.053 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.012 | 0.018 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".