at phase 1, every team will decide the following parts. abstract: a short (approximately one paragraph) description of the database application you propose to work with throughout the course. your description should be clear and concise. it should also include any constraints that need to be imposed based on the application being modeled. mission statement. mission objectives. a list of use cases that include actor and step-by-step descriptions. an e/r diagram for your proposed database. underline key attributes for entity sets, specify relationships with arrowheads. your e/r diagram must have at least 5 entities, in order to guarantee the sufficient database operations. when defining entities, you should avoid two common mistakes: splitting one entity into multiples ones, or mixing multiple entities into one. a draft report of the above will help you to identify the development objectives and implementation details. the draft can be refined and augmented in the next stage. g
