V2 ToDo List

V2Master

• Contents

  1. V2 ToDo List
  2. Introduction
     1. Immediate Goals
     2. Planning
     3. Working Sessions 4-18 November 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. Transmittals
     3. File Handling
     4. User Management
     5. User Permissions
     6. Classifications by Category
     7. Nested Form Rework
     8. Incoming Transmittals
     9. Delete Transactions
  6. Infrastructure
     1. Main Issues
     2. Server Setup
     3. Deployment & Operations

Introduction

Immediate Goals

1. Complete final V2 MVA features & configuration

2. Get V2 into the hands of reviewers

3. Deliver V2 to first paying customer

Planning

1. AH/JK - agree JK tasks/priorities & update JK Work Schedule wiki page - highest priority

2. JK - update V2UsabilityReview wiki page - high priority

3. Review & update V2LaunchPlan - lower priority

Working Sessions 4-18 November 2013

1. Define V2 release Road Map - AH/JK by phone, based on notes to be supplied by JK (AH/JK 2013-11-05, Tue at 11:30).

2. Usability review - AH/JK working separately

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

4. Design User roles & Project Structures - Schedule AH/JK working session (mid/late this week?)

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

Sales & Marketing

General

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

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

5. 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
   2. Aegir Johannsson
   3. Harald Schmitt
   4. Anthony Sullivan

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

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	Notes
  Transmittals	done	done	JK	Ready for final review
  File Handling	done	done	TN	Review by TN to see if anything else needs work
  User Management	done	started TN	open	Ready for AH/TN specification
  User Permissions	done	started TN	open	Spec. from JK done
  Classifications by Category	AH/TN	open	open	Concept defined
  Classifications Data Block	AH	open	open	Concept defined
  Nested Form Rework	done	open	open
  Incoming Transmittals	AH/TN	open	open
  Delete Transactions	done	open	JK	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)

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

Transmittals

1. Awaiting final review

File Handling

1. Final review of multi-file uploads - JK

2. Final check of JK review notes to make sure everything is complete - TN

User Management

1. See V2UserManagement for details

User Permissions

1. See V2UserManagement Permission Levels for details

Classifications by Category

1. This is the ability to have a category field in objects (docs, revs, tasks, users, etc.) which determines set of classification fields associated with an object

   1. E.g. docs with category Correspondence could have classifications sender, receiver, contract

   2. Docs with category Drawing could have classifications discipline, work type

2. Essentially this will be implemented with a many-to-many link table between classification_classes and the object's classificataion class

Nested Form Rework

1. TN has implemented transmittal new/update using nested form

2. This will allow a cancel when updating classifictation fields

3. The task is to re-factor the new/update to also use nested form screens for the following trnsactions:

   1. Document/Revision
   2. Tasks
   3. Users
   4. Other?

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

Main Issues

1. The Amazer server used to host the SoftXS Web Site and the Hydro Demo has problems:
   1. Performance varies between acceptably fast and unbearably slow

   2. When more than one person accesses the web site and/or the demo at the same time there are frequent Phusion Passenger errors, probably caused by running out of memory

2. We should therefore:
   1. How the web site and demo system on our own, more powerful server
   2. Learn more about the performance characteristic of Amazon EC2 servers
   3. Perhaps purchase a t1.micro server for a short time and see if paid for server are better

Server Setup

1. Setup 8-core Intel rack-mount server to replace existing zg-3 server - AH

   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 VM
      3. Web server VM 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 - AH

   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 - AH/TN

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

5. Buy AWS EC2 micro image for a year & see if performance is significantly better than free tier - AH

6. Complete implementation of Puppet-managed DNS for DMZ - AH

7. Monitoring prototype - AH

Deployment & Operations

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

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

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

4. Test VM-based V2 deployment on Ubuntu-based hosts - AH

   1. Currently implemented for VMs on FreeBSD

5. Implement additional deployment tasks: - AH

   1. Event daemon cronjobs
   2. Backup jobs
   3. Log rotation jobs