v2.3 (April 2018) Terms and Conditions PDF
We at Mom's Friendly Development Company (“MFDC”) pride ourselves on being as transparent as possible to ensure there are no misunderstandings within our relationships with our Customers.
If there’s anything you’re unsure about in our Terms and Conditions herein, please do not hesitate to contact us.
|1||Project Estimate||The estimated price and breakdown of service from MFDC and any relevant 3rd party contractors.||
☞ The Customer is required to sign-off for project commencement.
|2||Scope and Technical Research and Analysis||
Expanding upon the Estimate, the formal scoping of the Project provides a firm quote and identifies:
☞ The Customer is required to sign-off the Scoping Document before the Design stage commences.
|3||Design — Prototype (Technical Design & Wireframes)||Non-functional view of the system (generally a wireframe / high level design) is developed to meet requirements. This stage provides the Customer with a design overview of the technical design and an opportunity to provide feedback into the design process.||
Design presentation and / or a high level design document (which may include a wireframe and / or screen walk through of a non-functional prototype).
☞ The System Build Stage commences following closure of the customer feedback period.
|4a||System Build (Functional Prototype)||The build stage is where the core of the system and database are constructed. A functional working prototype of the system (i.e. around 60% complete) to provide the Customer with an opportunity to “use” the system and “see” how the system meets the requirements.||
Presentation of a functional prototype for customer walk-through (i.e. around 60% of all functionality).
☞ The System Build (UAT Release) Stage commences following closure of the customer feedback period.
|4b||System Build (UAT Release)||This build stage is where all feedback is incorporated into the system and it is declared ready for User Acceptance Testing (UAT). The system is at least 80% complete. Any requested variation will require further scoping, costing and approval before inclusion into the completed build.||Deployment of a complete system build (with all functionality) into a test environment ready for Customer’s User Acceptance Testing (UAT).|
|4c||System Integration (if required)||This is not a standard stage and is used if required. This is where the system has a requirement to integrate with 3rd party products and / or solutions.||
Customer and / or MFDC perform system integration testing against set criteria.
MFDC addresses any defects and releases further builds for re-testing.
|5||Customer User Acceptance Testing||
The Customer performs tests against the User Acceptance Testing criteria. MFDC addresses any defects to ensure system meets requirements and releases further UAT builds for re-testing by the Customer.
This stage does not introduce any new functionality to the application unless agreed by approved variation.
|The Customer is required to sign-off the UAT Closure Report before proceeding to the next stage.|
|6||Application Packing and Handover||MFDC will package the system ready for hosting or deployment and provide this to the customer.||The Customer is required to sign-off the Handover Document before the application is packaged and provided to the Customer.|
Please contact MFDC for up-to-date Hourly Charge Rates.