Description

Within the framework of a customer demand, PIVA Software proceeds in the realisation of a software or an intellectual service.

The realization of this benefit is made in Tunisia by consultants profile professional engineer in key technologies to realize the project.

The project is done according to the good software development practices commonly admitted in the industry.

It decomposes in the following phases:

• Study of suitability and feasibility
  
  
  • Decide the feasibility
  • Write the client specification
  • Define an outline solution
  • List key technologies to use
  • Set an approximative budget
• General analysis
  
  
  • Defining software and hardware architecture
  • Define the interfaces and data
  • Detailed cost estimate of specification development
  • Writing integration tests and overall
• Detailed analysis and coding:
  This phase is the actual production of software. It involves :
  
  
  • Conducting the detailed analysis and coding
  • Write unit and functional tests
  • Execution of unit and functional tests
  • Draft user manual
• Tests of integration and ensemble:
  This phase strengthens the software quality for its test with selected customers. It consists of:
  
  
  • Lead integration and ensemble test
  • Finalize the user manual
  • Write installation and start-up procedures
• Deployment phase abd recipe
  
  Following customer deployment and after three months of operation, a final receipt is issued for free delivery of the software
• Monitoring phase after sale

At the customer's request, it can be carried out a maintenance phase of 12 months and subject to a separate agreement.


Deliverables

At each of the phases described above is a detailed set of deliverables sum follows :

• Study of feasibility and desirability
  
  
  • Summary of feasibility study
  • Product specifications client side
  • Specification of external interfaces
  • Budget estimate of project cost
• General analysis
  
  
  • Document of general description and software architecture, modules definition.
  • Detailed cost estimates of development
  • Document interface for specifications and data
  • Document specifications for integration tests and global tests
• Detailed analysis and coding
  
  
  • Detailed specification document. These may be written in the project code.
  • Delivery of software modules
  • Document specifications for unit and functional tests
  • Record unit tests and functional
• Integration and global tests
  
  
  • All forms of integration tests and overall
  • The record of tests
  • Operations manuals (user manual, manual administrator if any)
  • A first version of the installation document
  • Passing of knowledge through a training session in the enterprise or remotely
• Deployment phase and recipe
  
  
  • Record Tracking of the first installations
  • Record recipe
  • Phase after s ales
  • Record periodic customer problems discovered during the investigation and are corrected

Prerequisite

The customer agrees to designate a person to keep the interface and provides the information necessary to achieve delivery.

If necessary, the client proceeds to the official invitation from the consultant to facilitate the end of his visa for a trip on the customer site.