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:
Document proposing our solution based on the client’s
brief or RFP.
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.
Illustrates counterparts as points of contact for each organization.
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 Model and Document
A functional on-line prototype of the application and documentation outlining how the user/business requirements will correspond to each part of the application..
Data Model and Dictionary
A description of every field used in the data model.
This is the software architecture for the entire application, which speaks to a number of audiences (both technical and non-technical).
A complete account of how the system will be migrated from the legacy data model to the new data model.
Development and QA
The road map that we will use for testing the application
from a QA perspective.
System Test Documentation
A complete account of all scripts tested within the application and corrective measures taken to remedy those that failed.
A complete manual for users to understand how the system functions.
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.)
This differs from the user manual in that the training manual provides multiple concrete examples and training exercises to ensure that the major concepts of the system are well understood.
Narrated videos of selected system functionality that is more difficult to comprehend and may require an illustrative video.
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.