Data Mining Practical Machine Learning Tools and Techniques

National Institute of Standards and Technology における超伝導研究及び生活

http://emamispnu.persiangig.com/Projects/Cloud%20Computing/science_2.pdf

Review: A survey on security issues in service delivery models of cloud computing

From the Book:
“Clean code that works” is Ron Jeffries’ pithy phrase. The goal is clean code that works, and for a whole bunch of reasons:
Clean code that works is a predictable way to develop. You know when you are finished, without having to worry about a long bug trail.Clean code that works gives you a chance to learn all the lessons that the code has to teach you. If you only ever slap together the first thing you think of, you never have time to think of a second, better, thing. Clean code that works improves the lives of users of our software.Clean code that works lets your teammates count on you, and you on them.Writing clean code that works feels good.But how do you get to clean code that works? Many forces drive you away from clean code, and even code that works. Without taking too much counsel of our fears, here’s what we do—drive development with automated tests, a style of development called “Test-Driven Development” (TDD for short). 
In Test-Driven Development, you:
Write new code only if you first have a failing automated test.Eliminate duplication.

Two simple rules, but they generate complex individual and group behavior. Some of the technical implications are:You must design organically, with running code providing feedback between decisionsYou must write your own tests, since you can’t wait twenty times a day for someone else to write a testYour development environment must provide rapid response to small changesYour designs must consist of many highly cohesive, loosely coupled components, just to make testing easy

The two rules imply an order to the tasks ofprogramming:
1. Red—write a little test that doesn’t work, perhaps doesn’t even compile at first
2. Green—make the test work quickly, committing whatever sins necessary in the process
3. Refactor—eliminate all the duplication created in just getting the test to work


Red/green/refactor. The TDD’s mantra.

Assuming for the moment that such a style is possible, it might be possible to dramatically reduce the defect density of code and make the subject of work crystal clear to all involved. If so, writing only code demanded by failing tests also has social implications:
If the defect density can be reduced enough, QA can shift from reactive to pro-active workIf the number of nasty surprises can be reduced enough, project managers can estimate accurately enough to involve real customers in daily developmentIf the topics of technical conversations can be made clear enough, programmers can work in minute-by-minute collaboration instead of daily or weekly collaborationAgain, if the defect density can be reduced enough, we can have shippable software with new functionality every day, leading to new business relationships with customers


So, the concept is simple, but what’s my motivation? Why would a programmer take on the additional work of writing automated tests? Why would a programmer work in tiny little steps when their mind is capable of great soaring swoops of design? Courage.
Courage
Test-driven development is a way of managing fear during programming. I don’t mean fear in a bad way, pow widdle prwogwammew needs a pacifiew, but fear in the legitimate, this-is-a-hard-problem-and-I-can’t-see-the-end-from-the-beginning sense. If pain is nature’s way of saying “Stop!”, fear is nature’s way of saying “Be careful.” Being careful is good, but fear has a host of other effects:
Makes you tentativeMakes you want to communicate lessMakes you shy from feedbackMakes you grumpy

None of these effects are helpful when programming, especially when programming something hard. So, how can you face a difficult situation and:
Instead of being tentative, begin learning concretely as quickly as possible.Instead of clamming up, communicate more clearly.Instead of avoiding feedback, search out helpful, concrete feedback.(You’ll have to work on grumpiness on your own.) 

Imagine programming as turning a crank to pull a bucket of water from a well. When the bucket is small, a free-spinning crank is fine. When the bucket is big and full of water, you’re going to get tired before the bucket is all the way up. You need a ratchet mechanism to enable you to rest between bouts of cranking. The heavier the bucket, the closer the teeth need to be on the ratchet.

The tests in test-driven development are the teeth of the ratchet. Once you get one test working, you know it is working, now and forever. You are one step closer to having everything working than you were when the test was broken. Now get the next one working, and the next, and the next. By analogy, the tougher the programming problem, the less ground should be covered by each test.

Readers of Extreme Programming Explained will notice a difference in tone between XP and TDD. TDD isn’t an absolute like Extreme Programming. XP says, “Here are things you must be able to do to be prepared to evolve further.” TDD is a little fuzzier. TDD is an awareness of the gap between decision and feedback during programming, and techniques to control that gap. “What if I do a paper design for a week, then test-drive the code? Is that TDD?” Sure, it’s TDD. You were aware of the gap between decision and feedback and you controlled the gap deliberately.

That said, most people who learn TDD find their programming practice changed for good. “Test Infected” is the phrase Erich Gamma coined to describe this shift. You might find yourself writing more tests earlier, and working in smaller steps than you ever dreamed would be sensible. On the other hand, some programmers learn TDD and go back to their earlier practices, reserving TDD for special occasions when ordinary programming isn’t making progress.

There are certainly programming tasks that can’t be driven solely by tests (or at least, not yet). Security software and concurrency, for example, are two topics where TDD is not sufficient to mechanically demonstrate that the goals of the software have been met. Security relies on essentially defect-free code, true, but also on human judgement about the methods used to secure the software. Subtle concurrency problems can’t be reliably duplicated by running the code.

