|
 |
 |
 FadeOut Software profile is very similar to an Engineering Study: we care about ICT and Industrial Automation using methodologies that are able to ensure the product quality that signifies our work.
Each new project starts with an analysis phase, achieved by means of informative questionnaires, on-the-job training, Use Cases and User Histories; all is done to understand and help the customer to focus product features and requirements, prevent troubles and formalize what come out with standards like UML.
An integral part of the design phase is to ensure the product complies with the requirements collected during the analysis phase We use tools such as Activity Diagrams, Class Diagrams, Entity-Relationship Diagrams and others depending upon their suitability to the actual project.
The development phase is done to realize and bring the project into production, using technologies identified in the previous phases. We can use high level languages like Visual C++, C#.NET, Java; DBMS like MS SQL Server, Oracle, MySql; low level languages like Assembler, ANSI C; Real Time O.S. like Wind RiverŪ VxWorks or RTLinux. The activity is subject to time scheduling and high quality standards, using development formal rules result from our professional background.
Our customer care continues with product maintenance, in order to adapt and evolve the project following market feedback and common expansions of a successful software product.
In the following picture a schematic summary of FadeOut Software methodology is reported. Each phase is represented with its major inputs and produced outputs. This methodology is also detailed in a manual that defines FadeOut Software internal rules and procedures. An extract of our manual was published in the magazine of Engineer Association of "Regione Liguria" in 2005. |
|
 |
|
