Changes

2) poor user experience (UX) is the single complaint that supports the current  " . . . not another spreadsheet!" cultural.  I have provided a breakthrough solution, ActiveX object embedded spreadsheets that look and feel like mature, full screen multi-color database forms, validate their inputs, navigate through records and automatically send their data to any drive location.

2) poor user experience (UX) is the single complaint that supports the current  " . . . not another spreadsheet!" cultural.  I have provided a breakthrough solution, ActiveX object embedded spreadsheets that look and feel like mature, full screen multi-color database forms, validate their inputs, navigate through records and automatically send their data to any drive location.

3) Database / Data Mangement practices and capability are insufficient to get to the next level.  To understand and build strategies upon data collections and models based on the possible outputs is a widespread issue.  Folks cannot "see" the many ways in which these systems can help.  Immersing some CS expertise in PHAC will organically change this limitation as that understanding  begins to take hold in the community.

3) Database / Data Mangement practices and capability are insufficient to get to the next level.  To understand and build strategies upon data collections and models based on the possible outputs is a widespread deficit.  Folks cannot "see" the many ways in which these systems can help.  Immersing some CS expertise in PHAC will organically change this limitation as that understanding  begins to take hold in the community.

4) Requirements Mangement is not being practiced at a level that will ensure the systems built will not "loose their way . . . " or that negotiations on where to focus the next increment of improvement will go smoother costing less time.  Delivery quality metrics are no possible when there is no agreed base of deliverables and expectations no how they will be  measured.  Without a proper foundation, quality measures will be regarded as a "claim" made by "the other side".  These relationships are important, important enough to protect with requirements.  Time, frustration, lack of direction and insecurity in deliveries are all part of a world without requirements defined.

4) Requirements Mangement is not being practiced at a level that will ensure the systems built will not "loose their way . . . " or that negotiations on where to focus the next increment of improvement will go smoother costing less time.  Delivery quality metrics are no possible when there is no agreed base of deliverables and expectations no how they will be  measured.  Without a proper foundation, quality measures will be regarded as a "claim" made by "the other side".  These relationships are important, important enough to protect with requirements.  Time, frustration, lack of direction and insecurity in deliveries are all part of a world without requirements defined.