• V2ToDo

V2 ToDo List

V2Master

• Contents

  1. V2 ToDo List
  2. Introduction
     1. Immediate Goals
     2. Planning
     3. Working Sessions December 2013
  3. Sales & Marketing
     1. General
     2. Web Site
     3. Demo Systems
     4. V2 System Trials
  4. MAPS
     1. MAPS Features
     2. Technical
     3. MAPS Other
     4. MAPS non-Payment System Items
  5. V2
     1. V2 To Do - Summary
        1. V2 Lower Priority Items
     2. Incoming Transmittals
     3. Delete Transactions
  6. Infrastructure
     1. Server Setup
     2. Deployment & Operations
        1. General
        2. Capistrano Deployment
        3. Puppet Provisioning
        4. Performance
        5. Monitoring

Introduction

Immediate Goals

1. Complete final V2 MVA features & usability reviews

2. Get V2 into the hands of reviewers

3. Deliver V2 to first paying customer

Planning

1. JK - complete reviews of nested forms, user management, classification schemes - highest priority

2. AH/JK - agree JK tasks/priorities for Dec/Jan & update JK Work Schedule wiki page

Working Sessions December 2013

1. Develop Demo scenarios & write end-user documentation - AH/JK

2. Design User roles & Project Structures - Schedule AH/JK working session

3. Design of Incoming Transmittals, potentially required for first customer

Sales & Marketing

General

1. Prepare offer for Aegir for Sisimiut archive system
2. Review V2 pricing in light of Hydro-2013 survey results
3. When the MAPS payment processing is implemented and tested:
   1. Sign-up for Six payments:

   2. Write up online purchase terms & conditions (AGB)

4. Review finances & ensure funding to mid-2014

Web Site

1. Review web pages for spelling & grammatical mistakes & make corrections - AH

2. Install new Features web page text - AH

3. PM Handbook - JK

   1. PM Handbook to be composed of three parts:

      1. Project Management - General, not V2 specific

      2. User's Guide to Works Organiser

      3. Configuration Handbook - including a Configuration Checklist

   2. Complete PM outline
   3. Identify initial chapters to write
   4. Start writing chapters

   5. Will there be Quickstart Guide as part of the PM Handbook? - priority?

4. Look into Google (or other) web analytics - JK

Demo Systems

1. Define Scoping Statement for each proposed demo system - JK

   1. Make prioritized list of demo systems to produce. Proposed list:

      1. Engineering Team Collaboration

      2. Proposal Preparation

      3. Metro system

      4. Drawing Manager

      5. Meeting Manager

      6. Site Investigations

   2. Make list of important transactions to demonstrate
   3. Demo system implementation:

      1. Update (minimum required) demo configuration & configure demo accordingly

      2. Create demo data
      3. Write up user instructions/documentation

2. Final updates to Hydro demo - JK

   1. Final tuning of WBS

   2. Complete minimum recommended configuration

3. More documentation for Hydro demo - JK

   1. Define what documentation is needed

4. Implement Engineering Collaboration demo - JK

5. Implement Proposal Preparation demo - JK

V2 System Trials

1. Emails to trial system reviewers - AH

   1. Robert Bartlett - Done. RB/JK started work on proposal system configuration

   2. Mary McGrath - Sent email. Received positive response, including willingness to work with use (on a rail system configuration?)

   3. Harald Schmitt - Sent email. Email acknowledged. Response expected by 2013-12-15
   4. Anthony Sullivan - Wait. Agreed in principal in a Skype call
   5. Aegir Johannsson - Wait.
2. Prepare personal systems for reviewers

   1. Requires completion of classification schemes

3. Consider getting reviewers to assist creating example configurations - AH/JK

   1. Robert Bartlett - Proposal system configuration

   2. Mary McGrath - Rail system config

   3. Harald Smith - Construction Collaboration? Design Management?

MAPS

MAPS Features

1. VAT Handling
2. Invoice/Receipt generation
3. User emails
   1. New purchase
   2. Upgrade
   3. Expired purchase
   4. New payment
4. 3rd Party purchases, i.e. purchase by other than system owner
5. Manual payments
6. Alternate currencies
7. Recurring Payments
8. Payments admin screen to detect expired purchases, set status and send reminder emails.
9. Limit reporting and checking

Technical

1. Review TODO's in code.
2. Merge back to main branch
3. Add Alan's notification mechanism for;
   1. Successful payments
   2. First time purchases
   3. Failed payments
   4. upgrades
4. Delayed_job logging
5. Testing Payments
   1. How to do
   2. Test cases and coverage
6. Testing coverage tool
7. Admin tool

