OZONE Asylum
Forums
Server-Side Scripting - Oh my!
Planning a PHP CMS
This page's ID:
28078
Search
QuickChanges
Forums
FAQ
Archives
Register
Edit Post
Who can edit a post?
The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.
Your User Name:
Your Password:
Login Options:
Remember Me On This Computer
Your Text:
Insert Slimies »
Insert UBB Code »
Close
Last Tag
|
All Tags
UBB Help
Here comes the nasty UML advocate.. muhuhahahahaha.... One word: outline is cool, it's always a plus, but before thinking features, you should think "overview". Another word: diagrams. What I do when I plan on doing something big, and you just can't imagine how much it eases out the process of app design, is: - lay out the "actors" and actions [b]from the user's perspective (very important).[/b] In other words, how will information flow through your app and how should it be used? UML provides two systems for this: use case diagram. Sample: "User logs in" "User is accepted" "User browses forums" "User browses threads" Etc... for each module or set of action, you can write down an outline of this kind. It's not the best diagram, but it gives an overview of usage, and is a good exercise to do on one of your big projects, or at least a small part of it (forums only, or news only, etc.). It's also very important to keep it general, in the above example, I am avoiding: "User types username" "User types password" "User presses button" Because it determines the implementation too much right from the start, this should remain a flexible overview. - lay out the class diagram. I've mentionned actors. In the context of a CMS, actors could be: - downloads - posts - threads - forums - news - user profiles - etc... Just lay them out as little boxes. They will become objects. Then tie them to one another. These will become relationships, and will point out the required methods. "post -> added/suppressed -> thread" / thread.addPost(new Post()) // *** Java pseudo-syntax It seems "silly" at first, but once you've been through the hassle of laying out the whole diagram, implementation becomes incredibly easy, because you know exactly what each member does, doesn't do, in other words, it contains the whole skeleton of your app in a single overview. Google "UML use case" and "UML class diagram" for more info on this. I do not recommend it for very small projects, but for mid-sized to big projects, it'll make wonders and will spare you loads of hassle and time.
Loading...
Options:
Enable Slimies
Enable Linkwords
« Backwards
—
Onwards »
Maximum Security
OZONE
DHTML/Javascript
Server-Side Scripting - Oh my!
CSS - DOM - XHTML - XML - XSL - XSLT
Stupid Basic HTML
Visual Therapy
Photoshop
Photoshop Pong, Anyone?
***WARNING*** BIG SIG APPROACHING
Photography
3D Modelling & Rendering
Multimedia/Animation
Print Graphics
Holding Pens
Philosophy and other Silliness
Outpatient Counseling
Site reviews!
Mad Scientists' Laboratory
Getting to know the Grail