Our Process
The development methodology that we follow is illustrated in the
diagram to the right and flows through five distinct stages: Pre-Project,
Planning, Design, Development, and Deployment. At each phase, there
are specific documents that are delivered to the client. These are
summarized in the table below:
Phase |
Document
|
Description |
| Pre-Project |
Proposal Document |
Document proposing our solution based on the client’s
brief or RFP.
|
Planning |
Project Schedule |
A revised project schedule is developed for the client
(based on initial meetings subsequent to contract award).
This project schedule is a dynamic document and will change
as the project progresses.
|
| H-Diagram |
Illustrates counterparts as points of contact for each organization.
|
| Design |
User Requirements Document
|
A consolidated document is usually issued for
these two documents, outlining functional requirements, non-functional
requirements, user characteristics, use cases, project scope
and business case for the project. All requirements are graded
as to priority level and whether or not they fall within the
current scope of the project.
|
| Business Requirements Document |
| Functional Screenshots |
A document outlining barebones screen shots of the application
and how the user/business requirements will correspond to each
part of the application.
|
| Data Dictionary |
A description of every field used in the data model.
|
| Architecture Document |
This is the software architecture for the entire application,
which speaks to a number of audiences (both technical and
non-technical).
|
| Development |
Test Plan |
The road map that we will use for testing the application
from a QA perspective.
|
| User Manual |
A complete manual for users to understand how the system functions.
|
| Administrator’s Manual |
A complete manual for administrators to understand how to
run the system (i.e. creation of new users, permission levels,
population of dynamic menus, etc.)
|
| Deployment |
Build Book |
Is geared toward system administrators from the client’s
perspective. This will detail step-by-step how to setup the
application for the first time on a system – i.e. requirements,
installations to run, configuration settings, etc.
|
|
|