Once you are finished reading this book, you should be ready to:
Start simplyWrite automated testsRefactor to add design decisions one at a time

This book is organized into three sections.
An example of writing typical model code using TDD. The example is one I got from Ward Cunningham years ago, and have used many times since, multi-currency arithmetic. In it you will learn to write tests before code and grow a design organically.An example of testing more complicated logic, including reflection and exceptions, by developing a framework for automated testing. This example also serves to introduce you to the xUnit architecture that is at the heart of many programmer-oriented testing tools. In the second example you will learn to work in even smaller steps than in the first example, including the kind of self-referential hooha beloved of computer scientists.Patterns for TDD. Included are patterns for the deciding what tests to write, how to write tests using xUnit, and a greatest hits selection of the design patterns and refactorings used in the examples.

I wrote the examples imagining a pair programming session. If you like looking at the map before wandering around, you may want to go straight to the patterns in Section 3 and use the examples as illustrations. If you prefer just wandering around and then looking at the map to see where you’ve been, try reading the examples through and refering to the patterns when you want more detail about a technique, then using the patterns as a reference.

Several reviewers have commented they got the most out of the examples when they started up a programming environment and entered the code and ran the tests as they read.

A note about the examples. Both examples, multi-currency calculation and a testing framework, appear simple. There are (and I have seen) complicated, ugly, messy ways of solving the same problems. I could have chosen one of those complicated, ugly, messy solutions to give the book an air of “reality.” However, my goal, and I hope your goal, is to write clean code that works. Before teeing off on the examples as being too simple, spend 15 seconds imagining a programming world in which all code was this clear and direct, where there were no complicated solutions, only apparently complicated problems begging for careful thought. TDD is a practice that can help you lead yourself to exactly that careful thought.

Test Driven Development: By Example

(1991). Soft Systems Methodology in Action. European Journal of Information Systems: Vol. 1, No. 3, pp. 215-216.

https://link.springer.com/content/pdf/10.1057%2Fejis.1991.37.pdf

Soft Systems Methodology in Action

Software Process Maturity and the Success of Free Software Projects The UID Approach -- the Balance Between Hard and Soft Methodologies Agile Software Development at Sabre Holdings Workflow Management System in Software Production & Maintenance Architecture of Parallel Spatial Data Warehouse: Balancing Algorithm and Resumption of Data Extraction Data Modelling with UML 20 Usability of UML Modelling Tools On Some Problems with Modelling of Exceptions in UML The ISMS Business Environment Elaboration Using a UML Approach Preliminary Analysis of the Effects of Pair Programming and Test-Driven Development on the External Code Quality Codespector -- a Tool for Increasing Source Code Quality Software Complexity Analysis for Multitasking Systems Implemented in the Programming Language Software Process Maturity and the Success of Free Software Projects The UID Approach - the Balance Between Hard and Soft Methodologies Agile Software Development at Sabre Holdings Workflow Management System in Software Production & Maintenance Architecture of Parallel Spatial Data Warehouse: Balancing Algorithm and Resumption of Data Extraction Data Modeling with UML 20 Usability of UML Modeling Tools On Some Problems with Modelling of Exceptions in UML The ISMS Business Environment Elaboration Using a UML Approach Preliminary Analysis of the Effects of Pair Programming and Test-Driven Development on the External Code Quality Codespector -- a Tool for Increasing Source Code Quality Software Complexity Analysis for Multitasking Systems Implemented in the Programming Language

Software engineering : evolution and emerging technologies

Introduction The goal of the paper is to present that aspect-oriented security provides very powerful mechanisms which could enhance container managed security. Security of container based systems usually depends on security mechanisms provided by containers in which the components run. The security functionality of containers is often limited and hard to modify. Aspect-oriented programming (AOP) allows weaving a security aspect into a component based application providing additional security functionality or introducing completely new security mechanisms. Implementation of security with AOP is a flexible method to develop separated, extensible and reusable pieces of code called aspects. In this paper we discuss some specific security solutions based on Java 2 Enterprise Edition (J2EE) architecture [1] and JBoss 3.0 application server [2], aspect-oriented programming with AspectJ 1.1 [3], Java Authentication and Authorization Service API (JAAS) [4] and Resource Access Decision Facility (RAD) [5]. First, the security requirements in component based systems have been discussed. Next, container managed and aspect-oriented security mechanisms are presented in more details. Then, to demonstrate and compare techniques of implementation of different security mechanisms we will use a simplified pseudo-banking application (written with EJB).

Comparison Study of Aspect-oriented and Container Managed Security

