Report of the user requirements and web based access for eResearch workshops

The User Requirements and Web Based Access for eResearch Workshop, organized jointly by NeSC and NCeSS, was held on 19 May 2006. The aim was to identify lessons learned from e-Science projects that would contribute to our capacity to make Grid infrastructures and tools usable and accessible for diverse user communities. Its focus was on providing an opportunity for a pragmatic discussion between e-Science end users and tool builders in order to understand usability challenges, technological options, community-specific content and needs, and methodologies for design and development. We invited members of six UK e-Science projects and one US project, trying as far as possible to pair a user and developer from each project in order to discuss their contrasting perspectives and experiences. Three breakout group sessions covered the topics of user-developer relations, commodification, and functionality. There was also extensive post-meeting discussion, summarized here. Additional information on the workshop, including the agenda, participant list, and talk slides, can be found online at http://www.nesc.ac.uk/esi/events/685/ Reference: NeSC report UKeS-2006-07 available from http://www.nesc.ac.uk/technical_papers/UKeS-2006-07.pd

Authentic learning experiences: complementary organizational strategy for academic professional development

There are numerous websites and considerable literature which describe approaches to learning and teaching using a range of technologies in higher education contexts for academic staff. Further, that as academic staff development is increasingly recognized as having an essential role to play in the recasting of ways in which teachers work with students and how students best learn, that this is an area ripe for new consideration. It is the author's contention here, that embracing the role of student, as a lived experience, can assist academic developers in reconsidering and renewing their conceptions of learning and teaching. This could go in some part in informing the practice and processes of academic staff developers in understanding, promoting and supporting flexible learning modes

Supporting organisational learning: an overview of the ENRICH approach

Traditional training separates learning from the work context in which the newly acquired knowledge is to be applied. This requires the worker themselves to apply imparted theoretical knowledge to knowledge in practice, a process that is grossly inefficient. The ENRICH approach builds on organisational learning theory to intertwine working and learning. The ENRICH methodology incorporates theories of learning at the individual, group and organisational level. Individual level learning is supported through the provision of semantically related resources to support problem reframing and to challenge assumptions. Group learning is supported through the evolution of domain concepts through work documents and representations linked to formal models of group knowledge, and the development of group practices and perspectives through enhanced sharing and collaboration. Organisational learning is supported through exposure to customs and conventions of other groups through shared best practices and knowledge models. The approach is being investigated in a range of industrial settings and applications

Migrating to Cloud-Native Architectures Using Microservices: An Experience Report

Migration to the cloud has been a popular topic in industry and academia in recent years. Despite many benefits that the cloud presents, such as high availability and scalability, most of the on-premise application architectures are not ready to fully exploit the benefits of this environment, and adapting them to this environment is a non-trivial task. Microservices have appeared recently as novel architectural styles that are native to the cloud. These cloud-native architectures can facilitate migrating on-premise architectures to fully benefit from the cloud environments because non-functional attributes, like scalability, are inherent in this style. The existing approaches on cloud migration does not mostly consider cloud-native architectures as their first-class citizens. As a result, the final product may not meet its primary drivers for migration. In this paper, we intend to report our experience and lessons learned in an ongoing project on migrating a monolithic on-premise software architecture to microservices. We concluded that microservices is not a one-fit-all solution as it introduces new complexities to the system, and many factors, such as distribution complexities, should be considered before adopting this style. However, if adopted in a context that needs high flexibility in terms of scalability and availability, it can deliver its promised benefits

Bronco Books: Textbook E-commerce Platform

College students purchase textbooks for the classes they take every quarter, but current solutions for selling back those textbooks are insufficient, requiring that the student pay to utilize the selling platforms or that the student build rapport within a given community. Our project, Bronco Books, offers a solution by being a native mobile application open to only SCU students. Bronco Books will be free to access and will act as an e-commerce platform where students go to sell their textbooks. We were motivated to create Bronco Books primarily because we wanted to help alleviate the financial burden that comes with purchasing textbooks. This document covers the requirements, use cases, and activity diagrams for Bronco Books. We also explain our rationale behind some of our design decisions, such as the technologies we will be using for this project, and our followed timeline. We conclude the document by discussing the lessons we learned and the developmental future of Bronco Books

Assessing architectural evolution: A case study

This is the post-print version of the Article. The official published can be accessed from the link below - Copyright @ 2011 SpringerThis paper proposes to use a historical perspective on generic laws, principles, and guidelines, like Lehman’s software evolution laws and Martin’s design principles, in order to achieve a multi-faceted process and structural assessment of a system’s architectural evolution. We present a simple structural model with associated historical metrics and visualizations that could form part of an architect’s dashboard. We perform such an assessment for the Eclipse SDK, as a case study of a large, complex, and long-lived system for which sustained effective architectural evolution is paramount. The twofold aim of checking generic principles on a well-know system is, on the one hand, to see whether there are certain lessons that could be learned for best practice of architectural evolution, and on the other hand to get more insights about the applicability of such principles. We find that while the Eclipse SDK does follow several of the laws and principles, there are some deviations, and we discuss areas of architectural improvement and limitations of the assessment approach