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
  5. V2
     1. Design & Specification
     2. Review
     3. Coding
     4. Testing
  6. Infrastructure
     1. Server Setup
     2. 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

1. Complete Six-payments interface - DS

   1. Implement manual payments. For handling systems given away & systems paid by invoice

   2. Implement non-CHF currencies. Currently everything hard-coded to CHF
   3. Implement VAT handling. Policy is that one price charged and we pay the VAT for CH customers
   4. Implement receipt generation
   5. Implement allowing other users to pay for a system

   6. Consider implementing a payment system test mode for Cucumber testing

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

3. Implement skeleton for V2 deployment daemon - AH

4. Complete implementation of Questionnaire module - AH

5. Implement display of audit trail - AH

   1. Investigate Google analytics?

V2

Design & Specification

1. Define future V2 releases - AH/JK

   1. Prioritized list of next V2 features to implement
   2. Proposed releases:

      • R1 - Organizing & Sharing

      • R2 - Structured Collaboration

      • R3 - Project Management

      • R4 - Scheduling

2. Make final list of V2 features to fix/improve before release:

   • AH to supply list of recently updated items

   • AH to update JK v2p0 system (http://v2.softxs.ch/v2p0-jk) with latest software

   • JK to review V2UsabilityReview wiki page & own notes & compare against current software

   • JK to supply complete replacement for V2UsabilityReview wiki page (keeping TN notes)

   • AH/JK to discuss any complex or unsatisfactory items & set priorities

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

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

5. Design user roles as specified in V2UsabilityReview - AH/JK

6. Decision/design of incoming transmittals - AH/JK

7. Design of project management structures - low priority

8. Ensure that V2 features can be enabled/disabled via settings to allow us the ability to charge separately for individual features in the future

Review

1. Review proposed user management - JK

2. Transmittals - JK

   1. Front-end GUI
   2. Transmittal email

3. Final review of multi-file uploads - JK

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

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

Coding

1. User Management - TN

   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 & external users

   3. Ability to put users into org chart to allow delegation user management

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

Testing

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

2. Prioritize list for implementing additional testing - AH/TN

3. Implement additional testing - TN

Infrastructure

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