Document Case
Autor: jon • November 23, 2011 • Study Guide • 404 Words (2 Pages) • 1,415 Views
Dennis: document it down, whether it has been validated with the vendors. Fact is not supporting preference scoring.
Aizuddin: There is a line by line item in the demo. Facts precedes preferential.
David: Usability aspect is big in this project.
Ramly: We need to know what we want. Need to find a baseline.
Mak: Baselining to be agreed. With Kah Chai. Question for email – do you want to work offline.
Clarify what can or cannot do. And see whether it change the scoring.
Is single experience important?
2 set of users, full web or just client, or both.
Aizuddin: can use Aventail takeup rate as a percentage of people using client based email.
Dennis: As Sime Darby, we need to set a standarf of what we use.
Web based accessibility, device independent.
Email will be client based as primary. What can be done with Google using client.
Decision on portal is required. If there is no dependency then we can take it out of the suite.
Lawrence: We need to know what is the endpoint solution.
Is integration more important or not? What is the advantage of having the link between Sharepoint and other Microsoft products. Is it out of box or need to customizable.
Transformational aspects for each part.
Cost at the end of the day.
Dennis: document it down, whether it has been validated with the vendors. Fact is not supporting preference scoring.
Aizuddin:
...