1. Review the Assigned Task: - Read the assigned task carefully to understand the requirements and constraints. - Identify key entities, attributes, and relationships specified in the scenario. 2. Understand Entity Types and Attributes: - Clearly define each entity type mentioned in the scenario. - Identify the key attributes for each entity type. Key attributes are those that uniquely identify instances of the entity. 3. Identify Relationships: - Determine the relationships between different entity types. - Specify the cardinality and participation constraints for each relationship. 4. Specify Key Attributes and Constraints: - Clearly mark key attributes for each entity type. - Document any structural constraints or business rules mentioned in the scenario. 5. Assumptions and Completeness: - Note any assumptions made during the design process. These should be reasonabl and align with the scenario. - Ensure that the E-R diagram is complete and covers all aspects mentioned in the assigned task. Consider the following set of requirements for an ALUMNI JOB PORTAL database: a. The system maintains information about alumni, including alumni ID, name, contact information, graduation year, and major. Each alumni is identified by a unique alumni ID. b. Job postings are made by companies and include a job ID, title, description, requirements, and the company offering the job. c. Alumni can apply for jobs. Each job application is associated with an application ID, alumni ID, job ID, and application date. d. The system records the skills possessed by each alumni. Skills are identified by a skill ID, name, and proficiency level. e. Companies are registered on the portal and are identified by a company ID, name, industry, and contact information. f. The portal keeps track of events, such as career fairs or alumni meet-ups. Each event has an event ID, name, date, and location. Design an ER schema for this alumni job portal application, and draw an ER diagram for the schema. Specify key attributes of each entity type, and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete