Abstract

The author has previously contributed to work on requirements definitions in digital forensic methods, and identified a potential gap which could not be fully explained at the time (Marshall and Paige, 2018). The former Forensic Science Regulator (FSR), with others, commented on this and challenged the finding (Tully et al., 2020). This paper re-addresses this issue and explores the issue of language used in the various standards from ISO/IEC 17 025 (2017) through to the FSR's own guidance on digital forensic method (Forensic Science Regulator, 2020), comparing it with language used in other related standards and in software engineering standards. From this, the author proposes that the language used by the FSR may cause an over-emphasis on establishing requirements for the ultimate end-user, to the detriment of requirements for purely internal use of processes. This can also result in overly complex methods, which are inherently difficult to fully validate, being produced. Furthermore, the use of overloaded terminology may also lead to confusion about some key concepts in the various stages of method validation and re-validation.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.