Chapter 1, Evolution of IT-enhanced Healthcare: from Telemedicine to e-Health, introduces the concept of telemedicine, including definitions and requirements of telemedical systems. The evolution of contemporary telemedical systems and challenges faced by future technologies are also shown. Additionally, this chapter reviews speciality-specific applications, including formal and legal aspects of telemedicine as well as its acceptance among users. An important item is the cost/benefit analysis of telemedical services. Chapter 2, Access Technologies in Telecare, overviews access telecommunication technologies. Basic requirements for such communications are considered, both in the hospital-to-patient scenario and the hospital-to-hospital scenario. The available and emerging solutions are also briefly presented. Chapter 3, Internet Technologies in Medical Systems, presents the requirements and architectures of Internet-based medical systems, with focus on Internet telemedical services, Web services and portal technologies. The next-generation point-of-care information systems are also described and the shift in the methodology associated with medical systems to suit new software architectures is analyzed. As a case study, the TELEDICOM system for collaborative teleradiology is presented. Chapter 4, Security and safety of Telemedical Systems, describes the requirements related to this important area, analyzing them in the context of legal acts affecting the security of e-medical systems. Subsequently, security system architecture modelling and techniques for securing e-medical systems are described. Chapter 5, Wireless systems in e-Health, focuses on modern wireless technologies. Security aspects and wireless interference issues are discussed. Wireless hospital and telecare applications are also described and the requirements for mobile access from PDA devices to medical databases are considered in more detail. As a case study, a wireless emergency system is presented. Chapter 6, Relevance of Terminological Standards and Services in Telemedicine, describes medical terminology standardization on several levels of granularity and overviews existing classifications and momenclatures. As a case study, this chapter presents the TOSCA Project dedicated to establishing a common terminology. Chapter 7, Electronic Health Records, describes the progress in constructing a common set of data structures contained in medical records and reports on the main standardization efforts in this area. The Electronic Patient Record has fundamental significance for the implementation of medical information systems and telemedical applications. Chapter 8, Decision Support Systems in Medicine, covers knowledge-based and expert systems which support physicians in making medical decisions by providing interactive tools. A classification of such systems is presented and their internal structures and architectures are evaluated. Several classes of expert systems are described and compared. Chapter 9, Health Telematics Networks, briefly describes the requirements and architecture of telematics networks and the organizational models for such networks. It also overviewes e-health network services available over the Internet. Chapter 10, IT Applications for Remote Testing of Hearing, presents innovative telemedical systems for sensory self-diagnostics over the Internet. The preconditions and structures of successful nationwide programs based on these systems are also described. Chapter 11, Model of chronic care enabled with information technology, defines the scope of the problem, describing Web-based and telemonitoring solutions as the most commonly used technologies in the area. Subsequently,

Information Technology Solutions for Healthcare

Long-term mechanical circulatory assistance opened new problems in ventricular assist device-patient interaction, especially in relation to autonomic controls Modeling studies, based on adequate models, could be a feasible approach of investigation The aim of this work is the exploitation of a hybrid (hydronumerical) cardiovascular simulator to reproduce and analyze in vivo experimental data acquired during a continuous flow left ventricular assistance The hybrid cardiovascular simulator embeds three submodels: a computational cardiovascular submodel, a computational baroreflex submodel, and a hydronumerical interface submodel The last one comprises two impedance transformers playing the role of physical interfaces able to provide a hydraulic connection with specific cardiovascular sites (in this article, the left atrium and the ascending/descending aorta) The impedance transformers are used to connect a continuous flow pump for partial left ventricular support (Synergy Micropump, CircuLite, Inc, Saddlebrooke, NJ, USA) to the hybrid cardiovascular simulator Data collected from five animals in physiological, pathological, and assisted conditions were reproduced using the hybrid cardiovascular simulator All parameters useful to characterize and tune the hybrid cardiovascular simulator to a specific hemodynamic condition were extracted from experimental data Results show that the simulator is able to reproduce animal-specific hemodynamic status both in physiological and pathological conditions, to reproduce cardiovascular left ventricular assist device (LVAD) interaction and the progressive unloading of the left ventricle for different pump speeds, and to investigate the effects of the LVAD on baroreflex activity Results in chronic heart failure conditions show that an increment of LVAD speed from 20 000 to 22 000 rpm provokes a decrement of left ventricular flow of 35% (from 2 to 13 L/min) Thanks to its flexibility and modular structure, the simulator is a platform potentially useful to test different assist devices, thus providing clinicians additional information about LVAD therapy strategy

Reproduction of continuous flow left ventricular assist device experimental data by means of a hybrid cardiovascular model with baroreflex control.

The paper analyses the challenges involved in constructing a dynamic monitoring framework compliant with the requirements of SOA application monitoring. The specification of these requirements provides a starting point for our multilayer framework architecture. We describe its Monitoring Scenario and Instrumentation layers in detail. The approach aims at runtime monitoring of container-based SOA execution environments. The Instrumentation layer exploits interceptor sockets, on top of which a powerful attribute-based reconfigurable monitoring service is constructed. The proposed solution is application-agnostic and can be used for enterprise and computational applications. We present a case study which further explains the functionality of the system. A prototype implementation for OSGi containers is also briefly described. Preliminary performance evaluation results are outlined and discussed.

/pdf/dynamic-monitoring-framework-for-the-soa-execution-2zfztgl1ta.pdf

Krzysztof Zieliński

Papers

Software engineering : evolution and emerging technologies

Comparison Study of Aspect-oriented and Container Managed Security

Information Technology Solutions for Healthcare

Reproduction of continuous flow left ventricular assist device experimental data by means of a hybrid cardiovascular model with baroreflex control.

Dynamic monitoring framework for the SOA execution environment