3rd EGEE User Forum

We have organized this book in a sequence of chapters, each chapter associated with an application or technical theme introduced by an overview of the contents, and a summary of the main conclusions coming from the Forum for the chapter topic. The first chapter gathers all the plenary session keynote addresses, and following this there is a sequence of chapters covering the application flavoured sessions. These are followed by chapters with the flavour of Computer Science and Grid Technology. The final chapter covers the important number of practical demonstrations and posters exhibited at the Forum. Much of the work presented has a direct link to specific areas of Science, and so we have created a Science Index, presented below. In addition, at the end of this book, we provide a complete list of the institutes and countries involved in the User Forum

Skilling up for CRM: qualifications for CRM professionals in the Fourth Industrial Revolution

The 4th industrial revolution (4IR) describes a series of innovations in artificial intelligence, ubiquitous internet connectivity, and robotics, along with the subsequent disruption to the means of production. The impact of 4IR on industry reveals a construct called Industry 4.0. Higher education, too, is called to transform to respond to the disruption of 4IR, to meet the needs of industry, and to maximize human flourishing. Education 4.0 describes 4IR’s impact or predicted impact or intended impact on higher education, including prescriptions for HE’s transformation to realize these challenges. Industry 4.0 requires a highly skilled workforce, and a 4IR world raises questions about skills portability, durability, and lifespan. Every vertical within industry will be impacted by 4IR and such impact will manifest in needs for diverse employees possessing distinct competencies. Customer relationship management (CRM) describes the use of information systems to implement a customer-centric strategy and to practice relationship marketing (RM). Salesforce, a market leading CRM vendor, proposes its products alone will generate 9 million new jobs and $1.6 trillion in new revenues for Salesforce customers by 2024. Despite the strong market for CRM skills, a recent paper in a prominent IS journal claims higher education is not preparing students for CRM careers. In order to supply the CRM domain with skilled workers, it is imperative that higher education develop curricula oriented toward the CRM professional. Assessing skills needed for specific industry roles has long been an important task in IS pedagogy, but we did not find a paper in our literature review that explored the Salesforce administrator role. In this paper, we report the background, methodology, and results of a content analysis of Salesforce Administrator job postings retrieved from popular job sites. We further report the results of semi-structured interviews with industry experts, which served to validate, revise, and extend the content analysis framework. Our resulting skills framework serves as a foundation for CRM curriculum development and our resulting analysis incorporates elements of Education 4.0 to provide a roadmap for educating students to be successful with CRM in a 4IR world

Contribution to Software Development Method based on Generalized Requirement Approach

Requirements’ gathering is one of the first steps in the software development process. Gathering business requirements, when the final product requirements are dictated by a known client, can be a difficult process. Even if the client knows their own business best, often their idea about a new business product is obscure, and described by general terms that contribute very much to common misunderstandings among the participants. Business requirement verification when the requirements are gathered using text and graphics can be a slow, error-prone, and expensive process. Misunderstandings and omitted requirements cause the need for revisions and increase project costs and delays. This research work proposes a new approach to the business software development process and is focused on the client’s understanding of how the business software development process works as well as a demonstration of the business requirement practices during requirement negotiation process. While the current software development process validates the business requirement at the end of the development process, this method implementation enables business requirement validation during the requirement negotiation phase. The process of the business requirement negotiation is guided by a set of predefined questions. These questions are guidelines for specifying a sufficient level of requirement details for generating executable code that is able to demonstrate each requirement. Effective implementation of the proposed method requires employment of the GRA Framework. Besides providing guidelines for requirement specification, the Framework shall create executable and provide the test environment for a requirement demonstration. This dissertation implements an example framework that is built around a central repository. Stored within the repository is the data collected during the requirement negotiations process. Access to the repository is managed by a Web interface that enables a collaborative and paperless environment. The result is that the data is stored in one place and updates are reflected to the stakeholders immediately. The executable code is generated by the Generator, a module that provides general programming units that are able to create source code files, databases, SQL statements, classes and methods, navigation menus, and demo applications, all from the data stored in the data repository. The generated software can then be used for the business requirement demonstration. This method assumes that any further development process is built around the requirements repository, which can provide continuous tracking of implementation changes. Besides readily documenting, tracking, and validating the requirements, this method addresses multiple requirement management syndromes such as the insufficient requirements description details provision, the IKIWISI (“I’ll know it when I see it”) Syndrome, the Yes, But Syndrome (“That is not exactly what I mean”), and the Undiscovered Ruins Syndrome (“Now that I see it, I have another requirement to add”).

