MER - Model entity and relationship

Navigation
0

I would like to know if my SRM is correct and if it is possible to make a N: N relationship between animals and schedules.

Specifications I've created for the system:

Computerize the schedules of a bath and cough, involving customers, attendants, animals, request schedules, schedules, services.

  • The system will allow the client to register in the system;
  • The system will allow the customer to register their animals in the system;
  • The system will allow the customer to choose which attendant will do the service;
  • The system will allow the client to make scheduling requests;
  • The system will allow the attendant to approve or cancel the requests;
  • The system will allow the attendant to register new services;
  • The system will allow the client to make the request for the search of the animal at home;
  • The system will allow you to parameterize the attendant availability schedule;
  • The system will allow you to parameterize the time of availability of the bath and cough;

    
asked by anonymous 25.06.2015 / 16:55

1 answer

2

This depends a lot on the flow of information / business rules of your application. For example, if you need more than one address, there could be the separate address and client table. In general (with exceptions), all information that is repeated must have a specific table and be "looped" with a referrer ID.

For an N: N relationship for animals and scheduling, perhaps adding a table with the ID - IDENTITY columns - ID_AGENDING would solve your problem.

I recommend a history of services for animals and the possibility of registering more than one service for an animal.

    
25.06.2015 / 18:25
How do I make a Redirect on the route if it's the first time it runs? Array of javascript data for PHP