Motivations. The evolutive maintenance (resp. corrective maintenance) has its origin in the DEPLOY description of work, and the various requests (resp. bug reports) listed by WP1-4 partners, developers and users. Since the DEPLOY project inception, various streams have been used to request new features or track known bugs: - dedicated trackers[10] [11] , - platform mailing lists [12] - DEPLOY WP9 mailing list. Maintenance tasks to perform are collected from the aforementioned streams and scheduled during WP9 meetings. These tasks are processed in the same way as the task planned in the description of work. The following table describes the main tasks (either performed or scheduled) motivating the evolutive maintenance: DoW / WP1-4 partners Prover efficiency and integrity x x Deliverable D25 Test reports and test coverage x WP1-4 partners Updating fields of records x WP1-4 partners Team work x WP1-4 partners Edition x WP1-4 partners Increase platform stability x WP1-4 partners Comments everywhere [13] x WP1-4 partners Plug-in incompatibilities x WP1-4 partners Search in goal window [14] x WP1-4 partners Preferences for the automatic tactics [15] x WP1-4 partners Hierarchy / refinement view[16] x x Plug-in developers API to extend the Pretty Printer view [17] x Plug-in developers View the error log [18] x Plug-in developers Prover API x Plug-in developers A different update site for unstable plug-ins x End Users 64-bit Rodin for Mac x End Users Adding a replay proof command in the Event-B explorer [19] x End Users Having auto-completion in proof control [20] x End Users Displaying instantiated hypotheses [21] x End Users Displaying the inherited elements x
Appears in 2 contracts
Sources: Grant Agreement, Grant Agreement