Class Diagram

Class Diagram made with UML Lab:

Version 1.2

Key decisions:

• We added missing attributes to allow every class to have primary keys.

Version 1.1

Key decisions:

• The former class User is now called Person as User is a reserved word in UML lab.

• We removed the relationship between AppUser and Question, and AddAdmin and Question. We figured that having Question related to Person and PetPost would be sufficient to achieving we functionality expected.

• In the same line of thought, we decided that the Donations could be related directly to Person.

Version 1.0

Key decisions:

• We created a UserProfile Class that contains important information from users who wish to apply for an adoption. Users are only required to have a User Profile if they wish to apply for adoption.

• We chose to create a AdoptRequest class in order to facilitate the process of listing adoption requests for both owners and adopters.

• We used enumerations to define AppUser roles: Owners create pet posts and Adopters create adoption requests.