8. Payments processing admin screens, i.e. verification and paycomplete on SIX_PAYMENTS admin screens.

9. Document messaging/call tree for payments;
   1. New purchase
   2. Renewal/extension
   3. New purchase
   4. Upgrades
10. Successful purchase bug
11. Multiple payments handling;
    1. During provisioning
    2. After provisioning
    3. Before after upgrade

12. Remove purchase.start_date? < redundant

13. Purpose of is_valid on purchase <- redundant?

14. Change purchase_date to be the last payment date?
15. Replace link_to with button_to for buttons.
16. Dry out purchase views and purchase controller.
17. Remove static_pages for works_pricing and works_pricing_options. Move works_pricing_options to works_products controller.

18. Set status on expired purchases to EXPIRED

    1. Using delayed_job? or admin screen?
19. Extend with multiple duration options.
20. Review Payment reference usage?
21. Remove is_in_maintenance on product_instance.
22. Review auth rules for purchases payments etc.

MAPS Other

1. Report expired purchases (screen or email report)
2. Complete provisioning delayed job

3. Add admin page to view delayed_job table? <- use rails_admin gem.

MAPS non-Payment System Items

1. Review user management to check if any updates are required

2. Implement skeleton for V2 deployment daemon - AH

3. Complete implementation of Questionnaire module - AH

4. Implement display of audit trail - AH

   1. Investigate Google analytics?

V2

V2 To Do - Summary

• Description	Spec.	Coding	Review	Wiki Page	Notes
  Nested Form Rework	done	done	open		JK review
  User Management	done	done	open	V2UserManagement	JK review
  Classifications by Category	done	open	open	V2Classification	TN final implementation
  Incoming Transmittals	AH/TN	open	open	See below	Not clear if Uma Oya sale still possible
  Delete Transactions	done	open	JK	See below	Check all necessary transactions are present and there are no locking issues

V2 Lower Priority Items

1. Write Workflow & User Role working paper in preparation for working session - JK

2. Write up requirements for Pöyry Uma Oya system (first V2 customer)

   • !. Issue: Is this still a possible sale?

3. Review to check if all back links & cancel buttons have been removed - AH/TN

4. Implement display of audit trail (mainly for transmittal downloads) - TN

Incoming Transmittals

1. This is the ability to create a transmittal, based on project receiving a transmittal
2. The transmittal cover letter and accompanying documents would be registered as documents/revisions in the system

3. A transmittal would be created with the cover letter and documents, and simply marked as received (with a date)

4. Issues

   1. Is special handling for the transmittal's cover letter needed
   2. Should it be possible to record both the transmittal date (the sender's date) and the actual date of receipt by the project?
      1. Ideally we could handle this later when we implement workflows

Delete Transactions

1. Review if all necessary 'delete' transactions are completed - AH/TN

Infrastructure

Server Setup

1. Setup old zg-3.softxs.ch server just like new one, for replacing current zg-1 server - AH

   1. 32 GB memory upgrade ordered at Steg PC - Delivery expected approx. 2013-12-10

2. Migrate all existing services from zg-1 server onto VMs on zg-3 server - AH/TN

   1. Setup Vagrant VM box capable or housing a DrawMGT system

   2. Resolve performance issues of Vagrant filesystem share vs. NFS share (with the host system)

   3. Design & setup DB and data backup system

3. Setup email deliver on zg-3.softxs.ch and all it's VMs
4. Setup backups on wiki server

Deployment & Operations

General

1. Migrate web site (MAPS) to zg-3.softxs.ch server
2. Migrate hydro demo to zg-3.softxs.ch server

3. Setup automated backups of for documents & database www.softxs.ch - AH

4. Setup automated database reset for demo.softxs.ch/hydro - AH

5. Setup email on az-1.softxs.ch server - AH

Capistrano Deployment

1. Refactor deployment to VMs (ssh port & user name)

2. Implement additional deployment tasks:
   1. Event daemon cronjobs
   2. Backup jobs
   3. Log rotation jobs

Puppet Provisioning

1. Refactor Passanger install
2. DNS. Implement multi-zone DNS with private DNS for virtual hosts

Performance

1. Investigate performance of virtual host systems & their VMs

2. Monitoring memory usage on host & MVs

3. CPU usage of DNS VM appear to be quite high

Monitoring

1. Implementing prototyp
   1. Nagios server
   2. Hosts and VMs up and running
2. Applications up:

   1. MAPS & V2 applications

   2. DrawMGT applications

3. Services up:
   1. Pupet server
   2. DNS server
   3. Mail server
   4. Wiki server