logo

Report on Database Design for Flare Company

   

Added on  2020-06-03

24 Pages1608 Words41 Views
Database design for Flare CompanySubmitted By:Date:

IntroductionBusiness rules approaches in software program development are concentrated in locating ways and providers that will support automatic propagation associated with business changes from company environment to software techniques. This would help to bridge the particular gap between technology plus business, as aligning info business and systems procedure is one of the fundamental problems in every organizations. To reach that objective, it has to be clear exactly how corporation rules should be proved helpful with, as a special type of software specs, in every phase of the software advancement lifecycle. Accordingly, at least the next aspects have to be considered within this process: rules rules management, rules implementation, identification and business rules specification. The business rules implementation method assumes identifying both the location and the way of how to apply a business rule.Term -- the focus on business, because there's no reference to information techniques or concepts of information techniques - focuses exclusively about how business people think.Reality - People involved in the company (as "customers") link language and business rules in order to computer professionals (as "suppliers"), in the form of system requirements specs.Derivation - Database style should be influenced on the means that business people and company specialists give to certain items or terms from the company vocabulary. And conversations concerning these aspects may become endless. If we consider a quite simple ecommerce applicationConstraint -- Constraint is a generic phrase related to table columns which usually limits info values to be able to preserve database integrity. Condition of the relational model limitations is behavioral and structuralData ArchitectureEntity Name:ADMINISTRATOR, AIRCRAFT, BOOKING, CUSTOMER, FLIGHT, ROUTENormalization: Databases Normalization is a technique associated with organizing the information within the database.Normalization is an organized approach of decomposing desks to eliminate data redundancy plusundesirable characteristics like Update, Insertion and Deletion Anomalies. It is a multi-step process thatwill put information into tabular form by simply removing copied data from the relation furniture.

Normalization is used for usually two purposes,oEliminating needless (useless) data.oEnsuring information dependencies make sense all of us. electronic. data is rationally saved.Normalization rule are split into following normal type.oFirst Normal FormoSecond Normal FormoThird Regular FormoBCNFFirst regular form (1NF)As per the particular rule of first regular form, a good attribute (column) of the particular table are notable to hold multiple values. It will hold only atomic ideals.AIRCRAFT INFO(ADMINISTRATOR_ID,ADMINISTRATOR_NAME, ADMINISTRATOR_ADDRESS, ADMINISTRATOR_PHONE, ADMINISTRATOR_AGE, AIRCRAFT_NAME, AIRCRAFT_MODEL, PASSENGER_CAPACITY, BOOKING_DESCRIPTION, BOOKING_DATE, SEAT_NO, CABIN_CLASS, CUST_NAME, CUST_ADDRESS, CUST_PHONE, CUST_EMAIL, CUST_AGE, CUST_CITY, CUST_STATE, CUST_ZIP, FLIGHT_NAME, FLIGHT_DATE, FLIGHT_INTIME, FLIGHT_OUTTIME, ROUTE_NAME, DEPARTURE_DESTINATION, ARRIVAL_DESTINATION, SCHEDULE, FARES)Second normal form (2NF)The table is said to stay 2NF if both the subsequent conditions hold:oTable is within 1NF (First normal form)oNo non-prime attribute depends on the correct subset associated with any candidatekey associated with table.ADMINISTRATORS (ADMINISTRATOR_ID,ADMINISTRATOR_NAME, ADMINISTRATOR_ADDRESS, ADMINISTRATOR_PHONE, ADMINISTRATOR_AGE, AIRCRAFT_NAME, AIRCRAFT_MODEL, PASSENGER_CAPACITY, ADMINISTRATOR_ID)BOOKINGS (BOOKING_ID, BOOKING_DESCRIPTION, BOOKING_DATE, CUST_ID, FLIGHT_ID, SEAT_NO, CABIN_CLASS, CUST_NAME, CUST_ADDRESS, CUST_PHONE, CUST_EMAIL, CUST_AGE, CUST_CITY, CUST_STATE, CUST_ZIP)FLIGHT (FLIGHT_ID, FLIGHT_NAME, FLIGHT_DATE, FLIGHT_INTIME, FLIGHT_OUTTIME, ROUTE_NAME, DEPARTURE_DESTINATION, ARRIVAL_DESTINATION, SCHEDULE, FARES, AIRCRAFT_ID)

Third Normal type (3NF)The particular table style is said to be in 3NF in case both the following conditions keep:oTable must be in 2NFoTransitive functional dependency associated with non-prime attribute on any kind ofsuper key should be eliminated.oAn attribute that is not section of any candidate key is called non-prime attribute.In other words 3NF can be explained like this: The table is in 3NF when it is in 2NF and for everyfunctional dependency X-> Y at least one of the subsequent conditions hold:oX is really a super key of deskADMINISTRATORS (ADMINISTRATOR_ID,ADMINISTRATOR_NAME, ADMINISTRATOR_ADDRESS, ADMINISTRATOR_PHONE, ADMINISTRATOR_EMAIL )AIRCRAFTS (AIRCRAFT_ID, AIRCRAFT_NAME, AIRCRAFT_MODEL, PASSENGER_CAPACITY, ADMINISTRATOR_ID)BOOKINGS (BOOKING_ID, BOOKING_DESCRIPTION, BOOKING_DATE, CUST_ID, FLIGHT_ID, SEAT_NO, CABIN_CLASS)CUSTOMERS (CUST_ID, CUST_NAME, CUST_ADDRESS, CUST_PHONE, CUST_EMAIL, CUST_AGE, CUST_CITY, CUST_STATE, CUST_ZIP)FLIGHT (FLIGHT_ID, FLIGHT_NAME, FLIGHT_DATE, FLIGHT_INTIME, FLIGHT_OUTTIME, AIRCRAFT_ID)ROUTE (ROUTE_ID, ROUTE_NAME, DEPARTURE_DESTINATION, ARRIVAL_DESTINATION, SCHEDULE, FARES, AIRCRAFT_ID)

Entity relationship Diagram

Data dictionaryTable Name : FLIGHTField NameData TypeSizePrimary Key OrForeign keyCommentsFLIGHT_IDNumber10Primary KeyFLIGHT_NAMETEXT100FLIGHT_DATETEXT100FLIGHT_INTIMETEXT150FLIGHT_OUTTIMETEXT30AIRCRAFT_IDNumber10Table Name : BOOKINGField NameData TypeSizePrimary Key OrForeign keyCommentsBOOKING_IDNumber10Primary KeyBOOKING_DESCRIPTIONTEXT100BOOKING_DATEDATEFK CUST_IDNumber10FK FLIGHT_IDNumber10SEAT_NONumber10CABIN_CLASSTEXT30Table Name : CUSTOMERField NameData TypeSizePrimary Key OrForeign keyCommentsCUST_IDNumber10Primary KeyCUST_NAMETEXT100CUST_ADDRESSTEXT12,2CUST_PHONETEXTCUST_EMAILTEXT2CUST_AGETEXT150CUST_CITYTEXT10CUST_STATETEXT10Foreign keyCUST_ZIPTEXT10

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Database Design for ABC Company
|22
|1388
|435