Software as a service

About: Software as a service is a research topic. Over the lifetime, 8514 publications have been published within this topic receiving 136177 citations. The topic is also known as: Service as a Software Substitute & SaaSS.

Detecting flooding based DoS attack in cloud computing environment using covariance matrix approach

Abstract: The internet is gaining a lot of importance day by day, especially with the emergence of cloud technology. This new technology has made a new computing service to end users that include, PaaS, SaaS. On the other hand, this technology was accompanied with some shortages. The most serious obstacle is the security challenges because of the cloud is characterized by computing resource sharing and multi-tenancy features and as a result flooding based denial of service attack has been observed. This effect on performance and quality of service on cloud. To overcome this security challenge, there are several methods to detect and prevent this kind of attack. Most of these approaches are using statistical and/or artificial intelligence methods.In this research paper a new model to detect flooding based DoS attack in cloud environment has been suggested consisting three phases. (1) The first-phase is to model the normal traffic pattern for baseline profiling and (2) the second phase is the intrusion detection processes and (3) finally prevention phase. The covariance Matrix mathematical model is used as detecting method. The phase (1) and (2) have been implemented in real test bed. From the result, it is proven that we can detect the flooding attack effectively.

Cloud Computing Standards: Where's the Beef?

Abstract: In this paper, cloud computing standards are discussed. The basic idea of cloud computing is simple: centralized service organizations maintain and support IT services, freeing users from nearly all operational and administrative burdens. These service organizations are often subdivided based on whether they provide software-as-a service, platform-as-a-service, and infrastructure as-a-service, but their need for standards appear similar. The biggest need is for evaluative standards that let customers assess the security and reliability of cloud vendors.

Effective Software Project Management

Abstract: Why another book on software project management? For some time, the fields of project management, computer science, and software development have been growing rapidly and concurrently. Effective support for the enterprise demands the merging of these efforts into a coordinated discipline, one that incorporates best practices from both systems development and project management life cycles. Robert K. Wysocki creates that discipline in this book--a ready reference for professionals and consultants as well as a textbook for students of computer information systems and project management. By their very nature, software projects defy a "one size fits all" approach. In these pages you will learn to apply best-practice principles while maintaining the flexibility that's essential for successful software development. Learn how to make the planning process fit the need * Understand how and why software development must be planned on a certainty-to-uncertainty continuum * Categorize your projects on a four-quadrant model * Learn when to use each of the five SDPM strategies--Linear, Incremental, Iterative, Adaptive, and Extreme * Explore the benefits of each strategic model and what types of projects it supports best * Recognize the activities that go into the Scoping, Planning, Launching, Monitoring/Controlling, and Closing phases of each strategy * Apply this knowledge to the specific projects you manage * Get a clear picture of where you are and how to get where you want to go

Applying the Tropos Methodology for Analysing Web Services Requirements and Reasoning about Qualities of Services

Abstract: The shift in software engineering from the design, implementation and management of isolated software elements towards a network of autonomous interoperable service is calling for a shift in the way software is designed. We propose the use of the agent-oriented methodology Tropos for the analysis of Web service requirements. We show how the Tropos methodology adapts to the case of Web services and in particular how it can be used to model quality of service requirements. We base the investigation on a representative case study in the retail industry.