From my perspective, if in order to accomplish your work, you need consult or active collaboration with a computer scientist and otherwise could not develop/test your theory or conduct your experiment, then they almost certainly should be cited as an author/collaborator.
If you utilize something OTS outside the project that just works for you and don't need a computer scientist, then whatever entity created that OTS IP isn't really an author/collaborator, but it's likely their work should be cited/referenced if it's part of the critical methodology (as part of disclosure and repeatability).
If your project used Microsoft Word to write up a report, it's not important to the underlying science you conducted. You could have substituted it with TeX, other Word processors, or pen/paper and it wouldn't change the outcome of the underlying theory/experiment you developed. If you used an Ansys package to perform analysis for some purpose, you should probably mention that out of rigor but Ansys isn't an author or collaborator.
If on the other hand you need someone to architect a solution to handle processing your massive dataset, needed someone to write custom code because nothing could do what you needed, needed a new algorithm because you had no clue how to approach the problem, or even needed someone to modify source code significantly to something that existed but couldn't do what you needed, then they are certainly an author/collaborator. If you took existing code/algorithm and made it more efficient in order to accomplish a task that would have taken too long otherwise, you're a contributor/collaborator and should be listed as an author.
This has been a huge issue in academic research but it's been getting a bit better and researchers are starting even more to acknowledge/credit computing professionals as crucial contributors and authors, as they rightfully should be.
From my perspective, if in order to accomplish your work, you need consult or active collaboration with a computer scientist and otherwise could not develop/test your theory or conduct your experiment, then they almost certainly should be cited as an author/collaborator.
If you utilize something OTS outside the project that just works for you and don't need a computer scientist, then whatever entity created that OTS IP isn't really an author/collaborator, but it's likely their work should be cited/referenced if it's part of the critical methodology (as part of disclosure and repeatability).
If your project used Microsoft Word to write up a report, it's not important to the underlying science you conducted. You could have substituted it with TeX, other Word processors, or pen/paper and it wouldn't change the outcome of the underlying theory/experiment you developed. If you used an Ansys package to perform analysis for some purpose, you should probably mention that out of rigor but Ansys isn't an author or collaborator.
If on the other hand you need someone to architect a solution to handle processing your massive dataset, needed someone to write custom code because nothing could do what you needed, needed a new algorithm because you had no clue how to approach the problem, or even needed someone to modify source code significantly to something that existed but couldn't do what you needed, then they are certainly an author/collaborator. If you took existing code/algorithm and made it more efficient in order to accomplish a task that would have taken too long otherwise, you're a contributor/collaborator and should be listed as an author.
This has been a huge issue in academic research but it's been getting a bit better and researchers are starting even more to acknowledge/credit computing professionals as crucial contributors and authors, as they rightfully should be.