Home > Our Process

Our Process

Digital library of meaningful ideas

Our Process

Below are the phases we utilize to ensure we have a complete understanding of the what the project will require. The knowledge we acquire throughout these phases is vital to our team in order to develop a positive user experience and completely functional technological application that will be the most beneficial to the client’s users.

Orange County Web and Mobile App Developers
with experience

Discovery

Collect information
Investigate existing systems and processes with client
  • Code for current systems
  • Credentials
  • Graphic assets
  • Copytext assets
  • Data assets
  • Summarize in the Investigation Summary Report
Interview client and potential users for:
  • User experience preferences
  • System needs and efficiencies
  • Review what is lacking
  • Copytext assets
  • Data assets
  • Summarize in the Interview Summary
    Report
Research 3rd party software and social media integrations
Examine findings
  • Review interview findings with administrative and project management personnel
  • Complete a User Stories exercise to identify optimal processes by examining overlap of desired functionality and desired user experience
  • Results of User Stories exercise is the User Stories Report
  • Review User Stories findings with administrative and project management personnel
  • Explore potential integrations
  • Recommend best fit solutions

Documentation

Draft
Finalize
  • Polish and detail Wireframes
  • Polish and detail Process Diagrams
  • Integrate wireframes and process diagrams into the Detailed Technical Specifications
  • Review Detailed Technical Specifications with the client
  • Update Detailed Technical Specifications based on findings
  • Continue process until Detailed Technical Specifications are approved
Draft
  • Draft summary of Discovery findings in the Discovery Report
  • Begin drafting diagrams of processes from the Discovery Report
  • Begin drafting wireframes of user experience components from the Discovery Report
  • Outline Detailed Technical Specifications
Review
  • Review drafts of wireframes and diagrams with the client
  • Update drafts based on findings
  • Continue process until drafts are approved

Design

Design work starts in parallel with Discovery and Documentation
Design Questionnaire
  • Completed by administrative and/or project management personnel which will give us the initial direction for the Design
Moodboards
  • Will be assembled based on Design Questionnaire feedback
  • Feedback on the presented Moodboards will help to identify the feel and general style desired
Style Guide
  • Will build on feedback from the Design Questionnaire and Moodboards and will provide the building blocks from which each page will be designed
Sample Designs
  • Draft a sampling of pages from the Detailed Wireframes following the Style Guide
  • Review Sample Designs with the client
  • Update Sample Designs based on findings
  • Continue process until Sample Designs are approved
Complete Designs
  • Sets of pages from the Detailed Wireframes are to be designed following the Style Guide and approved Sample Designs and presented to the client as they are completed
  • Review Complete Designs with the client
  • Update Complete Designs based on findings
  • Continue process until Complete Designs are approved

Development

Plan
  • Review Detailed Technical Documentation and Designs with development team
  • Identify individual tasks
  • Create a Development Schedule to map tasks and resources
Develop Alpha
  • Initiate development following the Development Schedule
  • During this process data migration is initiated (a final sync will be completed at the time of launch)
  • When completed, the Alpha version will be presented to the client
Develop Beta
  • Development continues which is still following the Development Schedule
  • The progress of the parallel process of Quality Assurance Testing is linked to the delivery of the Beta version
  • When completed, the Beta version will be presented to the client

Finalizing Assets

As Quality Assurance Testing begins it is important to have final assets in place to maximize the efficiency of the Quality Assurance Testing process.
Graphic assets
  • Examples:
  • Favicon
  • Photography
  • Videography
  • Banner Illustrations
  • App store listings graphics
Data assets
  • Examples:
  • 301 redirects
  • Page Migrations
Copytext assets
  • Examples:
  • Replace lorem ipsum
  • Metadata
  • App store listing summaries
Legal language
  • Examples:
  • Privacy policy
  • Acknowledgements
  • Terms of use

Quality Assurance Testing

Test Plans
  • Test Plans are drawn up based on the Detailed Technical Documentation and Designs.
Functional Testing
  • Functional Testing is testing focused on system functionality
  • From the Test Plans, Functional Quality Assurance Testing starts with the completion of the Alpha phase of development
User Acceptance Testing
  • User Acceptance Testing is where users from the client’s team will be granted access to the system for testing purposes
  • As Non-functional Testing wraps up, User Acceptance Testing will begin
  • Upon all errors being resolved, testing is considered complete
Non-Functional Testing
  • Non-Functional Testing is testing focused on user experience
  • As Functional Testing is nearing completion, Non-functional Testing will begin. The completion of this phase of Quality Assurance Testing is linked with the completion of the Beta phase of development
  • Non-Functional Testing is testing focused on user experience

Training

Produce Training Materials
  • Compose Quick References
  • Compose Detailed User Guide Documentation
  • Produce Video Tutorials
Train Admin Users

Onsite and remote training sessions for Admin Users

eFAIDA Technologies provides complete training documentation to all which covers:

  • System overview
  • Introduction to Training Materials
  • Processes (for both admin and non-admin users)
  • Operations (for both admin and non-admin users)
Via:
  • Presentations
  • Hands on training
  • User Story Scenarios
Train Non-Admin Users

Onsite and remote training sessions for Non-Admin Users which covers:

  • System overview
  • Introduction to Training Materials
  • Processes
  • Operations
Via:
  • Presentations
  • Hands on training
  • User Story Scenarios

Launch

Pre-launch migration
  • Copy across data/files as part of the development process with systems in place to make sure changes made to the content/files by the client during development are logged in both the old site and the new site.
  • There should be little to no disturbance caused by the launch.
  • Setup of 301 redirects for updated URLs where needed
Migration / Transition
  • Transition from previous system to the new system as a scheduled event post completion of Training and User Acceptance Testing. This will be conducted in accordance with a predetermined Launch Procedures Checklist from the Detailed Technical Documentation.
  • The transition event (from old system to new system) will be scheduled in order to minimize any delay and disruption.
  • As part of the transition, a final data migration will take place pushing updates / changes from the previously completed data migration to ensure there is no loss of data / records.
Launch Support
  • During the launch, support representatives will be on site and on call

Support

Issue Tracking
  • Support continues beyond launch resolving issues / bugs as they come up
  • All issues being tracked via tracking software to which the client will have access to log and monitor issues Management
  • UI / UX and other basic issues that can be replicated will be addressed or resolved within 24 hours.
  • Non-repeatable and other more complex issues will be addressed within 24 hours. After investigation has identified the cause we will provide a planned solution.
New Feature Requests
  • Add new feature requests in the Feature Request Log
  • Regularly review the Feature Request Log with the client
Urgent Support
  • Urgent support requests, such as server downtime, will be handled with the utmost haste
  • Regular automated and manual monitoring of server and system functionality
  • Performing server and other updates as needed
Let Us Contact You

Fill out the form below and we’ll get in touch within 24 hours

I agree to the Privacy policy