Personal Trainer, Inc. owns and operates fitness centers in a dozen Midwestern cities. The centers have done well, and the company is planning an international expansion by opening a new "supercenter" in the Toronto area. Personal Trainer’s president, Cassia Umi, hired an IT consul-tant, Susan Park, to help develop an information system for the new facility. During the project, Susan will work closely with Gray Lewis, who will manage the new operation. Background After evaluating various development strategies, Susan prepared a system requirements document and submitted her recommendations to Cassia Umi, Personal Trainer’s president. During her pre-sentation, Susan discussed in-house development and outsourcing options. She did not feel that a commercial software package would meet Personal Trainer’s needs. Based on her research, Susan felt it would be premature to select a development strategy at this time. Instead, she recommended to Cassia that an in-house team should develop a design proto-type, using a relational database as a model. Susan said that the prototype would have two main objectives: It would represent a user-approved model of the new system, and it would identify all systems entities and the relationships among them. Susan explained that it would be better to design the basic system first, and then address other issues, including Web enhancements and im-plementation options. She proposed a three-step plan: data design, user interface design, and ap-plication architecture. She explained that systems analysts refer to this as the systems design phase of a development project. Cassia agreed with Susan’s recommendation, and asked her to go forward with the plan Review the Personal Trainer fact-finding summary
1. In your discussion of the systems design phase, you mentioned normalization to Cassia. She would like you to explain the basics of normalization in plain English to help her understand the data design tasks.
2. Review the Personal Trainer fact-finding summary in Chapter 4 and draw an ERD with cardinality notation. Assume that system entities include members, classes, merchandise, and fitness instructors.
3. Design tables in 3NF. As you create the database, include various codes for at least three of the fields.
4. Use sample data to populate the fields for at least three records in each table.