this is the thing

eh


Formal Specification:

I will have two tables of daylillies. One of the tables will contain information about an average daylillies, including traits, predominant Color, color Traits, bloom type, scape height, common name, foliage type, ploidy, awards and hybridizer. The second table of daylillies will contain data on the daylillies in Jill’s garden. This second table will include the overall performance of each flower, common name, a picture, age, and an ID number associated with each daylily. Each of these actual daylillies will also be associated with a specific growing year, which will be demonstrated in a third table. In addition, this table will also contain information about each daylillies number of proliferations and blooms.
The number of proliferations and blooms will determine the performance for the individual daylily each year. One constraint is that each average, or abstract, daylily must have a trait, color, bloom type, scape height, common name, foliage type, and a picture. Entries without any one of these would not be accepted. The foliage type must be either dormant, evergreen, or semi-evergreen. The traits may be one or more of the following: Extended Bloom, Rebloom, Instant Rebloom, Bud Builder, Diurnal, Nocturnal, Early Morning Opener (EMO). Additionally, each of Jill’s daylillies must have a variety, hybridizer, and age. The ID number will be randomly generated and therefore is not required in the entry of a new record. Finally, for the growing year table, the minimum year value will be 2017. Jill, as the only user, will be able to add new records of her actual daylillies and update records of the yearly performances of her current daylillies.
She will also be able to query attributes to see how her daylillies compare to abstract daylillies. She will also be able to look at the performance of her daylillies over the course of a couple years to determine if it is time to life and gift. Finally, she will be able to look up information about her current daylillies including if they rebloom, the rate of proliferations, and if they are underperforming. She will be able to edit any of the records of the abstract daylillies so that she can update awards for each daylilly. One cool feature is that there are pictures of the daylillies in the database; these images will be stored as urls.


E/R Diagram:


an_image

Relational Schema:


an_image

Written Description:

This database will catalog daylillies. It will both detail instances of average daylillies, denoted AbstractDaylillies in the E/R diagram, and daylillies that are in Jill's garden, which are labeled ActualDaylillies in the E/R diagram. Each of these actual daylillies is associated with the specific growing season in which it was planted. During the course of that growing season, each daylilly will produce a number of proliforations and blooms. The number of proliferations and blooms will determine the performance for that year.