We need a new information system – it was the conclusion reached by the board after deliberation, the voices became blurred and the countenances were saddened, the concern was felt–.
This situation usually happens in many scenarios to the fear that the words imply: implementation, software, development… The reason lies in the difficulties that are usually found in the development processes and especially in the fulfillment of schedules and times established in the projects.
In the initial stages of developing a new information system (including custom development or use of BPMS), engineers must agree on what the client needs and interpret it properly. In the same way, the customer must validate that the interpretation given corresponds to reality. In an effort to achieve this objective, all kinds of strategies have been established ranging from detailed documentation of all known information to a more relaxed position of conversations and summary minutes. But, which approach should you use? Which is more appropriate? The answers to this question underlie the difficulties of making such software.
As the reader will know, the different methodologies are evolving and establishing in the industry like fashion, some with relatively greater success than others. In this case, we want to present the current possibility offered by wireframe modeling and how it contributes to the development of software projects.
Previously, the work teams used large amounts of resources constructing non-functional prototypes of the information systems with the objective that the client will validate and also mark a developmental north. The construction of this type of artifact, although much faster and more efficient than the construction of dense documentation, continue to present high inertia and difficulty to make changes due to the direct resort to a programmer. It is important to recognize that the prototyping strategy meets its communication goal and narrows the gap between developers and customers. In an evolutionary step, there are wireframes which are simply graphical user interfaces including explanatory notes for fields, validations, and others and basic and reduced interactivity, the best thing about wireframe is that it can be done by anyone, even the same client who does not have advanced knowledge of software development.
The facility to wireframe implies that they can even be built by freehand, or using some tool that allows adding the interactivity of some basic elements, such as navigation or opening a pop-up. The magic lies in simplicity, in addition to the benefits in communication, in times of development and adaptation of changes.
The extensive pages of documentation, requirements specification and system-human interactions remain in the past; achieving with techniques such as this, better, faster and more efficient achievement of the achievements of the early lifting of requirements.
In your BPMS project or tailor-made development, involve the technique that includes wireframe and the faces of the managers in the board will surely transform into a broader and ambitious vision of the objectives accompanied by an atmosphere of positivism and enthusiasm.
