IT solutions that bear fruit

Profinit Software Process

Profinit's software process is inspired by the best practices school, which is founded on minimal practices stipulated for each of the primary and supporting activities of software engineering.  Minimal practices are stipulated in order to ensure that we deliver to the customer the requested solution in the required quality, price and timeframe.  There is a range of steps leading to this outcome:

Area

Minimal practices

Offer
  • the customer receives from us an offer that will to maximum possible extent respect the customer's requirements and all known and probable peripheral conditions and that will best correspond to the future reality.

Requirements Specification
  • we and the customer precisely know what is and is not required from the system, not only in terms of functionality, but from many other standpoints, such as performance, reliability and security.
  • specification is clear and comprehensible even for non-technical partners on the customer's side.

Design
  • so that we are able to fulfil all of the customer's requirements, the system can be further developed effectively and the generally acknowledged technical quality of the design is respected.
  • during routine development, the same instances are handled in the same manner.

Programming
  • we create comprehensible, readable, testable, repairable and maintainable programs that correspond to the proposed design of the system.

Testing
  • we deliver to the customer a system that does not contain any serious errors or a large number of minor errors.
  • the customer is satisfied with the delivered solution.

Development environment
  • we know the environment in which our system will operate, we are able to develop the system in an environment that is maximally similar to the target environment and we can recreate this environment at any time.

Documentation
  • the system is easy to install and effectively operate and use; we are able to maintain and develop it ourselves.
  • we are able to communicate with the customer about the system.

Configuration management
  • we always know the components that our system is composed of.
  • we are able to work on several versions simultaneously.
  • we are able to simply and effectively manage and implement changes in the system (implementation of new requirements, repair of discovered errors) without endangering the system itself.

Validation and verification
  • we receive feedback and verification that we are developing the system efficiently in terms of resources, costs and future maintainability.

 

Implementation of the software process

Individual projects are regularly monitored and inspected. The basic mechanism from the software-process perspective consists in reviews (supervision) of the project, which are conducted every month with the aim of uncovering potential problems, risks, inefficient use of resources, etc. The software process also pertains to every individual - within the professional ladder, each employee participates in improving the quality of the development process at the project and organisational levels.

Documents
to download