Information systems architecture
An information system is built in the relationships between its components. Dtouch supports architecture choices to link applications, bases, processing, interfaces and operation.
Concrete functions.
Tools in situ.
Interfaces used to organize work, prepare data and track files. Each screen shows a specific function, with presentation data.
Enlarge screen A common view for teams
The weekly schedule brings together technicians, slots, locations and interventions.
Real interface · test environment · demo data.
Enlarge screen View folder progress
Requests are grouped by status, with their subject, an overview of the exchanges and the team in charge.
Real interface · test environment · demo data.Read the system before changing it
The visible need may depend on several applications: an interface, a repository, a processing service and file storage. We examine their roles, their exchanges and the operations that connect them.
The mapping also identifies responsibilities: who provides data, who can modify it and which tool should consume it. This reading allows you to prepare for changes by understanding their impact on overall functioning.
Define joints between components
An architecture must specify the interfaces, identifiers, formats and expected states. API, events, file exchange and delayed processing can meet different needs.
The Rey’actif course provides concrete context: PIM, PostgreSQL, office applications, WebSocket, tasks and InDesign Server. Architectural work brings these tools closer to production uses.
Preparing the steps and dependencies
We distinguish between what can evolve independently and what requires coordination between several components. Resources, access and test environments are part of the framework.
A new interface should not be evaluated in isolation: the demand should be monitored until processing and the result obtained. The recovery scenarios and error situations complete this verification.
A 2017 architectural study to organize applications and their exchanges.
Enlarge 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/2017Making architecture workable by teams
The documentation must allow developers, operations and users to locate a problem. A description of flows, control points and responsibilities serves future interventions.
Dtouch combines this overview with technical management: organizing the contributions of specialists and providing continuity between design, development and production.
Manage developers and project dependencies.
The technical management role brings together business teams, developers and specialists to maintain consistency from framing to production.
Enlarge the diagram - 01Set expectations ↓
Business need
Uses and priorities
Journey • constraints • challenges - 02Organize the production ↓
Technical framework
Perimeter and architecture
Data • dependencies • steps - 03Checking uses ▼
Developers
Implementation and integration
Team • partners • offshore - 04Preparing for commissioning ▼
Recipe
Check the routes
Scenarios • differences • arbitrations - 05Develop tools ↓
Put into production
Preparing for exploitation
Deployment • monitoring • continuity - 06
Developments
Organize returns
Uses • maintenance • priorities
Enlarge the diagram Frame
Define expected results and responsibilities.
Coordinate
Treat dependencies between developers and specialists.
Transmit
Make decisions and operating conditions understandable.
Projects and concrete situations.
Reymann : pilot developers and specialists
Founder's Experience · Reymann
Building an editorial platform requires an organization capable of linking internal developers, specialized partners and production teams. The Reymann route gives concrete reality to this piloting.
Explore the caseRey-Active: Connecting a complete platform
Founder's Experience · Reymann
PIM, office applications, web services, image tasks, InDesign Server and business bases: experience in the articulation between the components of a production platform.
Explore the caseDalim TWIST: unify flows and their parameters
Founder's Experience · Reymann
Moving from around twenty production flows to generic flows linked to file data: integration between 4D, Rey’actif, Dalim TWIST and ICC profiles.
Explore the caseYour job deserves
the right tools.
A specific need, a software to evolve, a project to frame.