Ryan Byrd dot net

• Back
• About
• Contact
• Blog
• Tech Blog
• Talk with my Robot
• Cheer Up
• Diamond Boycott
• Hosting

Segomo Institute's Recommendations for Enterprise Programming in PHP

• Who we are
• When to (and not to) use PHP
• Development Tools (Setup)
  • Overview (use good editor, agree on coding guidelines and naming conventions, etc.)
  • Separate out Presentation Layer with a Templating System (Smarty,...)
  • Version control (CVS)
  • Debugger
• Project Principles
  • Clean design -- start with a site map, define interactions, write tests, code, run tests
  • Object orientation
  • Abstract Database
  • Security (register globals turned off), XSS proof & tested
  • Standards Based (XML, SOAP, XHTML, etc.)
  • Regular Code Reviews
• Project Planning
  • Project requirements/specification
  • Functional specification, Logicial spec, Entity-Relationship
  • Time card/collaboration(forums/email/etc), project time trackers (phpproject)
• Project Elements
  • Document code with phpDoc
  • Event/Debug Logging
  • Error reporting/logging
  • Access control/logging
  • Admin interface
  • Scheduled backup for code/data
  • Language modules (language independence)
  • Up/response time monitoring
  • Failover backup systems
  • Standard look and feel w/ CSS
  • Visitor statistics -- referrals, bad links
• Testing
  • Manual testing in IE, Firefox
  • Auto testing scripts (Function Tests, Web Tests, Stress Tests) (simpletest)
  • Bug reporting/tracking (Double Choco Latte), web feedback forms
  • Useability testing

1. programmers use subversion to checkout code, make updates, test and check in code
2. programmers create unit tests to check/verify each of their functions/methods Check every aspect of the function/method that could possibly fail. Before checking in code, the Unit Tests must run at 100 percent.
3. on a development server there is a "development staging area" where everyone can go to see the lastest checked in development code
4. all unit tests are run / code reviews completed
5. automated functional tests are run (log into the system, perform a series of typical use cases, etc.) tests for the entire system must run at 100 percent
6. performance tests (speed/load simulation) jmeter/siege/badboy on development

1. production offline (maintenance mode)
2. create release notes detailing new features and major bug fixes.
3. the production database and production code is archived
4. the production database structure is sync'd with the staging area's
5. the production code is svn up'd
6. all unit tests are run
7. automated functional tests are run (log into the system, perform a series of typical use cases, etc.)
8. performance tests (speed/load simulation) jmeter/siege/badboy
9. go live