V2 ToDo List

Short-Term ToDos

Administrative Items

  1. Call Six payment services

    1. (AH) Start application for SaferPay

    2. Ask about recurring payments
    3. Constraints on customer domiciles? E.g. U.S. and high-risk nations

  2. (AH) Call Facto and ask about MWSt - who should pay?

  3. Get advice for Terms & Conditions (AGB)

Infrastructure

  1. (TN) Rail application server

  2. (AH) GIT server. Repositories:

    1. Prototyps

    2. MAPPS = Master Application Portal & Payment System

    3. V2 application
    4. Skeleton application
  3. Auto-deployment and Rails App setup to public test/beta server
  4. Log file handling i.e. rolling, archiving.

Application Services

  1. (AH) Application configuration management - Probably YAML based

    1. Define application API

  2. [DONE] Logging - Improve logging to include module/method/etc. Implemented log4r in sampleApp see email.

  3. Investigate/select GEM for authorization

  4. Prototype internationalization - Probably using I18n GEM

  5. Investigate background jobs
  6. Emailer
  7. Package application services library as a GEM (or set of GEMs)

Prototyping

  1. Implement MySQL with Rails

Application Definition: MAPPS

  1. (AH) List all use cases

    1. User and role management
    2. Transaction authorization
    3. Payment
    4. Subscriptions - The list of
    5. Invoicing - e.g. ability for MAPPS to produce invoices to customers
    6. Synchronization of users with V2
  2. Wireframes for screens
  3. DB model definition
  4. Define transactions API to V2 and other product systems

Application Definition: V2

  1. List AMVA use cases
  2. Define document/task data model
    1. Revisions
    2. Files
    3. Task notes
    4. Relations

Application Components

  1. (TN) User and user role management

  2. (AH) Classifications

  3. Generic reporting

Deployment

  1. Implement/document environments: dev, int, beta, test, prod
  2. Auto deployment to softxs server - is there an open source Heroku clone?
  3. Capture of production codebase and config changes
    1. E.g. all changes committed to a 'deployment instance' branch

Proposed Conventions

Move this to a separate page

  1. All SoftCS items name-spaced with prefix 'Sxs' or 'SXS'
  2. PDF generation

  3. XML parsing - probabaly based on REXML

  4. Internal function headers (comments) - Investigate RDoc

  5. App services code lives initially in /lib, and later gets converted to a SoftXS GEM
  6. All configuration should be possible via web screens
Copyright 2008-2014, SoftXS GmbH, Switzerland