= = = Location PK LocationID LocName LocDescription Loclmage WayPoints PK WayPointID Estimated Arrival Time Estimated Departure Time = Route PK RoutelD RouName RouStartTime RouWalkTime RouStartLoc PK ID Person PerName PerPassword PerEmail = RouEndLoc Plan PK PlanID PlanName PlanCreated PlanLastUpdated = Point of Interest PK InterestID POIName POIDescription POIMap {routes} {locations} POIImpage = = = Animal Plant Shop Historical classification description Name Image endangered property MAP description Row 3 Barcode #years Locations and routes: ....The system will need to store details of locations that can be visited. Each location would be uniquely identified in the system and also have a location name, description, and an image of the location. Using these locations, the state government want to be able to create "Routes" that can be pre-saved in the system, but also updated as needed. A route has a unique identifier, a name, and recommended start times, and estimated walking time. The Route starts at a location and ends at a location (which may be the same or different location). The route can also have waypoints (locations to be visited along the way). The waypoints would need to have an estimated time of arrival and departure. Points of interest: A Point of interest could be many things. It could be an Animal to look out for, a plant to find, a store / shop, or a historical place of significance. It could be many other things as well. A point of interest has a unique identifier, a name, a google maps reference, a sample photo, and a description. An animal has an extra description, and a classification for if it is poisonous, venomous, aggressive. Also, if it is common or endangered. Plants have a description and a property for poisonous, edible, or if it may cause allergies to flare up. A store / shop has a name, google maps reference, and a barcode you can scan to get a certain % off your purchases. The historical place has a sample photo, description, and number of years it has been in existence. There may be many locations that can be associated with a point of interest, and a point of interest might be viewable / visited from many locations. So some instructions would be provided for how you can view / access a point of interest from different locations. People and planning what to do: The main aim of this system is for people to be able to register with the app (name, password, email) and be assigned a unique identifier in the system. A person can create as many "plans" as they like. These plans could include: going on a particular route at a certain day / time (or possibly many different routes), going to any number of locations, or a combination of both routes and locations. A plan would have a unique id in the system, can be given a custom name by the person who created it, and would also store the day / time the plan was created + when it was last updated.
= = = Location PK LocationID LocName LocDescription Loclmage WayPoints PK WayPointID Estimated Arrival Time Estimated Departure Time = Route PK RoutelD RouName RouStartTime RouWalkTime RouStartLoc PK ID Person PerName PerPassword PerEmail = RouEndLoc Plan PK PlanID PlanName PlanCreated PlanLastUpdated = Point of Interest PK InterestID POIName POIDescription POIMap {routes} {locations} POIImpage = = = Animal Plant Shop Historical classification description Name Image endangered property MAP description Row 3 Barcode #years Locations and routes: ....The system will need to store details of locations that can be visited. Each location would be uniquely identified in the system and also have a location name, description, and an image of the location. Using these locations, the state government want to be able to create "Routes" that can be pre-saved in the system, but also updated as needed. A route has a unique identifier, a name, and recommended start times, and estimated walking time. The Route starts at a location and ends at a location (which may be the same or different location). The route can also have waypoints (locations to be visited along the way). The waypoints would need to have an estimated time of arrival and departure. Points of interest: A Point of interest could be many things. It could be an Animal to look out for, a plant to find, a store / shop, or a historical place of significance. It could be many other things as well. A point of interest has a unique identifier, a name, a google maps reference, a sample photo, and a description. An animal has an extra description, and a classification for if it is poisonous, venomous, aggressive. Also, if it is common or endangered. Plants have a description and a property for poisonous, edible, or if it may cause allergies to flare up. A store / shop has a name, google maps reference, and a barcode you can scan to get a certain % off your purchases. The historical place has a sample photo, description, and number of years it has been in existence. There may be many locations that can be associated with a point of interest, and a point of interest might be viewable / visited from many locations. So some instructions would be provided for how you can view / access a point of interest from different locations. People and planning what to do: The main aim of this system is for people to be able to register with the app (name, password, email) and be assigned a unique identifier in the system. A person can create as many "plans" as they like. These plans could include: going on a particular route at a certain day / time (or possibly many different routes), going to any number of locations, or a combination of both routes and locations. A plan would have a unique id in the system, can be given a custom name by the person who created it, and would also store the day / time the plan was created + when it was last updated.
Chapter10: Application Development
Section: Chapter Questions
Problem 9VE
Question
Is my Conceptual model correct in crow notation pls
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
Step by step
Solved in 2 steps
Recommended textbooks for you
Systems Architecture
Computer Science
ISBN:
9781305080195
Author:
Stephen D. Burd
Publisher:
Cengage Learning
LINUX+ AND LPIC-1 GDE.TO LINUX CERTIF.
Computer Science
ISBN:
9781337569798
Author:
ECKERT
Publisher:
CENGAGE L
Systems Architecture
Computer Science
ISBN:
9781305080195
Author:
Stephen D. Burd
Publisher:
Cengage Learning
LINUX+ AND LPIC-1 GDE.TO LINUX CERTIF.
Computer Science
ISBN:
9781337569798
Author:
ECKERT
Publisher:
CENGAGE L