TOPIC -

Gym Membership Management System- Design a system for a gym that allows the owner to keep track of the number of different types of members that are signed up. The system should allow trial memberships, 3-month memberships, and annual memberships. The system should keep track of users and what kind of membership they have. It should also keep track of whether the user has paid in full, or is paying monthly or is overdue in payment. For each user, the system should keep track of what types of activities the user prefers (weights vs. aerobic vs. spin classes vs. kickboxing, etc.) Inheritance: 1. Membership is sub-classed by the various types of membership. 2. Payment is sub- classed by method of payment.

Part 2 Create the project, and the classes (along with fields and methods in

each) (15%)

1. In NetBeans, create the project that corresponds to your UML diagram.

2. All fields referred to in your UML diagram must be present and must have characteristics matching those described in the UML diagram.

3. Every method referred to in your UML diagram must have at least a corresponding stub method defined in the project. Getters and setters should be implemented. See Part 3, #2 below.

Part 3 Pseudocode and Implementation (20%)

1. Write pseudocode inside ALL of the methods in your project that describe what the method needs to do to work. This is graded.

2. Choose at least three major functions your solution needs and implement them by replacing the pseudocode with working code and adding appropriate comments. (Getters and setters are not major functions.)

Part 4 Create a test plan that will prove the project works (20%)

1. Create a test harness program that tests the working code parts of your program. This should simulate the functionality of your program with test data. This test plan should accept user data via the console and use that data to do something with your program. (Look at the burger ordering system lab as an example of what we mean by this.)

2. Write a test plan document that walks a user through using all the functions you implemented in Part 3. This is nothing more than a series of step-by-step instructions, data, and results. The user follows the instructions, enters the data, and observes the results. The results you provide must be consistent with the proper function of your project.

3. Among other things, your test plan will be used to grade your projects performance.