VULAB-41: Plan API Structure

Metadata

Source
VULAB-41
Type
New Feature
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Blake E
Reporter
Blake E
Created
2008-10-03T11:38:38.000-0400
Updated
2014-03-04T09:04:36.146-0500
Versions
  1. 0.5B
Fixed Versions
  1. 0.5B
Component
  1. Web

Description

plan the larger scheme of how the classes of VULab and the api will interact with the survey tool

Comments

  • Blake E commented 2008-10-03T11:38:46.000-0400

    vulab3

  • Blake E commented 2008-10-07T12:40:57.000-0400

    I imagine that the core systems will fall into some major objects:

    • Survey Plug-in Services
    • - organized in /services/ folder for cleanliness (next to godliness)
    • - to interact with the survey data layer
    • - the /services/ folder should include all api files to integrate within the system (for future reference)
    • Project Object Layer
    • - create/manage/all project data.
    • Survey Data Layer
    • - save urls for survey tool
    • - pull unique id from survey to tie to project
    • - Results
    • - - system?
    • - - plug-in survey tool results system?
    • Core System Layer
    • - Workflow control (outside of the survey tool)
    • - Sessions management
    • - All major functions not outlined

  • Blake E commented 2008-10-07T12:43:19.000-0400

    note: I've named "the api" to "services"

  • Blake E commented 2008-10-20T10:41:36.000-0400

    research complete. Writing document for wiki/list.