1-1 relationships are extremely rare in the real world. Do not make a group of 1-1 relationships because you want to separate related attributes into their own tables to reduce the column count of the original table. If you have too many columns in a table, it is most likely because there is one or more repeating groups that should be moved to a 1-m table.
The normalization process creates a set of small (in width) tables to ensure that one piece of data occurs in one and only one table. For example, you don't repeat the customer name in both the customer table and the order table. Customer name belongs ONLY in the customer table. When you want to create an order, you include a field to hold the CustomerID and bind it to a combo. That lets you link the order to a customer and the combo will show the customer name but the customer name isn't stored in the Order table, only the customerID is. That lets you pick up the bill to address information as well as the name without duplicating them.
Once the data has been normalized to eliminate redundancy, you use queries to join the tables back together to provide "information"