What's included

• Deliverables

  The non-technical requirements (there was such a document, right?) The technical requirements A "decisions" document (if there was one) explaining why some decisions were made over others. This might already be in a different requirements or architecture document, but we usually do this separately for Big Decisions. The code and other resources (image files, CSS, etc...) The database model (as a diagram, document, whatever) DDL to create the database. DML to seed the database. A document explaining application setup and basic trouble shooting. A list of any important usernames and their passwords (for Admin accounts), as well as instructions on how to change the password. Ideally, when they set up the website for the first time, they should be prompted to enter a new admin password, but this is more of an architecture thing. System requirements, and for web apps, minimum hosting requirements as well (Does the app need MySQL or PostgreSQL? How much RAM?, etc...)