Biomedical Engineering Reference
In-Depth Information
among these is the integration of user accounts with users' Windows
network ID and passwords, as well as integration with the browser, that is
toolbar extensions. However, at that time Pfi zer's standard desktop was
based around Internet Explorer 6 and such browser extensions would have
required bespoke development. This highlights the confl icts we often see
between the rapidly moving external world, where technologies are
evolving at a rapid pace, and the internal world where technologies move
slower [18]. Finally, this experiment highlighted that the utilisation of this
service within the enterprise requires integration with internal systems in
ways not required on the web. On the internet, web pages are bookmarked
via a browser button or a scriptlet added to the browser links toolbar. This
works well in this environment, but within the enterprise users often want
to store links to other content, such as documents within content
management systems. In this case, the URL for these documents is often not
displayed in the browser toolbar but rather accessed via a right mouse click
or complex Javascript (or even Flash) functionality. At best, capturing these
bookmarks can be achieved through a manual cut and paste; additional
complexity that is far from ideal for users. Given these limitations it was
decided that if social bookmarking was to be developed as a production
service it would require signifi cant development of the Scuttle codebase,
development of browser extensions and potentially changes to the user
interface of a number of document management systems.
13.2.5 Production deployment phase
At this point in the FLOSS assessment framework, the value of a
collaboration tool has been proven and the requirements are well
understood. Here, in this phase, the production solution is selected and
deployed. Successful usage patterns identifi ed in the previous phases are
used to promote the software into the business and drive adoption. New
usage patterns will continue to emerge and these need to be captured and
utilised to continue to promote the system. At the same time, the wider
usage of the web site, service or tool may highlight areas were development/
extension of the capability is required.
Obviously one of the critical decisions at this stage is to determine
whether the software explored within earlier Discovery and Proof of
Concept phases is suitable to go forward into a production environment.
In taking this decision, each potential tool must be assessed with respect
to a standard capability requirements document as well as any other
factors that infl uence future support and development of the system. Up to
Search WWH ::
Custom Search