Feature requests and roadmap (guidelines)

Introduction

Objective

The goal of this section is to collecte as many feature requests as possible and group them into topics that make sens as a whole. Grouping them by use case could also be a potential reusable material for the "Tips & Tricks" website section. The idea being to see the whole enterprise and thus focus on several workflows/use cases Architects develop around Archi.

Workflow example

Create and share a baseline model

Typical workflow followed when one starts doing EA:

• Collect material from several sources (CMDB, misc. referentials...).
• Import this material in Archi -> this leads us to the import/export request (what format...).
• Explore the model through the visualizer.
• Create a few first "high level" views. When starting EA, there's much chances that ArchiMate is not well known -> this leads us to the teaching/learning part of Archi (included ArchiMate specs, feature request around magic connector...).
• Export these views to share them with stakeholders -> This leads us to the reporting features.
• ...

Proposed template for feature requests

• Summary: quick description of the feature request
• Rationale: why this seems needed, in which context
• Use cases: example of use cases where this feature can be used
• Description: details about the feature, its use or possible implementations

Proposed Wiki Organization

Each workflow or topic should have its own section. A summary of the workflow/topic should present it in brief and a link to a more detailed page can be added. A good way to document this workflow is to create a small ArchiMate view of the process alongside with supported application services or functions.

Then we should find the list of feature requests using the proposed template. Don't hesitate to create a dedicated page if the associated description starts growing.