✨ Fisheries Software Requirements
15 SEPTEMBER 2010 NEW ZEALAND GAZETTE, No. 119 3181
provided by FishServe (even if the application has warned the Authorised User that the data has a potential error).
(l) Allow an authorised user to print a copy of a form.
(m) Ensure that a Catch Effort Form with status "COPY" cannot be edited.
(n) Ensure that a Catch Effort Form with status "EXPORTED" cannot be edited.
(o) Ensure that a Catch Effort Form with status "ACCEPTED" cannot be edited and resubmitted.
(p) Allow an authorised user to view reference data stored by the API.
(q) Allow an authorised user to view explanatory notes stored by the API.
(r) Allow an authorised user to view maps stored by the API.
(s) Be able to initiate the transfer of the content of a Catch Effort Form completely and accurately from the API to the CE EDT System.
(t) Display receipt by the API of an electronic acknowledgement from FishServe.
(u) Display any error messages generated by the API.
- Off-line Tests—All off-line tests must be completed and passed before any on-line testing is performed. Off-line tests shall be carried out by answering all the questions presented in appendix 1. Each question shall be considered a complete test on its own. Answers shall be obtained by thorough examination of the software and any documentation supplied.
Unless otherwise stated, all questions relate to mandatory requirements and must therefore be passed for compliance. A question shall be passed if its answer is the same as the correct answer indicated on the question form in appendix 1.
(a) Creation of a form – The software under test must enable an Authorised User to create each new Catch Effort Form with a unique CE Form Number.
(b) Data entry – The software under test must enable an Authorised User to enter such data as is required on a Catch Effort Form and successfully save this data.
(c) View form data – The software under test must enable the data on a previously saved and/or endorsed form to be viewed.
(d) View form event history – The software under test must allow an Authorised User to view the event history of a form.
(e) View explanatory notes – The software under test must allow the viewing of any explanatory notes.
(f) View reference data – The software under test must allow an Authorised User to determine what codes are valid options for a given field.
- On-line Tests—On-line tests will only be carried out if all mandatory off-line tests are passed. On-line tests involve having the software under test communicate with the CE EDT Emulator to determine if the software can meet the requirements outlined in this circular. On-line tests shall be carried out by answering all the questions presented in appendix 2 to ascertain whether all the requirements have been met.
Unless otherwise stated, all questions relate to mandatory requirements and must therefore all be passed for the software to gain approval. A question shall be passed if its answer is the same as the correct answer indicated on the question form in appendix 2.
Next Page →
NZ Gazette 2010, No 119
✨ LLM interpretation of page content
🌾
Fisheries Electronic Software Requirements Circular 2010
(continued from previous page)
🌾 Primary Industries & ResourcesFisheries, Regulations, Electronic Software, Reporting, CE EDT, MFish, FishServe