Welcome to Spiralogics

Digital Asset Documentation

Your application works fine but nobody knows how it works. This is a problem we see with most legacy applications and sometimes new ones. We have a well defined process that will not only reverse engineer proper documents, but it will also provide a blue print for developing a new generation of software to replace the old.

Do you know how things work under the hood?

Let us reverse engineer your software, line by line, and provide a detail set of documents. We will read your code and provide you a complete picture of your asset and how it actually works.


a. Software Architecture diagram​ represents the overall system structure and integrity of the software. This diagram helps to scale applications faster, understand security risks quicker, manage upgradeability and complexity of the application. And overall, it helps increase the quality of the underlying software.

b. Infrastructure Architecture diagram​ represents the overall structure of the resources deployed in conjunction with the software that is being documented. It is important to understand where and how the software resides within an organization’s physical or virtual infrastructure to better understand its impact on future implementations.

a. Business Workflow ​diagram ​captures a business process, which is the outline of the key operations. It’s one of the many visual models that Business Analysts and managers use in their work. This outline of the key operations of the business is necessary for better understanding and management.

b. Technical Workflow​ defines the technical flow of data between systems. It is a diagrammatic representation of an algorithm and an essential part of planning the system. These are widely used in technical analysis and programming for ease of writing programs and explaining them to others.

defines the functionality, features, and the purpose of the software product being built. It contains, in detail, how each feature is implemented and the processes behind it. Ideally, this document is created at the beginning of a software development project. TDD becomes the foundation of how the software is built, maintained, upgraded, and implemented currently and in the future.

Risk Analysis Report
is a vital piece of documentation that helps an organization understand current risks within a software application and how to mitigate those risks. Any compromise to integrity, authentication, and availability makes a software unsecure. Software systems can be attacked to steal information, monitor content, introduce vulnerabilities and damage the behavior of the software. Malware can cause a DoS (denial of service) or crash the system itself. Buffer overflows, stack overflow, command injection and SQL injections are the most common attacks on the software.

The purpose of software documentation is to better understand the system and ultimately, better manage the system. This document will outline all the recommendations based on the analysis completed. Some of the recommendations may include corrective actions that need to be taken immediately and others in the short or long term. We highly encourage organizations to create a plan to implement these recommendations.

  • Frequently asked questions

Welcome to Spiralogics

We strive for excellence in everything we do.