scholarly journals MATLAB-Like Scripting of Java Scientific Libraries in ScalaLab

2014 ◽  
Vol 22 (3) ◽  
pp. 187-199
Author(s):  
Stergios Papadimitriou ◽  
Seferina Mavroudi ◽  
Kostas Theofilatos ◽  
Spiridon Likothanasis

Although there are a lot of robust and effective scientific libraries in Java, the utilization of these libraries in pure Java is difficult and cumbersome, especially for the average scientist that does not expertise in software development. We illustrate that ScalaLab presents an easier and productive MATLAB like front end. Also, the main strengths and weaknesses of the core Java libraries of ScalaLab are elaborated. Since performance is of paramount importance for scientific computation, the article discusses extensively performance aspects of the ScalaLab environment. Also, Java bytecode performance is compared to native code.

Author(s):  
Demian Katz ◽  
Andrew Nagy

Apache Solr, an open source Java-based search engine, forms the core of many Library 2.0 products. The use of an index in place of a relational database allows faster data retrieval along with key features like faceting and similarity analysis that are not practical in the previous generation of library software. The popular VuFind discovery tool was built to provide a library-friendly front-end for Solr’s powerful searching capabilities, and its development provides an informative case study on the use of Solr in a library setting. VuFind is just one of many library packages using Solr, and examples like Blacklight, Summon, and the eXtensible Catalog project show other possible approaches to its use.


Author(s):  
Janis Osis ◽  
Erika Nazaruka (Asnina)

Some experts opine that software is built in a primitive way. The role of modeling as a treatment for the weakness of software engineering became more important when the principles of Model Driven Architecture (MDA) appeared. Its main advantage is architectural separation of concerns. It showed the necessity of modeling and opened the way for software development to become an engineering discipline. However, this principle does not demonstrate its whole potential power in practice because of lack of mathematical accuracy in the very initial steps of software development. The sufficiency of modeling in software development is still disputable. The authors believe that software development in general (and modeling in particular) based on mathematical formalism in all of its stages and together with the implemented principle of architectural separation of concerns can become an important part of software engineering in its real sense. They propose the formalism by topological modeling of system functioning as the first step towards engineering.


Author(s):  
Mirna Muñoz

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.


2016 ◽  
Vol 26 ◽  
Author(s):  
XAVIER CLERC

AbstractThis article presents how the compiler from the OCaml-Java project generates Java bytecode from OCaml sources. Targeting the Java Virtual Machine (JVM) is a technological challenge, but gives access to a platform where OCaml can leverage multiple cores and access numerous libraries. We present the main design choices regarding the runtime and the various optimizations performed by the compiler that are crucial to get decent performance on a JVM. The challenge is indeed not only to generate bytecode but to generate efficient bytecode, and to provide a runtime library whose memory footprint does not impede the efficiency of the garbage collector. We focus on the strategies that differ from the original OCaml compiler, as the constraints are quite different on the JVM when compared to native code. The level of performance reached by the OCaml-Java compiler is assessed through benchmarks, comparing with both the original OCaml implementation and the Scala language.


2011 ◽  
Vol 11 (4-5) ◽  
pp. 503-520 ◽  
Author(s):  
MICHAEL CODISH ◽  
IGOR GONOPOLSKIY ◽  
AMIR M. BEN-AMRAM ◽  
CARSTEN FUHS ◽  
JÜRGEN GIESL

AbstractWe describe an algorithm for proving termination of programs abstracted to systems of monotonicity constraints in the integer domain. Monotonicity constraints are a nontrivial extension of the well-known size-change termination method. While deciding termination for systems of monotonicity constraints is PSPACE complete, we focus on a well-defined and significant subset, which we call MCNP (for “monotonicity constraints in NP”), designed to be amenable to a SAT-based solution. Our technique is based on the search for a special type of ranking function defined in terms of bounded differences between multisets of integer values. We describe the application of our approach as the back end for the termination analysis of Java Bytecode. At the front end, systems of monotonicity constraints are obtained by abstracting information, using two different termination analyzers:AProVEandCOSTA. Preliminary results reveal that our approach provides a good trade-off between precision and cost of analysis.


Author(s):  
Cătălin Tudose

The history of humankind offers lots of remarkable ideas and innovations in strategy and tactics. There is no area where people have shown more inventiveness than defending themselves or attacking and conquering others. On the other hand, the Agile methodology emerged from software development, where it tried to provide support for the successful organization of delivery projects, that have to fight and conquer the complexity. This article evidences similarities between the Agile methodology and attacking and war strategies, making extended references to one of the most renowned military treaties: Sun Tzu's The Art of War. Making inter-disciplinary analogies, comparing and contrasting the concepts from different disciplines are at the core of this article. We'll investigate what things as initial estimations, attack by stratagem, tactical dispositions, energy, weak points, and strong points, maneuvering, variation in tactics, the army on the march, terrain, arriving on unknown ground, concrete situations on the ground, the use of spies, or what the attack by fire may mean in software development. We'll analyze how these war strategy concepts transpose to Agile concepts like adding business value, getting to the business goals, managing complexity, conducting the work the incremental and non-incremental way.


Author(s):  
Johan Oomen ◽  
Maarten Brinkerink ◽  
Bouke Huurnink ◽  
Roeland Ordelman

Audiovisual archives are embracing the opportunities offered by digitization for managing their work processes and offering new services to a wide array of user groups. Organization strategy, working processes and software development need to be able to support a culture where innovation can flourish. Some institutions are beginning to adopt the concept of ‘two-speed IT’. The core strategy aims to accommodate two informational technology tracks simultaneously: foundational but ‘slow’ and innovative but exible and ‘fast’. This paper outlines the rationale behind the two-speed IT strategy. It highlights a specific implementation at the Netherlands Institute for Sound and Vision, a large audiovisual archive and museum where two-speed IT is enabling the institute to reach its business objectives.


2021 ◽  
Vol 6 (1) ◽  
pp. 25
Author(s):  
Nurudin Santoso ◽  
Faizatul Amalia

Most of failures of startup application in many countries reached 75%, while the startup failures in Indonesia reached 90%. These failures were caused by non-technical or management factors in managing startup. The RPL (Software Engineering) Laboratory of FILKOM of Brawijaya University has a roadmap to develop an application to guarantee the success of a management software project. The data analysis had been performed on FILKOM student’s thesis work which generally develops software that has main obstacle in the management. A study solution which was developed through scientific SDLC and PMLC combined with Scrum method becomes an application named SPM-SCRUM. The results of analysis carried out on several software development projects refer to the Iterative SDPM process. Furthermore, the strategy of Iterative SDPM combined with Scrum method produces a system architecture design that separates the Front End and Back End


Sign in / Sign up

Export Citation Format

Share Document