• V2Release1

V2 Release R1

V2Master | V2RoadMap | V2ReleaseMVA | V2Release1 | V2Release2 | V2Release3 | V2Release4 | V2Release5

• Contents

  1. V2 Release R1
  2. Planned Completion
  3. Release Goals
  4. User Features
  5. Demo Systems
  6. Technical Features
  7. Deployment Features

Planned Completion

1. Deadline: ASAP

Release Goals

1. Compelling

   1. Feature set & configuration data appropriate for:

      1. Proposal preparation

      2. Smaller projects & engineering collaboration

2. Scalable

   1. No application performance issues, even on larger systems

   2. On-line sales ready & proven

   3. Deployment & operations scalable & proven

User Features

1. Cloning items [PBI-0192]

2. Document & Task Codes: Automatic increment of sequence number part [PBI-0193]

3. Object links: documents, revisions, tasks, transmittals, dossiers ** [PBI-0055]

4. Unattached notes, with attached files(?) [PBI-0167]

5. Admin able to configure home page [PBI-0113]

6. Minor corrections to Sorting & Filtering - JK to supply requirements [PBI-0194]

7. Hidden/shared notes (low priority) [PBI-0133]

8. Rework page titles to use sub-headings, as suggested by RB (low priority) [PBI-0195]

Demo Systems

1. Rework Hydro Demo configuration to make use of object types JK [PBI-0147]

2. Complete Project Proposal configuration [PBI-0178]

Technical Features

1. File versioning

2. DB record versioning ** (AH delaying this increases long-term support risk) [PBI-0058]

3. Event log [PBI-0141]

4. Implement performance monitoring (in application code or via parsing of log files?) [PBI-0196]

5. Test system response with: [PBI-0197]

   1. Large data sets
   2. Large number of simultaneous transactions

Deployment Features

1. Automated deployment ?