 |
Our Services |
 |
|
|
|
|
Featured Site |
|
|
 |
| BCI Email (For Beckman Coulter, Inc.) |
|
 |
|
|
|
Testimonial |
|
|
"We are working on a complex scheduling system, built from scratch and Bobby and his team have been SUPER responsive. They've offered ideas that have improved usage of the system tremendously, their communication has been frequent and detailed and the quality of the documents provided to us to date have been excellent. I would strongly recommend them for any significant development effort."
|
|
|
|
|
|
|
FAQ |
|
|
|
|
|
| |
|
A solid work process is the foundation of any quality product. At Dever Goodwin, LLC, we pride ourselves on our consistent,
documented approach, which we have been building and shaping since our inception in 2001. Below are samples of process
documents we use for various stages of a project. Want to see more? Just ask!
|
Sample Application Design Document
This functional design document creates a vital bridge of communication between
the application programmers and the business requirements manager (the customer).
It consists of a database design, including a technical schema and an information
outline clarifying what information the system will store, and a business logic design,
a screen-by-screen storyboard of the user experience.
Together, these elements form a clear, written document stating exactly what the
scope of the application shall be, so there is no confusion, less rework, and
no scope surprises.
|
|
Sample Project Scope Outline
Having a detailed, written scope of work is vital to assuring customer
expectations are met on a project. At Dever Goodwin, LLC, we listen well
in our requirements-gathering sessions, and document the scope for our
customers to review, so there is never any question about what is to
be done. We include this document as part of the project agreement on every job.
|
|
Sample Application Test Document
The Dever Goodwin, LLC test document is a clear, objective instruction manual
provided to our application testers and quality control managers for a particular application,
defining exactly how the application should work.
Without a test document, a test process is hit-and-miss at best. Even so, few companies
have written documentation of their test process.
The test document defines the full gamut of our thorough test process, from
development testing, to module testing, system integration testing, load testing
and usability testing.
Together with our issue log and priority/status definitions (see page
138 of the sample document), this process ensures that the vast majority of issues and errors are found and corrected in
a deliberate, managed fashion, before the application is put into production.
|
|
|
|
|
|
| |
|
What would you like to do next?
|
|
|
