October 4, 2017

How does FLORIJN OfficeProfs work?

FLORIJN OfficeProfs

Florijn OfficeProfs develops custom software in 8 stages:

1. Explore

After the first introduction, a thorough analysis of the business case follows. What are the current processes? Who are the stakeholders? And what are the wishes and requirements according to the MoSCoW model:

  • Must Haves
  • Should Haves
  • Could Haves
  • Won’t Haves

2. Brainstorm

Now all conditions have been identified, the different solutions can be addressed during brainstorm-sessions with the stakeholders. We will use Out of the box thinking to reach targets.

3. Design

This is often the most exciting part of the process of development. The design of an application, often only on paper, is in many cases reason for new insights and the associated adjustments. All this with only one goal in mind: creating an optimal process between people and software.

4. Prototype

All the choices that are made are recorded in a functional design. Basis on the design we develope a prototype: screens without functionality for review.

Alle keuzes die zijn gemaakt worden vastgelegd in een Functioneel Ontwerp. Op basis daarvan wordt een prototype ontwikkeld: schermen zonder functionaliteit ter controle.

5. Develop

After consent about all the previous steps, it’s up to the programmer. Often becomes quiet for a while at this point and you wait until the delivery date.

6. Testing

The proof of the pudding. After thorough testing by the developer itself, it is the customer’ turn to test the whole system. In case of larger systems we have test protocols, to leave nothing to chance. All found bugs and imperfections are resolved until everything works in accordance with the specifications.

7. Deliver

Het moment van in gebruik name wordt zorgvuldig geregisseerd. Desgewenst wordt schaduw gedraaid met bestaande systemen of wordt de nieuwe software gefaseerd ingevoerd. Bij grotere systemen zal een draaiboek er voor zorgen dat de bedrijfsvoering geen risico loopt.

The time of implementation is carefully directed. When desired we ‘shadow-use’ with existing systems or implement the new software in phases. In case of larger systems there will be a roadmap to ensure that the business-processes are not at risk.

8. Service en onderhoudscontract

After delivery of the software you can always count on our support in case of emergencies. When desired, we will put the support arrangements in a maintenance-contract (SLA).