Base de Datos #4| Modelado de bd (sin normalizar)

Practice your database modeling and entity-relationship diagram. Don't forget to subscribe to take all the courses we'll be offering. Visit our channel: http://bit.ly/CodigoCompilado Our social media: Twitter:   / codigocompilado   Facebook: http://bit.ly/CodigoCompiladoFacebook Email: [email protected] ************************************************************************************************************************************ Business Rules We want to design a database to keep track of soldiers performing military service. The significant data to keep in mind are: A soldier is defined by their unique soldier code, first name, last name, and rank. There are several barracks, each defined by its barrack code, name, and location. There are Army Corps (Infantry, Artillery, Navy, etc.), each defined by a corps code and designation. Soldiers are grouped into companies, with the company number and primary activity being significant for each company. Soldiers perform duties (guard duty, barracksman, etc.) and are defined by their service and activity codes. Design Considerations: A soldier belongs to a single corps and a single company for the duration of their military service. Soldiers from different corps may belong to a company; there is no direct relationship between companies and corps. A company may be located in several barracks, and there may be several companies within a barracks. However, a soldier is only in one barracks. A soldier performs several duties throughout the Military Service, and the same duty may be performed by more than one soldier (regardless of the company), with the date of completion being significant.