To this end, we report an empirical study on data flow bugs in business (BPEL) processes. Although some work has focused on the detection of control flow bugs, few studies have comprehensively and empirically investigated data flow bugs in business processes. The profits and performance of enterprises strongly depend on the soundness of their processes being bereft of control flow and data flow bugs. As a by-product of this study, a number of points for future improvement and innovations in existing workflow technology are identified, which are exclusively relevant for multi-tenant SaaS applications.Īn increasing number of service-based business processes are being developed with the booming of BPaaS (Business Process as a Service) in cloud computing. The comparative study shows that there is no single best strategy, and provides SaaS architects with support for making appropriate trade-off decisions when adopting a workflow customization strategy. The customization strategies are selected from an existing survey and the comparison criteria are derived from two essential characteristics of SaaS: it is (i) a business model aiming at “economies of scale” and (ii) a software delivery model with specific automation requirements. This paper analyzes and compares the quality implications of different business process customization strategies for multi-tenant SaaS applications. Run-time customization involves a wide range of software artifacts such as user interfaces, databases, web-services and business process or workflow definitions. To account for differences in tenant requirements, they have to support run-time customization. Multi-tenant Software-as-a-Service (SaaS) applications share a single runtime instance among multiple customer organizations (tenants). Experimental results show that our method is more effective than the traditional coverage-based technique in testing case priority. On this basis, this paper proposes a new prioritization method for regression test cases. By analyzing the dependences between activities, the modification effects of activities on the modified version of service-oriented workflow applications are calculated. Unfortunately, most regression test case prioritization studies in service-oriented workflow applications neglect the use of activity dependency, which is an important factor that affects test case prioritization. As a result, those applications need more precise scheduling to run test cases that can detect faults earlier. Web services are orchestrated by service-oriented workflow applications to provide different functions, especially in cloud-based mobile systems. Existing prioritization methods prioritize test cases in different application environments according to different metrics (for example, statement coverage, and path coverage). Test case prioritization is a method to prioritize test cases to improve the testing efficiency of service-oriented workflow applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |