Objectives


Given the trends in Social Networking and the issues of information overload, how do we enable the information worker to be efficient and productive? As the adoption of QEDWiki increases, a measurement for it's success will be how well it served as an answer to this question.

In order for these information workers to take control of their information processing, they need to be empowered with the tools necessary to create their own applications. Pertinent to the creation of QEDWiki, we assumed that:

Essentially, business professionals are applying do-it-yourself principles to application development. They are leveraging the pervasiviness of XML and lighter less complex aspects of the web-scripting renisance to create their own richer application user experiences.

The objective of the QEDWiki Framework is to address the painpoints of the information work and to enable them to rapidly build and deploy content rich applications on their own terms. Such painpoints include but are not limited tose depicted in the table below.

Painpoint
QEDWiki Objective
Application construction lifecycle is too costly and timely.
Reduce application development time and significantly reduce situations whereby:
  • Solution development time will not meet the time constraints of the project
  • Solution development time is longer than the life expectency of the solution and/or the orginal  requirements and characterics of the project.
Priority given to the development of applications (especially situational, short life apps) using current development methodologies is much too low.
Enable rapid development of short-lived situational and data centric applications
Business user productivity is leveraged by their dependance on IT resources and processes.
Empower information workers to construct and manage their own business applications.
Waterfall development process is too costly and no longer in-tune with fast-paced needs of the information worker.
Provide an iterative framework that allows collaborative development of real-time prototypes and applications.
Data overload obfuscates needed information, yielding worker inefficiencyEnable quick and easy access to data services when how they are needed.