New Website Checklist

Checklist
· Twitter Account
· Facebook Business Page Account
· Google Business
· Linked In Business Page
· Human.txt
· Robot.txt
· Emails
· News Letters
· Privacy Policy
· Contact Us
· Sitemap
· Blog
· Forum
Website Tools
· Google Webmaster Tools
· Google Alerts
· Google Keyword Tools
· addThis
· Google Page Speed
· Mozrank (Metrics)
· Google Analytics (Metrics)
· Spotify
· Intense Debate
· Feedburner
Guidelines
· Schema.org
Features
· OpenAuth
WP Specific
· Forum
· Akismet
· Allow PHP
SEO
· Linkbuilding

Microsoft and PHP Patterns and Practices

http://msdn.microsoft.com/en-us/practices/default.aspx

According to Microsoft P&P (Patterns and Practices) were created to meet the demands of architects and application developers.By following proven patterns and practices it is suggested that more sound applications will be the result. Included in P&P

  • How to design
  • Develop
  • Deploy
  • Operate architecturally sound applications on a Microsoft platform.

P&P for Web Applications

http://msdn.microsoft.com/en-us/practices/bb969054.aspx#web_apps

PHP Patterns and Practices

http://www.phppatterns.com/docs/start

Software Development Process – Using Object Oriented Analysis and Design through Iterative Development

There are some general good practices to follow when building a new software application. Below provides a good outline of steps when following an Object-Oriented methodolgy when performing the Analysis and Design during Iterative development.

Following the Unified Process (UP)

  1. Inception (Artifacts (any work product) are Optional)
    A short phase to develop and analze the vision/business case, Use-Case (Some) & Models, Supplementary Specification, Glossary, Risk Management, Iteration Planning,  Proof of concepts, Scope, Estimations, Development Case.
  2. Elaboration Phase (Multi-iteration)
    Most requirements analysis should occure in the Elaboration phase. Refining vision, core architecture, resolution of risk, identify most requirements & Use Case, realistic estimates, Domain Models, SSD, Interaction Diagram, Class Diagram, TDD,
  3. Construction
    Full iterative implementation, preperation for deployment
  4. Transition
    Testing and Deployment

Following the Unified Process Disiplines

  1. Business Modeling
    Visual and noteworthy concepts in the application domain.
  2. Requirements
    Use-Case and Models,Specification artifacts showing functional and non-functional requirements.
  3. Design
    Design Model Artifacts, for architectual objects, UI
  4. Implementation
  5. Test
  6. Deployment
  7. Configuration & Change Management
  8. Project Management
    Agile, Scrum
  9. Environment
  10. Business Modeling
    Agile Modeling
  11. Requirements
  12. Design
    Agile Modeling
  13. Implementation
    Test-Driven Develoment TDD, Continuous integration, Coding Standards