Guideline Generation Methodology Sample Clauses

Guideline Generation Methodology. A key contribution of the TULIPP project is a workflow to produce guidelines. The require- ments of the workflow are that it should (a) generate guidelines for low power image process- ing, (b) evaluate the guidelines, and (c) be aligned with all project objectives. The workflow is illustrated in Figure 19. As evident from the illustration, the workflow captures a project-wide effort towards a common vision. We explain the different steps involved in the workflow starting with the critical path next. Image processing and embedded system expertise: The workflow starts by gathering insights from experts in the domains of image processing and embedded systems. Insights refer to deep, underpinning knowledge that comes from experience and modelling. The ex- pertise required to produce insights is not restricted to the project partners. External experts Figure 19: The workflow to generate and evaluate guidelines that define the platform in- stance. The critical path is shown in red. such as those in the advisory board can also contribute with insights. Insights have no re- strictions on format and can be expressed in any enlightening manner. As a running example of the workflow, consider the insight expressed by an embedded sys- tems expert as a single line of text: Insight: Real-time OS (RTOS) provide determinism often at the cost of performance. Guideline formulation: Gathered insights are analysed and formulated into guidelines. This involves judging the context and orientation of insights, translating them into advice, and de- ciding on a recommended implementation method. Translation is necessary since guidelines are goal-oriented, precise, and context-based whereas insights have no restrictions on their format. There is no one-to-one mapping between a guideline and an insight. Many insights can coalesce to produce a guideline, or a single insight can be fertile enough to produce several guidelines. Continuing the running example, the insight is translated into the following guideline: Advice: Balance between deterministic execution and performance while setting real-time OS (RTOS) parameters [40]. Recommended implementation method: Configure the RTOS using vendor suggested methods [36]. Test and document candidate configurations extensively. Application development: In this step, the formulated guidelines are implemented within the applications and evaluated for impact. Guidelines are implemented either using recom- mended or alternative methods. We assume...