Search

Summary: heatmaply is an R package for easily creating interactive cluster heatmaps that can be shared online as a stand-alone HTML file. Interactivity includes a tooltip display of values when hovering over cells, as well as the ability to zoom in to specific sections of the figure from the data matrix, the side dendrograms, or annotated labels. Thanks to the synergistic relationship between heatmaply and other R packages, the user is empowered by a refined control over the statistical and visual aspects of the heatmap layout. Availability and implementation: The heatmaply package is available under the GPL-2 Open Source license. It comes with a detailed vignette, and is freely available from: http://cran.r-project.org/package=heatmaply. Supplementary information: Supplementary data are available at Bioinformatics online., Comment: 3 pages

This paper offers a new framework to facilitate an interpretive approach to client-led information system development, referred to as CLIC (Client-Led Information System Creation). The challenge of moving seamlessly through a process of information systems (IS) design is still the subject of much research in the IS field. Attempts to address the difficulties of ‘bridging the gap’ between a client's business needs and an information system definition have hitherto not provided a coherent and practical approach. Rather than attempting to bridge the gap, this paper describes an approach to managing this gap by facilitating the clients’ navigating through the information system design process (or inquiry process) in a coherent manner. The framework has been developed through practice, and the paper provides an example of navigating through the design phase taken from an Action Research field study in a major UK bank.

When developing a software system, there are a number of principles, paradigms, and tools available to choose from. For a specific platform or programming language, a standard way can usually be found to archive the ultimate system; for example, a combination of an incremental development process, object-oriented analysis and design, and a well supported CASE (Computer-Aided Software Engineering) tool. Regardless of the technology to be adopted, the final outcome of the software development is always a working software system. However, when it comes to software reengineering, there is rather less consensus on either approaches or outcomes. Shall we use black-box or white-box reverse engineering for program understanding? Shall we produce data and control flow graphs, or some kind of formal specifications as the output of analysis? Each of these techniques has its pros and cons of tackling various software reengineering problems, and none of them on its own suffices to a whole reengineering project. A proper integration of various techniques capable of solving a specific issue could be an effective way to unravel a complicated software system. This kind of integration has to be done from an architectural point of view. One of the most exciting outcomes of recent efforts on software architecture is the Object Management Group’s (OMG) Model-Driven Architecture (MDA). MDA provides a unified framework for developing middleware-based modern distributed systems, and also a definite goal for software reengineering. This chapter presents a unified software reengineering methodology based on Model-Driven Architecture, which consists of a framework, a process, and related techniques.

Those who have used patterns are aware that this literary form, and its corresponding process and community support, is providing a way to capture best practices and communicate them throughout organizations and the entire software industry. However, many who have tried to introduce patterns (or any new idea) into their organizations have found it to be a difficult task. Therefore, a pattern language, currently titled Evolving a Patterns Culture, is being written to capture solutions to the challenges in introducing patterns (or any new idea) into an organization.