Abix Tecnologia - Specification for System Migration to the Cloud

Documentation prepared by Visionnaire enabled the migration of a system to a web platform

• 15/05/2025
• Professional Services

Client
Abix Tecnologia 

Area
Radiocommunication 

Summarized Problem
Abix Tecnologia needed to migrate a management solution to a more modern technology and prepare updated documentation for the new solution to enable the system’s migration to a Web platform. 

Summarized Solution
Abix already had an IT team specialized in implementing systems in a data center environment as well as managing infrastructure. Consequently, the new system was deployed on Abix’s own foundations, but with the goal of operating in the cloud for all branches. 

Results
A Project Document was prepared, specifying the processes and macro-processes (BPM: Level 01 and Level 02) that comprised the scope, as well as a Vision Document specifying the functionalities or activities (BPM: Level 03) that formed the scope. 

A Use Case Diagram was also produced, representing the functionalities or activities (BPM: Level 03) of the scope through diagrams. In addition, a Use Cases document with WireFrames or User Stories was created, detailing the user interface tasks (BPM: Level 04) included in the scope. 

With the extensive documentation prepared by Visionnaire, Abix’s IT department obtained precise inputs for estimating the development effort needed to migrate the Pro Radius system. 

Technologies
The previous Pro Radius system was developed in Clipper. The new Pro Radius was specified to run on the Web, on a cloud server, allowing all branches to use the same solution.

Visionnaire has been developing software for over 28 years, employing numerous development processes during this time, always adapting to customers’ needs.

For documentation, we use Atlassian Confluence; for other development processes, we use Atlassian Wiki; for administrative tasks/activities, we use Trello and Jira. We also use communication tools like Slack in all departments. 

For systems analysis and design, we apply the entire UML (Unified Modeling Language) methodology from the OMG (Object Management Group), using both free software tools and IBM/Rational tools (Visionnaire is an IBM development partner and has access to all such tools). 

However, what truly matters is that, in all cases, we primarily adapt to the needs and tools of our clients, as we are a Software Factory with almost three decades of history. 

Detailed Problem
Abix specializes in renting, selling, and developing radiocommunication systems, security cameras (CCTV), and wireless data transmission. With branches in Rio Grande do Sul, Paraná, São Paulo, Rio de Janeiro, Minas Gerais, Alagoas, and the Federal District, the company serves clients in all regions of Brazil. 

Due to the technological limitations of the Pro Radius system—used to manage logistics, commercial, and financial operations—Abix’s IT team deemed it necessary to migrate from the current solution (developed in Clipper with separate databases for each branch) to a more modern technology with integrated databases that follow market standards. 

Moreover, the documentation describing the functionalities of Pro Radius was outdated, making it imperative to develop new documents to support a more accurate development effort estimate and enable migrating the system to a Web-based platform. 

One of the requirements for the new solution was its integration with the ERP system in use—Protheus PIPA. 

A system specification is the document or set of documents that provides a detailed description of the behavior, requirements, and functionalities expected of a system before implementation. In other words, it defines what will be developed and serves as a guide for everyone involved in the project, from developers and testers to managers and clients. 

A well-prepared system specification typically includes: 

• Functional Requirements: The actions the software must perform to fulfill users’ needs.
• Non-Functional Requirements: Performance, security, availability, and other technical constraints.
• Process Flows: A description of how the various system components interact and communicate.
• Acceptance Criteria: Rules and metrics to validate that the functionalities are correct and complete. 

With a clear and comprehensive system specification, companies and entrepreneurs gain greater predictability in terms of timelines, costs, and resources needed. Moreover, this specification helps prevent potential conflicts or rework since all project participants share the same understanding of what must be delivered and how the software will meet business expectations. 

Detailed Solution
Abix already had an IT team specialized in implementing systems in a data center environment as well as managing infrastructure. Consequently, the new system was deployed on Abix’s own foundations, but with the goal of operating in the cloud for all branches. 

The new system’s specification began with: 

• Reviewing existing documentation;
• Interviewing the users and creators of the previous system;
• Analyzing usage of the previous system;
• Collecting requirements for the new system;
• Analyzing the new system;
• Documenting the specifications for the new system;
• Specifying screens for the new system. 

For this phase, screen specifications were made either in wireframe format or in low fidelity (meaning they did not need to be the final design, which could be developed and refined in a subsequent phase). 

In order to fulfill these objectives, the proposed activities included: 

• Identifying active functionalities of the Pro Radius system;
• Identifying business rules and exception handling in the Pro Radius system;
• Identifying integration points (exchange of TXT, DBF files, or REST APIs) between the Pro Radius system and the ERP;
• Identifying gaps in operational processes and defining solutions to address them. 

Brochure
Case Brochure  

Presentation
Case Presentation