During the last months activities on WP4 “Development of the systemic renovation support tool (RenoBIM)” have started. During the last general assembly in La Charité-sur-Loire (France) general approach and objectives were presented, with the detailed planning for 6 months.
The first achievement has been the delivery of D4.1 “Architecture of the RenoBIM Tool”, a report where the technical specifications and the design of the software architecture are described in detail. The methodology for the renovation process defined in WP2 has been the most valuable input for defining the architecture, particularly D2.4, the decision-making procedure.
This analysis has led to the identification of a global RenoBIM use case (shown in the diagram below) which graphically describes the phases, tasks, actors and key decisions in the process. A technical user (closely linked to the owner) has been identified as the main target role, although the manufacturer will also be involved in some tasks within RenoBIM. Then, detailed use cases have been defined for different user roles in different project phases, based on this general one.
In a next step, end user requirements have been formalized, divided in two main categories: functional requirements (what the tool should offer as functionalities and in which format and conditions) and non-functional requirements (dealing with general aspects to be handled like continuous availability, data security and privacy issues, scalability to different project sizes and functionalities, user friendliness, etc.).
Finally, these requirements have been translated into an architectural design which makes possible to support the use cases defined. The tool is conceived as a web platform, with the popular 3-layered approach (data servers, functionalities/services and user interfaces).
Considering user interfaces, initial prototypes have been designed and reflected in the document. It is a very useful mechanism to get early validation of the system from potential end-users, mainly in visual aspects and usability.