2023年11月25日

数据库代写 | FIT3171 Databases Assignment 1A

本次数据库代写是设计一个数据库，该数据库可用于支持跟踪由大火造成的建筑物损坏-火灾损坏评估系统（FDAS）

FIT3171 Databases
Assignment 1A – Conceptual Model – Fire Damage Assessment
System (FDAS)

Your task for this assignment is to design a database which can be used to support
tracking of the building damage caused by bushfires – a Fire Damage Assessment System
(FDAS).
When a bushfire starts it is noted as a fire event. Each fire event is assigned a unique
identifier such as F20200135 and given a name such as “West Forest Fire” (fire event
names are not unique, the same name may be reused many times). For a given fire, the
date on which the fire started, the coordinates of the estimated start location (latitude and
longitude), and the number of hectares which were burnt, are recorded. Sometimes one
fire event may spark further fire events, for example when embers travel many kilometres
in the wind and start a new fire. The FDAS needs to record if a particular fire event was
started by sparks from another fire event. Fire events occur within Local Government
Areas (LGAs) – a given fire event may involve many LGAs.
A bushfire may impact a property and damage buildings located on that property. The
assessment of such damage is the major task of the FDAS.
Properties are identified by a unique national property id and have their street
address/location and property size in hectares recorded as part of the system. Such
properties may be a farm property, a residential property (in a city or town) or a business
property. Each property has a single owner who is identified by an owner id. The owner’s
name and contact phone number are also recorded. A particular owner may own several
properties. For properties such as groups of apartments/villas or units owned by
individuals which share lawns, roads etc (i.e. a strata title), the owner of the property, for
this scenario, will be taken as the body corporate. In this way, all properties will be
regarded as having only a single owner.
Properties are located in a local government area or LGA. Each LGA is assigned a unique
LGA code, for example, 45. The LGA’s name, for example, “Wardinia”, size (in hectares),
Chief Executive Officer’s name and bushfire contact phone number are recorded.

TASKS
Please ENSURE you include your name and ID on every page of any document you submit. If
a document is a multipage document, please also make sure you include page numbers on every
page.
GIT STORAGE
All working files, as you work on this assignment task, must be stored in GIT and must show a
clear history of development. Your work for this task MUST be saved in your working directory in
your Assignment 1A folder and regularly pushed to the FIT GitLab server to build this history of
development. Any submission with less than two pushes to the FITGitLab server will incur a grade
penalty of 10 marks (a 10 mark deduction).
Students must regularly check that their pushes have been successful by logging in to the web
interface of the FIT GitLab server; you must not simply assume they are working. Before
submission, via Moodle, you must log in to the web interface of the GitLab server and ensure your
submission files are present on the GitLab server.
The task to complete:
Using LucidChart, prepare a FULL conceptual model (Entity Relationship Diagram) using crow’s
foot notation for the Fire Damage Assessment System (FDAS) described above.
● For this FULL conceptual model (ERD), include:
○ identifiers (keys) for each entity
○ all required attributes, and
○ all relationships. Cardinality (min and max) and connectivity for all
relationships must be shown on the diagram.
● In addition to creating the above ERD diagram, you are required to map this ERD
diagram into a UML diagram which must include:
○ identifiers {id} for each entity
○ all required attributes, and
○ all relationships/associations. Cardinality (min and max) and connectivity for
all relationships/associations must be shown on the diagram using
multiplicities.
● Surrogate keys must not be added to this model.
Your model must conform to the FIT3171 ERD and UML standards listed in tutorial 3.