Development · integration · reverse engineeringOstwald · Alsace · Remote projectscontact@dtouch.fr
Needs · scope · priorities

Functional framing & project management

Framing connects the people who ask for a solution to those who will build it. Dtouch specifies the uses, constraints and criteria which will allow the result to be verified.

Starting from operations and people

We describe the work situations: information available, decisions to be made, documents to be produced and people concerned. Actual practices complement the requests expressed in features.

This phase makes it possible to identify dependencies with other tools, entry difficulties and steps that require validation. The business vocabulary becomes the basis of the exchange with the developers.

Define a scope that can be evaluated

The project is organized into courses and stages. We specify the expected data, possible actions, rights and results to be controlled. Limits and dependencies are identified with the interlocutors.

This description provides benchmarks for arbitration. A request for development can be placed back in the planned operation and examined with regard to the other stages of the project.

Organize the production with specialists

The management divides the subjects between development, integration, data, infrastructure and professions. Checkpoints make it possible to check interfaces and resolve blockages with the people concerned.

Platform and distributed production experiences provide practice in this coordination. Technical decisions must remain linked to the uses that motivate them.

Period documents & interfaces

A 2017 architectural study to organize applications and their exchanges.

Study of architecture Akeneo, Nextcloud and Rey-ActiveEnlarge
Study of architecture Akeneo, Nextcloud and Rey-Active

Design document from January 2017: study of exchanges between Excel imports, PIM Akeneo, images in Nextcloud and Rey’actif production platform.

Architecture study · design document · 27/01/2017

Prepare the recipe and accompany

The verification scenarios are defined based on the useful paths: create, modify, validate, produce a document, correct an error or find information.

Commissioning also includes the transmission of practices and monitoring of feedback. The project becomes valuable when the teams can understand and use the solution in their activity.

Understanding the exchanges

Manage developers and project dependencies.

The technical management role brings together business teams, developers and specialists to maintain consistency from framing to production.

Manage developers and project dependencies.Enlarge the diagram
  1. 01

    Business need

    Uses and priorities

    Journey • constraints • challenges
    Set expectations ↓
  2. 02

    Technical framework

    Perimeter and architecture

    Data • dependencies • steps
    Organize the production ↓
  3. 03

    Developers

    Implementation and integration

    Team • partners • offshore
    Checking uses ▼
  4. 04

    Recipe

    Check the routes

    Scenarios • differences • arbitrations
    Preparing for commissioning ▼
  5. 05

    Put into production

    Preparing for exploitation

    Deployment • monitoring • continuity
    Develop tools ↓
  6. 06

    Developments

    Organize returns

    Uses • maintenance • priorities
Manage developers and project dependencies.Enlarge the diagram
Functional diagram · synthetic reading of flows and control points.
Frame

Define expected results and responsibilities.

Coordinate

Treat dependencies between developers and specialists.

Transmit

Make decisions and operating conditions understandable.

Your job deserves
the right tools.

A specific need, a software to evolve, a project to frame.

Exchange on your project

Complementary expertise, the same high standards.