We develop software that this world only dreams of
Chesalon USA
Our Process

Our Process

Phase 1: Discovery and Component Selection

Discovery

At Chesalon, our values are singularly focused on understanding our clients’ needs and serving our clients by developing solutions tailored to meet those needs. Every Chesalon client relationship begins with a rigorous Discovery and Needs Assessment Process which includes

  • A deep understanding of your company’s Mission, Vision, and Goals.
  • Specific information and interface needs of your employees and your clients.
  • A detailed understanding of current systems, methods, and materials being used to meet those needs.
  • Comprehensive identification of system gaps creating performance issues for employees and service issues for clients.
  • Anticipated organizational or industry changes that will drive future technology needs.

Analysis

With a full understanding of your unique component needs, Chesalon performs a targeted search for compatible software components. The most effective and cost-effective components are researched to provide a solution crafted specifically to meet the needs identified during Discovery. Your unique solution might include one, or a combination of the following software types:

  • Commercial off-the-shelf software used as-is, or with configurations, or customizations,
  • Open-source software sed as-is, or with configurations, or customizations,
  • Custom integrations connecting existing commercial or open-source software,
  • Custom-developed components to meet your specific requirements.

Each component involved in your tailored solution will be evaluated and rated according to compatibility, ease and degree of integration, customization requirements, and cost. You will receive a report detailing information related to all solutions involved in the analysis.

Phase 2: Application Architecture

Technologies

With confidence in the components that have been selected, our design and development team members create an Application Architecture which details how the components will be linked and deployed to deliver exceptional working solutions for you, your employees, and your clients. The Architecture incorporates the following technologies:

  • Hosting provider
  • PaasS services
  • Programming languages
  • Programming libraries and frameworks (the “development stack”)
  • Database(s)
  • File storage services
  • Open-source software
  • Commercial software
  • Custom software that needs to be developed
  • API (to communicate between applications)

Methods

  • Detailed explanation of all technologies considered
  • Detailed reasons for rejecting or recommending each technology

Organization

  • Comprehensive block diagram of all components and connections
  • Detailed descriptions of integrations between components

Cost

  • Estimated upfront cost of each component
  • Annual maintenance cost for each component (labor)
  • Annual license cost for each component (if any)
  • Annual hosting cost for each component

Phase 3: Proof of Concept

Upon completion of the Application Architecture, construction of the “Minimum Viable Product (MVP)” begins using sprints, which allow you to see progress as new features are added. It provided a preliminary review of scalability, security, and user experience, while allowing visualization and functionality demonstrations. It verifies the viability and feasibility of the design by demonstrating layout, navigation, etc. It provides

  • Tangible proof of the concepts behind the design and development process.
  • Demonstrable scalability, security, and scope.
  • A means for identifying potential risks and obstacles.
  • A means for sharing a preliminary system with stakeholders and investors.
  • A means for introducing the platform to the target market.
  • Benchmarks to evaluate agile and lean software development.
  • A means for documenting preliminary user-access procedures.

Phase 4: Production Version

After making the necessary adjustments identified during the Proof of Concept, the Chesalon team moves toward a production version which can be tested with a pilot group for further refinement prior to releasing the final version to your end users.