User Tools

Site Tools


feature_development_detail_step_-_primitive_service_project

Each Step requires Maintainer approval. However, I don't think every step does not require formal material or process. Just consensus looks fair enough.

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%
Sample Application
       For each platform.
       Android and Tizen application should be built by scons script together using Gradle or ANT build system.

Developer’s contents

API Document
     API document comment
       Doxyfile update
Programmer Guide
       Follow the template.
feature_development_detail_step_-_primitive_service_project.txt · Last modified: 2016/04/14 03:01 by Uze Choi