Best Practices For A Dynamic Web Application

Not for 'how-to' coding questions but PHP theory instead, this forum is here for those of us who wish to learn about design aspects of programming with PHP.

Moderator: General Moderators

Post Reply
dharmeshb
Forum Commoner
Posts: 36
Joined: Wed Dec 14, 2011 12:17 pm

Best Practices For A Dynamic Web Application

Post by dharmeshb »

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.
User avatar
social_experiment
DevNet Master
Posts: 2793
Joined: Sun Feb 15, 2009 11:08 am
Location: .za

Re: Best Practices For A Dynamic Web Application

Post by social_experiment »

dharmeshb wrote:Should I be implementing the permissions piece in the end after all the other pieces are done?
Personally i would create this first; reasoning behind it: it would make it easier to tie in the other parts of the system once you have the user roles figured out.
dharmeshb wrote:What would be the best approach from a beginner's point of view to start this?
Speaking from experience: make sure that you know exactly what the project is supposed to do; if you get half-way through coding and realize you have left out an additional feature you want incorporated it will probably cause the project to come to a halt. You see something to change, then you change that, once that's changed you see something else, ad infinitum. Proper planning will help avoid this.
“Don’t worry if it doesn’t work right. If everything did, you’d be out of a job.” - Mosher’s Law of Software Engineering
dharmeshb
Forum Commoner
Posts: 36
Joined: Wed Dec 14, 2011 12:17 pm

Re: Best Practices For A Dynamic Web Application

Post by dharmeshb »

Thanks social_experiment. I have created the users and roles tables but was going to add the code later. I won't need to be very granular and have permissions setup. Too much for my need right now so the access will be at page level.. Eg. League Admin will only be able to CRUD Seasons and Teams. Team Admin will only RU Teams and CRUD players, but not CRUD Seasons or CD Teams.. etc.

I have been taking time and planning as much as I can.. but again once I start coding.. it will be agile way ;)
Post Reply