Methodology

Our methodology is based on a simple rule: each project starts from a Functional Analysis that is gradually combined with a Data Analysis. Only later do we move on to the phase of technical development.
 
Functional Analysis 
First of all we ask questions, observe, listen and understand. Then we draw up a functional analysis document, using a visual type approach that immediately presents the forms that will constitute the prototype of the application. This document clearly defines all the operating characteristics of the project while illustrating the functional features of the software, in full compliance with the business rules noted during the research. We create logical structures that perform in accordance with your business procedures. The resulting software, in addition to adjusting to existing operating flows, ensures that they will be optimised. 

Document Structure 
The document containing the Functional Analysis follows a top-down logic: the topics, at first grouped together on the basis of the business rules, are presented at increasing levels of depth. Each level corresponds to a set of information illustrated at a uniform degree of detail. The levels range from 2 to 4, depending on the complexity of the project.
 
The simplest applications are found on two levels, such as a typical departmental application that processes information and manages functional features that are independent and can be grouped into a single set. In this case, the levels are: 

• Application Segment
• Function

More complex systems, on the other hand, given that they manage interdepartmental processes that call for the application segments to be grouped in separate components, are defined on 4 levels:

• Sector
• Application Segment
• Function
• Subfunction

The information presented is uniform, because each level presents and summarises all the information illustrated in the level below, though without repeating any information. The first level holds all the information that clearly indicates the goals of the sector and the organisational procedures used by the system to reach them. On the last level, the information is presented at a degree of detail that allows the programmer to write the code correctly without any other functional information. In this way, examination of the functional analysis guarantees, no matter what the level, a complete overview of the system.
When it is read, this multifunctional tool:

• on the first level provides management with a complete overview of the system and of the organisational logic of the processes;
• on the second level allows the departmental managers to control that the functions they require are complete;
• on the last two levels provides the operating personnel and the technicians assigned to draw up the code with an extremely analytical, detailed perspective. 

On request, an on-line help function can be provided for the document of functional analysis, with this being done through transformation into a hypertext.
 
Order of Presentation 
The Sector and Segment application levels normally lack operating functions, given that they are groupings of functions. All they contain are descriptions of the underlying levels.
The third and the fourth levels - Function and Sub-Function, contain a detailed description of the system functions. Each is structured in 4 parts:

• Initial Presentation
• Form Presentation
• Form Fields Description
• Available Operations

The first of these is the only one common to all the levels of a given analysis, while the other three belong specifically to the third and fourth levels. 
 
Initial Presentation
In the case of the first two levels - Sectors and Segments - an abbreviated description is given of the main processes detailed on the lower levels. Then the list continues, with a point-by-point outline containing the titles of all the paragraphs of the level below, accompanied by a phrase along the lines of: “This applied sector/segment holds the following application segments/functions …” In this way, those who wish to read only down to a certain level can still obtain a full overview of the contents and organisational approach on the next lowest level. The initial presentation of the Functions and Sub-Functions provides a complete explanation of the goals of the process being examined and of how these goals are reached, before going into the technical details.
The functions whose sole purpose is to launch complex batch processes in which the mask does nothing but present a message confirming the launch do not have mask fields, with the confirmation button being used only for the launch. All the parts of the process are detailed, even before the presentation of the mask, with an explanation of what is obtained and how.
 
Forms 
This is the visual component that presents the form of the application in its definitive version. The form, at first designed in the development environment, is captured and presented in the document. All the forms are then stored inside the “images” folder, which is contained in the folder holding the analysis.
 
Form Fields 
This section holds the first direct link with the Data Analysis, with a sequential presentation of all the fields found in the mask, moving from left to right and in a downward direction. There is a brief explanation of the contents of each field, plus an indication of the database table of origin or destination. This portion provides analytically detailed controls of the correctness of the data, with precise descriptions of the correlated fields and the tables of origin.
 
Available operations 
This is the part of the analysis where all the possible Events are presented at the maximum level of detail.
Illustrated from left to right, and in a downward direction, there are all the buttons of the mask, plus the activation process for each one. 
  
General Subfunctions 
These are included in an Annex and numbered in sequence. This is the structure followed:

• Synthetic Initial Presentation
• Input Parameters
• Complete Description
• Output Parameters 

Prototype 
The preparation of the prototype of the application is an integral part of the analytical methodology utilised. The prototype is delivered together with the document of Functional Analysis, making it possible to navigate among the forms of the application from the very first phase. There is no significant added cost, given that the prototype can be reused as backbone structure for the codification phase of the programs. 
 
Data Analysis 
The data analysis document provides a complete illustration of the database, which, at the moment, employs the relationship definition model. This explains the use of the Entity-Relationship Diagram, which makes possible a clear illustration of the logical structure of the data.
 
Technical Implementation 
Once the Functional Analysis is completed, the technical development is planned and the Technical Analysis and Codification are initiated, following the standards already defined in the previous phase. 
  
System Test & Release 
The quality of the software delivered is guaranteed by accurate procedures formulated under a standard approach. The operational start-up phase includes a period of parallel operation with the existing production environment, which guarantees proper activation of the new system.