A Proactive Approach to Intrusion Detection in Cloud Software as a Service

Cloud computing environment is very much malicious intrusion prone hence cloud security is very vital. Existing network security mechanisms face new challenges in the cloud such as DDOS attacks, virtual machine intrusion attacks and malicious user activities. This chapter includes brief introduction about cloud computing, concept of virtualization, cloud security, various DDOS attacks, tools to run these attacks & various techniques to detect these attacks, review of threshold methods used for detection of DDOS attacks & abnormal network behavior and proposed dynamic threshold based algorithmic approach. Although various cloud security measures are prevailing to avoid virtual machine attacks and malicious user activities but these are not foolproof. Hence, new security methods are required to increase users' level of trust in clouds. By scrubbing traffic at major Internet points and backbone connection, a defense line is created for mitigation of DDOS attacks. Dynamic threshold algorithm based approach is proposed as a proactive approach to detect DDOS attacks for achieving secure cloud environment.

Applicability of Lehman Laws on Open Source Evolution

Software evolution is the essential characteristic of the real world software as the user requirements changes software needs to change otherwise it becomes less useful. In order to be used for longer time period, software needs to evolve. The software evolution can be a result of software maintenance. In this chapter, a study has been conducted on 10 versions of GLE (Graphics Layout Engine) and FGS (Flight Gear Simulator) evolved over the period of eight years. An effort is made to find the applicability of Lehman Laws on different releases of two softwares developed in C++ using Object Oriented metrics. The laws of continuous change, growth and complexity are found applicable according to data collected.

Agile Enablers and Adoption Scenario in Industry Context

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.

Designing and Implementing an Innovation Management System in Young Academic Institutions Using Agile Methodology

This chapter proposes the use of agile methodology in designing the innovation management system in young academic institutes. Technology innovations from most universities and research institutes originate out of chaos. As a result, it is difficult to associate structure to its management. While there have been many social science research methodology based studies on this subject under the broad umbrella of “Innovation and Technology Management”, there is usually an absence of well defined process to help young academic institutions to manage their intellectual property better. There is a strongly desired need to associate a clearly articulated structure for translation of ideas into technology innovations that will help young academic institutes to inculcate research in students and faculties and would help identify the best commercial application of technology innovations. Agile methodologies are best suited to be adopted in the academic scenario as rapidly changing environment of academic institutes can be easily handled using agile methodology. The aim of this chapter is to produce an evolutionary advance practical innovation management process for academic institutes out of this chaos to inculcate research in students and faculties using agile methodologies.

The MFC Cybersecurity Model Extension and Diagnostic toward a Depth Measurement

This chapter presents a quantitative security risk management cybersecurity measure namely the Mean Failure Cost (MFC). We illustrate it to quantify the security of an e-Learning application while taking account of its respective stakeholders, security requirements, architectural components and the complete list of security threats. Moreover, in the mean time, security requirements are considered as appropriate mechanisms for preventing, detecting and recovering security attacks, for this reason an extension of the MFC measure is presented in order to detect the most critical security requirements to support the quantitative decision-making. Our focus is widespread to offer a diagnostic of the non secure system's problems and a depth insight interpretation about critical requirements, critical threats and critical components. This extension is beneficial and opens a wide range of possibilities for further economics based analysis. Also this chapter highlights the security measures for controlling e-Learning security problems regarding the most critical security requirements.

Communication and Awareness Patterns of Distributed Agile Teams

Agile methods emphasize on team's collaboration and so does the requirements engineering process. But how do agile teams collaborate with their geographically distributed counter parts to accomplish requirements related activities? Although, proved to be flexible and dynamic it needs to conduct more empirical investigation to identify the collaboration patterns of distributed agile teams. Therefore, in this chapter collaboration patterns of geographically distributed agile teams are identified in terms of reported communication (defined as information exchange) among team members and their awareness (defined as knowledge about each other) of each other. A multiple case study method is used in this chapter to study the geographically distributed agile teams in four IT organizations. Though, some of the findings revealed several patterns are corroborating the previous results available in literature. However, some of the patterns identified in this chapter are specific to distributed agile teams. For instance, the chapter identifies that high awareness among agile teams leads to more communication. Implications for research and software industry are discussed and future research directions are also provided.

Lean Manufacturing to Lean IT

Lean methodology is an improvement philosophy, an expansion of Lean manufacturing and lean principles to the management of Service and Information Technology industries. It articulates how waste can be minimal at Software Development Process (SDP) which begins from feasibility study and ends till the product is delivered to the customer. In today's competitive world throughout all the industries emphasis is on product's quality within the time constraints. To gear up with the market demand Lean improvement concepts is introduced in (information technology) IT industry. Lean IT is the translation of lean manufacturing practices applicable to the Software Development life cycle (SDLC). It works like a business model and oriented towards the principles that focuses on the non value added activities. This chapter will present how lean methodologies and principles works in service industries to deliver the best quality products. Although Lean concept is traditionally been used in manufacturing industries; but nowadays it is adapted by Services companies with the aim of improving their processes and enhance customer satisfaction.

Legacy Systems towards Aspect-Oriented Systems

Evolution and maintainability of legacy systems is all time attention drawing subject for researchers and especially practitioners. Discovering the crosscutting concerns and separating it from core functionalities of a software system may help in evolution of the legacy systems. Aspect-oriented software development (AOSD) tries to achieve the goal. AOSD is new programming paradigm which helps to bring in modularity in the program by writing the crosscutting concerns in the form of ‘aspects'. Modularity brings comprehensibility and hence maintainability of the software system. Tools and techniques, which aid in identifying the crosscutting concerns in such systems and refactoring them into aspects, are needed to apply aspect-oriented techniques to legacy systems at use in industry. This chapter aims to identify issues, problems and approaches used in the migration from legacy systems to aspect-oriented software system.

The Role of Business Process Reengineering in the Modern Business World

This chapter reveals the role of business process reengineering (BPR) in the modern business world, thus illustrating the theoretical and practical concept of BPR, the applications of BPR, the drivers of BRR (in terms of internal drivers and external drivers), the critical success factors of BPR (i.e., egalitarian leadership, collaborative working environment, top management commitment, supportive management, information technology, change management, project management, and cross-functional coordination), the implementation of BPR, and BPR software tools. BPR is a systematic approach to helping an organization analyze and improve its processes in digital age. BPR is a continuum of change initiatives in order to deliver better business performance standards through establishing sustainable process capability in modern organizations. BPR has become a popular tool to dealing with rapid technological and business change in the global competitive environment. Applying BPR will greatly improve business performance and reach business goals in global business.

A Cross-Platform Architecture with Intelligent Agents for Dynamic Processes and Services Composition

To meet business demands, enterprise software systems are required to be more dynamic, flexible and adaptive. Business processes must often be context-aware. Things get complicated when enterprise software systems, after a decade of evolution, comprise heterogeneous platforms and different technological stacks. This chapter presents the design and implementation of a cross-platform architecture with intelligent agents for dynamic business rules, process flows and services composition. The architecture includes an Enterprise Service Bus for service integration. Service agents are used to handle services. A Central Intelligent Agent that contains a Prolog-style rule-based engine is designed to execute business rules and processes. These agents are implemented in both Java and COBOL. Business process flows are completely rule- and context-driven. The services and components for the business processes are dynamically constructed. The proposed architecture and programming model enables fast prototyping and rapid development in an agile development process across different platforms.