Differences between revisions 16 and 17
Deletions are marked like this. Additions are marked like this.
Line 109: Line 109:
 || '''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 || AH/TN || open || open || Ready for AH/TN specification ||
 || User Permissions || AH/TN || open || 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 || done || '''JK''' || Check all necessary transactions are present and there are no ''locking'' issues ||
 || '''Description'''                                  || '''Spec.''' || '''Coding''' || '''Review''' || '''Notes''' ||
 || [[#Transmittals|Transmittals]] || done || done || '''JK''' || Ready for final review ||
 || [[#File Handling|File Handling]] || done || done || '''TN''' || Review by TN to see if anything else needs work ||
 || [[#User Management|User Management]] || AH/TN || '''open''' || '''open''' || Ready for AH/TN specification ||
 || [[#User Permissions|User Permissions]] || AH/TN || '''open''' || '''open''' || Spec. from JK done ||
 || [[#Classifications by Category|Classifications by Category]] || AH/TN || '''open''' || '''open''' || Concept defined ||
 || [[#Classifications Data Block|Classifications Data Block]] || AH || '''open''' || '''open''' || Concept defined ||
 || [[#Nested Form Rework|Nested Form Rework]] || done || '''open''' || '''open''' || ||
 || [[#Incoming Transmittals|Incoming Transmittals]] || AH/TN || '''open''' || '''open''' || ||
 || [[#Delete Transactions|Delete Transactions]] || done || '''open''' || '''JK''' || Check all necessary transactions are present and there are no ''locking'' issues ||

=== Lower Priority Items ===

 1. Write ''Workflow & User Role'' working paper in preparation for working session - '''JK'''
 1. Write up requirements for Pöyry Uma Oya system (first V2 customer)
 1. Review to check if all back links & cancel buttons have been removed - '''AH/TN'''
 1. Implement display of audit trail (mainly for transmittal downloads) - '''TN'''
Line 122: Line 129:
Line 128: Line 136:

 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 & external users
 1. Ability to put users into ''org chart'' to allow delegation user management
Line 129: Line 144:
Line 130: Line 146:
Line 131: Line 148:
Line 132: Line 150:
Line 134: Line 153:

== Design & Specification ==

 1. Write ''Workflow & User Role'' working paper in preparation for working session - '''JK'''
 1. Write up requirements for Pöyry Uma Oya system (first V2 customer)
 1. Design of project management structures - ''low priority''
 1. Ensure that V2 features can be enabled/disabled via settings to allow us the ability to charge separately for individual features in the future
 1. Review if all necessary 'delete' transactions are completed - '''AH/TN'''
Line 143: Line 156:
== Review ==

 1. Review if all necessary 'delete' transactions are completed - '''AH/TN'''
 1. 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
       1. All users with logins will be registered in MAPS
    1. Ability to enable/disable internal & external users
    1. Ability to put users into ''org chart'' to allow delegation user management
 1. 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'''
 1. Prioritize list for implementing additional testing - '''AH/TN'''
 1. Implement additional testing - '''TN'''

V2 ToDo List

V2Master

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

V2 To Do - Summary

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

File Handling

  1. Final review of multi-file uploads - JK

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

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

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

User Permissions

Classifications by Category

Nested Form Rework

Incoming Transmittals

Delete Transactions

  1. Review if all necessary 'delete' transactions are completed - AH/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

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

Copyright 2008-2014, SoftXS GmbH, Switzerland