![]() This section should present underlying theories or necessary background to understand the problem in sufficient detail to appreciate what the tool offers. The Introduction section should explain the relevant context and the specific issue that the software described is intended to address, what the software does to solve it, what competing software already exists, and how this tool is different. Review criteria should include applicability to large-scale assessment, scientific merit, a fully described background, evidence of feasibility and performance, and full reproducibility. comprehensive test files and results) should be provided or made available on a free, open-source repository. Alternatively, for relevant tools, detailed supporting documentation of performance (e.g. All submissions should include examples that are fully reproducible, including data and source code. ![]() ![]() Workflows should be well-documented, ideally with a completely worked example (see the Applications section below). It is important that manuscripts include the necessary background, theory, and relevant concepts to understand the implementation or tool and the importance of the submission. Manuscripts should generally be around 5,000 words and describe implementations of models and methods to analyze large-scale assessment data using software tools. Software articles are intended for software developers and advanced analysts who have developed innovative or useful ways of implementing existing methods. Software articles should describe a tool likely to be of broad utility that represents a significant advance over previously published software (usually demonstrated by direct comparison with available related software).
0 Comments
Leave a Reply. |