• V2ReleaseMVA

V2 Release MVA

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

• Contents

  1. V2 Release MVA
  2. Planned Completion
  3. Release Goals
  4. User Features
  5. Technical Features
  6. Deployment Features

Planned Completion

1. When?

Release Goals

1. Attractive

   1. Appropriate initial feature set

   2. Nice look & feel

   3. Rework transactions & details based on reviewer feedback

2. Stable

   1. A bug-free & stable system

   2. Adequate performance for smaller systems

   3. Deployment & operational procedures still underdevelopment development

User Features

1. Usability review of the entire system, looking for holes and inconsistencies

   • See V2UsabilityReview

2. Transmittals (outgoing)

3. User role configuration (assign user roles using business terminology)

4. Generic classifications based on object type

5. User management, including user classification, e.g. project organisation

6. Checkbox of drawing list (set by default) to show only the latest revisions [PBI-0189]

7. Incoming Transmittals (AH Only if required for Uma Oya. Would like to delay this) [PBI-0153]

   1. Transmittals that are not sent, but simply marked as received

Technical Features

1. File uploading (multiple file, single page)

2. Width of pull-down menus in classification fields and folders

3. Rework documents, tasks & user to make use of nested forms

4. Printable drawing & task lists [PBI-0180]

5. Get RSpec tests working again [PBI-0190]

6. Get Cucumber tests working again [PBI-0191 Hold]

Deployment Features

1. Automated deploy of V2 applications to a relative path