3. (a) Explain in plain English exactly what information is encoded in the following ER diagram. Do not use any technical terms such as "entity," "relationship," "participation," etc. Person Name email Press-release Astronaut Ground-crew Release-10 Release date Date started Location Role Flies in supports describes lob description Mission Missinnum Launch-date Spacecraft (b) For the diagram above, the designer would like to add a constraint that says that the captain of a mission (captain is a possible Role) must be somebody who has previously flown in a mission. This is not something that is easily represented directly in the diagram, and so the designer proposes to explicitly write down that constraint as part of the design. Explain why this constraint may not be appropriate for the application, and suggest an alternative that would overcome your concerns. 3. (a) Explain in plain English exactly what information is encoded in the following ER diagram. Do not use any technical terms such as "entity," "relationship," "participation," etc. Person Name email Press-release Astronaut Ground-crew Release-10 Release date Date started Location Role Flies in supports describes lob description Mission Missinnum Launch-date Spacecraft (b) For the diagram above, the designer would like to add a constraint that says that the captain of a mission (captain is a possible Role) must be somebody who has previously flown in a mission. This is not something that is easily represented directly in the diagram, and so the designer proposes to explicitly write down that constraint as part of the design. Explain why this constraint may not be appropriate for the application, and suggest an alternative that would overcome your concerns