Drupal Application Development Quote

 

In order to provide you with an accurate quote we will need the things listed below. If something is not clear, see the explanations below.

Required documentation

  1. Project Goals (required)
  2. Use Cases (ideally in the UML)
  3. A couple of scenarios (one instance of a use case)
  4. Non-functional Requirements
  5. Interactions with third-party applications and systems (like Web Services, external databases, XML RPC, etc).

Recommended documentation

  1. Class Diagrams with relationships and multiplicity
  2. Wireframes (required if the quote should contain theming)
  3. Site Navigation

If you cannot provide the required documentation we will not be able to provide you with a quote. We can create the documentation with you for an extra charge (£100/hour).

 

Please be aware that requests like "I want a site like MySpace" will not be treated seriously, and extracting documentation from an existing web page will incur an extra charge.

 

Explanations

1. Project Goals

Example:

"Allow users to buy our existing products on-line and pay via credit card"

2. Use Cases

Describes functionality abstracted from any implementation.

3. Scenarios

Example:

Preconditions

  1. User has an "invoice issuer" role and is active
  2. User is logged in

Actions

  1. User clicks on "New Invoice" button
  2. User clicks on "New Client" button
  3. User provides the following information: Company Name "Foo company inc.", Address: "13 Nowhere street, SE3 9SW London, United Kingdom"
  4. User submits the client form
  5. Issue date is automatically filled in with the current date
  6. User selects their company from a dropdown menu "Our Company Limited"
  7. User clicks on "Add item" button
  8. User adds following item: Name "Foo item", Quantity: 5, Unit: "litres", Unit prices: £100
  9. User selects payment terms "pay by cash"
  10. User submits the invoice
  11. User clicks on "print the invoice" and prints it

Post conditions

The invoice has been successfully created.

4. Non-functional requirements

  1. Average and maximum page load time
  2. Minimum throughput (pages per minute)
  3. Maximum number of users
  4. Predicted page views per second

5. Interactions with third-party applications and systems (like Web Services, external databases, XML RPC, etc)

If your application is going to retrieve data from or send data to another system, we should know this in advance.

Some common examples:

  • credit card payment
  • SMS voting
  • integration with current system
Tags: Drupal, Drupal Application, Drupal Application Development Quote, Drupal Development, Quote