Who will represent future end users and market parties?
Of course, one day in the future, end users will know the quality of the lot with certainty, depending upon the availability of all appropriate data.
Future end users can refer back to earlier Predictions associated with the particular Model in order to make more informed decisions.
We also describe current and future end-user services that our platform will support, including historical data retrieval, visualisation, processing and alarms.
Hence, although the solutions that they develop may satisfy specific requirements, it is impossible to guarantee the quality or the reusability of this software either for this user or for other developments by future end-user programmers.
Finally, we discuss how assistive robots could be designed considering the social context of the elderly and how to implicate the elderly as future end-users in the design process.
For this reason, the integration of the future end-users into the design process is all the more needed to get a continuous feedback and foster the usefulness and acceptability of the services.
Future end-user access to the workflow definitions and workflow engine will be integrated to the current web interface.
The involvement of stakeholders such as future system end users is a key success factor for Software Engineering (SE) in general, and for Requirements Engineering (RE) in particular [1].
But to succeed, they, others in the suborbital market, and others like SpaceX and Orbital in the commercial orbital market are being forced to develop new technologies and innovations that must lower the cost and increase the reliability of getting into space for any future market or end users.
This discussion concludes with several questions about the future of end-user programming for the World Wide Web, such as do authoring tools such as Yahoo!
