I would like to hire a Java Developer to code an Agenda

Create a WEB application to control information from a simple phone book. The DATA MODEL shall allow the following information to be stored: • Basic data of the person. ◦ Name, ◦ Email, ◦ Date of Anniversary. • Address of the person. ◦ State ◦ Town ◦ Neighborhood ◦ Street (street) ◦ Number • Telephones • Number of telephones (area code + number) • Type of telephone • Cellular • Fixed • Message • Which carrier belongs to the telephone line This data can be stored in 5 tables: • Person • Address • Telephone • Type of Telephone • Operator Proposed rules that will define data modeling: • A person will have a link with only one address • A person may have more than one phone number • A phone may be related to only one person • A phone has only one type of phone. • A phone type can have multiple numbers linked to it. • A phone has only one carrier. • An operator can have multiple numbers linked to it. BUSINESS RULES, which will define the operations in the application. • Repeat numbers should not be allowed to be included • When registering a person it is mandatory to include at least one telephone number, the address is not mandatory • Duplicate descriptions are not allowed for the type of telephone and operator name. • The anniversary date has to be a valid date, for work purposes we will consider a valid date where the age is from 1 day to 100 years. WHAT TO DO: • Create the database • Perform hibernate mapping on all tables • Create Classes for data persistence (DAO) • Create Business classes, where rules will be developed • Create the REST service classes that will perform the operations in the tables. • Create a simple HTML interface to enable the services to be tested, here, be careful not to worry too much about beauty, this can impact the development (delay) of the rest. • It must be possible in all tables: ◦ Include ◦ Change ◦ Remove (only records that do not have related data) ◦ Query (single list of all the data registered) Notes: • The number of DAO, BUSINESS and SERVICE classes to be created, is for the team that is doing the work. • Other auxiliary classes may be created to concentrate validations that may be reused.