Differences between revisions 1 and 2
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 1. Call Six
    1. Start application for SaferPay 		 1. Call Six payment services
    1. '''(AH)''' Start application for !SaferPay
Line 10: Line 10:
    1. Constraints on customer domiciles? U.S.? High-risk nations?
 1. Call Facto and ask about MWSt - who should pay? 		    1. Constraints on customer domiciles? E.g. U.S. and high-risk nations
 1. '''(AH)''' Call Facto and ask about MWSt - who should pay?
Line 13: Line 13:
 1.
Line 17: Line 16:
 1. Rail app server
 1. GIT server. Repositories: 		 1. '''(TN)''' Rail application server
 1. '''(AH)''' GIT server. Repositories:
Line 20: Line 19:
    1. APPS = Application Portal & Payment System
    1. V2 app
    1. Skeleton app 		    1. MAPPS = Master Application Portal & Payment System
    1. V2 application
    1. Skeleton application
Line 25: Line 24:
== Application Support == == Application Services ==
Line 27: Line 26:
 1. Application configuration management - Probably YAML based  1. '''(AH)''' Application configuration management - Probably YAML based
Line 29: Line 28:
 1. Logging - Improve logging to include module/method/etc.  1. '''(DS)''' Logging - Improve logging to include module/method/etc.
Line 31: Line 30:
 1. Prototype internationalization - Probably using I18n GEM  1. Prototype internationalization - Probably using '''I18n''' GEM
Line 33: Line 32:
 1. Convert app support library to GEM
Line 35: Line 33:
 1. Package application services library as a GEM (or set of GEMs)
Line 38: Line 37:
 1. Implement mySQL with Rails  1. Implement MySQL with Rails
Line 40: Line 39:
= Application Definition: APPS = = Application Definition: MAPPS =
Line 42: Line 41:
 1. List all use cases  1. '''(AH)''' List all use cases
Line 46: Line 45:
    1. Subscriptions
    1. Invoicing 		    1. Subscriptions - The list of
    1. Invoicing - e.g. ability for MAPPS to produce invoices to customers
    1. Synchronization of users with V2
Line 50: Line 50:
 1. Define transaction API to product system  1. Define transactions API to V2 and other product systems
Line 54: Line 54:
 1. List AMVA use cases
 1. Define document/task data model
    1. Revisions
    1. Files
    1. Task notes
    1. Relations
Line 57: Line 63:
 1. '''(TN)''' User and user role management
 1. '''(AH)''' Classifications
Line 58: Line 66:
 1.
Line 63: Line 70:
 1. Auto deployment to softxs server  1. Auto deployment to softxs server - is there an open source Heroku clone?
Line 71: Line 78:
 1. All SoftCS items name-spaced with 'Sxs' or 'SXS'  1. All SoftCS items name-spaced with prefix 'Sxs' or 'SXS'
Line 73: Line 80:
 1. XML parsing - probabaly baed on REXML
 1. Internal function headers (comments) - Investigate RDoc 		 1. XML parsing - probabaly based on '''REXML'''
 1. Internal function headers (comments) - Investigate '''RDoc'''

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

Application Services

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

    1. Define application API

  2. (DS) Logging - Improve logging to include module/method/etc.

  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

V2ToDo (last edited 2013-12-10 15:25:25 by gw)

Copyright 2008-2014, SoftXS GmbH, Switzerland