Sign Up Now
Get instant access to over 1 million+ study documents
OR
Already registered? click here to login
By creating your account, you agree to our terms of service, privacy policy and student honor code.
Software-as-A-Service
The purpose of the research done by Benlian and Hess (2011) was to examine software-as-a-service (SaaS) and see if it provides value to companies. There have been arguments that SaaS is already on the decline despite its newness. Most of these arguments come from those who feel that SaaS is not providing the value that it was designed to provide - mostly because of the difficulties with its deployment. With SaaS being so difficult, most companies end up spending too much on it. That can stop them from really getting value out of it. While they will get plenty of use from SaaS, the amount they spent based on the effort, time, and cost to set up and deploy SaaS can keep their value down. Benlian and Hess (2011) wanted to see the value that was being offered by SaaS in order to make determinations about SaaS' potential future in the IT industry.
The study was designed through the development of a research model (Benlian & Hess, 2011). The model was grounded in...
Then, 349 German IT executives were surveyed and the data from the surveys was analyzed (Benlian & Hess, 2011). The sample size was relatively small, but the design of the study was a strong one that was grounded in theory. The reasoned action theory addresses the idea that anything done has to be done after taking a look at the cost and benefit of that action (Benlian & Hess, 2011). The opportunities that are provided by SaaS would need to be greater than the risks involved with buying, implementing, and using it in order for SaaS to have value for the people (companies) that would purchase it for their IT needs (Benlian & Hess, 2011). If there was no value in SaaS, it would quickly die out in the marketplace.
The study was very valid. The main threats were not to the study, but to the adaptation and usage of SaaS itself. As for the study, there was no real threat…
References
Benlian, A. & Hess, T. (2011). Opportunities and risks of software-as-a-service: Findings from a survey of IT executives. Decision Support Systems, 52: 232-246.
Software Development Life Cycle Agile Software Development Agile software development is a popular software development process or methodology that has gained a lot of popularity in the recent years due to its effectiveness and ease of use. Firstly, it encourages collaboration and teamwork throughout the life cycle of development and this makes it easy to plan and implement. Agile software development is all about breaking a task into small chunks that make it
Software Development Life Cycle ( SDLC) Explain Requirement process ( in SDLC) in detail. Why is this exercise important? Requirements engineering is a fundamental activity in systems development and it is the process by which the requirements for software systems are identified, systematized and implemented and are followed through the complete lifecycle. Traditionally engineers focused on narrow functional requirements. Now it is being argued by Aurum and Wohlin (2005) that focusing only
Software Development Life Cycle Social Media Software Implementation Project Social media is an important aspect of every business today because it gives companies a unique chance to understand the customers better and to interact with them at a more personal level. A wide range of social networking tools are used by companies to attract customers to the products and services offered by the company and this makes social media software implementation essential
Software documentation is an integral part of the software development process. However, the process is often challenging because over the course of a software development project the scope can often change and evolve several times with updates and new builds. Despite the challenges that are presented in effectively documenting the development process, the documentation that is produced can serve as a valuable asset that can be used in future projects
On this aspect of agent-based SDLC performance, both approaches are limited in terms of their applicability and scalability. The reliance on heuristics can only go so far with the embedding of business, technical and organizational elements into the overall structure of an SDLC methodology (Kumar, Goyal, 2011). The reliance on an agent-based model fits well with the development of modules that are designed to align with these innately unquantifiable
Software Application Process for a Clinician Provider Order Entry (CPOE) system Software Application Process Clinician Provider Order Entry (CPOE) System The planning, customization, launch and continued use of a Clinician Provider Order Entry (CPOE) system in a local hospital forms the foundation of this analysis. The processes being used prior to the systems' planning and implementation are detailed to provide a basis of comparison of system contribution and performance. A timeline of the