Best Practices For A Dynamic Web Application
Posted: Wed Feb 22, 2012 1:06 pm
To learn PHP I have chosen to develop a Cricket League website. The main functions of the website will be
Add/Modify/Delete
Season
Teams
Players for each team
Schedule of Games
Scores for each game
Statistics
Team level (Total scores, wickets for each team per game)
Player level (Bowling, Batting, Fielding)
Permissions
League Admins (Add/Modify/Delete seasons and teams)
Team Admins (Add/Modify/Delete players and scores for respective teams)
Players (Each player will be able to modify only his personal profile)
I plan to use few tables like users and roles with a reference table like UserRoles to manage permissions. Should I be implementing the permissions piece in the end after all the other pieces are done?
I started half way but then go confused as to if I should do all the "add" modules first or start from a hierarchical level, eg. Seasons (add/modify/delete), Teams (add/modify/delete), etc.
What would be the best approach from a beginner's point of view to start this?
Please advise.
Add/Modify/Delete
Season
Teams
Players for each team
Schedule of Games
Scores for each game
Statistics
Team level (Total scores, wickets for each team per game)
Player level (Bowling, Batting, Fielding)
Permissions
League Admins (Add/Modify/Delete seasons and teams)
Team Admins (Add/Modify/Delete players and scores for respective teams)
Players (Each player will be able to modify only his personal profile)
I plan to use few tables like users and roles with a reference table like UserRoles to manage permissions. Should I be implementing the permissions piece in the end after all the other pieces are done?
I started half way but then go confused as to if I should do all the "add" modules first or start from a hierarchical level, eg. Seasons (add/modify/delete), Teams (add/modify/delete), etc.
What would be the best approach from a beginner's point of view to start this?
Please advise.