System design and analysis:

$*$Develop a smartphone application named PredatorFree $2024$ to support the japanese Government's initiative of making Japan predator$-$free by $2050.$

$*$Enable the public to report pest sightings via the app, contributing to monitoring and control efforts.

$*$Facilitate reporting by civilian reporters, pest and predator control officers, volunteers, and DoC rangers.

$*$Store reported data in a database for analysis and reporting purposes.

Ensure the app's functionality includes reporting pest sightings, managing user profiles, administrative functions, and linking to pest fact sheets.

Deliverables

Produce a system requirements report. This report is for an app for a smartphone to

support the needs of the organisation described in the case study $$ PredatorFree $2024.$ The

following information must be included in the report:

$1.$ An executive summary explaining the contents of the report. Short, a few sentences.

$2.$ A statement of scope that explains the purpose of the app, who will benefit from the app, and the main business requirements for the new system.

$3.$ A use$-$case diagram for the system. Present all use cases and actors.

Use cases MUST express functional requirements of the system. That is$,$ they must be verb$-$noun expressions of functionality. $$Login$$ and $$Store Data$$ are not use cases.

$4.$ Full list of functional requirements for the system as expressed in the PredatorFree $2024$ document. Provide the requirements $($expressed as use cases$)$ with short descriptions in a numbered list.

$5.$ List some of the important non$-$functional requirements for the system. As above provide the requirements in a numbered list with a brief description of each. Make any assumptions as you feel appropriate. This list does not have to be

comprehensive. Just show that you are thinking about some of the important nonfunctional requirements such as security, back up etc.

$6.$ A list of system stakeholders stating their interest in the system. Put this analysis in a table. Assumptions are ok$.$ Think about all the possible people that might have anything to do with the system, even if they may never be actual users.

$7.$ A domain class diagram or an entity relationship diagram for the system including classes, attributes, associations, and multiplicity. Show inheritance hierarchies if necessary.

$8.$ A prototype sketches of the new app. There are various online apps that allow you to draw up wire frames or mockups of iPhone and Android phone apps. Use on of those or$,$ draw by hand in pen or dark pencil. Photograph the sketch and insert the photograph into your report as a figure. Show some functionality that is modelled in your Use Case diagram in your design, just a fancy picture with a DOC logo and a kiwi will get a low mark. Check out some popular apps to get ideas, the Air NZ App for example shows bit of functionality as well as your latest flights on its main page.