Object Model description should relate these objects to the ones mentioned in the Subject Facet. Explain which ones are included and which ones are ignored. If there are objects that are not in the Subject Facet, explain why they ended up in the model.

Add textual description to each diagram (Interaction Model, State Model).

• Text for Interaction Model should explain which scenario it is depicting.
• Text for State Model should explain the object whose states these belong to. (It appears to show states of a booking.)

Scenarios:
School Management is not listed as an actor in the Goal Model nor the Usage Facet.

Legal/Ethical Considerations:
consider also that a volunteer driver should not have contact information of underage kids, thus should hold communications only with the guardian.

IT Facet is not necessary:

• using emberJS and Django is your design decision and not something imposed by the context.

Use Case Diagram:
make sure that each bubble in the diagram corresponds to a user story. (“Accepts Ride” does not have a corresponding user story.)

What should go in notification message to

• Volunteer: Pickup time/date, pickup location, profile of student, drop-off location.
• Student: Pickup time/date/location, volunteer's profile.
• Guardian: Pickup time/date/location, volunteer's profile.

Usage Facet:

• For existing systems, study apps that serve kids, for example: GoKid (http://www.gokid.mobi/), Carpool-Kids (https://carpool-kids.com/), HopSkipDrive (https://www.hopskipdrive.com/) - these may describe more relevant features and scenarios than the grownup options.
• Describe each user group. Make assumptions clear. Is the volunteer driver also a guardian with a kid in the school? Are you assuming that guardians generally don’t know the volunteer driver?
• Add a current-state, context scenario narrative describing how carpooling might be organized today.

When student requests for a ride, guardian must be notified regarding the same, so that guardian can book a ride.