eBooks
Issue link: https://read.uberflip.com/i/1067336
2019 Buyer's Guide to Accounting and Financial So ware 5 So ware Delivery Models at a Glance On-premises so ware Hosted so ware Cloud computing/SaaS Application development Developed for the 1980s innovation of client/server, Windows-based computing. Runs on-premises so ware in a third-party data center and adds a layer for online delivery (e�g� Citrix)� Developed from the ground up for online delivery� Deployment Installed on the customer's own hardware. Installed on a third-party vendor's hardware – delivered via an internet connection� A single vendor both develops and operates the applications – delivered via an internet connection� Implementation Usually 3-6 months. Usually 3-6 months. Usually 6-12 weeks. Customization Can be expensive and time consuming. Risk of "dead-end" customizations that break when new versions of so ware are released. Same as on-premises. Clickable configurations replace costly customization and do not break with application upgrades� User interface Designed for Windows machines in a client/server environment, and not always optimized for ease of use and learning� Same as on-premises, with an extra layer for presentation (e�g� Citrix)� Designed from scratch for the Web environment, to match the paradigm users expect and are familiar with. Built from the ground up to be easy to use on multiple devices, with multiple operating systems� Upgrades 12+ months� Same as on-premises. Generally quarterly. Integration Difficult and expensive. Same as on-premises. Readily available via application programming interfaces (APIs). IT Support Generally provided by the customer� Same as on-premises, but complicated by existence of third-party hosting vendor. Generally included in the package from vendor� Multi-tenancy Not multi-tenant. Each instance of the application requires its own hardware/ so ware/networking environment� Same as on-premises. Applications are designed to be multi-tenant. Hardware requirements Requires a specific operating environment� Same as on-premises. Users typically limited to Windows only. Delivered via a Web browser so generally operating system- and browser- agnostic� Accountability Vendor is responsible for the so ware, IT department is responsible for operations� Hosting provider and so ware developer are two different organizations so accountability is complex� IT department is still responsible for operations� One vendor provides end-to-end solution so accountability is inherent