"ContentsBusiness Rules ........................................................................................................................................ 3Assumptions ............................................................................................................................................ 3Entity and Attributes ............................................................................................................................... 3Entity Relationship Diagram ................................................................................................................... 7 Business Rules Max of one proposal can be submitted by a researcher. A task has one or more than one tasks where each task may have pre-requisites and notask can be completed before its pre-requisites. Grant amount cannot exceed project budget Only one audit is permitted for proposal and project A panel consists of three experts An applicant required to be granted approval before he can submit a proposal. A project can only be started if a proposal is approved.Assumptions An applicant needs to be granted before he can become a researcher and submit aproposal. In order to store details of application applied by applicant, three fields areadded to applicant table which are listed below? ApplicationStatus: Stores the status of application? ApplicationDate: Date when the applicant applied for last time? ReasonofDApproval: Reason why grant was not approved.A foreign key relates a task to its pre-requisite. A date field is added to panel table, for storing details when the panel was created.„DateOfApproval? field is used to store the details when the applicant got a grant. Entity and AttributesThe entities and attributes required for maintain the database are listed below? Applicanto UniqueID: Provides unique identification to applicant. This is primary keyo fName: First name of applicant o lName: Last name of applicanto researchExpertise: Areas of research of applicant. o department: Name of departmento correspondantAddresses: Address of applicanto Phone: Contact number of applicanto Mobileno: Mobile number of applicanto email: EmailID of the applicanto applicantStatus: status of applicationo ApplicationDate: The date on which applicant last applied for granto ReasonofdApproval: Reason why the applicant?s application is on hold/rejected. ? Researcher:o UniqueID: Provides unique identification to researcher. This is primary keyand foreign key from applicant table. o DateOfApproval: This field is used to store the details when the applicant gota grant.? Proposalo ProjectID: This attribute gives a unique identification to proposal. It is primarykey. o Projecttitle: Title given to proposal.o GrantAmount: Proposed funding amount for the projecto UniqueID: This is foreign key form researcher table which related theproposal to the researcher who submitted it. ? ProjectTask o TaskID: A unique identity attribute which is primary key for providinguniqunesso StartDate: Start date of the tasko FinishDate: The date on which task will be completed.o Status: There are two values for this attribute i.e. pending or completedreflects the status of task.o Pre-requisites: Details of pre-requisites. o projectID:it is foreign key from project table to which a task relates too TaskID: This is self foreign key which shows pre-requisites? Projecto projectID: Unique identification for ech project. It is primary key. o Title: Title given to projecto Budget: Budget approved for the project.o startDate: Start date of the projecto finishDate: The date on which project will be completedo Status: Status of project which is “Pending” or “completed”. o UniqueID: This is foreign key from researcher table which realted a project toresearcher who created it. o proposalID: Foreign key from proposal table. ? ProjectAudito AuditID: This is primary key for unique identification for every audit entry.o Date: Date on which audit process is/ will start. o Budget:Budget approved for the project o Status: Status of the projecto projectID: Foreign key from project table specifies the project which is underaudit.o panelID: Foreign key from panel table who will audit the project.? Expertso expertID: Unique ID given to every expert. It is primary key. o Type: Type of expert i.e. internal expert or external expert. o fName: First name of the expert.o LName: Last name of the experto expertiseAreas: Area of expertise of the expert.o Phone: Contact number of the expert.o Email: Email id of the expert. o Department: Department to which expert belongs.? AuditPanelo PanelID: Primary key of the table. o ExpertID: This is foreign key from expert table will enrol the experts for audit. o Date: This is date on which panel was created. ? ProposalForApprovalo ProposalID: This is attribute which store the proposal detail under audit. It isprimary key for this table and foreign key from proposal table. o Deadline: Maximum time available for audit process. o Outcome: Results of audit process i.e. Exceptional, Rejected, superior orrecommendedo GrantAmount: Project amount for project. o dateOfAssessment: Date of which the project was assessed.o Comment: Comment for proposal o panelID: Panel id is foreign key from panel table. Entity Relationship DiagramAssessment Proposal PK,FK1 ProposalID PK ProposalID developed to sent for approvalDeadlineprojectTitle pre-requistiesoutcomeGrantAmountgrantAmount FK1 UniqueID ProjectTask dateOfassessment submits comments PK TaskID FK2 PanelID ResearcherStartDate appointed in PK,FK1 UniqueIDFinishDate AuditPanelstatusDateofApprovalpre-requisites PK PanelID FK1 UniqueID after approval developes appointed in FK1 ExpertID Applicant have date make PK UniqueID Project ExpertsfName ProjectAudit PK,FK1 UniqueIDlName PK ExpertID PK AuditIDresearchexpertisesProjectIDdepartments ExpertTypetitledatecorrespondentAddresses audited fNamebudgetbudgetPhoneLNamestartDatestatusMobileNoexpertiseAreasfinishDate FK2 PanelIDemail contactNostatus FK1 UniqueIDapplicationStatus email FK2 ProposalIDApplicationDateDepartmentReasonOfdApproval"