[m2m-iwg] Format for Scenario and Problem Descriptions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[m2m-iwg] Format for Scenario and Problem Descriptions

From: Scott de Deugd <dedeugd@xxxxxxxxxx>
Date: Fri, 16 Mar 2012 13:47:41 -0400
Delivered-to: m2m-iwg@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/mailman/private/m2m-iwg>
List-help: <mailto:m2m-iwg-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/m2m-iwg>, <mailto:m2m-iwg-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/options/m2m-iwg>, <mailto:m2m-iwg-request@eclipse.org?subject=unsubscribe>

Based on the IWG M2M meeting discussions, the Wiki now has a proposed format for capturing high level requirements in the form of scenarios and related problems that can eventually be mapped to requirements. The goal would be to capture these as input to IWG architecture work and prioritization for new and existing projects. A couple of examples are included.

Please reply if you have comments or suggestions for this format and/or approach.

http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M_Scenarios
http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M-Problems

.................Scott

Prev by Date: [m2m-iwg] New low-cost, ultra low-power ARM micro controller targeting IoT
Next by Date: [m2m-iwg] M2M meta-model feedback
Previous by thread: [m2m-iwg] New low-cost, ultra low-power ARM micro controller targeting IoT
Next by thread: [m2m-iwg] M2M meta-model feedback
Index(es):
- Date
- Thread

Breadcrumbs