50,545 research outputs found

    The financial clouds review

    No full text
    This paper demonstrates financial enterprise portability, which involves moving entire application services from desktops to clouds and between different clouds, and is transparent to users who can work as if on their familiar systems. To demonstrate portability, reviews for several financial models are studied, where Monte Carlo Methods (MCM) and Black Scholes Model (BSM) are chosen. A special technique in MCM, Least Square Methods, is used to reduce errors while performing accurate calculations. The coding algorithm for MCM written in MATLAB is explained. Simulations for MCM are performed on different types of Clouds. Benchmark and experimental results are presented for discussion. 3D Black Scholes are used to explain the impacts and added values for risk analysis, and three different scenarios with 3D risk analysis are explained. We also discuss implications for banking and ways to track risks in order to improve accuracy. We have used a conceptual Cloud platform to explain our contributions in Financial Software as a Service (FSaaS) and the IBM Fined Grained Security Framework. Our objective is to demonstrate portability, speed, accuracy and reliability of applications in the clouds, while demonstrating portability for FSaaS and the Cloud Computing Business Framework (CCBF), which is proposed to deal with cloud portability

    Executive Authority to Reform Health: Options and Limitations

    Get PDF
    Presidential power has provoked increasingly vigorous debate since the turn of this century. In recent years, scholars and lawyers have been grappling with how Congress\u27s dictates may limit the President\u27s Commander-in-Chief power to detain enemy combatants at Guantanamo Bay, to fight wars abroad, and to conduct intelligence activities at home. But policymakers have not yet explored the many possibilities for invoking the President\u27s Take Care power to change health care policy. This paper explores the scope and limits of President Barack Obama\u27s ability to invoke his executive authority to reform health care. Specifically, it identifies ways the Obama Administration can use directives to: (1) expand Medicaid and SCHIP coverage through section 1115 waivers; (2) test quality initiatives through Medicare demonstration authority; (3) expand health information technology; (4) allow drug reimportation and experiment with contracting power under Medicare; (5) enhance patient protections and private coverage requirements; (6) lift coverage restrictions on Medicaid and SCHIP; and (7) build on the health insurance program for federal employees. Consistent with the mission of the Legal Solutions in Health Reform project, this paper does not endorse a particular policy. Instead of recommending what, it explains how

    Four Easy Steps to a Fiscal Train Wreck: The Florida How-To Guide

    Get PDF
    This report is the second of three reports that address the fiscal conditions of other states, explores the factors that explain the conditions, and the likely future trends. FRC Report 13

    Legal Solutions in Health Reform: Executive Authority to Reform Health: Options and Limitations

    Get PDF
    Examines which healthcare reforms the president can implement without congressional approval and how. Identifies options for promoting and directing agency actions on specific policy goals, as well as legal, budgetary, and legislative constraints

    Interoperability standards for cloud architecture

    Get PDF
    Enabling cloud infrastructures to evolve into a transparent platform raises interoperability issues. Interoperability requires standard data models and communication technologies compatible with the existing Internet infrastructure. To reduce vendor lock-in situations, cloud computing must implement common strategies regarding standards, interoperability and portability. Open standards are of critical importance and need to be embedded into interoperability solutions. Interoperability is determined at the data level as well as the service level. Relevant modelling standards and integration solutions shall be analysed in the context of clouds

    Study of Tools Interoperability

    Get PDF
    Interoperability of tools usually refers to a combination of methods and techniques that address the problem of making a collection of tools to work together. In this study we survey different notions that are used in this context: interoperability, interaction and integration. We point out relation between these notions, and how it maps to the interoperability problem. We narrow the problem area to the tools development in academia. Tools developed in such environment have a small basis for development, documentation and maintenance. We scrutinise some of the problems and potential solutions related with tools interoperability in such environment. Moreover, we look at two tools developed in the Formal Methods and Tools group1, and analyse the use of different integration techniques

    Two ways to Grid: the contribution of Open Grid Services Architecture (OGSA) mechanisms to service-centric and resource-centric lifecycles

    Get PDF
    Service Oriented Architectures (SOAs) support service lifecycle tasks, including Development, Deployment, Discovery and Use. We observe that there are two disparate ways to use Grid SOAs such as the Open Grid Services Architecture (OGSA) as exemplified in the Globus Toolkit (GT3/4). One is a traditional enterprise SOA use where end-user services are developed, deployed and resourced behind firewalls, for use by external consumers: a service-centric (or ā€˜first-orderā€™) approach. The other supports end-user development, deployment, and resourcing of applications across organizations via the use of execution and resource management services: A Resource-centric (or ā€˜second-orderā€™) approach. We analyze and compare the two approaches using a combination of empirical experiments and an architectural evaluation methodology (scenario, mechanism, and quality attributes) to reveal common and distinct strengths and weaknesses. The impact of potential improvements (which are likely to be manifested by GT4) is estimated, and opportunities for alternative architectures and technologies explored. We conclude by investigating if the two approaches can be converged or combined, and if they are compatible on shared resources
    • ā€¦
    corecore