Thank you for your feedback.
Developer?s contents should be provided also.
Sample Application, API document and Programmer?s guide according to the
guideline should be filled with.
[Developer?s contents]
Sample Application
For each platform.
Android and Tizen application should be built by scons script together
using Gradle or ANT build system.
API Document
API document comment
Doxyfile update
Programmer Guide
Follow the template.
I wish we have the common template across projects and some specialization
for each specific project to be allowed.
All the detail step is described below.
https://wiki.iotivity.org/feature_development_detail_step_-
_primitive_service_project
BR, Uze Choi
From: ??? [mailto:[email protected]]
Sent: Tuesday, April 12, 2016 7:22 PM
To: ???; iotivity-dev at lists.iotivity.org
Subject: Re: [dev] [Primitive Service] Open Source development process
announcement
Dear Uze,
Your suggestion is clear and reasonable. Can I just give my 2 cents?
How about adding "Document" and "Writing sample code" to Implementation
step?
Synchorinization between codes and document(API doc, developers guide etc)
can be a mandatory step.
Also sample code can be helpful for developers and increasing usability of
new features.
Thanks & BR,
Sungkyu Ko.
------- Original Message -------
Sender : ???<uzchoi at samsung.com> S6(??)/??/IoT Lab(S/W??)/????
Date : 2016-04-04 13:37 (GMT+09:00)
Title : [dev] [Primitive Service] Open Source development process
announcement
Hi IoTivity developer
I?d like to announce the primitive service development process with items
to be approved from maintainer.
For each service, I recommend to follow up approval steps from each
development stage.
All following items are subject to be approved from maintainer.
However, the Implementation stage can be approved by sub-maintainer
according to service category.
Of course, implementation can be done in advance before Feature/concept and
design approval,
However, maintainer and sub-maintainer can start the code review after
these steps has been approved.
[Feature/Concept]
Use Case Diagram
Some of the major use cases with the peer to peer device
interaction perspective.
Feature Definition
Feature level description from the Scenario Level (use case)
[Design]
Resource Modeling
Resource Data Model for each device
Protocol Flow for each major use case
Architecture
Module view and interaction View (Class diagram or Sequence
Diagram in case of OOP)
Deployment Diagram is preferable to be provided
API Design
API Prototyping
API with detail signature
(This could be redundant step from class diagram but will be
valid in case Class diagram is not detail and conceptual)
[Implementation]
Coding
Initial Code is preferred to cover the basic path of major use
case not for whole detail.
Feature level incremental submit
Unit Test
Code Coverage should be over the 70%
Either waterfall process or Agile process with iterative update will do.
I believe these process can be differentiated according to the
characteristic of each sub project.
Any feedback will be welcomed.
BR, Uze Choi
-------------- next part --------------
HTML ?????? ??????????????...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160414/b8a645b2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13168 bytes
Desc: ?????? ?? ????????.
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160414/b8a645b2/attachment.gif>
