How filiksyos/gymmanagementsystem works
Major Classes
• Controllers / Entry Points
– GymManagementSystem
• Methods: start(Stage), main(String[])
– FXMLDocumentController
• Attributes: username, password
• Methods: loginBtn(), registerBtn(), closeBtn(), minimizeBtn()
– dashboardController
• Attributes: main_form, dashboard_form, coaches_form, members_form, payment_Form
• Methods: initialize(URL, ResourceBundle), switchForm(ActionEvent), displayUsername(), dashboardNM(), dashboardTC(), dashboardTI(), dashboardChart()
• Data Access & DB
– database
• Methods: connectDb(): Connection
– dataAccess (if present)
• Methods: CRUD operations for all data classes
• Domain Data Classes
– memberData
• Attributes: id, memberId, name, address, phoneNum, gender, schedule, startDate, endDate, price, status
• Methods: getters for each attribute
– coachData
• Attributes: id, coachId, name, address, gender, phoneNum, status
• Methods: getters
– equipmentData
• Attributes: id, equipmentId, name, type, purchaseDate, condition, status
• Methods: getters
– scheduleData
• Attributes: id, scheduleId, classType, coachId, memberId, dateTime, duration
• Methods: getters
– paymentData
• Attributes: id, paymentId, memberId, amount, date, status
• Methods: getters
– reportData, reportGenerator, reportExporter, activityLogData, roleData, adminData, passwordUtil
• Under “Utilities & Reporting”
• reportGenerator/reportExporter: methods to generate and export reports
Relationships Between Classes
• GymManagementSystem
– dependency → dashboardController (launches dashboard)
• FXMLDocumentController
– dependency → database (for authentication)
• dashboardController
– association → memberData, coachData, equipmentData, scheduleData, paymentData (to retrieve/display domain data)
– dependency → database (executes queries via dataAccess)
• database
– no outgoing associations (provides Connection)
• dataAccess (if used)
– uses → database, domain data classes
• reportGenerator & reportExporter
– association → reportData
Attributes & Methods
• For each class, show only the public interface (constructors, getters/setters, primary business methods)
• Omit trivial methods (toString(), equals()) for clarity
Important Design Principles & Patterns
• MVC‐like separation: Controllers vs. Data classes vs. DB layer
• Single Responsibility: Each data class encapsulates a single table’s schema
• Dependency Inversion: Controllers depend on abstractions (database or dataAccess) rather than concrete JDBC code
Step‐by‐Step Construction
c. Lay out domain data classes in a grid, grouping by feature (Members, Coaches, Equipment, Schedules, Payments).
d. ReportGenerator, reportExporter, and utility classes on one side.
e. Controllers → dataAccess/database → domain classes.
Final Touches
• Confirm cardinalities where collections are returned (e.g., 1 database → * scheduleData)