2,797 research outputs found
Transforming a Java Application in an Equivalent Web-services Based Application: Toward a Tool Supported Stepwise Approach
No full textMigration of legacy applications toward service-oriented systems is a hard task complicated by the lack of appropriate approaches and tools able to drive step by step a developer in the process. In this paper, an operational tools-based stepwise approach is proposed to transform Java applications in equivalent Web-service based applications. In each migration step a functionality of the target application is migrated in a Web service and the migration process stops when all the functionalities, one after the other, are migrated. Java tools and details on how to face practical problems involved in the migration task (e.g., wrapping, deployment and testing) are also presented. We conducted a case study in which the approach has been applied to a simple Java application. The case study indicates the applicability of the proposed approach and explains encountered problems and adopted solution
From objects to services: toward a stepwise migration approach for Java applications
No full textMigrating legacy applications toward service-oriented systems is a hard task complicated by the lack of appropriate approaches and tools. In this paper, a stepwise approach is proposed to migrate a Java application into an equivalent application composed of a set of Web services invoked by an orchestrator. In each migration step, a portion of the target application is identified and migrated into a Web service. In this approach, the role of testing is central since after each migration step the new service-oriented application is tested with the aim of checking `its equivalence` with the original version. An experiment based on four Java applications has been conducted to tune the approach and evaluate applicability and effort involved in the migration process. The obtained results confirm the viability of the proposed approach and highlight some encountered SOA migration difficulties
Are Heroes common in FLOSS projects?
No full textSeveral projects rely on one or more Heroes who are the only ones who understand and know certain critical parts of a system. Often Heroes are very useful in the economy of a project but, their presence can increase the risk of project failure if they decide to leave the project. For this reason, tools for measuring the amount of spread of knowledge within a team (i.e. the Truck factor) and identifying possible Heroes are welcomed. In this paper, we have implemented a tool to compute the Truck factor and identify Heroes in a project. To assess the applicability and usefulness of the tool we have applied it to 20 randomly selected FLOSS projects. Preliminary results are encouraging: the approach seems to be applicable and useful. We found that Heroes are common in the considered set of FLOSS projects and that the Truck factor is in general lo
Heroes in FLOSS projects: an explorative study
No full textIt is well recognized that the presence of Heroes, i.e., tireless developers who are the only ones who know certain critical parts of a system, can increase the risk of project failure, especially if these developers decide to leave the project. Instead, the relationship between Heroes and maintenance tasks is unknown because little investigated so far. In this paper, we first have implemented a tool to identify Heroes. Then, we have conducted an explorative study with 37 randomly selected open source projects to discover existing relationships between the presence of Heroes and the time required to implement change requests. Preliminary results show that: (i) Heroes are common in FLOSS projects and (ii) their presence seems to be beneficial because reduce the time to implement change request
AOP -> HiddenMetrics: a non-invasive approach to invasive software measurements
No full textNowadays, the quality of software is becoming more and more important. The software must be efficient, correct,
secure, flexible, reusable and adaptable just to cite few of wished characteristics. Therefore, to measure the software is an activity whose popularity and importance is increasing but, especially when related to dynamic aspects, it results very invasive and it poses serious constraints to its applicability, e.g., it needs the access to the source code or to adopt specific tools that need a high skill to be used.
Aspect-oriented programming provides the mechanisms for reducing the invasiveness necessary to measure the software, and therefore for widening the software measurement applicability. In this paper, we present an aspectoriented approach to software measurements and a supporting
framework
(Session 7) Case Study: Orbital Sciences Corporation: From Startup to Billion Dollar Company
No full textCarl Marchetto presents the business model for 25-year-old Orbital Sciences with some 3,200 employees. Marchetto focuses on the company\u27s activities, growth, customer needs, and their importance to Orbital. The Q&A round includes discussions of other topics of contemporary business interest
A concern-oriented framework for dynamic measurements
No full textEvolving software programs requires that software developers reason extit{quantitatively} about the modularity impact of several concerns, which are often scattered over the
system. To this respect, concern-oriented software analysis is rising to a dominant position in software development. Hence, measurement techniques play a fundamental role in
assessing the concern modularity of a software system. Unfortunately, existing measurements are still fundamentally module-oriented rather than concern-oriented. Moreover, th
e few available concern-oriented metrics are defined in a non-systematic and shared way and mainly focus on static properties of a concern, even if many properties can only be
accurately quantified at run-time. Hence, novel concern-oriented measurements and, in particular, shared and systematic ways to define them are still welcome. This paper pose
s the basis for a unified framework for concern-driven measurement. The framework provides a basic terminology and criteria for defining novel concern metrics. To evaluate the
framework feasibility and effectiveness, we have shown how it can be used to adapt some classic metrics to quantify concerns and in particular to instantiate new dynamic conc
ern metrics from their static counterparts
A Case Study-based Comparison of Web Testing Techniques applied to AJAX Web Applications
No full textAJAX is a recent technology used to develop rich and dynamicWeb applications. Differently from traditional Web applications, AJAX applications consist of a single page whose elements are updated dynamically in response to callbacks activated asynchronously by the user or by a server message. On the one hand, AJAX improves the responsiveness and usability of a Web application, but on the other hand, it makes the testing phase more difficult. In this paper, our state-based testing technique, developed to test AJAX-based applications, is compared to existing Web testing techniques, such as white-box and black-box ones. To this aim, an experiment based on two case studies has been conducted to evaluate effectiveness and test effort involved in the compared Web testing techniques. In particular, the capability of each technique to reveal injected faults of different fault categories is analyzed in detail. The associated effort was also measured. The results show that state-based testing is complementary to the existing Web testing techniques and can reveal faults otherwise unnoticed or hard to reveal with the other techniques
- …
