Differences between revisions 6 and 7
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Short-Term ToDos = [[V2Master]]
Line 5: Line 5:
= Administrative Items =   <<TableOfContents>>
Line 7: Line 7:
 1. Call Six payment services
    1. '''(AH)''' Start application for !SaferPay
    1. Ask about recurring payments
    1. Constraints on customer domiciles? E.g. U.S. and high-risk nations
 1. '''(AH)''' Call Facto and ask about MWSt - who should pay?
 1. Get advice for Terms & Conditions (AGB) 		= Priorities =

 1. Complete final V2 show stoppers
 1. Get V2 into the hands of reviewers
 1. Deliver to first paying customer
Line 16: Line 15:
 1. '''(TN)''' Rail application server
 1. '''(AH)''' GIT server. Repositories:
    1. Prototyps
    1. MAPPS = Master Application Portal & Payment System
    1. V2 application
    1. Skeleton application
 1. Auto-deployment and Rails App setup to public test/beta server
 1. Log file handling i.e. rolling, archiving. 		 1. Setup 8-core Intel rackmount server to replace existing zg-3 server
    1. Memory upgrade: Determine what SIMMs to buy & order 32 GB memory (approx. 400 CHF)
    1. Install 'Ubuntu 12.04.3 LTS Server'
    1. Setup 2 x 4TB mirrored disks
    1. Install Virtual``Box & Vagrant
    1. Setup basic VMs
       1. rinetd port forwarder
       1. Gateway system
       1. Web server for zg-3.softxs.ch
    1. Setup packet filter?
    1. Setup VM suitable for hosting DrawMGT
 1. Install rackmount server in Datawire data center in Cham
    1. Bring back existing zg-3server, which has 8-cores & 12 GB main memory
 1. Migrate all existing services from zg-1 server onto VMs on zg-3 server
 1. Setup old zg-3 server just like new one, for replacing current zg-1 server
 1. Complete implementation of Puppet-managed DNS for DMZ
 1. Concept & design for monitoring
Line 25: Line 33:
== Application Services == = Deployment & Operations =
Line 27: Line 35:
 1. '''[DONE]''' Application configuration management - Probably YAML based. Use rails_config see email.
    1. '''(AH)''' Define application API
 1. '''[DONE]''' Logging - Improve logging to include module/method/etc. Implemented log4r in sampleApp see email.
 1. Investigate/select GEM for authorization
 1. Prototype internationalization - Probably using '''I18n''' GEM
 1. Investigate background jobs
 1. Emailer
 1. Package application services library as a GEM (or set of GEMs) 		 1. Setup automated backups for www.softxs.ch: documents and database
 1. Setup automated database reset for demo.softxs.ch/hydro
 1. Implement deployment of event daemon cronjobs
 1. Implement deployment of backup jobs
 1. Implement deployment of log rotation jobs
 1. Test VM-based V2 deployment, currently implemented for Free``BSD, to ensure it works with Ubuntu
 1. Setup email on az-1 server
Line 36: Line 43:
= Prototyping = = MAPS System =
Line 38: Line 45:
 1. Implement MySQL with Rails  1. Complete Six-payments interface
 1. Review user management to check if any updates are required
 1. Implement skeleton for V2 deployment daemon
 1. Complete implementation of Questionnaire module
 1. Implement display of audit trail, investigate online analytics
Line 40: Line 51:
= Application Definition: MAPPS = = V2 Application =
Line 42: Line 53:
 1. '''(AH)''' List all use cases
    1. User and role management
    1. Transaction authorization
    1. Payment
    1. Subscriptions - The list of
    1. Invoicing - e.g. ability for MAPPS to produce invoices to customers
    1. Synchronization of users with V2
 1. Wireframes for screens
 1. DB model definition
 1. Define transactions API to V2 and other product systems 		== Planning & Specification ==
Line 53: Line 55:
= Application Definition: V2 =  1. List of V2 features to fix/improve
 1. Prioritized list of next V2 features to implement
 1. Design/rework of user roles as specified by JK
 1. Decision/design of multi-file uploads (will be difficult to implement)
 1. Decision/design of incoming transmittals
 1. Design of workflows
 1. Design of reporting
 1. Design of project management structures
Line 55: Line 64:
 1. List AMVA use cases
 1. Define document/task data model
    1. Revisions
    1. Files
    1. Task notes
    1. Relations 		== Coding ==
Line 62: Line 66:
= Application Components =  1. User Management
    1. Ability to manage external users. E.g. transmittal recipients
       1. External users will not be registered in MAPS
       1. All users with logins will be registered in MAPS
    1. Ability to enable/disable internal and external users
    1. Ability to put users into folders to allow delegation user management
 1. Implement display of audit trail
Line 64: Line 74:
 1. '''(TN)''' User and user role management
 1. '''(AH)''' Classifications
 1. Generic reporting 		== Testing ==
Line 68: Line 76:
= Deployment =  1. Make a list of what application areas do not have automated testing
Line 70: Line 78:
 1. Implement/document environments: dev, int, beta, test, prod
 1. Auto deployment to softxs server - is there an open source Heroku clone?
 1. Capture of production codebase and config changes
    1. E.g. all changes committed to a 'deployment instance' branch 		== Review ==
Line 75: Line 80:
= Proposed Conventions =  1. Transmittals
    1. Front-end GUI
    1. Transmittal email
 1. Final check of Usability Review
 1. Review if all necessary 'delete' transactions are completed
 1. Review to check if all back links and cancel buttons have been removed
 1. Review pricing vs. Hydro-2013 survey results
Line 77: Line 88:
''Move this to a separate page'' = Web Site =
Line 79: Line 90:
 1. All SoftCS items name-spaced with prefix 'Sxs' or 'SXS'
 1. PDF generation
 1. XML parsing - probabaly based on '''REXML'''
 1. Internal function headers (comments) - Investigate '''RDoc'''
 1. App services code lives initially in /lib, and later gets converted to a SoftXS GEM
 1. All configuration should be possible via web screens
 
= Confirmed Conventions = 		 1. Make spelling and grammar fixes
 1. Install new features text
 1. Install specification draft
 1. PM Handbook
    1. Complete outline
    1. Identify initial chapters to work on
 1. Write some 'news articles'
 1. Outline for a webcast
Line 88: Line 99:
''Move this to a separate page'' == Demo Systems ==
Line 90: Line 101:
 1. Use rails_config gem for application configuration and settings.
 1. Use log4r for logging. 		 1. More documentation for Hydro demo
    1. Define what documentation is needed
 1. Implement Engineering Collaboration demo
 1. Implement Proposal Preparation demo

= Sales & Marketing =

 1. Follow-up on Tokyu offer
 1. Prepare offer for Aegir for Sisimiut archive system

== V2 System Trials ==

 1. Emails to trial system reviewers
    1. Robert Bartlett
    1. Aegir Johannsson
    1. Harald Schmitt
    1. Anthony Sullivan

= Administration =

 1. Determine when to sign-up for Six payments
 1. Write up terms and conditions (AGB)

V2 ToDo List

V2Master

Priorities

  1. Complete final V2 show stoppers
  2. Get V2 into the hands of reviewers
  3. Deliver to first paying customer

Infrastructure

  1. Setup 8-core Intel rackmount server to replace existing zg-3 server

    1. Memory upgrade: Determine what SIMMs to buy & order 32 GB memory (approx. 400 CHF)

    2. Install 'Ubuntu 12.04.3 LTS Server'
    3. Setup 2 x 4TB mirrored disks

    4. Install VirtualBox & Vagrant

    5. Setup basic VMs
      1. rinetd port forwarder
      2. Gateway system
      3. Web server for zg-3.softxs.ch
    6. Setup packet filter?
    7. Setup VM suitable for hosting DrawMGT
  2. Install rackmount server in Datawire data center in Cham

    1. Bring back existing zg-3server, which has 8-cores & 12 GB main memory

  3. Migrate all existing services from zg-1 server onto VMs on zg-3 server
  4. Setup old zg-3 server just like new one, for replacing current zg-1 server
  5. Complete implementation of Puppet-managed DNS for DMZ

  6. Concept & design for monitoring

Deployment & Operations

  1. Setup automated backups for www.softxs.ch: documents and database
  2. Setup automated database reset for demo.softxs.ch/hydro
  3. Implement deployment of event daemon cronjobs
  4. Implement deployment of backup jobs
  5. Implement deployment of log rotation jobs

  6. Test VM-based V2 deployment, currently implemented for FreeBSD, to ensure it works with Ubuntu

  7. Setup email on az-1 server

MAPS System

  1. Complete Six-payments interface
  2. Review user management to check if any updates are required
  3. Implement skeleton for V2 deployment daemon
  4. Complete implementation of Questionnaire module
  5. Implement display of audit trail, investigate online analytics

V2 Application

Planning & Specification

  1. List of V2 features to fix/improve
  2. Prioritized list of next V2 features to implement
  3. Design/rework of user roles as specified by JK
  4. Decision/design of multi-file uploads (will be difficult to implement)
  5. Decision/design of incoming transmittals
  6. Design of workflows
  7. Design of reporting
  8. Design of project management structures

Coding

  1. User Management
    1. Ability to manage external users. E.g. transmittal recipients
      1. External users will not be registered in MAPS
      2. All users with logins will be registered in MAPS
    2. Ability to enable/disable internal and external users
    3. Ability to put users into folders to allow delegation user management
  2. Implement display of audit trail

Testing

  1. Make a list of what application areas do not have automated testing

Review

  1. Transmittals
    1. Front-end GUI
    2. Transmittal email
  2. Final check of Usability Review
  3. Review if all necessary 'delete' transactions are completed
  4. Review to check if all back links and cancel buttons have been removed
  5. Review pricing vs. Hydro-2013 survey results

Web Site

  1. Make spelling and grammar fixes
  2. Install new features text
  3. Install specification draft
  4. PM Handbook
    1. Complete outline
    2. Identify initial chapters to work on
  5. Write some 'news articles'
  6. Outline for a webcast

Demo Systems

  1. More documentation for Hydro demo
    1. Define what documentation is needed
  2. Implement Engineering Collaboration demo
  3. Implement Proposal Preparation demo

Sales & Marketing

  1. Follow-up on Tokyu offer
  2. Prepare offer for Aegir for Sisimiut archive system

V2 System Trials

  1. Emails to trial system reviewers
    1. Robert Bartlett
    2. Aegir Johannsson
    3. Harald Schmitt
    4. Anthony Sullivan

Administration

  1. Determine when to sign-up for Six payments
  2. Write up terms and conditions (AGB)

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

Copyright 2008-2014, SoftXS GmbH, Switzerland