This document provides information about Aleksandra Pawlik's PhD research project which aims to explore how best to support scientific end-user software development. The research will focus on identifying problematic and successful tools/techniques used by scientific developers through case studies of projects that transition from limited to extended contexts or involve software professionals. Qualitative methods like interviews and observation will be used to understand the challenges and how support can be improved.
ANALYSIS OF DEVELOPMENT COOPERATION WITH SHARED AUTHORING ENVIRONMENT IN ACAD...IJITE
Â
Team work is an important training element of future software engineers. However, the evaluation of the
performance of collaboration among individuals is very subjective. Meanwhile, how to effectively
promote the collaboration in an academic setting is an even more challenging task. The lack of a common
standard or method for the assessment is a practical issue in software engineering projects. With the
rapid development of shared authoring environments, such as Wiki, more and more educational
institutions are studying the adaptability of such kind of collaborative platforms. In order to study the
applicability of adopting wiki-based shared authoring environments in software engineering education,
we have proposed three major research questions. By solving these problems, we try to answer some of
the most important questions in adopting shared authoring platforms in academic settings.
EMPLOYERSâ NEEDS FOR COMPUTER SCIENCE, INFORMATION TECHNOLOGY AND SOFTWARE EN...ijcseit
Â
Graduates of computer science programs often lack skills that employers desire among software
developers. These include, for example, weaknesses in the areas of collaboration, communication, and
software testing. Further research can help to refine this list by providing insight into additional skills that
are of rising or regional importance. This paper therefore presents a study aimed at uncovering desirable
technical and soft skills for graduates of computer science in the Pacific Northwest region of the United
States. Interviews of 11 employers, including both managers and recruiters, highlighted the prominent
importance of skills related to web development, relational databases, and testing. Additionally, it
spotlighted not only widely-recognized soft skills such as those related to collaboration and
communication, but additionally on skills tied to personal attributes such as innovating, coping with
ambiguity and learning quickly. The results provide insights for what skills and personal attributes to
include in a future survey of employers aimed at quantifying the importance of skills on this list.
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
This is a North Central University paper about analyzing qualitative software. It is written in APA format, includes references, and is graded an instructor.
ANALYSIS OF DEVELOPMENT COOPERATION WITH SHARED AUTHORING ENVIRONMENT IN ACAD...IJITE
Â
Team work is an important training element of future software engineers. However, the evaluation of the
performance of collaboration among individuals is very subjective. Meanwhile, how to effectively
promote the collaboration in an academic setting is an even more challenging task. The lack of a common
standard or method for the assessment is a practical issue in software engineering projects. With the
rapid development of shared authoring environments, such as Wiki, more and more educational
institutions are studying the adaptability of such kind of collaborative platforms. In order to study the
applicability of adopting wiki-based shared authoring environments in software engineering education,
we have proposed three major research questions. By solving these problems, we try to answer some of
the most important questions in adopting shared authoring platforms in academic settings.
EMPLOYERSâ NEEDS FOR COMPUTER SCIENCE, INFORMATION TECHNOLOGY AND SOFTWARE EN...ijcseit
Â
Graduates of computer science programs often lack skills that employers desire among software
developers. These include, for example, weaknesses in the areas of collaboration, communication, and
software testing. Further research can help to refine this list by providing insight into additional skills that
are of rising or regional importance. This paper therefore presents a study aimed at uncovering desirable
technical and soft skills for graduates of computer science in the Pacific Northwest region of the United
States. Interviews of 11 employers, including both managers and recruiters, highlighted the prominent
importance of skills related to web development, relational databases, and testing. Additionally, it
spotlighted not only widely-recognized soft skills such as those related to collaboration and
communication, but additionally on skills tied to personal attributes such as innovating, coping with
ambiguity and learning quickly. The results provide insights for what skills and personal attributes to
include in a future survey of employers aimed at quantifying the importance of skills on this list.
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
This is a North Central University paper about analyzing qualitative software. It is written in APA format, includes references, and is graded an instructor.
Managing Large-scale Multimedia Development ProjectsSimon Price
Â
Keynote presentation at IEEE International Conference on Multimedia in Engineering Education 1998, Hong Kong. This paper presents generally applicable techniques drawn from the experience of managing the UK's Teaching and Learning Technology Programme (TLTP) Economics Consortium project to develop WinEcon - a computer based package covering an entire first year introductory economics degree course. The WinEcon project has been a highly successful, large scale multimedia project. It has received multiple international awards, is site licensed by over 80% of UK universities and over 200 organisations world wide. However, what really happens when you set out to develop the world's largest computer based training package for economics with a team of 35 content experts and 17 programmers distributed across eight geographically separate sites is a far cry from the typical case study found in a 'software project management' textbook. There are inherent characteristics of multimedia software which make its development difficult. Consequently any multimedia project carries a high risk of failing to deliver on time, quality or budget and the nature of large scale development projects only serves to amplify the risk to such a degree that many such projects fail to deliver satisfactorily in any of these three areas. These management challenges encountered by the WinEcon project are independent of subject matter and must be addressed when managing any large scale multimedia development.
Understanding software quality assurance in Open Source SoftwareHwer Aron
Â
The paper gives an insight into the different factors associated with ensuring software quality in open source software.
Stakeholders and processes that are influencing Open source software quality are assessed.
112 - The Role of Mentoring and Project Characteristics for Onboarding in Ope...ESEM 2014
Â
Context: Onboarding is a process that helps newcomers become integrated members of their organisation. Successful onboarding programs can result in increased performance in conventional organisations, but there is little guidance on how to onboard new developers in Open Source Software (OSS) projects. Goal: In this study, we examine how mentoring and project characteristics influence the effectiveness and effi ciency of the onboarding process. We study a collaboration program involving a total of nine Open Source Software projects and more than 120 students from dfferent universities around the world as part of Facebookâs Education Modernization Program. Method: We use quantitative measurements of source code repositories, issue tracking systems, and discussion fora to examine how newcomers become contributing members of their OSS projects. Results: We found that developers receiving deliberate onboarding support through mentoring were more active at an earlier stage than developers entering projects through conventional means. Also, we found that project size and lifetime influenced on- boarding. Conclusion: Empirical decision support can contribute to a more effective onboarding process in OSS projects. Mentor sup- port in critical stages can accelerate the process, but project maturity is also a significant factor that increases the effect of onboarding.
Supporting software documentation with source code summarization Ra'Fat Al-Msie'deen
Â
Source code summarization is a process of generating summaries that describe software code, the majority of source code summarization usually generated manually, where the summaries are written by software developers. Recently, new automated approaches are becoming more useful. These approaches have been found to be effective in some cases. The main weaknesses of these approaches are that they never exploit code dependencies and summarize either the software classes or methods but not both. This paper proposes a source code summarization approach (Suncode) that produces a short description for each class and method in the software system. To validate the approach, it has been applied to several case studies. Moreover, the generated summaries are compared to summaries that written by human experts and to summaries that written by a state-of-the-art solution. Results of this paper found that Suncode summaries provide better information about code dependencies comparing with other studies. In addition, Suncode summaries can improve and support the current software documentation. The results found that manually written summaries were more precise and short as well.
2011 version of the Knowledge Transfer Toolkit presentation. Includes:
Developing a knowledge sharing toolkit
Keeping content up to date
Encouraging knowledge-sharing behaviours
Social Media principles
Using multiple media
10 Insightful Quotes On Designing A Better Customer ExperienceYuan Wang
Â
In an ever-changing landscape of one digital disruption after another, companies and organisations are looking for new ways to understand their target markets and engage them better. Increasingly they invest in user experience (UX) and customer experience design (CX) capabilities by working with a specialist UX agency or developing their own UX lab. Some UX practitioners are touting leaner and faster ways of developing customer-centric products and services, via methodologies such as guerilla research, rapid prototyping and Agile UX. Others seek innovation and fulfilment by spending more time in research, being more inclusive, and designing for social goods.
Experience is more than just an interface. It is a relationship, as well as a series of touch points between your brand and your customer. Here are our top 10 highlights and takeaways from the recent UX Australia conference to help you transform your customer experience design.
For full article, continue reading at https://yump.com.au/10-ways-supercharge-customer-experience-design/
How to Build a Dynamic Social Media PlanPost Planner
Â
Stop guessing and wasting your time on networks and strategies that donât work!
Join Rebekah Radice and Katie Lance to learn how to optimize your social networks, the best kept secrets for hot content, top time management tools, and much more!
Watch the replay here: bit.ly/socialmedia-plan
http://inarocket.com
Learn BEM fundamentals as fast as possible. What is BEM (Block, element, modifier), BEM syntax, how it works with a real example, etc.
Content personalisation is becoming more prevalent. A site, it's content and/or it's products, change dynamically according to the specific needs of the user. SEO needs to ensure we do not fall behind of this trend.
It is impossible to separate the human factors from software engineering expertise during
software development, because software is developed by people and for people. The intangible
nature of software has made it a difficult product to successfully create, and an examination of
the many reasons for major software system failures show that the reasons for failures
eventually come down to human issues. Software developers, immersed as they are in the
technological aspect of the product, can quickly learn lessons from technological failures and
readily come up with solutions to avoid them in the future, yet they do not learn lessons from
human aspects in software engineering. Dealing with human errors is much more difficult for
developers and often this aspect is overlooked in the evaluation process as developers move on
to issues that they are more comfortable solving. A major reason for this oversight is that
software psychology (the softer side) has not developed as extensively
Supporting The Initial Stages of The Product Design Process: Towards Knowledg...CSCJournals
Â
The creation of new products and services is an everyday activity for many industries, often assisted by professional design studios. It is evident that extensive knowledge is required by designers during the conceptual product design process, matching the complexity of design problems. Techniques based on association, analogy and metaphors are often used to facilitate the process of creative thinking and inspiration leading to new product designs. This paper presents a novel semantic tool, which has been developed to seamlessly assist product designers with knowledge management tasks during information discovery and support the formulation of new product concepts. The technology can be used in combination with a sketching application to support the generation of relevant visual content, helping to stimulate associative thinking, and thus assist creativity at the initial stage of the product design process.
Excited to share our vision for bioinformatics education available for students and researchers that want to apply advanced multi-omics integration and machine learning to large biomedical datasets. Practice and learn from real-life projects.
Requirement engineering is a key ingredient for software development to be effective. Apart from the
traditional software requirement which is not much appropriate for new emerging software such as smart
handheld device based software. In many perspectives of requirement engineering, traditional and new
emerging software are not similar. Whereas requirement engineering of traditional software needs more
research, it is obvious that new emerging software needs methodically and in-depth research for improved
productivity, quality, risk management and validity. In particular, the result of this paper shows that how
effective requirement engineering can improve in project negotiation, project planning, managing feature
creep, testing, defect, rework and product quality. This paper also shows a new methodology which is
focused on users work process applicable for eliciting the requirement of traditional software and any new
type software of smart handheld device such as iPad. As an example, the paper shows how the methodology
will be applied as a software requirement of iPad-based software for play-group students.
Open Source Software is the major rival in the software market previously dominated by proprietary software products. Open Source Software(OSS) is available in various forms including web servers, Enterprise Resource Planning systems (ERPs), Academic management systems and network management systems and the development and uptake of such software by both commercial and non-commercial companies and institutions is still on the rise. The availability of OSS applications for every common type of enterprise, minimal licensing issues and availability of source code as well as ease of access has made the technology even more attractive in learning and teaching of software based courses in institutions of learning. Through embracing this technology, institutions of learning have been able to minimize general operations cost that could have otherwise been incurred in procuring similar proprietary software. Students and teaching staff can nowadays interact and modify the readily available source code hence making learning and teaching more practical.
Managing Large-scale Multimedia Development ProjectsSimon Price
Â
Keynote presentation at IEEE International Conference on Multimedia in Engineering Education 1998, Hong Kong. This paper presents generally applicable techniques drawn from the experience of managing the UK's Teaching and Learning Technology Programme (TLTP) Economics Consortium project to develop WinEcon - a computer based package covering an entire first year introductory economics degree course. The WinEcon project has been a highly successful, large scale multimedia project. It has received multiple international awards, is site licensed by over 80% of UK universities and over 200 organisations world wide. However, what really happens when you set out to develop the world's largest computer based training package for economics with a team of 35 content experts and 17 programmers distributed across eight geographically separate sites is a far cry from the typical case study found in a 'software project management' textbook. There are inherent characteristics of multimedia software which make its development difficult. Consequently any multimedia project carries a high risk of failing to deliver on time, quality or budget and the nature of large scale development projects only serves to amplify the risk to such a degree that many such projects fail to deliver satisfactorily in any of these three areas. These management challenges encountered by the WinEcon project are independent of subject matter and must be addressed when managing any large scale multimedia development.
Understanding software quality assurance in Open Source SoftwareHwer Aron
Â
The paper gives an insight into the different factors associated with ensuring software quality in open source software.
Stakeholders and processes that are influencing Open source software quality are assessed.
112 - The Role of Mentoring and Project Characteristics for Onboarding in Ope...ESEM 2014
Â
Context: Onboarding is a process that helps newcomers become integrated members of their organisation. Successful onboarding programs can result in increased performance in conventional organisations, but there is little guidance on how to onboard new developers in Open Source Software (OSS) projects. Goal: In this study, we examine how mentoring and project characteristics influence the effectiveness and effi ciency of the onboarding process. We study a collaboration program involving a total of nine Open Source Software projects and more than 120 students from dfferent universities around the world as part of Facebookâs Education Modernization Program. Method: We use quantitative measurements of source code repositories, issue tracking systems, and discussion fora to examine how newcomers become contributing members of their OSS projects. Results: We found that developers receiving deliberate onboarding support through mentoring were more active at an earlier stage than developers entering projects through conventional means. Also, we found that project size and lifetime influenced on- boarding. Conclusion: Empirical decision support can contribute to a more effective onboarding process in OSS projects. Mentor sup- port in critical stages can accelerate the process, but project maturity is also a significant factor that increases the effect of onboarding.
Supporting software documentation with source code summarization Ra'Fat Al-Msie'deen
Â
Source code summarization is a process of generating summaries that describe software code, the majority of source code summarization usually generated manually, where the summaries are written by software developers. Recently, new automated approaches are becoming more useful. These approaches have been found to be effective in some cases. The main weaknesses of these approaches are that they never exploit code dependencies and summarize either the software classes or methods but not both. This paper proposes a source code summarization approach (Suncode) that produces a short description for each class and method in the software system. To validate the approach, it has been applied to several case studies. Moreover, the generated summaries are compared to summaries that written by human experts and to summaries that written by a state-of-the-art solution. Results of this paper found that Suncode summaries provide better information about code dependencies comparing with other studies. In addition, Suncode summaries can improve and support the current software documentation. The results found that manually written summaries were more precise and short as well.
2011 version of the Knowledge Transfer Toolkit presentation. Includes:
Developing a knowledge sharing toolkit
Keeping content up to date
Encouraging knowledge-sharing behaviours
Social Media principles
Using multiple media
10 Insightful Quotes On Designing A Better Customer ExperienceYuan Wang
Â
In an ever-changing landscape of one digital disruption after another, companies and organisations are looking for new ways to understand their target markets and engage them better. Increasingly they invest in user experience (UX) and customer experience design (CX) capabilities by working with a specialist UX agency or developing their own UX lab. Some UX practitioners are touting leaner and faster ways of developing customer-centric products and services, via methodologies such as guerilla research, rapid prototyping and Agile UX. Others seek innovation and fulfilment by spending more time in research, being more inclusive, and designing for social goods.
Experience is more than just an interface. It is a relationship, as well as a series of touch points between your brand and your customer. Here are our top 10 highlights and takeaways from the recent UX Australia conference to help you transform your customer experience design.
For full article, continue reading at https://yump.com.au/10-ways-supercharge-customer-experience-design/
How to Build a Dynamic Social Media PlanPost Planner
Â
Stop guessing and wasting your time on networks and strategies that donât work!
Join Rebekah Radice and Katie Lance to learn how to optimize your social networks, the best kept secrets for hot content, top time management tools, and much more!
Watch the replay here: bit.ly/socialmedia-plan
http://inarocket.com
Learn BEM fundamentals as fast as possible. What is BEM (Block, element, modifier), BEM syntax, how it works with a real example, etc.
Content personalisation is becoming more prevalent. A site, it's content and/or it's products, change dynamically according to the specific needs of the user. SEO needs to ensure we do not fall behind of this trend.
It is impossible to separate the human factors from software engineering expertise during
software development, because software is developed by people and for people. The intangible
nature of software has made it a difficult product to successfully create, and an examination of
the many reasons for major software system failures show that the reasons for failures
eventually come down to human issues. Software developers, immersed as they are in the
technological aspect of the product, can quickly learn lessons from technological failures and
readily come up with solutions to avoid them in the future, yet they do not learn lessons from
human aspects in software engineering. Dealing with human errors is much more difficult for
developers and often this aspect is overlooked in the evaluation process as developers move on
to issues that they are more comfortable solving. A major reason for this oversight is that
software psychology (the softer side) has not developed as extensively
Supporting The Initial Stages of The Product Design Process: Towards Knowledg...CSCJournals
Â
The creation of new products and services is an everyday activity for many industries, often assisted by professional design studios. It is evident that extensive knowledge is required by designers during the conceptual product design process, matching the complexity of design problems. Techniques based on association, analogy and metaphors are often used to facilitate the process of creative thinking and inspiration leading to new product designs. This paper presents a novel semantic tool, which has been developed to seamlessly assist product designers with knowledge management tasks during information discovery and support the formulation of new product concepts. The technology can be used in combination with a sketching application to support the generation of relevant visual content, helping to stimulate associative thinking, and thus assist creativity at the initial stage of the product design process.
Excited to share our vision for bioinformatics education available for students and researchers that want to apply advanced multi-omics integration and machine learning to large biomedical datasets. Practice and learn from real-life projects.
Requirement engineering is a key ingredient for software development to be effective. Apart from the
traditional software requirement which is not much appropriate for new emerging software such as smart
handheld device based software. In many perspectives of requirement engineering, traditional and new
emerging software are not similar. Whereas requirement engineering of traditional software needs more
research, it is obvious that new emerging software needs methodically and in-depth research for improved
productivity, quality, risk management and validity. In particular, the result of this paper shows that how
effective requirement engineering can improve in project negotiation, project planning, managing feature
creep, testing, defect, rework and product quality. This paper also shows a new methodology which is
focused on users work process applicable for eliciting the requirement of traditional software and any new
type software of smart handheld device such as iPad. As an example, the paper shows how the methodology
will be applied as a software requirement of iPad-based software for play-group students.
Open Source Software is the major rival in the software market previously dominated by proprietary software products. Open Source Software(OSS) is available in various forms including web servers, Enterprise Resource Planning systems (ERPs), Academic management systems and network management systems and the development and uptake of such software by both commercial and non-commercial companies and institutions is still on the rise. The availability of OSS applications for every common type of enterprise, minimal licensing issues and availability of source code as well as ease of access has made the technology even more attractive in learning and teaching of software based courses in institutions of learning. Through embracing this technology, institutions of learning have been able to minimize general operations cost that could have otherwise been incurred in procuring similar proprietary software. Students and teaching staff can nowadays interact and modify the readily available source code hence making learning and teaching more practical.
OPEN SOURCE TECHNOLOGY: AN EMERGING AND VITAL PARADIGM IN INSTITUTIONS OF LEA...ijcsit
Â
Open Source Software is the major rival in the software market previously dominated by proprietary software products. Open Source Software(OSS) is available in various forms including web servers, Enterprise Resource Planning systems (ERPs), Academic management systems and network management systems and the development and uptake of such software by both commercial and non-commercial companies and institutions is still on the rise. The availability of OSS applications for every common type of enterprise, minimal licensing issues and availability of source code as well as ease of access has made the technology even more attractive in learning and teaching of software based courses in institutions of learning. Through embracing this technology, institutions of learning have been able to minimize general operations cost that could have otherwise been incurred in procuring similar proprietary software. Students and teaching staff can nowadays interact and modify the readily available source code hence making learning and teaching more practical
The report will covers case studies of mobile technology pilots over two sessions in 2012 in a learning and teaching context. It will discusses the results of the surveys undertaken as part of the Project, to highlight the successes and failures of these pilots. The report also outlines the work done, and the results so far, in the development of a mobile solution for CSU Subject Outlines and learning resources.
Improving usage and impact of digitised resourcesAlastair Dunning
Â
A presentation from the JISC Programme Meeting for its Content Programme for 2011 http://www.jisc.ac.uk/whatwedo/programmes/digitisation/econtent11.aspx
SciForge Workshop@Potsdam Institute for Climate Impact Reserach; Nov 2014dreusser
Â
SciForge: Is your code worth a full citation?
Development of the software used for research at PIK is discussed in order to strengthen quality and reproducibility. Often, efforts put into good maintenance of software is not sufficiently recognised. However, the community is actively working on concepts and solutions enabling researchers to publish software, cite it and be credited for it.
Software must meet the quality criteria of the scientific discourse to be a valuable and citeable contribution to science. Solutions also need to be developed regarding versioning and documentation, traceability, reproducibility and reusability. Furthermore, the archiving of source code and executables, the use of persistent identifiers, and metrics measuring productivity, impact, and recognition have to be addressed.
SciForge is a network and a currently running project at GFZ addressing these questions. In the joint seminar, the current debate on scientific software publication will be presented and discussed.
Student perceptions and attitudes towards the software factory as a learning ...Muhammad Ahmad
Â
Industry needs graduates from universities having knowledge and skills to tackle the practical issues of real life software development. To facilitate software engineering students and fulfill industry need, the Department of Information Processing Science, University of Oulu, Finland, built a Software Factory laboratory (SWF) in 2012 based on Lean concept. This study examines factors in the SWF learning environment that affect learning of a SWF course by the students. It employs amended Computer laboratory Environment Inventory (CLEI) and Attitude towards Computers and Computing Courses Questionnaire instrument (ACCC) with two additional constructs: 1) Kanban board 2) Collaborative learning. The general findings indicate that SWF learning environment, collaborative learning and Kanban board play important role in software engineering students learning, academic achievements and professional skills gaining. The findings are helpful to develop a better understanding about learning environments. The information gathered in this study can also be used to improve the software engineering learning environment.
CREW (Collaborative Research Events on the Web) aims to improve access to research event content by capturing and publishing the scholarly communication that occurs at events like conferences and workshops. This is a Virtual Research Environment funded by JISC within the UK.
This slide show describes release 5 of the development. See site: http://www.crew-vre.net/
Understanding Continuous Design in F/OSS ProjectsBetsey Merkel
Â
By authors Les Gasser1,2
gasser@uiuc.edu
Gabriel Ripoche1, 3
gripoche@uiuc.edu
Walt Scacchi2
wscacchi@ics.uci.edu
Bryan Penne1
bpenne@uiuc.edu
Abstract
Open Source Software (OSS) is in regular widespread use supporting critical
applications and infrastructure, including the Internet and World Wide Web themselves. The communities of OSS users and developers are often interwoven. The deep engagement of users and developers, coupled with the openness of systems lead to community-based system design and re-design activities that are continuous. Continuous redesign is facilitated by communication and knowledge-
sharing infrastructures such as persistent chat rooms, newsgroups, issue-
reporting/tracking repositories, sharable design representations and many kinds of
"software informalisms." These tools are arenas for managing the extensive, varied,
multimedia community knowledge that forms the foundation and the substance of
system requirements. Active community-based design processes and knowledge repositories create new ways of learning about, representing, and defining systems that challenge current models of representation and design. This paper presents several aspects of our research into continuous, open, community-based design
practices. We discuss several new insights into how communities represent
knowledge and capture requirements that derive from our qualitative empirical
studies of large (ca. 2GB+) repositories of problem-report data, primarily from the
Mozilla project.
Introduction to the Software Sustainability Institute and a record of the discussion held at the JISC RI Software Sustainability Workshop on the 12th May 2010.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Â
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Â
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overviewâ
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
Â
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Â
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Â
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as âpredictable inferenceâ.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
DevOps and Testing slides at DASA ConnectKari Kakkonen
Â
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Â
Are you looking to streamline your workflows and boost your projectsâ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, youâre in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part âEssentials of Automationâ series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Hereâs what youâll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
Weâll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Donât miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
Â
As AI technology is pushing into IT I was wondering myself, as an âinfrastructure container kubernetes guyâ, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefitâs both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Â
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
Â
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...
Â
Pawlik
1. 2010 CRC PhD Student Conference
How best to support scientific end-user software
development?
Aleksandra Pawlik
a.n.pawlik@open.ac.uk
Supervisors Dr. Judith Segal
Prof. Marian Petre
Prof. Helen Sharp
Department/Institute Computing
Status Full-time
Probation viva Before
Starting date October 2009
Introduction
End-user software development has received substantial amounts of attention within
both the academic and software engineering communities [1-3]. One of the sub-
groups that can be distinguished amongst end-user developers is that of scientific end-
user developers [4]. A particular set of characteristics differentiates scientists from
other end-user developers. Firstly, working in the field of science often necessitates
the use of various software packages on a daily basis. Secondly, scientists are familiar
with and utilize formal languages as well as particular modelling techniques.
Additionally, the majority of science degree curriculums offered by universities
contain at least one course in programming. Thus, many scientists have some
experience with coding at a relatively early stage of their academic and professional
career. In many cases, conducting a scientific research project means developing a
tailor-made software tool which will address a particular scientific problem. Therefore,
it may seem that scientists are âpredisposedâ to being effective and successful end-
user software developers more likely to produce a sustainable end-product software.
However, numerous problematic issues related to scientific end-user software
development have been reported by researchers in computing [5, 6], software
engineers [7] and scientists themselves [8]. For the purpose of my research project, I
will make the distinction between two different contexts within scientific end-user
software development:
- Limited Context: when software is developed (usually in a purely academic
environment) in order to address a specific problem within a particular project
which is being run by a limited group of anticipated users;
- Extended Context: when it is expected that the software will be reusable,
maintainable and flexible (i.e. potentially used by an extended group of as yet
undetermined users).
Scientific end-user software development needs, therefore, relevant and effective
support from the software development professionalsâ community. Despite the fact
that some related help exists and is available [9], scientists who develop software and
software engineers who collaborate with them at various levels may find scientific
software development problematic. This indicates that the assistance and support
provided may need adjustments and improvements, an objective that may be
approached from different angles. First of all, it is essential to identify and examine
difficulties which may crop up during scientific end-user software development. The
second approach is to investigate and understand the origins of these problems.
Page 78 of 125
2. 2010 CRC PhD Student Conference
Finally, we need to comprehend why the support available for scientific end-users
provided by the software development professionalsâ community does not seem to be
working effectively and what steps should be taken to attempt to remedy this. I argue
that these steps need to involve observing the practices applied during scientific
software development in a number of different contexts.
In my PhD research project, I intend to focus on exploring the tools and methods
which scientific end-user developers employ in their work. The answer to the
question âWhat techniques do scientific end-user developers use?â should allow me
to identify the ways in which scientists address issues that emerge during software
development. Additionally, I will pay special attention to the methods which scientific
end-user developers find successful. By âsuccessfulâ I mean those that were
introduced and maintained during part or indeed the whole cycle of software
development, and which resulted in sustainable software. Thus, my second research
question is âWhat are the problematic and successful applications of tools and
techniques for supporting end-user software developers?". The results of my study
may potentially provide sufficient information which could be used to tailor and
improve ways of assisting scientific end-user development.
Background
A number of researchers investigated the characteristics and issues related to
scientific end-user development. For example, Segal [10] notes that the software
development process consists of short cycles and proposes an âiterative and
incrementalâ model of scientific software development which is a result of the fact
that the majority of scientific work remains experimental and is based on
approximation models. Moreover, some scientific projects involve tacit knowledge,
something which creates difficulties in establishing requirements and designing
software packages [11]. The experimental nature of these scientific projects, the
application of tacit knowledge and the approximations generated by mathematical
models create a further problem, that of software testing [12] [13].
Some problems are generated by the fact that many scientific end-user developers
make software within a very limited context of usage. The main aim of scientific
projects is to advance science, deliver and publish the findings. The resources (time,
finances and people) allocated to software development within the framework of a
scientific project tend to be insufficient [14]. Therefore, scientistsâ reluctance to
apprehend, for example, object-oriented programming languages, and their preference
to implement code in Fortran seems justified. Moreover, by sticking with familiar
programming languages, scientific end-user developers reduce the risk of errors that
might result from the use of languages which are new or unfamiliar to them [6]. Since,
within the scientific working culture [5], software development is not made a high
priority, scientists who develop software packages do not, as a result, receive relevant
credit, something which tends to discourage them from putting more effort into
creating sustainable software [14]. Other factors which contribute to problems with
scientific end-user software development, such as lack of effective project
management or problems with the labour division, may dissuade developers from
making use of any version control systems or configuration management tools [15].
Page 79 of 125
3. 2010 CRC PhD Student Conference
In fact, tailor-made resources relating directly to software engineering techniques and
methods supporting scientific end-user software development are available and being
continuously developed, mainly by software development professionals [16].
However, these resources only receive rather a poor uptake from the scientific
community, as scientists prefer to teach themselves from, for example, generic
textbooks, colleagues, the Internet, and so on [17] [6]. Additionally, as described by
Kelly [18], the chasm that divides the different approaches to software development
between the communities of scientific end-user developers and software development
professionals only serves to cause further discrepancies in the overall communication
between the two groups.
Methodology
I intend to investigate case studies of scientific end-user software development in
which various software engineering techniques and methods were used in covering
the following:
- The transition of turning purely academic (Limited Context) scientific software
packages into commercial ones;
- The transition of turning purely academic (Limited Context) scientific software
packages into open source (Extended Context) ones;
- The development of scientific software which directly involves software
development professionals (Extended Context).
Since this PhD research project is exploratory in nature, qualitative research methods
would seem to be the most appropriate. Moreover, studies in information systems are
highly context-dependent and interpretative [19], something which requires making
use of methods that allow researchers to investigate issues in depth. I will use
interviews and participant observation as the main methods of data collection. The
interviews will be conducted with both scientific end-user developers and software
development professionals who are directly involved, together with scientists, in
scientific software development teams. The former will constitute the majority of the
respondent group whilst interviews with software development professionals will aim
to provide additional information about the application of methods and techniques for
supporting scientific end-user development. Ideally the interviews will be combined
with participant observation enabling me to obtain a fuller picture of the process and
to perceive any issues related to scientific end-user development. Two things will be
crucial in the sampling of the case studies: being able to obtain maximum variation
within the sample, but also the ability to include convenient sampling (e.g. contacting
respondents, access to the fieldwork etc.), something which will doubtless have an
impact on the final construction of the set of case studies.
References
[1] B. A. Myers, M. M. Burnett, S. Wiedenbeck, A. J. Ko, and M. B. Rosson,
"End user software engineering: CHI: 2009 special interest group meeting," in
Proceedings of the 27th international conference extended abstracts on
Human factors in computing systems Boston, MA, USA: ACM, 2009.
[2] H. Lieberman, Paternò, F., Wulf, V., "End user development," Dordrecht, The
Netherlands: Springer, 2006.
Page 80 of 125
4. 2010 CRC PhD Student Conference
[3] M. F. Costabile, P. Mussio, L. P. Provenza, and A. Piccinno, "End users as
unwitting software developers," in Proceedings of the 4th international
workshop on End-user software engineering Leipzig, Germany: ACM, 2008.
[4] J. Segal and S. Clarke, "Point/Counterpoint: Software Engineers Don't Know
Everything about End-User Programming," Software, IEEE, vol. 26, pp. 54-57,
2009.
[5] J. Segal, "Software Development Cultures and Cooperation Problems: A field
Study of the Early Stages of Development of Software for a Scientific
Community," Computer Supported Cooperative Work (CSCW), vol. 18, pp.
581-606, 2009.
[6] R. Sanders and D. Kelly, "Dealing with risk in scientific software
development," Software, IEEE, pp. 21-28, 2008.
[7] V. R. Basili, D. Cruzes, J. C. Carver, L. M. Hochstein, J. K. Hollingsworth, M.
V. Zelkowitz, and F. Shull, "Understanding the high-performance-computing
community: A software engineer's perspective," Software, IEEE, vol. 25, pp.
29-36, 2008.
[8] C. Rickett, S. Choi, C. Rasmussen, and M. Sottile, "Rapid prototyping
frameworks for developing scientific applications: A case study," The Journal
of Supercomputing, vol. 36, pp. 123-134, 2006.
[9] G. Wilson, "Those Who Will Not Learn From History," Computing in Science
and Engineering, vol. 10, p. 5, 2008.
[10] J. Segal, "Models of scientific software development," in Workshop on
Software Engineering in Computational Science and Engineering, Leipzig,
Germany, 2008
[11] S. Thew, A. Sutcliffe, R. Procter, O. de Bruijn, J. McNaught, C. C. Venters,
and I. Buchan, "Requirements Engineering for E-science: Experiences in
Epidemiology," Software, IEEE, vol. 26, pp. 80-87, 2009.
[12] D. Hook and D. Kelly, "Testing for trustworthiness in scientific software," in
Proceedings of the 2009 ICSE Workshop on Software Engineering for
Computational Science and Engineering: IEEE Computer Society, 2009.
[13] S. Easterbrook and T. Johns, "Engineering the Software for Understanding
Climate Change," Computing in Science and Engineering, vol. 26, 2009.
[14] "Reporting Back - Open Middleware Infrastructure Institute Collaboration
Workshops 2010," http://www.omii.ac.uk/wiki/CW10ReportingBack, 2010.
[15] M. Vigder, "End-user software development in a scientific organization," in
Proceedings of the 2009 ICSE Workshop on Software Engineering
Foundations for End User Programming: IEEE Computer Society, 2009.
[16] "Software Carpentry - an intensive introduction to basic software development
practices for scientists and engineers," http://software-carpentry.org/.
[17] G. Wilson, "How Do Scientists Really Use Computers?," American Scientist,
vol. 97, pp. 360-362, 2009.
[18] D. Kelly, "A software chasm: Software engineering and scientific computing,"
Software, IEEE, p. 120, 2007.
[19] H. K. Klein and M. D. Myers, "A set of principles for conducting and
evaluating interpretive field studies in information systems," MIS Quarterly,
vol. 23, p. 67(2), 1999.
Page 81 of 125