Talk:Developer Space Repository

From wiki.gpii
Jump to: navigation, search

Comments from Martin:

How to get to the ontologies / component descriptions ?

  • Exemplary own components describe consider meaningful criteria
  • After similar ontologies in the network such as search Amazon webshop, pdadb , google play gates, EASTIN and out of there looking for the similarities

How to structure this , the SW / HW info How can the application / use case are described ? How to get the Component Repository platform?

  • Define Personas : Who should visit the site , what is his motivation / objective
    • Developer
      • what developer who implements a sub-component of a larger SW / HW system
      • . Motivation / Objective: Seeking concrete after
        • 1:1 ready-made solutions or
        • adaptable solutions or
        • examples or
        • Instructions / Tutorials / Webinars / assistance a la Forum

or linked , itself documented components , examples

    • . Technical Expert
      • What : Experienced developers , technical expert
      • . Motivation / Goal:
        • Link / document components
        • Creating tutorials / webinars, examples
        • Provides help in forums
    • . AT / Rehab . Expert
      • What : "User - expert" : rehabilitation technicians, experts in the AT field , medical rehabilitation with focus ?
      • . Motivation / Goal:
        • Writes Tutorials / Feedback / need / literature from the user's perspective
    • Product Manager / Implementer
      • What : Responsible for the design of integrated solutions
      • . Motivation / Goal:
        • Seeking compatible / combinable components
        • Is feedback regarding demand because practical experience with users is available
    • Consumer ?
      • What : Dedicated users of AT, AT- components
      • . Motivation / Goal:
        • Want to contribute his part, that he is doing or like-minded people better
  • Provides feedback , describes his situation or describes required
  • Describe Use Cases
  • defne requirements
  • Choose CMS / Tools
  • iteratively improve

Some Notes

Notes from KIT internal discussion on possible influencing factors that need documentation:

  • Licenses
    • free software
    • payed licenses?
  • API
  • Modules and interfaces
  • Target needs of end users
    • common terms repository
  • GPII comaptibility
  • Use Case Examples
    • one could be adapter to GPII Autopersonalization?
  • Standards
  • Technology / Platform
  • Maturity "Rating" / Experiences
  • Problem Solving/Pratical Feedback from existing users
    • stackoverflow nad alike