ICSEA 2021: the sixteenth international conference on software engineering advances

The Sixteenth International Conference on Software Engineering Advances (ICSEA 2021), held on October 3 - 7, 2021 in Barcelona, Spain, continued a series of events covering a broad spectrum of software-related topics. The conference covered fundamentals on designing, implementing, testing, validating and maintaining various kinds of software. The tracks treated the topics from theory to practice, in terms of methodologies, design, implementation, testing, use cases, tools, and lessons learnt. The conference topics covered classical and advanced methodologies, open source, agile software, as well as software deployment and software economics and education. The conference had the following tracks: Advances in fundamentals for software development Advanced mechanisms for software development Advanced design tools for developing software Software engineering for service computing (SOA and Cloud) Advanced facilities for accessing software Software performance Software security, privacy, safeness Advances in software testing Specialized software advanced applications Web Accessibility Open source software Agile and Lean approaches in software engineering Software deployment and maintenance Software engineering techniques, metrics, and formalisms Software economics, adoption, and education Business technology Improving productivity in research on software engineering Trends and achievements Similar to the previous edition, this event continued to be very competitive in its selection process and very well perceived by the international software engineering community. As such, it is attracting excellent contributions and active participation from all over the world. We were very pleased to receive a large amount of top quality contributions. We take here the opportunity to warmly thank all the members of the ICSEA 2021 technical program committee as well as the numerous reviewers. The creation of such a broad and high quality conference program would not have been possible without their involvement. We also kindly thank all the authors that dedicated much of their time and efforts to contribute to the ICSEA 2021. We truly believe that thanks to all these efforts, the final conference program consists of top quality contributions. This event could also not have been a reality without the support of many individuals, organizations and sponsors. We also gratefully thank the members of the ICSEA 2021 organizing committee for their help in handling the logistics and for their work that is making this professional meeting a success. We hope the ICSEA 2021 was a successful international forum for the exchange of ideas and results between academia and industry and to promote further progress in software engineering research

An investigation into manufacturing execution systems

Hardware and software developments of this decade have exposed an hiatus between business/management applications and process control in heavy industry in the implementation of computer technology. This document examines the development of discrete manufacturing and of relevant implementations of computing. It seeks to examine and to clarify the issues involved in a perceived current drive to bridge this gap, to integrate all the systems in a manufacturing enterprise in a Manufacturing Execution System (MES) in order to address two hypotheses: I) That overseas trends towards the development of manufacturing execution systems have application in the Australian industrial context. 2) That significant gains in production efficiency and quality may be achieved by the application of an MES. It became apparent early in this study that any understanding the function of an MES requires an understanding of the context in which it works. Following the Introduction, therefore, Section Two contains a brief overview of the history and development of modem industry with particular attention to the subject of inventory and inventory management. Since the 1970s, three main streams of change in manufacturing management methodology developed. These are dealt with in some detail in Section Three. Section Four outlines a variety of areas of increasing computerisation on the shop floor while Section Five addresses the integration of the whole system, management and shop floor, seeking to demonstrate the complexity of the subject and to discover current trends and developments. Section Five includes a survey of some of the software and hardware options currently available and Section Six summarises the work and presents some observations and conclusions. Three appendices provide more detailed information on MES software availability, pricing and market penetratio

An Integrated Conceptual Environment based on Collective Intelligence and Distributed Artificial Intelligence for Connecting People on Problem Solving

This paper aims to analyze the different forms of intelligence within organizations in a systemic and inclusive vision, in order to conceptualize an integrated environment based on Distributed Artificial Intelligence (DAI) and Collective Intelligence (CI). In this way we effectively shift the classical approaches of connecting people with people using collaboration tools (which allow people to work together, such as videoconferencing or email, groupware in virtual space, forums, workflow), of connecting people with a series of content management knowledge (taxonomies and documents classification, ontologies or thesauri, search engines, portals), to the current approaches of connecting people on the use (automatic) of operational knowledge to solve problems and make decisions based on intellectual cooperation. The best way to use collective intelligence is based on knowledge mobilization and semantic technologies. We must not let computers to imitate people but to support people think and develop their ideas within a group. CI helps people to think together, while DAI tries to support people so as to limit human error. Within an organization, to manage CI is to combine instruments like Semantic Technologies (STs), knowledge mobilization methods for developing Knowledge Management (KM) strategies, and the processes that promote connection and collaboration between individual minds in order to achieve collective objectives, to perform a task or to solve increasingly economic complex problems